 Soybomb
join:2002-07-15
Carbondale, IL | pap2t, one line loses registration when in use I have a pap2t, both lines register with the same provider on the same server. When I make a call for more than a couple minutes on line1 I notice that it loses registration. Line 2 stays registered. I haven't used line 2 enough yet to see if it behaves the same. Any suggestions? |
|
PX EliezerPremium
join:2008-08-09
HuttRiver US
kudos:11 | What are the re-registration intervals?
You may want to post your advanced configs.
Are these cloned lines, or two different lines on one account, or one line with two channels....??
Also important, who is the provider?? |
|
Soybomb
join:2002-07-15
Carbondale, IL | reply to Soybomb
re-reg every 3600
voip.ms, 1 sub account per line
I've turned on debugging and am sending it to a syslog server so hopefully I'll have more detailed info after my next call. |
|
Jet101Jet101Premium
join:2009-10-01
Pflugerville, TX Reviews:
 ·Clearwire Wireless
 ·Callcentric
2 edits | Try setting your "register expires" to something way less than 3600. Try 120 and see what happens. You can set it higher if that works until you see expired registrations again. I was fiddling with this yesterday for the same reason on a PAP2T.
Are the SIP ports on both lines set to 5060? You could also try something like 5062 on the 2nd line. But I'm running 3 devices through the same network all registered to voip.ms on port 5060, and all three are staying registered fine. Oh yeah...I might mention, I have these on a Clear internet network, so it's going through a double NAT. Still working great. All three devices are set up in a ring group, and all ring fine on incoming call. |
|
Soybomb
join:2002-07-15
Carbondale, IL | reply to Soybomb
Finally seeing some issues logged although I'm not sure it was the original problem. It did cause a dropped call and brief outage.
Sep 7 08:22:52 192.168.0.204 [0]Reg Addr Change(0) 207816f2:5060->0:5060
Sep 7 08:22:52 192.168.0.204 [0]Reg Addr Change(0) 207816f2:5060->0:5060
Sep 7 08:22:52 192.168.0.204 [1]Reg Addr Change(0) 207816f2:5060->0:5060
Sep 7 08:22:52 192.168.0.204 [1]Reg Addr Change(0) 207816f2:5060->0:5060
Sep 7 08:23:07 192.168.0.204 [0]Reg Addr Change(0) 0:5060->207816f2:5060
Sep 7 08:23:07 192.168.0.204 [0]Reg Addr Change(0) 0:5060->207816f2:5060
Sep 7 08:23:07 192.168.0.204 [1]Reg Addr Change(0) 0:5060->207816f2:5060
Sep 7 08:23:07 192.168.0.204 [1]Reg Addr Change(0) 0:5060->207816f2:5060
From a little googling around it seems like the common suspect in this is a dns resolution issue. Originally I had the pap2t getting dns from my local dns proxy. I've also pointed it direct to 8.8.8.8 and it still does it. Any other ideas? |
|
