[asterisk-bugs] [JIRA] (ASTERISK-13145) [patch] Presence subscription on Cisco SIP phone needs special Cisco-styled XML

[Darren Philips (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-13145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=215576#comment-215576 ] 

Darren Philips edited comment on ASTERISK-13145 at 2/24/14 5:02 AM:
--------------------------------------------------------------------

try setting the Video BW to something stupid,
don't use the latest firmware it does some weird things ( I use sip9971.9-3-4-24)
my sip_custom_post.conf looks like

[239](+)
cisco_usecallmanager=yes
dndbusy=yes
subscribe=131
subscribe=136
subscribe=150
 

Video is set in the sip_general_additional has

allow=alaw
allow=h263p
allow=h263
allow=h264
allow=h261
tcpenable=yes
videosupport=yes


if you want to use a working config from the provisioner use my git release ( currently pushing to main proivisioner git)
https://github.com/dazza76/Provisioner
I have added all of the cisco phones I can get my hands on 

                
      was (Author: darren76):
    try setting the Video BW to something stupid,
don't use the latest firmware it does some weird things ( I use)
my sip_custom_post.conf looks like

[239](+)
cisco_usecallmanager=yes
dndbusy=yes
subscribe=131
subscribe=136
subscribe=150
 

Video is set in the sip_general_additional has

allow=alaw
allow=h263p
allow=h263
allow=h264
allow=h261
tcpenable=yes
videosupport=yes


if you want to use a working config from the provisioner use my git release ( currently pushing to main proivisioner git)
https://github.com/dazza76/Provisioner
I have added all of the cisco phones I can get my hands on 

                  
> [patch] Presence subscription on Cisco SIP phone needs special Cisco-styled XML
> -------------------------------------------------------------------------------
>
>                 Key: ASTERISK-13145
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-13145
>             Project: Asterisk
>          Issue Type: New Feature
>          Components: Channels/chan_sip/NewFeature
>            Reporter: David McNett
>         Attachments: 01-btias.patch, 02-media-attrib-sdp.patch, 03-media-attrib-sdp-backport.patch, 04-imageattr.patch, 7965.xml, 8001 to 8003 and hangup.pcap, 8001 to 8003 and pickup then talk then hangup.pcap, asterisk-1.8.7.0-chan_sip.patch, backtrace.txt, Capture - CSO Presence - Lift and Replace Handset.pcap, Capture - CSO Presence - Ring between 2 monitored extensions.pcap, chan_sip.c_available_on-the-phone.patch, chan_sip.c_blf_available_on-the-phone.patch, chan_sip.c.patch, cisco-blf-asterisk.1.6.0.26.patch, cisco-blf-asterisk.1.6.2.13.patch, cisco-blf-asterisk.1.8.0.patch, core-ast115-sccp.tar.gz, gareth-10.6.0.patch, gareth-11.2.1-dndbusy.patch, gareth-11.7.0.patch, gareth-1.8.14.0.patch, gareth-featurepolicy.xml, gareth-mk-1.8.13.0.patch, gareth-softkeys.xml, gareth-softkeys.xml, memleak_astdb.patch, messages-1, Poly_reboot.log, rjw-11.4.0.patch, second-sip-trace-7941-9-1-1SR1.txt, sip-trace-7941-9-1-1SR1.txt, trace2.txt
>
>
> 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.
> {{****** ADDITIONAL INFORMATION ******}}
> I believe that this requires the Cisco phones be configured to use SIP TCP when connecting to Asterisk.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira