I have 3 simple (I hope) questions:
1. How to configure OBi100 to send REGISTER requests every 10 min?
2. How to make it send REGISTER requests containing common "Expires: 600" filed?
3. How to make it send Keep Alive packets to keep hole in NAT/firewall opened all the registration time?
And here is some points related to each question correspondingly:
1. To send REGISTER requests every 10 min I configured OBi100 (in "Service Providers | ITSP Profile A"):
RegistrationPeriod = 1100
Why it must be 1100 instead of 600 as expected? If it's set to 1100, OBi sends its next REGISTER request in 600 sec, instead of 1100 as specified. Keep in mind that SIP server may offer a grace period (usually 1 min) over the specified by SIP client time (1100 sec in this case) to keep registration active...
2. To include common "Expires: 600" filed I configured OBi100 (in "Service Providers | ITSP Profile A"):
RegisterExpires = 600
But there is no any "Expires: 600" filed in the REGISTER requests, sent by OBi100... Is it a bug?
3. If I configure OBi100 to send REGISTER requests every 10 min, I start loosing incoming calls (NAT/firewall closes its hole after a timeout since last REGISTER requests was sent). See perhaps related thread
here.
I'm looking at some KeepAlive parameter here. SIP clients usually use KeepAlive. It's interval (in sec) between a ping-like packets, sent by SIP client to SIP server to keep the registration connection (formally it uses UDP, not a TCP connection) alive.
Does OBi support KeepAlive?
BTW, I think there is a small bug, not mentioned above. Every time OBi sends double REGISTER requests when it needs to register itself:
1. OBi sends one REGISTER request
2. gets "401 Unauthorized" back and ignores it
3. OBi sends second REGISTER request
4. gets "401 Unauthorized" back
5. OBi replies with new REGISTER request, now containing "Authorization:" data
6. OBi gets "200 OK"
Steps 1 and 2 are redundant and should be eliminated.