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

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13996 
====================================================================== 
Reported By:                Nugget
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   13996
Category:                   Channels/chan_sip/Subscriptions
Reproducibility:            always
Severity:                   feature
Priority:                   normal
Status:                     confirmed
Asterisk Version:           1.6.0.1 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2008-11-30 15:13 CST
Last Modified:              2009-02-26 03:33 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.
====================================================================== 

---------------------------------------------------------------------- 
 (0100779) damage (reporter) - 2009-02-26 03:33
 http://bugs.digium.com/view.php?id=13996#c100779 
---------------------------------------------------------------------- 
I get crazy with that stuff :-(

If I add the whole XML from the trace captured by jbrookes I get:

-------------------------------------------------------------------------------
NOT 10:28:46.766551 JVM: -XML| unknown element or attribute name
("sc:servcaps") (line=14)
NOT 10:28:46.767499 JVM: -XML| unknown element or attribute name
("timestamp") (line=18)
-------------------------------------------------------------------------------

Also ringing is not working but alerting is present in xml and log console
is not reporting any problems. May it stops parsing XML because of above
erros. But it is also not working if I remove the "sc:servcaps" and
"timestamp" tags.

-------------------------------------------------------------------------------
(dots at the beginning of a line are whitespaces)
-------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<presence entity="sip:*3 at 192.168.11.1" xmlns="urn:ietf:params:xml:ns:pidf"
xmlns:e="urn:ietf:params:xml:ns:pidf:status:rpid"
xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model"
xmlns:ce="urn:cisco:params:xml:ns:pidf:rpid"
xmlns:sc="urn:ietf:params:xml:ns:pidf:servcaps">
.<dm:person>
..<status>
...<basic>open</basic>
..</status>
..<e:activities>
...<ce:alerting/>
..</e:activities>
.</dm:person>
.<tuple id="*3">
..<status>
...<basic>open</basic>
...<e:activities>
....<ce:alerting/>
...</e:activities>
..</status>
..<sc:servcaps>
...<sc:audio>true</sc:audio>
..</sc:servcaps>
..<contact priority="1">sip:*3 at 192.168.11.1</contact>
..<timestamp>2009-02-26T09:27:33Z</timestamp>
.</tuple>
</presence>
-------------------------------------------------------------------------------


Any ideas? 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-02-26 03:33 damage         Note Added: 0100779                          
======================================================================