what is "device registration" and how is it accomplished?
RonR:
The OBi sends a consistent UA value in its SIP registrations:
User-Agent: OBIHAI/OBi110-1.3.0.2675
The information sent in the SIP header is also sufficient to uniquely identify your particular unit:
Contact-URI User Part: 14157025555
Contact-URI Host Part: 192.168.1.127
Contact-URI Host Port: 5060
Contact parameter: +sip.instance="<urn:uuid:00000000-0000-0000-0000-9cadef012345>"
Consequently, PhonePower's server can tell that it's a single unit that's making the registration requests.
I suspect PhonePower is trying to protect itself from SIP clients who use a very short registration period and register way too often. The OBi is one of those clients and tries to register every 60 seconds by default.
Try the making the following change:
Service Providers -> ITSP Profile x -> SIP -> RegistrationPeriod : 3600
where x is your PhonePower configuration.
Name:
I am sorry but this is not it.
My RegistrationPeriod is set to 86400.
There should be another issue. They claim Obi110 is changing ports with each request. I have 12060 set up, so I don;t know what to say at this point.
Stewart:
Is the 2210 in bridge mode, with PPPoE set up on the Draytek? If not, please explain the setup. If you have a problem with the 2210 losing sync, putting it in bridge mode may enable the Draytek to sustain the PPPoE connection over a sync loss.
Quote from: Name on February 25, 2012, 09:14:38 am
It appears that Obi110 registeres as new UA the same service, every time the service is turned on/off in Obi.
What do you mean by that? Once registration is established, nothing should be turned off. Possibly, the Draytek assigns a different source port, after the NAT association is lost. You can set up syslog in the OBi and set X_SipDebugOption to Log All Messages. Then, look at the received and rport tags sent in the Via header in response to REGISTER requests (it should be present on both successful (200) and failing (403) responses. Or, use the Port Redirection feature to forward the UDP port corresponding to X_UserAgentPort for the SPx in question.
Does your static IP service from AT&T include multiple IP addresses? If so, it may be possible to dedicate one to the OBi, avoiding NAT altogether.
Why do you believe your Internet connection is unstable? If the noise margins are consistently poor, perhaps an interleaved or slightly lower speed profile will improve performance as well as stability. If margins are normally good, but burst noise causes the modem to lose sync, you are probably on a bad cable pair and should be able to get AT&T to fix it. It's also possible that the trouble is in your in-home wiring, or caused by a missing or defective filter on some device. Have you tried connecting your modem directly to the test jack at the NID?
RonR:
Quote from: Name on February 25, 2012, 11:13:51 am
My RegistrationPeriod is set to 86400.
That's an absurd registration period : 24 hours
Quote from: Name on February 25, 2012, 11:13:51 am
I have 12060 set up, so I don;t know what to say at this point.
Have you tried the standard configuration?:
http://www.obitalk.com/forum/index.php?topic=2643.msg17184#msg17184
Stewart:
Quote from: Name on February 25, 2012, 11:13:51 am
There should be another issue. They claim Obi110 is changing ports with each request. I have 12060 set up, so I don;t know what to say at this point.
12060 is the destination port of the REGISTER request, i.e. the port on Phonepower's server to which it is connecting. However, it's the source port that is changing, which is causing your problem. Try setting up Port Redirection: Mode: Range. Protocol: UDP. WAN IP: All. Public Port: 5060-5061. Private IP: (the static IP of the OBi). Private Port: 5060.
Navigation
[0] Message Index
[#] Next page
[*] Previous page