Re: [reSIProcate-users] Multipart mixed message not getting parsed

[Nihar Junotele <nihar@xxxxxxxxxxxx>]

Sorry Scott, I am getting following error now

INFO | 20150429-112459.688 |  | RESIP | 1077785408 | SipMessage.cxx:925 | 57 extra bytes after body. Ignoring these bytes.
INFO | 20150429-112459.688 |  | RESIP:DUM | 1077785408 | DialogUsageManager.cxx:1591 | Got: SipReq:  INVITE 31879150000007@192.168.10.180:5060 tid=003c76c552f46557ed7 cseq=6054 INVITE contact=9142000044@192.168.10.180:5065 / 6054 from(wire)
UAS(INVITE): testAppDialogSet: created.
UAS(INVITE): testAppDialogSet: UAS UserProfile requested for msg: SipReq:  INVITE 31879150000007@192.168.10.180:5060 tid=003c76c552f46557ed7 cseq=6054 INVITE contact=9142000044@192.168.10.180:5065 / 6054 from(wire)
UAS(INVITE): testAppDialog: created.
ERR | 20150429-112459.689 |  | RESIP | 1077785408 | Helper.cxx:2146 | ParseException
../../rutil/ParseBuffer.hxx:226, Parse failed unexpected eof in context: Contents
--zx-msce
Content-Type: application/sdp

v=0
o=ZTE-MSCe 14194 14194 IN IP4 192.168.10.180
s=Phone Call via ZTE MSCe
c=IN IP4 ...
t=0 0
m=audio 7882/1 RTP/AVP 96 97 8 12 0 99 100 18 4 98
a=rtpmap:96 EVRC0/8000
a=rtpmap:97 EVRC/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:12 QCELP/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:99 QCELP8K/8000
a=rtpmap:100 IWF/8000
a=rtpmap:18 G729/8000
a=rtpmap:4 G723/8000
a=rtpmap:98 TELEPHONE-EVENT/8000
a=sendrecv

--zx-msce
Content-Type: application/ISUP; base=chn; version=chn
Content-Disposition: signal; handling=optional

01 00 00 00 00 02 0b 09 03 10 13 78 19 0
                                        ^

I am constructing SIP packet as follows for local testing which I actually got from MSC:

<send retrans="500">
<![CDATA[

INVITE sip:31879150000007@192.168.10.180:5060;transport=UDP;user=phone SIP/2.0
Via: SIP/2.0/UDP 192.168.10.180:5065;branch=z9hG4bK003c76c552f46557ed7
To: <sip:31879150000007@192.168.10.180;user=phone>
From: <sip:9142000044@192.168.10.180;user=phone>;tag=003-57978710321b555210bec-25b57c32
Call-ID: 30384-003010258vx@...
CSeq: 6054 INVITE
Contact: <sip:9142000044@192.168.10.180:5065>
Accept: application/sdp,multipart/mixed,application/dtmf,application/dtmf-relay
Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,INFO,REGISTER,PRACK,UPDATE,REFER,NOTIFY
Max-Forwards: 70
MIME-Version: 1.0
Supported: 100rel
User-Agent: ZTE-MSCe
P-Asserted-Identity: <sip:9142000044@..;user=phone>
Content-Type: multipart/mixed;boundary=zx-msce
Content-Length: 619

--zx-msce
Content-Type: application/sdp

v=0
o=ZTE-MSCe 14194 14194 IN IP4 192.168.10.180
s=Phone Call via ZTE MSCe
c=IN IP4 192.168.10.180
t=0 0
m=audio 7882/1 RTP/AVP 96 97 8 12 0 99 100 18 4 98
a=rtpmap:96 EVRC0/8000
a=rtpmap:97 EVRC/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:12 QCELP/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:99 QCELP8K/8000
a=rtpmap:100 IWF/8000
a=rtpmap:18 G729/8000
a=rtpmap:4 G723/8000
a=rtpmap:98 TELEPHONE-EVENT/8000
a=sendrecv

--zx-msce
Content-Type: application/ISUP; base=chn; version=chn
Content-Disposition: signal; handling=optional

01 00 00 00 00 02 0b 09 03 10 13 78 19 05 00 00 70 08 83 11 19 24 00 00 44 0f 00

--zx-msce--

]]>
</send>

