Hello everyone,
Feel free to set $OSSPROXY to whatever you like = Kamailio/OpenSIPS/OpenSER (for those of you who can't let go).
$OSSPROXY is my favorite SIP toolkit. In addition to being an excellent proxy and registrar it serves as a platform to do SIP mangling and wrangling. With that in mind let me propose a crazy idea...
How hard would it be to get $OSSPROXY to be able to parse what is commonly referred to as SIP-T (RFC 3372)? I understand $OSSPROXY has no business getting too involved in the SDP but I feel it makes sense in some instances (like this one). What if I want to make a routing decision based on an encapsulated ISUP parameter of some sort? Who knows what it could be!?!? Maybe there are some other uses but that makes the most sense and seems to be the most practical. It should be possible to develop an $OSSPROXY module to:
- Use the SDP parser to find the ISUP SDP part:
http://www.kamailio.net/dokuwiki/doku.php/development:sdp-parsing
- Pass that part into a "real" ISUP parser (if necessary). I couldn't seem to find the perfect library but perhaps something like this could work:
http://www.openss7.org/isup.html
- Make the ISUP parameters available via AVPs, pseudo variables, etc for use in the $OSSPROXY script.
I don't really have a need for this but it seems like it could be cool. Am I nuts?
Hello,
On 09/03/08 19:10, Kristian Kielhofner wrote:
Hello everyone,
Feel free to set $OSSPROXY to whatever you like = Kamailio/OpenSIPS/OpenSER (for those of you who can't let go).
$OSSPROXY is my favorite SIP toolkit. In addition to being an excellent proxy and registrar it serves as a platform to do SIP mangling and wrangling. With that in mind let me propose a crazy idea...
How hard would it be to get $OSSPROXY to be able to parse what is commonly referred to as SIP-T (RFC 3372)? I understand $OSSPROXY has no business getting too involved in the SDP but I feel it makes sense in some instances (like this one). What if I want to make a routing decision based on an encapsulated ISUP parameter of some sort? Who knows what it could be!?!? Maybe there are some other uses but that makes the most sense and seems to be the most practical. It should be possible to develop an $OSSPROXY module to:
- Use the SDP parser to find the ISUP SDP part:
http://www.kamailio.net/dokuwiki/doku.php/development:sdp-parsing
- Pass that part into a "real" ISUP parser (if necessary). I couldn't
seem to find the perfect library but perhaps something like this could work:
http://www.openss7.org/isup.html
- Make the ISUP parameters available via AVPs, pseudo variables, etc
for use in the $OSSPROXY script.
I don't really have a need for this but it seems like it could be cool. Am I nuts?
I would expose the body as a dynamic structure, so components will be accessible in the script, e.g. (naming schema just for example),
if($body(0=>content-type)=="application/sdp") { if($body(0=>m=>type) == "audio") { } }
Based on the available content type parsers (sdp, isup), the structure has different attributes.
Cheers, Daniel
General support for the idea from me. It would be fanstatic to be able to part the payload esp. For ISUP messages.
Neill...;o)
Neill Wilkinson Principal Consultant Aeonvista Ltd - opening up new ideas
-----Original Message----- From: users-bounces@lists.kamailio.org [mailto:users-bounces@lists.kamailio.org] On Behalf Of Daniel-Constantin Mierla Sent: 03 September 2008 17:45 To: Kristian Kielhofner Cc: users@lists.kamailio.org Subject: Re: [Kamailio-Users] SIP-T: Multipart SDPs, ISUP parsing, etc
Hello,
On 09/03/08 19:10, Kristian Kielhofner wrote:
Hello everyone,
Feel free to set $OSSPROXY to whatever you like = Kamailio/OpenSIPS/OpenSER (for those of you who can't let go).
$OSSPROXY is my favorite SIP toolkit. In addition to being an excellent proxy and registrar it serves as a platform to do SIP mangling and wrangling. With that in mind let me propose a crazy idea...
How hard would it be to get $OSSPROXY to be able to parse what is commonly referred to as SIP-T (RFC 3372)? I understand $OSSPROXY has no business getting too involved in the SDP but I feel it makes sense in some instances (like this one). What if I want to make a routing decision based on an encapsulated ISUP parameter of some sort? Who knows what it could be!?!? Maybe there are some other uses but that makes the most sense and seems to be the most practical. It should be possible to develop an $OSSPROXY module to:
- Use the SDP parser to find the ISUP SDP part:
http://www.kamailio.net/dokuwiki/doku.php/development:sdp-parsing
- Pass that part into a "real" ISUP parser (if necessary). I couldn't
seem to find the perfect library but perhaps something like this could work:
http://www.openss7.org/isup.html
- Make the ISUP parameters available via AVPs, pseudo variables, etc
for use in the $OSSPROXY script.
I don't really have a need for this but it seems like it could be cool. Am I nuts?
I would expose the body as a dynamic structure, so components will be accessible in the script, e.g. (naming schema just for example),
if($body(0=>content-type)=="application/sdp") { if($body(0=>m=>type) == "audio") { } }
Based on the available content type parsers (sdp, isup), the structure has different attributes.
Cheers, Daniel
On Wed, Sep 3, 2008 at 12:44 PM, Daniel-Constantin Mierla miconda@gmail.com wrote:
Hello,
I would expose the body as a dynamic structure, so components will be accessible in the script, e.g. (naming schema just for example),
if($body(0=>content-type)=="application/sdp") { if($body(0=>m=>type) == "audio") { } }
Based on the available content type parsers (sdp, isup), the structure has different attributes.
Cheers, Daniel
Yeah, my fault. It's certainly not "multipart SDP" as much as MIME Multipart with application/sdp and application/isup parts... application/isup is what I'm interested in, obviously!
-
Daniel-Constantin Mierla -
Kristian Kielhofner -
neill.wilkinson＠btinternet.com