| I can't get my PAP2T-na to work with 2 sip accounts Last night I created a second sub account on my voip.ms DID account. I tried to set it up as a second line on my PAP2T-na and it would not work.
I can get the sub account to work with a soft phone just fine.
If I try and set it up in the PAP2T it drops line one off and line two, the SIP account works.
The only way I can get it to work on the PAP2T is to change the server location and have the DID on one server and the SIP on another.
The second line on the PAP2T works with a Gizmo5 account just fine with my voip.ms on line one.
Any suggestions?
I would switch to voip phones and cure the problem, but I have an ooma line that I use also. |
|
|
|
Mangowww.toao.net
join:2008-12-25
Alberta
kudos:8 | Try changing the SIP Port. 5060 on one line and 5061 on the other.
m. |
|
| reply to Stunata
They are already set that way. |
|
Mangowww.toao.net
join:2008-12-25
Alberta
kudos:8 Reviews:
 ·voip.ms
·Anveo
 ·Shaw
·FreePhoneLine
 ·TELUS
·Callcentric
·callwithus
·LINGO
| Tell us more about the problem. What does Registration State say on the info page of the PAP2T, and what does the Sub Account Diagnostics page say on the VoIP.ms website?
What are the symptoms? I'm not sure what "drops line one off" means.
m. |
|
| reply to Stunata
Is your modem configured as router? Separate router, if any? Special settings in router? |
|
| reply to Stunata
voip.ms stat page just does not register the line 1
the line 2 sub account registers just fine.
PAP2T says "can't connect to login server" for line 1
Line 2 says online.
I can change the server on line 1 or 2 from LA to Dallas or another server and it hooks right up. (but I can't use multi ring feature this way)
If I use a soft phone for the line 2 sip sub account it works fine. I can even dial to the extension 102 and it rings.
It seems like the PAP2T does not like the fact that it is trying to use the same IP address for the server on line 2. Or the server does not like that fact that the PAP2T has one IP address to forward things to even though I have the ports set to separate addresses. |
|
| Try changing the setting of NAT Mapping Enable for one or both lines. If no luck, please give modem type, whether configured as router, type of external router if any, router firmware, any voip-related settings in router or modem.
I have run PAP2T with both lines registered to same IP/port with no trouble. |
|
| I tried the NAT Mapping on and off for both lines on the PAP2T. Same results.
The modem/router is a Netopia/Motorola 3347 and it is configured as a router with QOS giving the PAP2T and an ooma box priority based on their ip addresses.
I can configure a second line on the PAP2T and it works fine. Just as long as it is a different provider. |
|
maziloFrom MaziloPremium
join:2002-05-30
Lilburn, GA
kudos:1 | You may want to post your configurations here. Until then, all suggestions are based on wild guesses. |
|
| A Screen shot of the PAP2T setup? would that work?
What is strange is that it works with different service provider on each line. Maybe I should try and test two free Callcentric lines and see if it does the same thing. This way I can rule out if it is me or voip.ms |
|
Reviews:
 ·Verizon FiOS
| Yes, that would work... Get the screenies for both lines (switch to advanced view first). I have an unlocked pap2 with 2 lines on voip.ms registered to the same server. The only thing different about my configuration is that it's optimized for faxing. |
|
| reply to Stunata
IMO this is likely a router issue and cannot be (only) a server problem. If NAT mapping is operating correctly, the server should not see the PAP2T (or softphone) private address at all. In both the working line 1 + softphone case and the failing line 1 + line 2 case, the server should see the two registrations from the same public IP but with different source ports.
Try turning off any SIP, ALG, SPI, or firewall options or try forwarding UDP ports 5060 and 5061 to the PAP2T. If no luck, try to confirm a router problem by testing with another kind of router (with modem in bridge mode). If you don't have one, just try the PAP2T at a friend's. (If it's set for static IP, you may need to change the config or enable DHCP to be compatible with your friend's network.) |
|
| You hit it right on. It was a router forwarding problem. I forwarded UDP port 5060 and 5061 and it works. |
|
| said by Stunata:You hit it right on. It was a router forwarding problem. I forwarded UDP port 5060 and 5061 and it works. Glad to hear that you got it working. However, I believe that in your case the forwarding happens to cover up a bug in the router firmware. I can duplicate the same setup with my combined router/modem (Cisco 827) and it works fine without forwarding. I'd like to say "without any special settings", but even Cisco has bugs that require the SIP ALG to be turned off  |
|
| reply to Stunata
said by Stunata:You hit it right on. It was a router forwarding problem. I forwarded UDP port 5060 and 5061 and it works. Glad you got it to work. I have voip.ms installed on the second line of an old PAP2 too, but with nothing special in my configuration. |
|
| I had to forward ports 5060-5061 UPD
port 53 UDP
port 96 UDP
ports 10000-20000 UDP
It also works if you put it in the DMZ outside the firewall, but I didn't like doing that.
On the Netopia 3347 they are called pinholes.
I figured I would post those incase someone else runs across this at some later date. |
|
 brg
join:2001-01-03
Chicago, IL
kudos:1 | said by Stunata:I had to forward ports 5060-5061 UPD port 53 UDP port 96 UDP ports 10000-20000 UDP I'm not familiar with forwarding UDP ports 53, 96 and 10000-20000 (which, at 10,000 ports, is a pretty big range; hardly a "pinhole.") What lead you to those particular ports as ones that you had to forward? My forwarding rules so as to support my PAP2T-NA with both lines registering, as well as 3 separate softphones (X-Lite, Zoiper and occasionally Phoner) don't look anything like yours... |
|
| These values came from the PAP2T manual. Not the service provider. I also looked in my router to see which ports were being used by the PAP2T based on its NAT ip address and 53, 5060 and 5061 along with a 16000+ value were being used.
I'm not sure where they got 96 but I put it in there also.
So, I figured I would forward what they told me to. These were all UDP ports and not TCP ports.
Yes, it is a pretty large range. I actually had to move another pinhole that was in that range for another piece of hardware on my system. |
|
