Respond with SIP 480 instead of 603

JimLeBeef · January 24, 2020, 1:18pm

Hi Guys,

First time poster!

We are running an interop test with our SIP trunk provider and FreePBX.
If an inbound call to an extension on the PBX is not answered within 15 seconds, the PBX responds with a SIP 603. The provider have asked is we can send a SIP 480 in that scenario.

Whether it’s really right or wrong, is there a quick way to modify FreePBX to accommodate the request? I did have a look around and tried toggling the extension options under ‘Optional Destinations>No Answer>Terminate’ between Hangup/Congestion/Busy however nothing seemed to change the SIP response codes witnessed in my pcap, it was 603 each time.

Any help much appreciated,

James

lgaetz · January 24, 2020, 1:56pm

Hi James

Ugh, I hate these requests. But here’s a small bag of tricks I’ve accumulated:

gist.github.com

https://gist.github.com/lgaetz/480582a1827cc98db1ee539c249f074b

SIP First Responder

[send-sip-response-code]
; Context to send a specific SIP response code and terminate the channel
; Create Custom Destination in FreePBX with a dial string of the format
;          send-sip-response-code,404,1
; substitute the appropriate response code in place of the 404
; Reference: https://wiki.asterisk.org/wiki/display/AST/Hangup+Cause+Mappings
;
; latest version: https://gist.github.com/lgaetz/480582a1827cc98db1ee539c249f074b
;
; License; GPL/2

This file has been truncated. show original

system · January 31, 2020, 1:56pm

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.