My user domain is listed as magicjack.com and not a specific IP address.
The ata works fine, i just picked an ip from one of the other posts, but it takes a very long time to get connected after dialing. Is there a way to determine what userdomain ip address I should use??
UserDomain info for sip settings on ata
Moderators: Bill Smith, Pilot
i think you can setup your dialplan to help with time but it isnt going to be as fast as say a land line
http://www.netphonedirectory.com/pap2_dialplan.htm
http://www.netphonedirectory.com/pap2_dialplan.htm
Thanks for the reply
I will play with that for a while and see how it goes!!
The MagicJack connects and starts ringing in about 4 seconds, the ata takes 10-12 seconds. I was hoping to shorten that time down a bit and thought maybe it was the userdomain ip. I will see how adjusting the dial plan goes.
I will play with that for a while and see how it goes!!
The MagicJack connects and starts ringing in about 4 seconds, the ata takes 10-12 seconds. I was hoping to shorten that time down a bit and thought maybe it was the userdomain ip. I will see how adjusting the dial plan goes.
I'm gonna try to help with this question in two parts:
userdomain: The userdomain is part of the 401 authentication scheme. It's normally used to authenticate a web-browsing user against a specific server or forrest. In MJ's case, I've authenticated with out (I can't see why they would need to use it anyway), so you should be able to leave it empty.
slow connection time: I've noticed a considerable difference in omitting the ":S0" in my dial plan. I had to do so, because I added a rule for 7 digit dialing (to automatically prefix the area code). I do have the ":S0" on my 9 digit rule, and it works much faster. There's a timeout in there for when you stop dialing, that the ATA will look to see if any rules have been met, and will attemp to connect. If you use the ":S0" (straight out) parameter, as soon as the first (left to right) rule is met, it will attempt to connect.
slow connection time2: check the proxy server you're using. Run a "ping -t" on it for a little while and see how many packets get dropped, as well as the reponse times. If it's not a very reliable outcome, you can try another MJ proxy server to see if that could be the problem.
-Some
userdomain: The userdomain is part of the 401 authentication scheme. It's normally used to authenticate a web-browsing user against a specific server or forrest. In MJ's case, I've authenticated with out (I can't see why they would need to use it anyway), so you should be able to leave it empty.
slow connection time: I've noticed a considerable difference in omitting the ":S0" in my dial plan. I had to do so, because I added a rule for 7 digit dialing (to automatically prefix the area code). I do have the ":S0" on my 9 digit rule, and it works much faster. There's a timeout in there for when you stop dialing, that the ATA will look to see if any rules have been met, and will attemp to connect. If you use the ":S0" (straight out) parameter, as soon as the first (left to right) rule is met, it will attempt to connect.
slow connection time2: check the proxy server you're using. Run a "ping -t" on it for a little while and see how many packets get dropped, as well as the reponse times. If it's not a very reliable outcome, you can try another MJ proxy server to see if that could be the problem.
-Some