Hi Richard,
See rfc3261, chapter 6 "Choosing the best response", Page 111 :
A proxy which receives a 503 (Service Unavailable) response
SHOULD NOT forward it upstream unless it can determine that any
subsequent requests it might proxy will also generate a 503.
In other words, forwarding a 503 means that the proxy knows it
cannot service any requests, not just the one for the Request-
URI in the request which generated the 503. If the only
response that was received is a 503, the proxy SHOULD generate
a 500 response and forward that upstream.
Still, this gives you access (at script level) to the 503 reply (the
change is done when sending it out), so you can investigate the Reason
hdr (if present).
And yes, we got your other email.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 06.01.2017 17:14, Richard Robson wrote:
hmm,
both our suppliers translate an unavailable number (Q.850;cause=41) as
a 503.
I Guess Im going to have to live with that.
Did you see the other email this morning regarding opensips crashing?
I unhelpfully called the email opensipsp
On 06/01/2017 14:41, Bogdan-Andrei Iancu wrote:
Hi Richard,
Any incoming 503 reply is converted by OpenSIPS to a 500 reply (as
per RFC3261).
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 06.01.2017 16:22, Richard Robson wrote:
Hi,
we are getting 503 messages back but when this is stored on Homer as
a 500. I'm not sure if its Opensips's sipcapture module or Homer
doing the translation
This is the packet captured in sngrep in the sip box
2017/01/06 14:13:59.210301 141.170.24.20:5060 -> 192.168.36.141:5060
SIP/2.0 503 Service Unavailable
Via: SIP/2.0/UDP 141.170.9.156:5060;branch=z9hG4bKd116.a30f9976.0
From: <sip:442035420637@192.168.36.68>;tag=as55dfe54a
To: <sip:+447910705624@141.170.24.20>;tag=gK00d54f0d
Call-ID:
DLGCH_e0lXV2Z/MWR7SFYIMHFjZ3oSAwoyL2YwfkdXX2F5YGsPQVxcfXhma2FDU0BlcWpmf0ZV
CSeq: 103 INVITE
X-ISUPMtype:0c
Reason: Q.850;cause=41;x-source=a
Content-Length: 0
this is the same packet viewed in Homer
2017-01-06 14:13:59 +0000 : 141.170.24.20:5060 -> 192.168.36.141:5060
SIP/2.0 *500* Service Unavailable Via: SIP/2.0/UDP
141.170.9.156:5060;branch=*z9hG4bKd116.a30f9976.0* From:
<sip:442035420637@192.168.36.68>;tag=*as55dfe54a* To:
<sip:+447910705624@141.170.24.20>;tag=gK00d54f0d Call-ID:
*492956a7483fc8345bfdaf6c17212008@192.168.36.68:5060* CSeq: 103
INVITE X-ISUPMtype:0c Reason: Q.850;cause=41;x-source=a
Content-Length: 0
the sip code and the callid have been changed. the call id is the
same as the original call from the outbound asterisk box
Regards,
--
Richard Robson
Greenlight Support
01382 843843
supp...@greenlightcrm.com
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
--
Richard Robson
Greenlight Support
01382 843843
supp...@greenlightcrm.com
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
