Hello, I can see that the function pjsip_rx_data_clone was added end 2012. And it is a new pjsip API function. https://trac.pjsip.org/repos/ticket/1590 I think there is not documentation for this function yet? Unless there is a later doc update I have missed. I think there are not tests for this function? It looks like there is a problem with this function if it tries to copy/clone a message with multipart data in it. I am surprised it doesn't work as the message is a quite simple multipart: just 2 parts. I'm looking more into pjsip_rx_data_clone and multipart_data_clone. If anyone can comment I would appreciate it. Thanks & Best Regards, James. >>> The INVITE from clearwater bono log: (with some munging of host and >>> phone numbers) >>> >>> 04-02-2014 12:45:17.017 Verbose pjsip: tcps0x7f73b40d TCP connection >>> closed >>> 04-02-2014 12:45:17.017 Verbose pjsip: tcps0x7f73b40d TCP transport >>> destroyed with reason 70016: End of file (PJ_EEOF) >>> 04-02-2014 12:45:26.726 Verbose stack.cpp:200: RX 2169 bytes Request msg >>> INVITE/cseq=1 (rdata0x7f73b4092a98) from UDP 88.888.888.888:16399: >>> --start msg-- >>> >>> INVITE sip:+888888888888 at openims.test;user=phone SIP/2.0^M >>> Call-ID: 7rn78PURzC at 888.888.888.888^M >>> CSeq: 1 INVITE^M >>> From: <sip:+888889999999@xxxxxxxxxxxx>;tag=Bsn78PUSzC^M >>> To: <sip:+888888888888 at openims.test;user=phone>^M >>> Via: SIP/2.0/UDP >>> 888.888.888.888:5060;branch=z9hG4bK89c6df1ba8b54f300f0400b952d16259353036;rport^M >>> Max-Forwards: 70^M >>> Contact: <sip:+888889999999 at 888.888.888.888 >>> :5060;transport=udp>;+sip.instance="<urn:uuid:ee388fc4-f9e1-3dd6-90d8-48c2947787fb>";+g.oma.sip-im;+g.3gpp.iari-ref="urn%3Aurn-7%3A3gpp-application.ims.iari.rcs.geopush"^M >>> Accept-Contact: >>> *;+g.oma.sip-im;+g.3gpp.iari-ref="urn%3Aurn-7%3A3gpp-application.ims.iari.rcs.geopush"^M >>> Allow: INVITE,UPDATE,ACK,CANCEL,BYE,NOTIFY,OPTIONS,MESSAGE,REFER^M >>> Route: >>> <sip:888.88.88.88:5060;transport=udp;lr>,<sip:888-88-88-88:5054;transport=tcp;lr;orig>^M >>> P-Preferred-Identity: <sip:+888889999999 at openims.test>^M >>> User-Agent: IM-client/OMA1.0 Neusoft-Silta-RCSe-client/2.0.1344.33_TR^M >>> Content-Type: multipart/mixed;boundary=boundary1^M >>> Subject: Amazeballs or ?^M >>> Contribution-ID: d9d5ea4a46d8e0180393a3e7cd0cdda2^M >>> Proxy-Authorization: Digest username="+888889999999 at openims.test >>> ",uri="sip:+888888888888 at openims.test >>> ;user=phone",algorithm=MD5,realm="openims.test",nc=00000002,nonce="6728054437e0f19d",response="f7b30628a50eff6cfff1cbf4441b25cb",cnonce="1391517852372",qop=auth^M >>> Content-Length: 791^M >>> ^M >>> --boundary1^M >>> Content-Type: application/sdp^M >>> Content-Length: 343^M >>> ^M >>> v=0^M >>> o=- 3600506724 3600506724 IN IP4 888.888.888.888^M >>> s=-^M >>> c=IN IP4 888.888.888.888^M >>> t=0 0^M >>> m=message 9 TCP/MSRP *^M >>> a=path:msrp://888.888.888.888:7777/1391517924073;tcp^M >>> a=setup:active^M >>> a=accept-types:message/cpim application/im-iscomposing+xml^M >>> a=accept-wrapped-types:text/plain message/imdn+xml >>> application/rcspushlocation+xml^M >>> a=sendrecv^M >>> ^M >>> --boundary1^M >>> Content-Type: message/cpim^M >>> Content-Length: 300^M >>> ^M >>> From: <sip:anonymous@anonymous.invalid>^M >>> To: <sip:anonymous at anonymous.invalid>^M >>> NS: imdn <urn:ietf:params:imdn>^M >>> imdn.Message-ID: Msg6rn78PUQzC^M >>> DateTime: 2014-02-04T12:45:24.000Z^M >>> imdn.Disposition-Notification: positive-delivery, display^M >>> ^M >>> Content-type: text/plain; charset=utf-8^M >>> ^M >>> Amazeballs or ?^M >>> --boundary1-- >>> >>> >>> >> > -- <http://openmindnetworks.com/mobile-operators> <http://www.linkedin.com/company/76647?trk=fc_badge> openmindnetworks.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20140210/dda3a5f1/attachment-0001.html>
