Obi100 dropping sip registration

chunkylover · April 16, 2011, 01:57:56 PM

Currently IPSP-A is on google voice
IPSP-B connects to my FreeSWITCH server.

Obi100 behind a Tomato-VPN router (port forwarding disabled [because it didn't help]). It's registering fine on an initial boot, but there's some weirdness.

FreeSWITCH is configured with a sip registration time of 3600 (as is the obi100). FreeSWITCH status shows the registration expire time is always 120 seconds max (it doesn't do this for any other device).

SipDroid stays registered and works fine behind the same router.

What happens is, it registers fine initially and reregisters every 30 seconds (this is good). After some period of time, it fails registration. The FreeSwitch folks thought this might have something to do with the nonce.

Trial 1: 14:54:32 registers - 14:59:05 fails
Trial 2: 15:42:22 registers - 15:46:44 fails

I've tried STUN and ICE as well to no avail.

Advice?

here's a siptrace:

THIS WORKS (several times)
--------------------------
------------------------------------------------------------------------
recv 779 bytes from udp/[1.2.3.4]:23821 at 19:33:28.000494:
------------------------------------------------------------------------
REGISTER sip:me.example.net:5060 SIP/2.0
Call-ID: 4627c6a5@192.168.77.200
Content-Length: 0
CSeq: 44463 REGISTER
From: <sip:1000@me.example.net>;tag=SP2697b790218d6ab81
Max-Forwards: 70
To: <sip:1000@me.example.net>
Via: SIP/2.0/UDP 192.168.77.200:5060;branch=z9hG4bK-669ca1b5;rport
Authorization: DIGEST algorithm=MD5,nc=00000009,qop=auth,cnonce="6497d2de2faa6631",nonce="d63ef078-685f-11e0-aba1-6feceeda3349",realm="me.example.net",response="25b400ca306771cc11c9c300a1394760",uri="sip:me.example.net:5060",username="1000"
User-Agent: OBIHAI/OBi100-1.2.1.2103
Contact: <sip:1000@1.2.3.4:23821>;expires=60;+sip.instance="<urn:uuid:00000000-0000-0000-0000-9cadef100711>"
Allow: ACK,BYE,CANCEL,INFO,INVITE,NOTIFY,OPTIONS,REFER
Supported: replaces

------------------------------------------------------------------------
send 690 bytes to udp/[1.2.3.4]:23821 at 19:33:28.080131:
------------------------------------------------------------------------
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.77.200:5060;branch=z9hG4bK-669ca1b5;rport=23821;received=1.2.3.4
From: <sip:1000@me.example.net>;tag=SP2697b790218d6ab81
To: <sip:1000@me.example.net>;tag=8cmm6aXFmjrFN
Call-ID: 4627c6a5@192.168.77.200
CSeq: 44463 REGISTER
Contact: <sip:1000@1.2.3.4:23821>;expires=60;+sip.instance="<urn:uuid:00000000-0000-0000-0000-9cadef100711>"
Date: Sat, 16 Apr 2011 19:33:28 GMT
User-Agent: FreeSWITCH-mod_sofia/1.0.head-git-e5fb456 2011-02-03 11-19-24 -0600
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, UPDATE, INFO, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE
Supported: timer, precondition, path, replaces
Content-Length: 0

---------------
THEN FAILS
---------------
------------------------------------------------------------------------
recv 779 bytes from udp/[1.2.3.4]:23821 at 19:34:28.273775:
------------------------------------------------------------------------
REGISTER sip:me.example.net:5060 SIP/2.0
Call-ID: c9ea76c4@192.168.77.200
Content-Length: 0
CSeq: 41698 REGISTER
From: <sip:1000@me.example.net>;tag=SP2697b790218d6ab81
Max-Forwards: 70
To: <sip:1000@me.example.net>
Via: SIP/2.0/UDP 192.168.77.200:5060;branch=z9hG4bK-635b38cd;rport
Authorization: DIGEST algorithm=MD5,nc=00000011,qop=auth,cnonce="6497d2de2faa6631",nonce="d63ef078-685f-11e0-aba1-6feceeda3349",realm="me.example.net",response="e5a110727324db9b9de5c272e1396a47",uri="sip:me.example.net:5060",username="1000"
User-Agent: OBIHAI/OBi100-1.2.1.2103
Contact: <sip:1000@1.2.3.4:23821>;expires=60;+sip.instance="<urn:uuid:00000000-0000-0000-0000-9cadef100711>"
Allow: ACK,BYE,CANCEL,INFO,INVITE,NOTIFY,OPTIONS,REFER
Supported: replaces

------------------------------------------------------------------------
send 546 bytes to udp/[1.2.3.4]:23821 at 19:34:28.299104:
------------------------------------------------------------------------
SIP/2.0 403 Forbidden
Via: SIP/2.0/UDP 192.168.77.200:5060;branch=z9hG4bK-635b38cd;rport=23821;received=1.2.3.4
From: <sip:1000@me.example.net>;tag=SP2697b790218d6ab81
To: <sip:1000@me.example.net>;tag=e3B9gD2427XZa
Call-ID: c9ea76c4@192.168.77.200
CSeq: 41698 REGISTER
User-Agent: FreeSWITCH-mod_sofia/1.0.head-git-e5fb456 2011-02-03 11-19-24 -0600
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, UPDATE, INFO, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE
Supported: timer, precondition, path, replaces
Content-Length: 0

------------------------------------------------------------------------
2011-04-16 14:34:28.298307 [WARNING] sofia_reg.c:1205 SIP auth failure (REGISTER) on sofia profile 'internal' for [1000@me.example.net] from ip 1.2.3.4

jjdeluxe · April 24, 2011, 08:25:53 PM

I have the same problem. initial registration works, then within a minute or two, drops.

chunkylover · April 25, 2011, 05:57:29 AM

There is a bug in the Obi Firmware that prevents the no-once from changing as it should. This has been resolved, in an unreleased firmware version: 1.2.1 (Build: 2196M7C9DCA28)

I'd share the firmware but it was pushed to my device, and this not being an open source product, I'm not sure how to get it *out*, or if it would even be legal to do so.

Email support@obihai.com. They were actually very responsive about this issue.

jjdeluxe · April 25, 2011, 08:44:05 AM

a ha - now I've got the connection.

OK. i've initiated the email to Obi Support. thanks for sharing.

obi-support2 · April 25, 2011, 01:53:26 PM

Indeed there is a bug in the OBi that may trigger FreeSwitch to send a 403 response (instead
the normal 401/407 to tell OBi to use new nonce for authentication).

If you need test f/w with this fix, please email support@obihai.com.

RonR · April 25, 2011, 02:04:44 PM

obi-support2,

Are you aware of anything that might cause the following problem...

I'm currently using Ribbit Mobile VoIP on SP2/ITSPB. It registers and outbound calling works fine (SIP registration is required for outbound calling). Immediately after a reboot, incoming calls work fine. Shortly thereafter, incoming calls to my Ribbit DID go to Ribbit voicemail as if I'm no longer registered (I am, however, and can still outgoing calls which require registration). Syslog doesn't log any activity on the missing incoming calls. Registration interval is set to the recommended 3600. Other values don't help.

I have no problems receiving incoming calls though Sip Sorcery with Ribbit Mobile registered there.

RonR · April 27, 2011, 11:36:10 AM

Quote from: RonR on April 25, 2011, 02:04:44 PM
obi-support2,

Are you aware of anything that might cause the following problem...

I'm currently using Ribbit Mobile VoIP on SP2/ITSPB. It registers and outbound calling works fine (SIP registration is required for outbound calling). Immediately after a reboot, incoming calls work fine. Shortly thereafter, incoming calls to my Ribbit DID go to Ribbit voicemail as if I'm no longer registered (I am, however, and can still outgoing calls which require registration). Syslog doesn't log any activity on the missing incoming calls. Registration interval is set to the recommended 3600. Other values don't help.

I have no problems receiving incoming calls though Sip Sorcery with Ribbit Mobile registered there.

obi-support2,

Did you miss my question to you?

Since posting the original question, I have tested Ribbit Mobile registered on a PAP2 and the problem does not occur there either. The problem appears to be limited to the OBi.

RonR · April 28, 2011, 11:01:22 AM

Is Obihai on vacation? I'm still hoping for an answer and a plan for resolving this problem.

Thanks,

Ron

obi-support2 · April 29, 2011, 07:18:44 AM

RonR,

Please email support@obihai.com and we can do some trouble-shooting on your unit.
Please provide your obi number, and also the number to call the unit to reproduce the
no incoming problem. We may need to try some debug f/w on the unit in order to see more
details.

I assume you have tried much smaller values of registration period, such as 60 or 30s.

Thank you.

News:

Obi100 dropping sip registration