| < Previous by Date | Date Index | Next by Date > |
| < Previous in Thread | Thread Index | Next in Thread > |
|
Subscriptions are added to the map in DialogUsageManager as they
are created. Besides matching event types, the AOR in the request URI of
the subscriptions must match the AOR in the request URI of the publish in order
for updateMatchingSubscriptions to work. I can’t think of what else you might be missing. You
could try examining/posting a DEBUG level log, or try stepping through the code
in a debug session in order to understand why things are not working. Scott From: phanivenkata.krishna@xxxxxxxxx
[mailto:phanivenkata.krishna@xxxxxxxxx] Yes, i have registered (my own) both ServerSubscription and
ServerPublication with event type as "presence". I'm able to receive SUBSCRIBE message from SIP client and send a
NOTIFY for the same. However, when a PUBLISH message is received only 200 OK is sent
but not a Notify. The reason i found was the call back method OnPublished() of
ServerSubscription is not called. In updateMatchingSubscriptions(), there is a check to find the
existing ServerSubscriptions. I'm not sure when these subscriptions are added
to the map mServerSubscriptions. Do you require any other specific information? - Krishna From: Scott
Godin [mailto:slgodin@xxxxxxxxxxxx] Did you register a server subscription handler with the correct
event type with dum? From: phanivenkata.krishna@xxxxxxxxx
[mailto:phanivenkata.krishna@xxxxxxxxx] 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.
Any
problem with updateMatchingSubscriptions() where the condition fails?
Please suggest me the correct way. - Krishna From: Scott Godin [mailto:slgodin@xxxxxxxxxxxx] 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 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
|