Hello, I'm sending an Invite request thru an Application Server. When the Invite arrives to the Clearwater IMS and is sent to the AS, the Content-Type header is enconded and the boundary is changed. That provokes a wrong behavior in the AS when the Invite reaches it.
Here you have a piece of both Invites. *Invite sent from the client to the CW:* INVITE sip:xxxxx@xxxxxx SIP/2.0 Call-ID: [email protected] CSeq: 1 INVITE ........ ....... ...... Content-Type: multipart/mixed; *boundary="----=_Part_5_606947969.1398418702748"* Via: SIP/2.0/TCP 192.168.0.128:5180 ;branch=z9hG4bKc50f33ae-5514-415d-a7d6-d4ac4f14e76d_0415af62_1375448837674952 Content-Length: 841 ------=_Part_5_606947969.1398418702748 Content-Type: application/sdp Content-Length: 294 v=0 o=- 3344 3344 IN IP4 192.168.0.128 s=- c=IN IP4 192.168.0.128 t=0 0 m=message 2855 TCP/MSRP * a=path:msrp://192.168.0.128:2855/9lEkrP9Tf1;tcp a=accept-types:message/cpim application/im-iscomposing+xml a=accept-wrapped-types:text/plain message/imdn+xml a=msrp-acm a=setup:actpass ........ ....... *Invite sent from the CW to the AS:* INVITE sip:xxxxx@xxxxxx SIP/2.0 Call-ID: [email protected] CSeq: 1 INVITE ........ ....... ...... P-Asserted-Identity: <sip:xxxx@xxxxxxx> Content-Type: multipart/mixed; *boundary=----%3d_Part_5_606947969.1398418702748* Content-Length: 948 ------=_Part_5_606947969.1398418702748 Content-Type: application/sdp Content-Length: 294 Content-Type: application/sdp Content-Length: 294 ....... ...... ...... Regards, Sergio _______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/listinfo/clearwater
