Hi ,
I managed to run Kamailio to replace OpenIMSCore. I am using boghe client to sign in, when I do so , my registration is forwarded as per the trigger point to my AS server.
As I notice , the REGISTER request miss Content-Type header which is mandatory in the 3gpp TS .
Is this configurable ? Am I doing something wrong or is it a bug?
Thank you for your help
Ziad Habchi
On 07.08.2013 13:42, Ziad Habchi wrote:
Hi ,
I managed to run Kamailio to replace OpenIMSCore. I am using boghe client to sign in, when I do so , my registration is forwarded as per the trigger point to my AS server.
As I notice , the REGISTER request miss Content-Type header which is mandatory in the 3gpp TS .
Is this configurable ? Am I doing something wrong or is it a bug?
So, what is the problem? If the header is missing in the request, the the client has to add it to the request.
In what way do you want to change the behavior of Kamailio? What is it currently doing with the malformed REGISTER request and what do you expect Kamailio to do with the malformed REGISTER request?
regards Klaus
Hi Klaus,
According to 3GPP TS 24.229 Release 5 , section 5.4.1.7 - g (Notification of Application Servers about registration status) the S-CSCF shall set the value of the Content-Type header to include the MIME type specified
The Register is being forwarded to the Application Server and not to a client , and according to the specs, the content-type header should be included in the forwarded SIP packet.
Please let me know if I clarified my point well. Thank you for your support.
Ziad Habchi
-----Original Message----- From: Klaus Darilion [mailto:klaus.mailinglists@pernau.at] Sent: Wednesday, August 7, 2013 5:38 PM To: Kamailio (SER) - Users Mailing List Cc: Ziad Habchi; Dragos.Vingarzan@fokus.fraunhofer.de Subject: Re: [SR-Users] Content-Type Header missing from third part registration
On 07.08.2013 13:42, Ziad Habchi wrote:
Hi ,
I managed to run Kamailio to replace OpenIMSCore. I am using boghe client to sign in, when I do so , my registration is forwarded as per the trigger point to my AS server.
As I notice , the REGISTER request miss Content-Type header which is mandatory in the 3gpp TS .
Is this configurable ? Am I doing something wrong or is it a bug?
So, what is the problem? If the header is missing in the request, the the client has to add it to the request.
In what way do you want to change the behavior of Kamailio? What is it currently doing with the malformed REGISTER request and what do you expect Kamailio to do with the malformed REGISTER request?
regards Klaus
Hello Ziad,
maybe you should make a clarification, because, AFAIR, the REGISTER is not really forwarded! It is actually that the S-CSCF is creating additional B2B dummy REGISTER messages. And these might not be up to the spec...
But anyway, what should this B2B REGISTER requests contain? Because I think now they don't include anything, hence why the header ?...
Cheers, -Dragos
On 08/07/2013 05:05 PM, Ziad Habchi wrote:
Hi Klaus,
According to 3GPP TS 24.229 Release 5 , section 5.4.1.7 - g (Notification of Application Servers about registration status) the S-CSCF shall set the value of the Content-Type header to include the MIME type specified
The Register is being forwarded to the Application Server and not to a client , and according to the specs, the content-type header should be included in the forwarded SIP packet.
Please let me know if I clarified my point well. Thank you for your support.
Ziad Habchi
-----Original Message----- From: Klaus Darilion [mailto:klaus.mailinglists@pernau.at] Sent: Wednesday, August 7, 2013 5:38 PM To: Kamailio (SER) - Users Mailing List Cc: Ziad Habchi; Dragos.Vingarzan@fokus.fraunhofer.de Subject: Re: [SR-Users] Content-Type Header missing from third part registration
On 07.08.2013 13:42, Ziad Habchi wrote:
Hi ,
I managed to run Kamailio to replace OpenIMSCore. I am using boghe client to sign in, when I do so , my registration is forwarded as per the trigger point to my AS server.
As I notice , the REGISTER request miss Content-Type header which is mandatory in the 3gpp TS .
Is this configurable ? Am I doing something wrong or is it a bug?
So, what is the problem? If the header is missing in the request, the the client has to add it to the request.
In what way do you want to change the behavior of Kamailio? What is it currently doing with the malformed REGISTER request and what do you expect Kamailio to do with the malformed REGISTER request?
regards Klaus
.
Hi Dragos,
Thank you again for your quick reply. As per the current implementation of the ims_isc module, the S-CSCF is sending the 3-rd party REGISTER towards the ASs listed in the reply from the HSS.
In the third_party_reg.c source file, line 113 to 130 lists the header and body of the register that is being generated and send to the AS.
Those headers and body is done according to the specs, but the only header missing is the Content-Type header. I believe that this header should be included according to the 3GPP TS 24.229.
Let me know if I am still not being clear, I appreciate your help, and I am waiting for your reply.
Thank you, Ziad Habchi
-----Original Message----- From: Dragos Vingarzan [mailto:dragos.vingarzan@fokus.fraunhofer.de] Sent: Wednesday, August 7, 2013 6:19 PM To: Ziad Habchi Cc: 'Klaus Darilion'; 'Kamailio (SER) - Users Mailing List' Subject: Re: [SR-Users] Content-Type Header missing from third part registration
Hello Ziad,
maybe you should make a clarification, because, AFAIR, the REGISTER is not really forwarded! It is actually that the S-CSCF is creating additional B2B dummy REGISTER messages. And these might not be up to the spec...
But anyway, what should this B2B REGISTER requests contain? Because I think now they don't include anything, hence why the header ?...
Cheers, -Dragos
On 08/07/2013 05:05 PM, Ziad Habchi wrote:
Hi Klaus,
According to 3GPP TS 24.229 Release 5 , section 5.4.1.7 - g (Notification of Application Servers about registration status) the S-CSCF shall set the value of the Content-Type header to include the MIME type specified
The Register is being forwarded to the Application Server and not to a client , and according to the specs, the content-type header should be included in the forwarded SIP packet.
Please let me know if I clarified my point well. Thank you for your support.
Ziad Habchi
-----Original Message----- From: Klaus Darilion [mailto:klaus.mailinglists@pernau.at] Sent: Wednesday, August 7, 2013 5:38 PM To: Kamailio (SER) - Users Mailing List Cc: Ziad Habchi; Dragos.Vingarzan@fokus.fraunhofer.de Subject: Re: [SR-Users] Content-Type Header missing from third part registration
On 07.08.2013 13:42, Ziad Habchi wrote:
Hi ,
I managed to run Kamailio to replace OpenIMSCore. I am using boghe client to sign in, when I do so , my registration is forwarded as per the trigger point to my AS server.
As I notice , the REGISTER request miss Content-Type header which is mandatory in the 3gpp TS .
Is this configurable ? Am I doing something wrong or is it a bug?
So, what is the problem? If the header is missing in the request, the the client has to add it to the request.
In what way do you want to change the behavior of Kamailio? What is it currently doing with the malformed REGISTER request and what do you expect Kamailio to do with the malformed REGISTER request?
regards Klaus
.
-- ----------------------------------------- Dipl. Eng. Dragos Vingarzan Fraunhofer FOKUS/NGNI Kaiserin-Augusta-Allee 31 10589 Berlin,Germany Phone +49 (0)30 - 3463 - 7385 Mobile +49 (0)176 - 48 32 16 00 Web www.fokus.fraunhofer.de www.openepc.net www.openimscore.org -----------------------------------------------------------------
Drogos,
Below is a sample sip packet sent from the Kamailio S-CSCF to the AS
RREGISTER sip:ip-sm-gw.ims-core:5070 SIP/2.0 Via: SIP/2.0/UDP 192.168.49.164:6060;branch=z9hG4bKf162.bf939204.0 To: sip:+1234567890@ims-core From: sip:scscf;tag=8c3594ac027a3ba0f0a908969aadf227-6014 CSeq: 10 REGISTER Call-ID: 7fefec00-10930@192.168.49.164 Content-Length: 72 User-Agent: Kamailio S-CSCF Event: registration Max-Forwards: 10 Expires: 600120 Contact: sip:scscf P-Visited-Network-ID: ims-core P-Access-Network-Info: ADSL;utran-cell-id-3gpp=00000000
<ims-3gpp version="1"><service-info>1234567890</service-info></ims-3gpp>
As you can see, the Content-Type Header is missing from the packet.
Regards, Ziad Habchi
-----Original Message----- From: Ziad Habchi [mailto:ziad.habchi@jinnysoftware.com] Sent: Thursday, August 8, 2013 10:08 AM To: 'Dragos Vingarzan' Cc: 'Klaus Darilion'; 'Kamailio (SER) - Users Mailing List'; 'mona.hanna@jinnysoftware.com' Subject: RE: [SR-Users] Content-Type Header missing from third part registration
Hi Dragos,
Thank you again for your quick reply. As per the current implementation of the ims_isc module, the S-CSCF is sending the 3-rd party REGISTER towards the ASs listed in the reply from the HSS.
In the third_party_reg.c source file, line 113 to 130 lists the header and body of the register that is being generated and send to the AS.
Those headers and body is done according to the specs, but the only header missing is the Content-Type header. I believe that this header should be included according to the 3GPP TS 24.229.
Let me know if I am still not being clear, I appreciate your help, and I am waiting for your reply.
Thank you, Ziad Habchi
-----Original Message----- From: Dragos Vingarzan [mailto:dragos.vingarzan@fokus.fraunhofer.de] Sent: Wednesday, August 7, 2013 6:19 PM To: Ziad Habchi Cc: 'Klaus Darilion'; 'Kamailio (SER) - Users Mailing List' Subject: Re: [SR-Users] Content-Type Header missing from third part registration
Hello Ziad,
maybe you should make a clarification, because, AFAIR, the REGISTER is not really forwarded! It is actually that the S-CSCF is creating additional B2B dummy REGISTER messages. And these might not be up to the spec...
But anyway, what should this B2B REGISTER requests contain? Because I think now they don't include anything, hence why the header ?...
Cheers, -Dragos
On 08/07/2013 05:05 PM, Ziad Habchi wrote:
Hi Klaus,
According to 3GPP TS 24.229 Release 5 , section 5.4.1.7 - g (Notification of Application Servers about registration status) the S-CSCF shall set the value of the Content-Type header to include the MIME type specified
The Register is being forwarded to the Application Server and not to a client , and according to the specs, the content-type header should be included in the forwarded SIP packet.
Please let me know if I clarified my point well. Thank you for your support.
Ziad Habchi
-----Original Message----- From: Klaus Darilion [mailto:klaus.mailinglists@pernau.at] Sent: Wednesday, August 7, 2013 5:38 PM To: Kamailio (SER) - Users Mailing List Cc: Ziad Habchi; Dragos.Vingarzan@fokus.fraunhofer.de Subject: Re: [SR-Users] Content-Type Header missing from third part registration
On 07.08.2013 13:42, Ziad Habchi wrote:
Hi ,
I managed to run Kamailio to replace OpenIMSCore. I am using boghe client to sign in, when I do so , my registration is forwarded as per the trigger point to my AS server.
As I notice , the REGISTER request miss Content-Type header which is mandatory in the 3gpp TS .
Is this configurable ? Am I doing something wrong or is it a bug?
So, what is the problem? If the header is missing in the request, the the client has to add it to the request.
In what way do you want to change the behavior of Kamailio? What is it currently doing with the malformed REGISTER request and what do you expect Kamailio to do with the malformed REGISTER request?
regards Klaus
.
-- ----------------------------------------- Dipl. Eng. Dragos Vingarzan Fraunhofer FOKUS/NGNI Kaiserin-Augusta-Allee 31 10589 Berlin,Germany Phone +49 (0)30 - 3463 - 7385 Mobile +49 (0)176 - 48 32 16 00 Web www.fokus.fraunhofer.de www.openepc.net www.openimscore.org -----------------------------------------------------------------
Dear Dragos,
Did you get my email ? any updates regarding the below?
Regards, Ziad Habchi
-----Original Message----- From: Ziad Habchi [mailto:ziad.habchi@jinnysoftware.com] Sent: Thursday, August 8, 2013 10:38 AM To: 'Dragos Vingarzan' Cc: 'Klaus Darilion'; 'Kamailio (SER) - Users Mailing List'; 'mona.hanna@jinnysoftware.com' Subject: RE: [SR-Users] Content-Type Header missing from third part registration
Drogos,
Below is a sample sip packet sent from the Kamailio S-CSCF to the AS
RREGISTER sip:ip-sm-gw.ims-core:5070 SIP/2.0 Via: SIP/2.0/UDP 192.168.49.164:6060;branch=z9hG4bKf162.bf939204.0 To: sip:+1234567890@ims-core From: sip:scscf;tag=8c3594ac027a3ba0f0a908969aadf227-6014 CSeq: 10 REGISTER Call-ID: 7fefec00-10930@192.168.49.164 Content-Length: 72 User-Agent: Kamailio S-CSCF Event: registration Max-Forwards: 10 Expires: 600120 Contact: sip:scscf P-Visited-Network-ID: ims-core P-Access-Network-Info: ADSL;utran-cell-id-3gpp=00000000
<ims-3gpp version="1"><service-info>1234567890</service-info></ims-3gpp>
As you can see, the Content-Type Header is missing from the packet.
Regards, Ziad Habchi
-----Original Message----- From: Ziad Habchi [mailto:ziad.habchi@jinnysoftware.com] Sent: Thursday, August 8, 2013 10:08 AM To: 'Dragos Vingarzan' Cc: 'Klaus Darilion'; 'Kamailio (SER) - Users Mailing List'; 'mona.hanna@jinnysoftware.com' Subject: RE: [SR-Users] Content-Type Header missing from third part registration
Hi Dragos,
Thank you again for your quick reply. As per the current implementation of the ims_isc module, the S-CSCF is sending the 3-rd party REGISTER towards the ASs listed in the reply from the HSS.
In the third_party_reg.c source file, line 113 to 130 lists the header and body of the register that is being generated and send to the AS.
Those headers and body is done according to the specs, but the only header missing is the Content-Type header. I believe that this header should be included according to the 3GPP TS 24.229.
Let me know if I am still not being clear, I appreciate your help, and I am waiting for your reply.
Thank you, Ziad Habchi
-----Original Message----- From: Dragos Vingarzan [mailto:dragos.vingarzan@fokus.fraunhofer.de] Sent: Wednesday, August 7, 2013 6:19 PM To: Ziad Habchi Cc: 'Klaus Darilion'; 'Kamailio (SER) - Users Mailing List' Subject: Re: [SR-Users] Content-Type Header missing from third part registration
Hello Ziad,
maybe you should make a clarification, because, AFAIR, the REGISTER is not really forwarded! It is actually that the S-CSCF is creating additional B2B dummy REGISTER messages. And these might not be up to the spec...
But anyway, what should this B2B REGISTER requests contain? Because I think now they don't include anything, hence why the header ?...
Cheers, -Dragos
On 08/07/2013 05:05 PM, Ziad Habchi wrote:
Hi Klaus,
According to 3GPP TS 24.229 Release 5 , section 5.4.1.7 - g (Notification of Application Servers about registration status) the S-CSCF shall set the value of the Content-Type header to include the MIME type specified
The Register is being forwarded to the Application Server and not to a client , and according to the specs, the content-type header should be included in the forwarded SIP packet.
Please let me know if I clarified my point well. Thank you for your support.
Ziad Habchi
-----Original Message----- From: Klaus Darilion [mailto:klaus.mailinglists@pernau.at] Sent: Wednesday, August 7, 2013 5:38 PM To: Kamailio (SER) - Users Mailing List Cc: Ziad Habchi; Dragos.Vingarzan@fokus.fraunhofer.de Subject: Re: [SR-Users] Content-Type Header missing from third part registration
On 07.08.2013 13:42, Ziad Habchi wrote:
Hi ,
I managed to run Kamailio to replace OpenIMSCore. I am using boghe client to sign in, when I do so , my registration is forwarded as per the trigger point to my AS server.
As I notice , the REGISTER request miss Content-Type header which is mandatory in the 3gpp TS .
Is this configurable ? Am I doing something wrong or is it a bug?
So, what is the problem? If the header is missing in the request, the the client has to add it to the request.
In what way do you want to change the behavior of Kamailio? What is it currently doing with the malformed REGISTER request and what do you expect Kamailio to do with the malformed REGISTER request?
regards Klaus
.
-- ----------------------------------------- Dipl. Eng. Dragos Vingarzan Fraunhofer FOKUS/NGNI Kaiserin-Augusta-Allee 31 10589 Berlin,Germany Phone +49 (0)30 - 3463 - 7385 Mobile +49 (0)176 - 48 32 16 00 Web www.fokus.fraunhofer.de www.openepc.net www.openimscore.org -----------------------------------------------------------------
Yes, it seems that you detected a bug. You can try to add it yourself and submit a patch to the tracker, or send another email with "bug in S-CSCF module" with the below REGISTER trace and the description to sr-dev. Maybe the IMS guys will then handle it.
regards Klaus
On 12.08.2013 16:06, Ziad Habchi wrote:
Dear Dragos,
Did you get my email ? any updates regarding the below?
Regards, Ziad Habchi
-----Original Message----- From: Ziad Habchi [mailto:ziad.habchi@jinnysoftware.com] Sent: Thursday, August 8, 2013 10:38 AM To: 'Dragos Vingarzan' Cc: 'Klaus Darilion'; 'Kamailio (SER) - Users Mailing List'; 'mona.hanna@jinnysoftware.com' Subject: RE: [SR-Users] Content-Type Header missing from third part registration
Drogos,
Below is a sample sip packet sent from the Kamailio S-CSCF to the AS
RREGISTER sip:ip-sm-gw.ims-core:5070 SIP/2.0 Via: SIP/2.0/UDP 192.168.49.164:6060;branch=z9hG4bKf162.bf939204.0 To: sip:+1234567890@ims-core From: sip:scscf;tag=8c3594ac027a3ba0f0a908969aadf227-6014 CSeq: 10 REGISTER Call-ID: 7fefec00-10930@192.168.49.164 Content-Length: 72 User-Agent: Kamailio S-CSCF Event: registration Max-Forwards: 10 Expires: 600120 Contact: sip:scscf P-Visited-Network-ID: ims-core P-Access-Network-Info: ADSL;utran-cell-id-3gpp=00000000
<ims-3gpp version="1"><service-info>1234567890</service-info></ims-3gpp>
As you can see, the Content-Type Header is missing from the packet.
Regards, Ziad Habchi
-----Original Message----- From: Ziad Habchi [mailto:ziad.habchi@jinnysoftware.com] Sent: Thursday, August 8, 2013 10:08 AM To: 'Dragos Vingarzan' Cc: 'Klaus Darilion'; 'Kamailio (SER) - Users Mailing List'; 'mona.hanna@jinnysoftware.com' Subject: RE: [SR-Users] Content-Type Header missing from third part registration
Hi Dragos,
Thank you again for your quick reply. As per the current implementation of the ims_isc module, the S-CSCF is sending the 3-rd party REGISTER towards the ASs listed in the reply from the HSS.
In the third_party_reg.c source file, line 113 to 130 lists the header and body of the register that is being generated and send to the AS.
Those headers and body is done according to the specs, but the only header missing is the Content-Type header. I believe that this header should be included according to the 3GPP TS 24.229.
Let me know if I am still not being clear, I appreciate your help, and I am waiting for your reply.
Thank you, Ziad Habchi
-----Original Message----- From: Dragos Vingarzan [mailto:dragos.vingarzan@fokus.fraunhofer.de] Sent: Wednesday, August 7, 2013 6:19 PM To: Ziad Habchi Cc: 'Klaus Darilion'; 'Kamailio (SER) - Users Mailing List' Subject: Re: [SR-Users] Content-Type Header missing from third part registration
Hello Ziad,
maybe you should make a clarification, because, AFAIR, the REGISTER is not really forwarded! It is actually that the S-CSCF is creating additional B2B dummy REGISTER messages. And these might not be up to the spec...
But anyway, what should this B2B REGISTER requests contain? Because I think now they don't include anything, hence why the header ?...
Cheers, -Dragos
On 08/07/2013 05:05 PM, Ziad Habchi wrote:
Hi Klaus,
According to 3GPP TS 24.229 Release 5 , section 5.4.1.7 - g (Notification of Application Servers about registration status) the S-CSCF shall set the value of the Content-Type header to include the MIME type specified
The Register is being forwarded to the Application Server and not to a client , and according to the specs, the content-type header should be included in the forwarded SIP packet.
Please let me know if I clarified my point well. Thank you for your support.
Ziad Habchi
-----Original Message----- From: Klaus Darilion [mailto:klaus.mailinglists@pernau.at] Sent: Wednesday, August 7, 2013 5:38 PM To: Kamailio (SER) - Users Mailing List Cc: Ziad Habchi; Dragos.Vingarzan@fokus.fraunhofer.de Subject: Re: [SR-Users] Content-Type Header missing from third part registration
On 07.08.2013 13:42, Ziad Habchi wrote:
Hi ,
I managed to run Kamailio to replace OpenIMSCore. I am using boghe client to sign in, when I do so , my registration is forwarded as per the trigger point to my AS server.
As I notice , the REGISTER request miss Content-Type header which is mandatory in the 3gpp TS .
Is this configurable ? Am I doing something wrong or is it a bug?
So, what is the problem? If the header is missing in the request, the the client has to add it to the request.
In what way do you want to change the behavior of Kamailio? What is it currently doing with the malformed REGISTER request and what do you expect Kamailio to do with the malformed REGISTER request?
regards Klaus
.
--
Dipl. Eng. Dragos Vingarzan Fraunhofer FOKUS/NGNI Kaiserin-Augusta-Allee 31 10589 Berlin,Germany Phone +49 (0)30 - 3463 - 7385 Mobile +49 (0)176 - 48 32 16 00 Web www.fokus.fraunhofer.de www.openepc.net www.openimscore.org
-
Dragos Vingarzan -
Klaus Darilion -
Ziad Habchi