Hello,

this 503 to 500 is a requirement from RFC, to prevent propagation of blacklisting/disabling destination hosts. I don't remember right now any configuration option for it, but you can try to enforce it from the failure route, like:

t_reply("503", "...");

Cheers,
Daniel

On 6/24/12 4:30 PM, Uri Shacked wrote:

I just read the topic - "Copy reason field from 503 to 500. "

Is there a way to change it if i want to send back the original leg 2 503 reply?

On Sun, Jun 24, 2012 at 4:17 PM, Uri Shacked <ushacked@gmail.com> wrote:

Hi,

Kamailio server is behind our company's softswitch and acts as a sip application server.

I notice that there are calls that the softswitch replied with 503 "service unavailable" and kamailio sent to the originator leg 500 "service unavaileable".

When kamailio recieved 504 or 502 it sends them back as is. shouldn't it be the same with 503?

It also does not have a "to tag" in the CDR. And the "to tag" in the 503 that was recieved is not equal to the 500 reply "to tag" kamailio sent back.

any ideas?

BR,

Uri
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

-- 
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Training, Seattle, USA, Sep 23-26, 2012 - http://asipto.com/u/katu
Kamailio Practical Workshop, Netherlands, Sep 10-12, 2012 - http://asipto.com/u/kpw