Ring time drops after two minutes

[akashlal]

Hi

We have two SIP clients (soft phones) which we call tacticall phones. These are SIP based soft phones.
Phones are registered to FusionPBX successfully and can establish the call. Our issue is extension 45001 rings 45002, the ringing times out after 120 seconds and call ended.
We want to increase the ringing time to 30 minutes if possible.
from the logs I can see, we are getting continuous 200 OK and then after a while 603 Decline.

I have some logs attached here, zipped.

SIP logs - calling number 45001 and called number 45002


It would be a great help if anyone have a look of the logs and let me know what I am missing in the FusionPBX settings.

Regards
Robi

 

[gflow]

I just posted a similar issue last night on this forum. Are you phones ringing as part of a ring group?

Ring Group - Timeout 120 seconds

Hey Guys, I have ring groups setup using both “enterprise” and “simultaneous”. I set the ring group timeout for 400 seconds and set the timeout for each extension in the ring group to 400 seconds. However all calls hangup at 120 seconds. Also note I play a greeting file at the start of the ring...

www.pbxforums.com

 

[Adrian Fretwell]

Hi Akashlal,
The 200 OKs are in response to the OPTIONS messages, so you can probably ignore those.
This is almost certainly an issue with the ring timeout on the soft phone. We had a similar thing with Yealink desk phones and solved it by setting:
phone_setting.ringing_timeout = 600

Obviously all phones are different.

 

[akashlal]

Thanks, Adrian.
In this case, the settings for indefinite ring, it has to be set to 0, but that didn't help.
phone.disconnect.unanswered.calls.after.seconds=0

Also I changed time from 0 to 1800
phone.disconnect.unanswered.calls.after.seconds=1800

Same result, ring drops after 180 seconds both time.

Will there be anything in Fusion or freeswitch?

@gflow, thanks for sharing your post.

 

[Adrian Fretwell]

I don't think it can be Fusion/Freeswitch related because the 603 Decline message comes from the phone. Maybe test it using different soft phones?

 

[akashlal]

Hi Adrian
Digging into more, I cannot see any more 603 Declined error, rather I am seeing 401 Unauthorised.
Tracing back the packet capture, this is what I am getting-



SIP client 172.16.202.155 is getting 401 Unauthorised from the FusionPBX 172.16.75.44.



Is that something in FusionPBX I need to check?

Regards
Robi

 

[Adrian Fretwell]

Hi Robi,
No, the 401 Unauthorized is a normal part of the authentication process. In the example you show above, if you inspect the packet headers, you will see that the first REGISTER will not contain any credentials, so the response is 401 Unauthorized, but this 401 response will contain a nonce to hash against, now the second REGISTER message contains credentials and password hashed against the nonce. Now the response to the REGISTER is 200 OK.

Understanding the SIP protocol is essential if you want to run a reliable VoIP platform.

You can find lots of SIP related resources here: https://github.com/miconda/sip-resources

Kind regards,
Adrian.