[asterisk-bugs] [Asterisk 0015552]: [patch] SIP_BODY function to get a body part of a SIP message

Asterisk Bug Tracker noreply at bugs.digium.com
Fri Sep 4 03:41:11 CDT 2009


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15552 
====================================================================== 
Reported By:                khw
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   15552
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 206090 
Request Review:              
====================================================================== 
Date Submitted:             2009-07-22 05:10 CDT
Last Modified:              2009-09-04 03:41 CDT
====================================================================== 
Summary:                    [patch] SIP_BODY function to get a body part of a
SIP message
Description: 
this patch adds the function SIP_BODY for chan_sip to get a body part by
its Content-Type. Therefore, the existing find_sdp() is generalized to
find_content() and find_sdp() calls find_content() with the parameter
"application/sdp". 

usage example: ${SIP_BODY(application/pidf+xml)} to get a PIDF document
from the SIP body.
====================================================================== 

---------------------------------------------------------------------- 
 (0110213) klaus3000 (reporter) - 2009-09-04 03:41
 https://issues.asterisk.org/view.php?id=15552#c110213 
---------------------------------------------------------------------- 
Hi Olle.

Of course this function can get the bodies only from the initial INVITE,
as other requests do not trigger dialplan execution. 

Nevertheless, the location in emergency calls is usually always in the
initial INVITE - as the call routing depends already on this location. 

I do not think that this will promise too much. Other functions
(SIP_HEADER) also operate only on the initial requests.

This is a very usefull extension as it allows routing of emergency calls
which do supply location information in call setup. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-09-04 03:41 klaus3000      Note Added: 0110213                          
======================================================================




More information about the asterisk-bugs mailing list