reSIProcate

Mailing Lists

Source Code

< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index Next in Thread >

Re: [reSIProcate-users] Does resip support pidf - rpid in message body?

How are you sending this NOTIFY?

Best regards,
Byron Campen


Hi,

 

I have observed a strange behavior with pidf message body in Notify.

I’m thankful for any kind of help to resolve the issue.

 

From X-Lite soft phone, I’m receiving a PUBLISH method with state as pidf – rpid. For simple test, I’m using the same Content * reference to send in Notify. So, the same state received shall be sent in NOTIFY message.

However, in Notify, the rpid part is missing !!!

 

Did I miss any thing to make this work?

Note: I have added the Mime application/pidf+xml to the master profile for both Publish and Notify methods.

 

Thanks in advance.

 

Regards,

Krishna

 

----------------------

PUBLISH sip:46001@xxxxxxxxxxxxxx SIP/2.0^M

Via: SIP/2.0/UDP 172.16.58.216:50696;branch=z9hG4bK-d87543-ad54e4652f0b1905-1--d87543-^M

Max-Forwards: 70^M

Contact: <sip:46001@xxxxxxxxxxxxx:50696>^M

To: "46001"<sip:46001@xxxxxxxxxxxxxx>^M

From: "46001"<sip:46001@xxxxxxxxxxxxxx>;tag=db040169^M

Call-ID: ODc5OTBkZGZjNzg5ZTc3YTJiYTI1YzVjMjBiZTQzYmY.^M

CSeq: 2 PUBLISH^M

Expires: 3600^M

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO^M

Content-Type: application/pidf+xml^M

SIP-If-Match: ·®^\Ò^R<8b>À^A^M

Supported: timer^M

User-Agent: X-Lite release 1006e stamp 34025^M

Event: presence^M

Content-Length: 444^M

^M

<?xml version='1.0' encoding='UTF-8'?><presence xmlns='urn:ietf:params:xml:ns:pidf' xmlns:dm='urn:ietf:params:

xml:ns:pidf:data-model' xmlns:rpid='urn:ietf:params:xml:ns:pidf:rpid' xmlns:c='urn:ietf:params:xml:ns:pidf:cip

id' entity='pres:46001@xxxxxxxxxxxxxx'><tuple id='t5440610b'><status><basic>open</basic></status></tuple><dm:p

erson id='p4400c50b'><rpid:activities><rpid:busy/></rpid:activities><dm:note>Busy</dm:note></dm:person></prese

nce>

----------------------

 

NOTIFY sip:46002@xxxxxxxxxxxxx:55412 SIP/2.0^M

Via: SIP/2.0/UDP 192.168.27.114:5060;branch=z9hG4bK-d87543-2106445a15c29219-1--d87543-;rport^M

Max-Forwards: 70^M

Contact: <sip:46001@xxxxxxxxxxxxxx>^M

To: "46002"<sip:46002@xxxxxxxxxxxxxx>;tag=c174c90c^M

From: <sip:46001@xxxxxxxxxxxxxx>;tag=f088ec21^M

Call-ID: N2U2NzVlODE2NjdjMmM3MTA0ZDhmOGFmOTViZjhjZmM.^M

CSeq: 6 NOTIFY^M

Content-Type: application/pidf+xml^M

User-Agent: MX-ONE/Resiprocate^M

Subscription-State: active^M

Event: presence^M

Content-Length: 229^M

^M

<?xml version="1.0" encoding="UTF-8"?>^M

<presence xmlns="urn:ietf:params:xml:ns:pidf"^M

          entity="pres:46001@xxxxxxxxxxxxxx">^M

  <tuple id="t5440610b" >^M

     <status><basic>open</basic></status>^M

  </tuple>^M

</presence>^M

 


The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments.

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.

www.wipro.com
_______________________________________________
resiprocate-users mailing list

Attachment: smime.p7s
Description: S/MIME cryptographic signature