<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Hello,</p>
<p>so, the register request has to be sent out in this case via
diameter? If yes, then not much to be done in kamailio.cfg, needs
an enhancement in the c code, if not supported yet -- IMS devs can
comment more, I don't do much in that part of the code.</p>
<p>Cheers,<br>
Daniel<br>
</p>
<br>
<div class="moz-cite-prefix">On 17.05.17 15:47, Haggerty, Paul
(phaggert) wrote:<br>
</div>
<blockquote
cite="mid:9c2a9f6ec89d41afa04a481c4a4ab5e6@ROCXCH18.cs.myharris.net"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:black;}
h3
{mso-style-priority:9;
mso-style-link:"Heading 3 Char";
margin-top:2.0pt;
margin-right:0in;
margin-bottom:0in;
margin-left:0in;
margin-bottom:.0001pt;
page-break-after:avoid;
font-size:12.0pt;
font-family:"Calibri Light",sans-serif;
color:#1F4D78;
font-weight:normal;}
h4
{mso-style-name:"Heading 4\,h4\,H4\,E4\,RFQ3\,4\,H4-Heading 4\,a\.\,Heading4\,H41\,H42\,H43\,H44\,H45\,heading 4\,I4\,l4\,heading\000D4\,Heading No\. L4\,heading4\,44\,4H\,heading";
mso-style-link:"Heading 4 Char\,h4 Char1\,H4 Char1\,E4 Char1\,RFQ3 Char1\,4 Char1\,H4-Heading 4 Char1\,a\. Char1\,Heading4 Char1\,H41 Char1\,H42 Char1\,H43 Char1\,H44 Char1\,H45 Char1\,heading 4 Char1\,I4 Char1\,l4 Char1\,heading\000D4 Char\,Heading No\. L4 Char\,heading4 Char1\,44 Char";
margin-top:6.0pt;
margin-right:0in;
margin-bottom:9.0pt;
margin-left:70.9pt;
text-indent:-70.9pt;
page-break-after:avoid;
punctuation-wrap:simple;
text-autospace:none;
font-size:12.0pt;
font-family:"Arial",sans-serif;
color:windowtext;
font-weight:normal;}
p.MsoList, li.MsoList, div.MsoList
{mso-style-priority:99;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.25in;
margin-bottom:.0001pt;
text-indent:-.25in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:black;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;
color:black;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
span.Heading4Char
{mso-style-name:"Heading 4 Char\,h4 Char1\,H4 Char1\,E4 Char1\,RFQ3 Char1\,4 Char1\,H4-Heading 4 Char1\,a\. Char1\,Heading4 Char1\,H41 Char1\,H42 Char1\,H43 Char1\,H44 Char1\,H45 Char1\,heading 4 Char1\,I4 Char1\,l4 Char1\,heading\000D4 Char\,Heading No\. L4 Char\,heading4 Char1\,44 Char";
mso-style-link:"Heading 4\,h4\,H4\,E4\,RFQ3\,4\,H4-Heading 4\,a\.\,Heading4\,H41\,H42\,H43\,H44\,H45\,heading 4\,I4\,l4\,heading\000D4\,Heading No\. L4\,heading4\,44\,4H\,heading";
font-family:"Arial",sans-serif;}
span.B1Char
{mso-style-name:"B1 Char";
mso-style-link:B1;}
p.B1, li.B1, div.B1
{mso-style-name:B1;
mso-style-link:"B1 Char";
margin-top:0in;
margin-right:0in;
margin-bottom:9.0pt;
margin-left:28.4pt;
text-indent:-14.2pt;
punctuation-wrap:simple;
text-autospace:none;
font-size:10.0pt;
font-family:"Times New Roman",serif;
color:windowtext;}
span.Heading3Char
{mso-style-name:"Heading 3 Char";
mso-style-priority:9;
mso-style-link:"Heading 3";
font-family:"Calibri Light",sans-serif;
color:#1F4D78;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-size:12.0pt;color:#1F497D">Hi Daniel,<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:12.0pt;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:12.0pt;color:#1F497D">Ok, I’ll try to
explain more on this. We have an application server
configured in the HSS with triggers to receive third party
Register requests when the UE registers with the IMS core.
The application server does receive the Register message
when the UE registers but the register message does not
contain all the information from the original Register
request to the PCSCF. In particular, the UE sends a JWT
token in the body of the Register message. The application
server needs this information and according to </span><span
style="font-size:12.0pt">3GPP TS 24.229
</span> <span style="font-size:12.0pt;color:#1F497D"> this
should be supported by the SCSCF with a configuration option
in the HSS called “IncludeRegisterRequest”. When this
configuration option is used the third party Register
message sent to the application server will contain the
original register message in the body of the register
message.
<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:12.0pt;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:12.0pt;color:#1F497D">So, we’re looking for
the SCSCF to do this. At this point as long as we can get
the original Register request in the contents of the Third
party register request it should be enough. Any help on this
would be very appreciated. </span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:12.0pt;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:12.0pt;color:#1F497D">FYI … Below is an
excerpt from the specification.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:12.0pt;color:#1F497D"><o:p> </o:p></span></p>
<h4><a moz-do-not-send="true" name="_Toc477523356"><span
lang="EN-GB">5.4.1.7A Including contents in the
body of the third-party REGISTER request</span></a><span
lang="EN-GB"><o:p></o:p></span></h4>
<p class="MsoNormal">If there is a service information XML
element provided in the HSS Filter Criteria for an AS (see
3GPP TS 29.228 [14]), then in the third-party REGISTER request
the S-CSCF shall:<o:p></o:p></p>
<p class="B1"><span lang="X-NONE">- include in the message
body the service information within the <service-info>
XML which is a child XML element of an <ims-3gpp>
element with the "version" attribute set to "1" element as
described in subclause 7.6; and<o:p></o:p></span></p>
<p class="B1"><span lang="X-NONE">- set the value of the
content type to the MIME type specified in subclause 7.6.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="background:lime;mso-highlight:lime">If there is an
Include Register Request XML element provided in the HSS
Filter Criteria for an AS (see 3GPP TS 29.228 [14]), then in
the third-party REGISTER request the S-CSCF shall:<o:p></o:p></span></p>
<p class="B1"><span style="background:lime;mso-highlight:lime"
lang="X-NONE">- include in the message body the incoming
SIP REGISTER request within a
</span><span
style="background:lime;mso-highlight:lime;mso-fareast-language:JA"
lang="X-NONE">"</span><span
style="background:lime;mso-highlight:lime" lang="X-NONE">message/sip</span><span
style="background:lime;mso-highlight:lime;mso-fareast-language:JA"
lang="X-NONE">"</span><span
style="background:lime;mso-highlight:lime" lang="X-NONE">
MIME body as defined in RFC 3261 [26]; and<o:p></o:p></span></p>
<p class="B1"><span style="background:lime;mso-highlight:lime"
lang="X-NONE">- set the value of the content type to
</span><span
style="background:lime;mso-highlight:lime;mso-fareast-language:JA"
lang="X-NONE">"</span><span
style="background:lime;mso-highlight:lime" lang="X-NONE">message/sip</span><span
style="background:lime;mso-highlight:lime;mso-fareast-language:JA"
lang="X-NONE">"</span><span
style="background:lime;mso-highlight:lime" lang="X-NONE">.</span><span
lang="X-NONE"><o:p></o:p></span></p>
<p class="MsoNormal">If there is an Include Register Response
XML element provided in the HSS Filter Criteria for an AS (see
3GPP TS 29.228 [14]), then in the third-party REGISTER
request, the S-CSCF shall:<o:p></o:p></p>
<p class="B1"><span lang="X-NONE">- include in the message
body the 200 (OK) response to the incoming SIP REGISTER
request within a
</span><span style="mso-fareast-language:JA" lang="X-NONE">"</span><span
lang="X-NONE">message/sip</span><span
style="mso-fareast-language:JA" lang="X-NONE">"</span><span
lang="X-NONE"> MIME body as defined in RFC 3261 [26]; and<o:p></o:p></span></p>
<p class="B1"><span lang="X-NONE">- set the value of the
content type to </span>
<span style="mso-fareast-language:JA" lang="X-NONE">"</span><span
lang="X-NONE">message/sip</span><span
style="mso-fareast-language:JA" lang="X-NONE">"</span><span
lang="X-NONE">.<o:p></o:p></span></p>
<p class="MsoNormal">If there is more than one message body to
be included in the third-party REGISTER request then in the
third-party REGISTER request the S-CSCF shall:<o:p></o:p></p>
<p class="B1"><span lang="X-NONE">- include a multipart
message body and set the value of the Content-Type header
field to "multipart/mixed" as specified in RFC 2046 [149]
and RFC 5621 [150]; and<o:p></o:p></span></p>
<p class="B1"><span lang="X-NONE">- set the Content-Type of
the elements of the MIME body to the content type specified
for the body.<o:p></o:p></span></p>
<p class="MsoNormal">If there is only one message body to be
included in the third-party REGISTER request then the S-CSCF
sets the Content-Type header field to the content type
specified for the body<span
style="font-size:12.0pt;color:#1F497D">.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:12.0pt;color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="color:windowtext">From:</span></b><span
style="color:windowtext"> sr-users
[<a class="moz-txt-link-freetext" href="mailto:sr-users-bounces@lists.kamailio.org">mailto:sr-users-bounces@lists.kamailio.org</a>]
<b>On Behalf Of </b>Daniel-Constantin Mierla<br>
<b>Sent:</b> Wednesday, May 17, 2017 8:43 AM<br>
<b>To:</b> Kamailio (SER) - Users Mailing List
<a class="moz-txt-link-rfc2396E" href="mailto:sr-users@lists.kamailio.org"><sr-users@lists.kamailio.org></a><br>
<b>Subject:</b> Re: [SR-Users] IMS: Including contents
in the body of third-party REGIISTER request.<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p>Hello,<span style="font-size:12.0pt"><o:p></o:p></span></p>
<p>maybe you can give a more specific example of what is
happening and what you would like to get. There might be some
operations in the config scripting that can help.<o:p></o:p></p>
<p>Cheers,<br>
Daniel<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On 16.05.17 17:31, Haggerty, Paul
(phaggert) wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal"><span style="font-size:12.0pt">It looks
like the Kamailio IMS modules don’t support including the
original REGISTER request in third party registrations as
defined in 3GPP TS 24.229.
</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt">Can
someone confirm this? Should this be a tracked defect or
enhancement?</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt">In the
meantime, is there any workaround available? Our
application server needs to get the contents from the
original REGISTER message from the UE.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt">Thanks,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt">Paul</span><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:12.0pt;font-family:"Times New
Roman",serif"><br>
<br>
<br>
<o:p></o:p></span></p>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>Kamailio (SER) - Users Mailing List<o:p></o:p></pre>
<pre><a moz-do-not-send="true" href="mailto:sr-users@lists.kamailio.org">sr-users@lists.kamailio.org</a><o:p></o:p></pre>
<pre><a moz-do-not-send="true" href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a><o:p></o:p></pre>
</blockquote>
<p class="MsoNormal"><span
style="font-size:12.0pt;font-family:"Times New
Roman",serif"><br>
<br>
<o:p></o:p></span></p>
<pre>-- <o:p></o:p></pre>
<pre>Daniel-Constantin Mierla<o:p></o:p></pre>
<pre><a moz-do-not-send="true" href="http://www.twitter.com/miconda">www.twitter.com/miconda</a> -- <a moz-do-not-send="true" href="http://www.linkedin.com/in/miconda">www.linkedin.com/in/miconda</a><o:p></o:p></pre>
<pre>Kamailio Advanced Training - May 22-24 (USA) - <a moz-do-not-send="true" href="http://www.asipto.com">www.asipto.com</a><o:p></o:p></pre>
<pre>Kamailio World Conference - May 8-10, 2017 - <a moz-do-not-send="true" href="http://www.kamailioworld.com">www.kamailioworld.com</a><o:p></o:p></pre>
</div>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Daniel-Constantin Mierla
<a class="moz-txt-link-abbreviated" href="http://www.twitter.com/miconda">www.twitter.com/miconda</a> -- <a class="moz-txt-link-abbreviated" href="http://www.linkedin.com/in/miconda">www.linkedin.com/in/miconda</a>
Kamailio Advanced Training - May 22-24 (USA) - <a class="moz-txt-link-abbreviated" href="http://www.asipto.com">www.asipto.com</a>
Kamailio World Conference - May 8-10, 2017 - <a class="moz-txt-link-abbreviated" href="http://www.kamailioworld.com">www.kamailioworld.com</a></pre>
</body>
</html>