Re-registration problem when provider stops sending expires

[Lukas]

Hello all!

I am having a hard-time making 3CX work with one of our providers. 3CX registers correctly, sends a few re-registration packets when 90% of the provider's expire time has elapsed, but then stops sending the re-registration packets when the provider sends back an "ok" that does not contain the "expires" header. 3CX keeps showing the external port as "registered" even though for the provider it is not (the provider does not receive the registers and hence considers 3CX no longer registered).

Example of a provider response that makes 3CX re-register after 270 seconds (IP adresses/user names/domains masked for security):

Session Initiation Protocol
Status-Line: SIP/2.0 200 OK
Message Header
Via: SIP/2.0/UDP xxx.xxx.xxx.xxx:5060;branch=z9hG4bK-d8754z-5f08cc40e12f535c-1---d8754z-;rport=5060
Contact: <sip:[email protected]:5060;rinstance=df885ae8ecf74d06>;expires=300
Contact-URI: sip:[email protected]:5060;rinstance=df885ae8ecf74d06
Contactt-URI User Part: username
Contact-URI Host Part: xxx.xxx.xxx.xxx
Contact-URI Host Port: 5060
Contact parameter: rinstance=df885ae8ecf74d06>
Contact parameter: expires=300
To: <sip:[email protected]:5060>;tag=0f252131
SIP to address: sip:[email protected]:5060
SIP tag: 0f252131
From: <sip:[email protected]:5060>;tag=f3071042
SIP from address: sip:[email protected]:5060
SIP tag: f3071042
Call-ID: OTIzMmQ4ZjRhZDJmOTQyOWI3NWM5YjEyMTliYzkzYjk.
CSeq: 3 REGISTER
Date: Mon, 17 Oct 2011 17:56:47 GMT
Content-Length: 0

Example of provider response that makes 3CX stop registering:

Session Initiation Protocol
Status-Line: SIP/2.0 200 OK
Message Header
Via: SIP/2.0/UDP xxx.xxx.xxx.xxx:5060;branch=z9hG4bK-d8754z-5c015e69ea5dc100-1---d8754z-;rport=5060
Contact: <sip:[email protected]:5060;rinstance=df885ae8ecf74d06>
Contact-URI: sip:[email protected]:5060;rinstance=df885ae8ecf74d06
Contactt-URI User Part: username
Contact-URI Host Part: xxx.xxx.xxx.xxx
Contact-URI Host Port: 5060
Contact parameter: rinstance=df885ae8ecf74d06>
To: <sip:[email protected]:5060>;tag=5636d439
SIP to address: sip:[email protected]:5060
SIP tag: 5636d439
From: <sip:[email protected]:5060>;tag=f3071042
SIP from address: sip:[email protected]:5060
SIP tag: f3071042
Call-ID: OTIzMmQ4ZjRhZDJmOTQyOWI3NWM5YjEyMTliYzkzYjk.
CSeq: 6 REGISTER
Date: Mon, 17 Oct 2011 18:05:48 GMT
Content-Length: 0

I understand that here the provider is not behaving in a coherent manner, but is there any way to tell 3CX to keep registering at the last known interval (or just force an interval) if the provider stops sending the expires header? This would increase compatibility, I guess.

Thank you!!

 

[LCC]

Re: Re-registration problem when provider stops sending expi

I wonder if this is the same problem I am having. Is this provider Nextiva? Folloing is an excerpt from what the provider says is the issue after they put a trap on my IP.

When the refresh time hits (normally around the 15 minute mark) we send you an invite to refresh the call. Most of the time the invite is simply responded to with a 200OK from your PBX and the call is good to go for another 15 minutes. What appears to be happening here though however, is when the invite is sent to your PBX to refresh the call, instead of sending back a 200OK, you send back a 407 Proxy Authentication Required, a message that should only be sent by US not you. Your PBX basically asks US to authenticate with IT, and since we dont get a 200OK in response to the refresher invite as we should be, our server thinks there is no valid source to establish the refreshed call to on the other end and sends a disconnect message to your PBX telling it that we have ended the call (a sip BYE message).

 

[Lukas]

Re: Re-registration problem when provider stops sending expi

The provider is Ticinocom. It seems a different problem, however. In my case active calls are not impacted, only inbound calls are not delivered because the provider thinks the PBX is disconnected since the registration has expired.

 

[Lukas]

Re: Re-registration problem when provider stops sending expi

I spoke to the provider to see if they could in any way sort out the problem.

Unfortunately it seems that I am the only user connecting with a 3CX pbx, and all the other users with pbxs do not have the problem I am encountering. It sounded like a polite way to say that 3CX does not comply with the standard by stopping sending REGISTERS when the provide does not offer an "expires" header or contact header parameter.

It would be helpful to know if the "expires" information is mandatory or if it is optional, in which case I could try to appeal to the fact that they are not respecting the standard, despite of the fact that all other software pbxs do not have a problem with that.

Your expert help would really be beneficial and much appreciated!

Thank you!

 

[nb]

Re: Re-registration problem when provider stops sending expi

Contact me via email [email protected]
Subject - Refresh registration voip provider

I will send you a patch and try it out with this provider.

Thanks

 

[Lukas]

Re: Re-registration problem when provider stops sending expi

Thanks, Nicky -- I sent you the email.

Thanks,

Luca

 

[Lukas]

Re: Re-registration problem when provider stops sending expi

Thank you so much, Nicky! The patch seems to be working quite well!!

Thanks a lot for the fantastic support!

 

[SY]

Re: Re-registration problem when provider stops sending expi

Thank you so much, Nicky! The patch seems to be working quite well!!

Thanks a lot for the fantastic support!

Please try to persuade Ticinocom to find a way to fix this bug in software/hardware.
After update, PBX informs about applying the workaround, so it can be used for debugging.

Thanks