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

[Denis Kulikov (JIRA)]

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

Denis Kulikov edited comment on ASTERISK-13145 at 9/1/13 2:34 AM:
------------------------------------------------------------------

I use chan_sccp for some devices and after patching my 11.5.0 installation on calls between SCCP devices got:
Aug 31 22:59:07 asterisk kernel: asterisk[11463]: segfault at ee ip 000000000048bfc0 sp 00007f943b349758 error 4 in asterisk[400000+203000]
SIP->SCCP device call:
Aug 31 23:03:56 asterisk kernel: asterisk[11575]: segfault at 10 ip 00007fc15b1960ac sp 00007fc0b76acb10 error 4 in libc-2.12.so[7fc15b14e000+18a000]

With rjw patch and 11.4.0 - same crashes:
Sep 1 18:30:19 asterisk kernel: asterisk[20450]: segfault at 10 ip 00007f109581f0ac sp 00007f1035e66b10 error 4 in libc-2.12.so[7f10957d7000+18a000]
Sep 1 18:31:08 asterisk kernel: asterisk[20520]: segfault at ee ip 000000000048bfc0 sp 00007f2f4d2ad758 error 4 in asterisk[400000+203000]

Can anyone help? 
What additional information needed?

                
      was (Author: coobic):
    I`m use chan_sccp for some devices and after patching my 11.5.0 installation on calls between SCCP devices i`m got:
Aug 31 22:59:07 asterisk kernel: asterisk[11463]: segfault at ee ip 000000000048bfc0 sp 00007f943b349758 error 4 in asterisk[400000+203000]
SIP->SCCP device call:
Aug 31 23:03:56 asterisk kernel: asterisk[11575]: segfault at 10 ip 00007fc15b1960ac sp 00007fc0b76acb10 error 4 in libc-2.12.so[7fc15b14e000+18a000]

Can anyone help? 
What additional information needed?

                  
> [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, gareth-10.6.0.patch, gareth-11.2.1-dndbusy.patch, gareth-11.5.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