turtle-speed's profile

Contributor

 • 

47 Messages

Closed

level 2.5 escalation

Im having a problem receiving magicJack calls locally from cox phone subscribers. I have a cm400 with my mj attached only, router has been deleted for ease of troubleshooting. Currently at level 2 ...

cox claims they do not block ports on there end, if not, what else would be causing this routing issue?

before thinking its the device(or any other void device)   I can connect my mj device to a different ISP within the neighborhood and it works as it should.---important

Why is cox reluctant to fix the internal hub issue and whom do I escalate to?

I would like to receive all my incoming calls instead of half please

Moderator

 • 

779 Messages

Hi turtle-speed,

We’d can investigate this however we will need some information in order to do so. Please email our team at cox.help@cox.com. Be sure to include your name, complete service address, the telephone number and the issue you’re experiencing.

Valued Contributor II

 • 

2.8K Messages

What MagicJack device do you have that it can be attached directly to the modem? Most I know are USB powered. 

Also, can you receive calls OK from non Cox subscribers? The VOIP doesn't know one caller from another, so if you are receiving any calls, then the VOIP over Cox is working and it's not a port issue IMO. 

What error or sound do you get when you call your MJ number? Can you test with other Cox telephone numbers or just your own? 

Contributor

 • 

47 Messages

I can receive incoming calls from most I believe except LOCAL cox subscribers.

After getting no were with tech again, I believe it is a cox central software issue in there switch as of now do to others having similar issues.

When they call into me, they receive a busy signal, not the standard magiclack customer not available message.,Calling out is never an issue. There is no delay ever.

as of this weekend, I used a friends magic jack with the same results...this proves to me its in the cox switch some were and there is an software issue.

please respond to this with thoughts, thank you

Contributor

 • 

47 Messages

THIS QUESTION HAS NOT BEEN SOLVED

Valued Contributor

 • 

1.7K Messages

Have you tried it from the other side ... have someone with Cox service call them and report they can't call ###-###-####, your MJ number?  You may have better luck saying I can't call a specific number than I can't receive calls.

Valued Contributor II

 • 

2.8K Messages

Do you have Voicemail with MJ? If so, do Cox numbers atleast go to VM if your on the MJ line?

Could be a issue in Cox's switch, but I some how doubt it. Usually if it's a switch error, you get a switch announcement. Seems more like a routing issue. Like the call can't even make it to Cox's switch. If you look at your call history/caller ID, do you see the number?

Last, who owns the Cox phone line your testing with? Can it call other MJ numbers? Could it be a general routing issue between MJ and Cox? Have you tried calling/asking MJ about it?

Contributor

 • 

47 Messages

-no voice mail. No error, just a busy signal when calling into my MJ at my residence.

(for testing purposes, MJ has been previously tethered directly  to my modem via Ethernet with zero change)-router out of equation

-this does not happen when I move it to a different ISP provider two houses down-non Cox F******r carrier

a buddies MJ was connected to my modem and had exact same issue when trying to receive local cox calls

-I would agree on routing issue possibly on COXs end do to the simple tests performed above

Valued Contributor II

 • 

2.8K Messages

turtle-speed said:
just a busy signal when calling into my MJ at my residence.

Is it a fast or slow busy signal? As in is it the same as you hear when you call your MJ number while using it or different? Trying to see if it's a routing issue inside MJ or between MJ and Cox. Have you asked MJ about it?

turtle-speed said:
MJ has been previously tethered directly  to my modem via Ethernet

What model MJ device do you have? How do you have it wired to your phones? Is the Cox telephone number you were testing with installed on site? Another words, do you have the Cox phone line and MJ phone line on same physical RJ11?

turtle-speed said:
had exact same issue when trying to receive local cox calls

And he/she was able to receive calls from the same test Cox number when it was reconnected at their site?  

Contributor

 • 

47 Messages

-fast busy signal

mj support is primitive but they trouble shot it and found no issue repeatedly

-why do I keep reading that cox does block ports and that may be the whole issue even though the tech says they dont. There own page says they do?????

--this is why I used other peoples devices and my device elsewhere problem lies in a computer somewhere as Cox tech 2 said, "people smarter then us get paid alot to figure it out" guessing its sub'd out tech company.

I only have internet through cox, and phone is connected directly to MJ, its not on my end. It works fine any were else outside of this immediately area.---note-same exact issue when used at my neighbors house whom is a cox subscriber

as for buds MJ, yes, he can receive calls from cox customers as well as me if I take the magic jack else-ware, say Glastonbury area. Works with cox down there just fine, its my area the issue is with, thus routing IP ??cox hub??

Valued Contributor II

 • 

2.8K Messages

turtle-speed said:
why do I keep reading that cox does block ports and that may be the whole issue even though the tech says they dont.

What are you reading? These are the ports block by Cox. MagicJack uses UPnP, so mostly uses random UDP traffic or around ports 5060-5070. These ports are not blocked by Cox. If they did, you MagicJack wouldn't work at all, inbound/outbound Cox or otherwise. It not like when someone from Cox calls MJ uses a different port.

turtle-speed said:
this is why I used other peoples devices and my device elsewhere problem lies in a computer somewhere as Cox tech 2 said, "people smarter then us get paid alot to figure it out" guessing its sub'd out tech company.

I don't understand this. Can you explain? 

turtle-speed said:
say Glastonbury area. Works with cox down there just fine,

This doesn't seem like a IP or internet issue. Seems like a call routing issue between Cox and MJ localized to a specific area. The people you pay are the ones who need to troubleshoot the issue, even if the issue is on Cox's side. Just like if you had Cox telephone and was having trouble receiving calls from MJ users, you would call Cox. 

As for troubleshooting the MJ device, I don't see how I can do that since you still haven't even stated what it is.

Contributor

 • 

47 Messages

Ok, ill type slow so as you can completely uinderstand....

other friends working magic jack devices, when installed at my residence have the same incoming call issue as my device.

-this tells me its on Cox Hub end

next

my device works and receives incoming calls when attached to another ISP locally( Fr*****r)

-this tells me its on Cox hub end

next

my device works fine and receives incoming calls on cox ISP in g-burry area

-this tells me its on Cox hub end

are we clear now or shall we go in circles some more as your very good at that and discrediting any factual findings

Valued Contributor II

 • 

2.8K Messages

turtle-speed said:
Ok, ill type slow so as you can completely uinderstand....

turtle-speed said:
are we clear now or shall we go in circles some more

Go in circles more you jerk. It's your problem. You fix it. I was a user just trying to help, but now I HOPE you don't get it fixed. Next time don't bye junk from the "As seen on TV" isle at Walmart. Bye.

Contributor

 • 

47 Messages

so internet hero, you cant fix it , understand it and now your mad, so sorry..

if there's a cox tech whom is able to comprehend the complexity of this issue, do chime in

thank you

Valued Contributor II

 • 

2.8K Messages

turtle-speed said:
you cant fix it , understand it and now your mad, so sorry..

Isn't that why you're here? You have a problem, YOU can't fix it, and now your mad so your taking it out on someone else. 

What a surprise, no one wants to help you.