[Spce-user] 503 error code being converted to 500

JESUS MANUEL VILLAVICENCIO ESPINOZA kachuy at msn.com
Fri Aug 19 00:38:53 EDT 2016


WEQGFEASVGFA<EVG

________________________________
From: Spce-user <spce-user-bounces at lists.sipwise.com> on behalf of JESUS MANUEL VILLAVICENCIO ESPINOZA <kachuy at msn.com>
Sent: Friday, August 19, 2016 4:32:48 AM
To: Spce-user at lists.sipwise.com
Subject: Re: [Spce-user] 503 error code being converted to 500


eres un pendejo

________________________________
From: Spce-user <spce-user-bounces at lists.sipwise.com> on behalf of Roberto Oliveira <roberto.oliveira at tmco.com.br>
Sent: Friday, August 19, 2016 2:46:42 AM
To: spce-user at lists.sipwise.com
Subject: [Spce-user] 503 error code being converted to 500

Hello,
I'm using mr4.2.1.
I have a  scenario where sipwise is working as a transit peer (i.e. Peer A
sends a call to Sipwise which in turn forward the same call to peer B).
Peer B is returning a 503 error code and there is no more peer available to
route the call. However, for some reason, sipwise is passing a 500 error
code back to peer A.

I would like to passthrough the 503 error to Peer A so that it could try a
failover route.

Anybody could help here?

Thanks a lot



Roberto Oliveira
_______________________________________________
Spce-user mailing list
Spce-user at lists.sipwise.com
https://lists.sipwise.com/listinfo/spce-user
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20160819/fd794a16/attachment-0001.html>


More information about the Spce-user mailing list