<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hello,</p>
<p>As far as I know there is no way to read or write the INVITE's
body, neither with chan_sip nor chan_pjsip.</p>
<p>Jean Aunis<br>
</p>
<br>
<div class="moz-cite-prefix">Le 07/12/2017 à 17:35, Olivier a
écrit :<br>
</div>
<blockquote type="cite"
cite="mid:CAPeT9jh=taAV0tjPyv=D8aH=YmRSQ_kdKt4VAEgdVC=x=b_-FQ@mail.gmail.com">
<div dir="ltr">
<div>
<div>Hello,<br>
<br>
</div>
I'm having a look at section 13.1 from SIP Connect v2 doc (see
[1]).<br>
</div>
It refers to RFC6442 which gives the following example (sorry
for its length):<br>
<br>
INVITE <a href="mailto:sips%3Abob@biloxi.example.com"
moz-do-not-send="true">sips:bob@biloxi.example.com</a> SIP/2.0<br>
Via: SIPS/2.0/TLS <a href="http://pc33.atlanta.example.com"
moz-do-not-send="true">pc33.atlanta.example.com</a>;branch=z9hG4bK74bf9<br>
Max-Forwards: 70<br>
To: Bob <<a href="mailto:sips%3Abob@biloxi.example.com"
moz-do-not-send="true">sips:bob@biloxi.example.com</a>><br>
From: Alice <<a
href="mailto:sips%3Aalice@atlanta.example.com"
moz-do-not-send="true">sips:alice@atlanta.example.com</a>>;tag=9fxced76sl<br>
Call-ID: <a
href="mailto:3848276298220188511@atlanta.example.com"
moz-do-not-send="true">3848276298220188511@atlanta.example.com</a><br>
Geolocation: <<a
href="mailto:cid%3Atarget123@atlanta.example.com"
moz-do-not-send="true">cid:target123@atlanta.example.com</a>><br>
Geolocation-Routing: no<br>
Accept: application/sdp, application/pidf+xml<br>
CSeq: 31862 INVITE<br>
Contact: <<a
href="mailto:sips%3Aalice@atlanta.example.com"
moz-do-not-send="true">sips:alice@atlanta.example.com</a>><br>
Content-Type: multipart/mixed; boundary=boundary1<br>
Content-Length: ...<br>
<br>
--boundary1<br>
<br>
Content-Type: application/sdp<br>
<br>
...Session Description Protocol (SDP) goes here<br>
<br>
--boundary1<br>
<br>
Content-Type: application/pidf+xml<br>
Content-ID: <<a
href="mailto:target123@atlanta.example.com"
moz-do-not-send="true">target123@atlanta.example.com</a>><br>
<?xml version="1.0" encoding="UTF-8"?><br>
<presence<br>
xmlns="urn:ietf:params:xml:ns:pidf"<br>
xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10"<br>
xmlns:gbp="urn:ietf:params:xml:ns:pidf:geopriv10:basicPolicy"<br>
xmlns:cl="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr"<br>
xmlns:gml="<a href="http://www.opengis.net/gml"
moz-do-not-send="true">http://www.opengis.net/gml</a>"<br>
xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model"<br>
entity="<a
href="mailto:pres%3Aalice@atlanta.example.com"
moz-do-not-send="true">pres:alice@atlanta.example.com</a>"><br>
<dm:device id="target123-1"><br>
<gp:geopriv><br>
<gp:location-info><br>
<gml:location><br>
<gml:Point
srsName="urn:ogc:def:crs:EPSG::4326"><br>
<gml:pos>32.86726
-97.16054</gml:pos><br>
</gml:Point><br>
</gml:location><br>
</gp:location-info><br>
<gp:usage-rules><br>
<gbp:retransmission-allowed>false<br>
</gbp:retransmission-allowed><br>
<gbp:retention-expiry>2010-11-14T20:00:00Z<br>
</gbp:retention-expiry><br>
</gp:usage-rules><br>
<gp:method>802.11</gp:method><br>
</gp:geopriv><br>
<dm:deviceID>mac:1234567890ab</dm:deviceID><br>
<dm:timestamp>2010-11-04T20:57:29Z</dm:timestamp><br>
</dm:device><br>
</presence><br>
--boundary1--<br>
<div><br>
<br>
</div>
<div>1. Adding or reading the lines bellow seems easy. How can
you add a whole application/pidf+xml section as above either
using SIP or PJSIP ?<br>
Geolocation: <<a
href="mailto:cid%3Atarget123@atlanta.example.com"
moz-do-not-send="true">cid:target123@atlanta.example.com</a>><br>
Geolocation-Routing: no<br>
<br>
</div>
<div>2. Reciprocally, how can you read such application/pidf+xml
section an incoming call ?<br>
<br>
</div>
<div>3. What do you know of this RFC 6442 adoption within SIP
industry ?<br>
</div>
<div><br>
</div>
<div>Best regards<br>
</div>
<div><br>
[1] <a
href="https://www.sipforum.org/download/sipconnect-technical-recommendation-version-2-0/?wpdmdl=2818"
moz-do-not-send="true">https://www.sipforum.org/download/sipconnect-technical-recommendation-version-2-0/?wpdmdl=2818</a><br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
</blockquote>
<br>
</body>
</html>