March 20, 2018, 02:27:43 pm *
Welcome, Guest. Please login or register.
   Forum Home   Search Login Register OBiTALK  
Pages: [1]
Author Topic: Obi202 / Twilio SIP - Too many bindings for a registration endpoint  (Read 3506 times)
Posts: 2

« on: January 10, 2018, 04:20:35 am »

I connected SP2 on my Obi202 to Twilio's SIP registration service.

Incoming/outgoing calls worked great (ie had full working setup).  Incoming calls seem to still work (depends on registration) but meanwhile there are a huge number of errors on twilio's end in their debugger.

On the obitalk side you can see the 403/Forbidden and "register failed"...but this doesn't actually seem to mean register is failed since incoming calls still work.

My intuition says that for some reason the Obi202 is trying to register multiple times while other registrations are still considered alive and valid by Twilio and this gets the Obi202 over the max of 10 concurrent registrations imposed by twilio.  So the box is still registered but is trying to register again for some reason.

When I set this up I did a lot of testing (scripts on the twilio end to manage incoming/outgoing calls) and was frequently using the twilio debugging console...these errors weren't happening then.  I am guessing in the meantime there was either an Obi firmware update changing behaviour or a change on the twilio side that exposed existing Obi firmware behaviour (could be twilio just didn't complain about this before).

In any case it blows up my logs and would be great to get a firmware update to make sure the Obi202 is releasing registrations properly or not trying to create new ones while an old one is still valid.

I searched but couldn't find any details on this issue.  Maybe there is some type of "keep alive" setting I can use to address this issue?

Happy for any constructive advice.
« Last Edit: January 10, 2018, 04:24:01 am by mattp » Logged
Jr. Member
Posts: 63

« Reply #1 on: January 10, 2018, 09:11:00 am »

Find out what Twilio's default registration time is and set the Obi to use that for its own registration timer. It is probably trying to register every minute (which is an insane default).
Posts: 2

« Reply #2 on: March 02, 2018, 02:32:53 am »

Thanks for the idea.  Looks like 10 minutes for register refresh.

Obitalk indeed had RegistrationPeriod set to 60 seconds.  Changed to 600, we'll see if that makes a difference.  Sorry for not responding sooner, didn't get any reply notifications.
« Last Edit: March 02, 2018, 02:36:03 am by mattp » Logged
Pages: [1]
Jump to:  

Powered by SMF 1.1.11 | SMF © 2006-2009, Simple Machines LLC