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

Asterisk Bug Tracker noreply at bugs.digium.com
Sun Nov 14 22:50:07 CST 2010


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:                     confirmed
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:              2010-11-14 22:50 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.
====================================================================== 

---------------------------------------------------------------------- 
 (0128860) MKemner (reporter) - 2010-11-14 22:50
 https://issues.asterisk.org/view.php?id=13996#c128860 
---------------------------------------------------------------------- 
Patch for 1.6.2.13 uploaded.  Note that 1.6.2.14 has changed again so this
will not patch cleanly.  

I also have a patch for 1.6.2.14 (it's only a very minor change) but am
unable to do any testing on this right now as I am running 1.8 so can not
guarantee on 1.6.2.14 it will compile or run.

Also, I made a change to damage's patch to allow for an extension that is
busy AND ringing.  In my patch it treats it the same as "busy" however on
my local system I actually replace  e:on-the-phone with ce:dnd for lack of
a better option on the Cisco phones themselves. This means the light stays
red, but I get a little cross to say this extension is also ringing.

As this is not the "right way" to do things, the patch I have uploaded
just uses "e:on-the-phone" :) - you are free to change this on line 41 of
the patch. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-11-14 22:50 MKemner        Note Added: 0128860                          
======================================================================




More information about the asterisk-bugs mailing list