Hi,
if you look writing some c module to deal with SIP-T, there is a parser
that supports multi-part body:
by playing with regexp transformation over $rb you can extract values
from body and decide the routing based on that:
Of course, I'll throw in the obligatory mention
that this is the
Kamailio list, not the OpenSIPS list.
But what I said applies to both because the issue is one of fundamentals.
Alex Balashov wrote:
SIP-T is an encapsulated payload in SIP.
Therefore, OpenSIPS "supports" it.
Can OpenSIPS do anything with it, like make routing decisions based on
encapsulated ISUP attributes natively? Well, no. Not unless you want
to go fish stuff out of the message body with textops, I guess.
So, the real question is, what do you mean by "supports?" OpenSIPS is a
SIP proxy, nothing more and nothing less.
Kaeman Chris wrote:
> Hello,
>
> Does opensips support SIP-T?
>
> Thank you!
> KC
>
>