Can you please help out what's wrong with the packet I am sending?

 Regards,

 Nihar

On Fri, Apr 24, 2015 at 7:12 PM, Scott Godin <sgodin@xxxxxxxxxxxxxxx> wrote:

You need to tell dum that you will be supporting this body type via the MasterProfile with something like:

m_MasterProfile->addSupportedMimeType(INVITE, Mime("multipart", "mixed")); 

Scott

On Fri, Apr 24, 2015 at 8:52 AM, Nihar Junotele <nihar@xxxxxxxxxxxx> wrote:

Hi,

I am using resiprocate 1.6.

I got an INVITE with following SDP:

Content-Type: multipart/mixed;boundary=zx-msce
Content-Length: 619

--zx-msce
Content-Type: application/sdp
v=0
..........................
--zx-msce
Content-Type: application/ISUP; base=chn; version=chn
Content-Disposition: signal; handling=optional
01 00 00 00
00 02 0b 09 03 10 13 78 19 05 00 00 70
08 83 11 19 24 00 00 44 0f 00
--zx-msce--

Resiprocate cannot parse this SDP. I am getting following error

INFO | 20150424-092303.447 |  | RESIP | 1077785408 | SipMessage.cxx:925 | 53 extra bytes after body. Ignoring these bytes.
INFO | 20150424-092303.447 |  | RESIP:DUM | 1077785408 | DialogUsageManager.cxx:1591 | Got: SipReq:  INVITE 31879150000007@192.168.10.180:5060 tid=003c76c552f46557ed7 cseq=6054 INVITE contact=9142000044@192.168.10.180:5065 / 6054 from(wire)
INFO | 20150424-092303.447 |  | RESIP:DUM | 1077785408 | DialogUsageManager.cxx:1831 | Received an unsupported mime type: multipart/mixed;boundary=zx-msce for SipReq:  INVITE 31879150000007@192.168.10.180:5060 tid=003c76c552f46557ed7 cseq=6054 INVITE contact=9142000044@192.168.10.180:5065 / 6054 from(wire)
INFO | 20150424-092303.940 |  | RESIP | 1077785408 | SipMessage.cxx:925 | 53 extra bytes after body. Ignoring these bytes.
will try to reconnect with hostmgr!!!
INFO | 20150424-092304.946 |  | RESIP | 1077785408 | SipMessage.cxx:925 | 53 extra bytes after body. Ignoring these bytes.
will try to reconnect with hostmgr!!!
register_HostMgr from reconnect attempt!!!
JT_libcomm::register_HostMgr sent PING message to Host Manager
INFO | 20150424-092306.956 |  | RESIP | 1077785408 | SipMessage.cxx:925 | 53 extra bytes after body. Ignoring these bytes.
will try to reconnect with hostmgr!!!
will try to reconnect with hostmgr!!!
INFO | 20150424-092310.977 |  | RESIP | 1077785408 | SipMessage.cxx:925 | 53 extra bytes after body. Ignoring these bytes.

Can anyone please help me. Does resiprocate support Content-Type: multipart/mixed;boundary=zx-msce.?

If yes, please let me know how to add support for multipart.

 Regards,

 Nihar

JunoTele Solutions Private Limited, 
26/3, 38th Cross, 18th Main Road,
Jayanagar 4th 'T' Block,Bangalore - 560041
T/F: +91-78-46-99-88-77,
Email: 

nihar

@junotele.com

Disclaimer :
The information in this e-mail and any attachments is confidential and may be legally privileged. It is intended solely for the addressee(s). If you are not an intended recipient, please delete the message and any attachments and notify the sender immediately. Any use or disclosure of the contents of either is unauthorised and may be unlawful. JunoTele has taken every reasonable precaution to minimize this risk viruses, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment.

_______________________________________________
resiprocate-users mailing list
resiprocate-users@xxxxxxxxxxxxxxx
List Archive: http://list.resiprocate.org/archive/resiprocate-users/