Re: [reSIProcate-users] Publish - 415 Unsupported Media Type

["Scott Godin" <slgodin@xxxxxxxxxxxx>]

Did you register a server subscription handler with the correct event type with dum?

 

From: phanivenkata.krishna@xxxxxxxxx [mailto:phanivenkata.krishna@xxxxxxxxx]
Sent: Friday, July 20, 2007 5:02 AM
To: Scott Godin; resiprocate-users@xxxxxxxxxxxxxxxxxxxx
Subject: RE: [reSIProcate-users] Publish - 415 Unsupported Media Type

 

Thanks Scott, with this change I could receive Publish methods in my class.

I have another problem of sending Notify message when Publish is received.

 

I have my own class of ServerSubscription and ServerPublication to dum.

 

1. When I change the state of SIP client (to busy, offline etc), a Publish method is received and <MyPublishClass>::onUpdate() method is called.
2. Here I’m calling accept() and sends the response. When there is a state change, I shall Notify to all the subscribed users for this Agent.
3. I thought the accept() method shall invoke <MySubscribeClass>::onPublished(), but doesn’t happen.

Any problem with updateMatchingSubscriptions() where the condition fails?

4. Am I missing some thing here?

 

Please suggest me the correct way.

 

- Krishna

 

---

From: Scott Godin [mailto:slgodin@xxxxxxxxxxxx]
Sent: Thursday, July 19, 2007 9:26 PM
To: A.P.V. Krishna (WT01 - TES-Enterprise Networks); resiprocate-users@xxxxxxxxxxxxxxxxxxxx
Subject: RE: [reSIProcate-users] Publish - 415 Unsupported Media Type

 

Did you add application/pidf+xml to the supported Mime types of the MasterProfile?  See MasterProfile.hxx.  You also need to add a publication hander to DialogUsageManager (addClientPublicationHandler).

 

Scott

 

From: resiprocate-users-bounces@xxxxxxxxxxxxxxxxxxxx [mailto:resiprocate-users-bounces@xxxxxxxxxxxxxxxxxxxx] On Behalf Of phanivenkata.krishna@xxxxxxxxx
Sent: Thursday, July 19, 2007 10:48 AM
To: resiprocate-users@xxxxxxxxxxxxxxxxxxxx
Subject: [reSIProcate-users] Publish - 415 Unsupported Media Type

 

Hi,

 

I’m trying out the Presence functionality with resip stack (Resiprocate version: 1.0.2) and struck at handling Publish method. I have created my own Subscription and Publication handler classes to handle the respective call-back methods. I’m using X-Lite soft SIP client.

 

Xlite sends a Publish method when its state is changed. However, the response “415 Unsupported Media Type” is sent in return.

 

I felt that this message is returned from Stack itself before triggering the call-back method.

Also, how to send application/pidf+xml information in Notify message with user state etc?

 

Any information would be of great help.

Thanks in advance.

 

Regards,

Krishna

 

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

 

PUBLISH sip:46001@xxxxxxxxxxxxxx SIP/2.0

Via: SIP/2.0/UDP 172.16.58.216:38300;branch=z9hG4bK-d87543-7a4b8c31901a935f-1--d87543-

Max-Forwards: 70

Contact: <sip:46001@xxxxxxxxxxxxx:38300>

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

From: "46001"<sip:46001@xxxxxxxxxxxxxx>;tag=dd61654b

Call-ID: ZjIyMGVmMjc5MzJiYjdjYmEwNmEwYmIyNWNmMDYyZDA.

CSeq: 1 PUBLISH

Expires: 3600

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

Content-Type: application/pidf+xml

Supported: timer

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

Event: presence

Content-Length: 424

 

<?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:cipid' entity='pres:46001@xxxxxxxxxxxxxx'><tuple id='t791f641e'><status><basic>open</basic></status></tuple><dm:person id='p723f9e43'><rpid:activities><rpid:unknown/></rpid:activities></dm:person></presence>

 

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

 

SIP/2.0 415 Unsupported Media Type

Via: SIP/2.0/UDP 172.16.58.216:38300;branch=z9hG4bK-d87543-7a4b8c31901a935f-1--d87543-

To: "46001"<sip:46001@xxxxxxxxxxxxxx>;tag=61053e0d

From: "46001"<sip:46001@xxxxxxxxxxxxxx>;tag=dd61654b

Call-ID: ZjIyMGVmMjc5MzJiYjdjYmEwNmEwYmIyNWNmMDYyZDA.

CSeq: 1 PUBLISH

Content-Length: 0

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

 

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