[asterisk-bugs] [Asterisk 0013996]: [patch] Presence subscription on Cisco SIP phone needs special Cisco-styled XML

Asterisk Bug Tracker noreply at bugs.digium.com
Mon Feb 14 19:30:45 CST 2011


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=13996 
====================================================================== 
Reported By:                Nugget
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   13996
Category:                   Channels/chan_sip/NewFeature
Reproducibility:            always
Severity:                   feature
Priority:                   normal
Status:                     ready for testing
Asterisk Version:           SVN 
JIRA:                       SWP-202 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2008-11-30 15:13 CST
Last Modified:              2011-02-14 19:30 CST
====================================================================== 
Summary:                    [patch] Presence subscription on Cisco SIP phone
needs special Cisco-styled XML
Description: 
Cisco phones appear to be unable to parse the existing PIDF XML being
generated by Asterisk for presence notification.  I've attached a patch
which produces well-formed (but incomplete) XML which will satisfy a Cisco
phone.  The patch as supplied will successfully render a "busy"
subscription, but does not send a subsequent "available" notification, so
presence detection only half works currently.

I suspect the next step might be to watch some CallManager SIP traffic to
identify precisely what XML tags the phone is expecting in order to
properly parse an available subscription, but I'm not in a position to do
that.  I'll continue to work with this, though, and perhaps may be able to
stumble upon the precise data the Cisco phone is looking for.
====================================================================== 

---------------------------------------------------------------------- 
 (0131946) kuj (reporter) - 2011-02-14 19:30
 https://issues.asterisk.org/view.php?id=13996#c131946 
---------------------------------------------------------------------- 
1.8.2.2.-patch works well on asterisk 1.8.2.3 build for showing "ringing"
and "in use" state of subscribed lines on a 7970, 9-1-1SR1. DND does seem
to get published, as the console reports "Extension Changed
<ext>[<context>] new state DoNotDisturb for Notify User <user>".

Two small issues (I'll have to do some debugging on these, but won't be
able to do so before the weekend at the earliest):
- if the Cisco subscriptions are lost (e.g. after restarting asterisk),
the phone doesn't re-subscribe, not even after a couple of hours. (Not sure
whether the phone doesn't renew the subscription, or if a renewal attempts
doesn't succeed.) Other phones (e.g. Polycom) do eventually renew their
subscriptions.
- the mapping of "DoNotDisturb" to presence state for subscribers using
xpidf+xml (here: Polycom 500) seems to be to "online" state. When the Cisco
endpoint goes to DND, the Polycom is sent a presence update with "<status
status="open" /> <msnsubstatus substatus="online" />" 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-02-14 19:30 kuj            Note Added: 0131946                          
======================================================================




More information about the asterisk-bugs mailing list