[OpenSIPS-Users] How to add ISUP part to 403 via send_reply function?

[Vlad Patrascu]

Hi Oleg,

Unfortunately, at the moment there is no way to do this, as the 
/add_isup_part()/ function appends an ISUP body to the SIP message 
exposed in the current script route. So the only option is to add the 
ISUP body to a received reply, not a locally generated one.

Also, it's not an easy/quick feature to implement, but if you don't find 
a way around it and think it would be useful, please open a feature 
request on Github.

Regards,

Vlad Patrascu
OpenSIPS Developer
http://www.opensips-solutions.com

On 06/12/2019 07:42 PM, Олег Подгуйко via Users wrote:
> My opensips works as state-full-proxy. At the one side it works via 
> SIP-I, at another side via SIP. Everything is ok.
> In one of my business-cases I get some INVITE with ISUP body with 
> certain parameters from SIP-I side I need to send 403 with ISUP body 
> including ISUP reason.
> To do this I try to use function:  send_reply("403","Some reason").
>
> It looks like
>
> # Encapsulate a REL
> add_isup_part("REL");
> $isup_param(Cause Indicators | Cause value) = 21;
> send_reply("403","The reason is 21");
> xlog("L_WARN","The call was rejected with 21");
> exit;
>
> But actually 403 is sending without any ISUP body.
>
> Is it possible to do such action?
>
>
> -- 
> Oleg Podguyko
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20190613/843eccaa/attachment.html>