Can't find Contact Header in REGISTER when using cipango with sipml5

[Mirror Xu]

Hello,

Forgive my poor English.

Had someone tested cipango with SIPML5 before? During this time, I am testing cipango with sipml5. When sipml5 starts register, it will send a REGISTER message with a contact header, but from the cipango logs, the REGISTER message don't have a Contact Header. Is there someone who had this problem before, help me please, thank you.

Below is my logs, the first is the logs of the client(sipml5),next is the logs of the server(Cipango).

========================================================================================

Client (sipml5):

SEND: REGISTER sip:10.166.41.126:18080 SIP/2.0 Via: SIP/2.0/WS df7jal23ls0d.invalid;branch=z9hG4bKwAWfKXhbUC12dGL8d8cWkoRCydD7gUb5;rport From: <sip:b...@10.166.41.126:18080>;tag=rO04hbBy1UQDNXEopiJT To: <sip:b...@10.166.41.126:18080> Contact: <sip:b...@df7jal23ls0d.invalid;rtcweb-breaker=no;transport=ws>;expires=200;click2call=no;+g.oma.sip-im;+audio;language="en,fr" Call-ID: b8b4282d-e262-edf4-12d5-78819a862c57 CSeq: 6808 REGISTER Content-Length: 0 Max-Forwards: 70 User-Agent: IM-client/OMA1.0 sipML5-v1.2013.05.24 Organization: Doubango Telecom

Server(Cipango):

2013-07-04 22:14:48 IN WS /10.166.41.126:18080 < /10.166.41.126:58147 REGISTER sip:10.166.41.126:18080 SIP/2.0 Call-ID: 5a2cfc64-a2bb-5787-e471-0035b250ad63 Content-Length: 0 CSeq: 11432 REGISTER From: <sip:a...@10.166.41.126:18080>;tag=72f1PWO7epi8TUXa2wbT Max-Forwards: 70 Organization: Doubango Telecom To: <sip:a...@10.166.41.126:18080> User-Agent: IM-client/OMA1.0 sipML5-v1.2013.05.24 Via: SIP/2.0/WS df7jal23ls0d.invalid;branch=z9hG4bKnB2HFPK9gUIzJdRLXDKUgqe9fFdpquqH;rport

========================================================================================

As you can see, the Contact header was lost. I don't know whether this is the issue of cipango or the issue of sipml5.

Your help will be appreciative. 

Thanks in advance,

Mirror

[Nicolas Trangosi]

Hi Mirror,
These two messages are not the same: for instance Call-IDs are not identical...

Regards,
Nicolas

--
You received this message because you are subscribed to the Google Groups "cipango-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cipango-dev...@googlegroups.com.
To post to this group, send email to cipan...@googlegroups.com.
Visit this group at http://groups.google.com/group/cipango-dev.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Mirror Xu]

Hi Nicolas,

I am so sorry for my careless!

Below is the right messages.

=======================================================================

Client(sipml5)

SEND: REGISTER sip:10.166.41.126:18080 SIP/2.0 Via: SIP/2.0/WS df7jal23ls0d.invalid;branch=z9hG4bKaKkMckT0t3noG816WywV4ve4x6xTaJ7g;rport From: <sip:b...@10.166.41.126:18080>;tag=o7Xgo1mPkuqLSSQCNCu4 To: <sip:b...@10.166.41.126:18080> Contact: <sip:b...@df7jal23ls0d.invalid;rtcweb-breaker=no;transport=ws>;expires=200;click2call=no;+g.oma.sip-im;+audio;language="en,fr" Call-ID: caba3247-d95f-1ba7-e5c7-93fd52af1400 CSeq: 12794 REGISTER Content-Length: 0 Max-Forwards: 70 User-Agent: IM-client/OMA1.0 sipML5-v1.2013.05.24 Organization: Doubango Telecom Supported: path

Server(Cipango)

2013-07-05 09:15:51 IN WS /10.166.41.126:18080 < /10.166.41.126:60180 REGISTER sip:10.166.41.126:18080 SIP/2.0 Call-ID: caba3247-d95f-1ba7-e5c7-93fd52af1400 Content-Length: 0 CSeq: 12794 REGISTER From: <sip:b...@10.166.41.126:18080>;tag=o7Xgo1mPkuqLSSQCNCu4 Max-Forwards: 70 Organization: Doubango Telecom Supported: path To: <sip:b...@10.166.41.126:18080> User-Agent: IM-client/OMA1.0 sipML5-v1.2013.05.24 Via: SIP/2.0/WS df7jal23ls0d.invalid;branch=z9hG4bKaKkMckT0t3noG816WywV4ve4x6xTaJ7g;rport

=======================================================================

Best Regards,

Mirror

在 2013年7月4日星期四UTC+8下午10时25分06秒，Nicolas Trangosi写道：

[Nicolas Trangosi]

Mirror,
This issue is now fixed.
For more details, please look up at CIPANGO-205 on jira

Regards,
Nicolas

[Mirror Xu]

Hi Nicolas,

Thanks for having resolved this issue. As I can see from the jira page, this issue has been fixed in Version 3.0.0.M2. These days I am developing a demo with cipango(3.0.0.M1), so I want to know when will the version 3.0.0.M2 be released ? thanks.

Best Regards,

Mirror 

在 2013年7月5日星期五UTC+8下午4时11分14秒，Nicolas Trangosi写道：

[Nicolas Trangosi]

Hi Mirror,
We are currently developing a new experimental feature (replication) and we have planned to create M2 when it will be finished. This will be probably this summer.

If you want to test the patch, you could get source code from git at https://github.com/cipango/cipango. The procedure to compile Cipango is available on http://confluence.cipango.org/

Kind regards,
Nicolas

[Mirror Xu]

If required, I will build the source code.

Thanks a lot.

Best Regards,

Mirror

在 2013年7月8日星期一UTC+8下午3时06分23秒，Nicolas Trangosi写道：