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

[Giovanni Di Cicco (JIRA)]

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

Giovanni Di Cicco commented on ASTERISK-13145:
----------------------------------------------

Hi, I have BLF Pick-Up working but it seems that when I try and pick up a ringing extension within a Ring Group I get the following error:

[2014-09-07 12:44:16] NOTICE[5266][C-00000009]: app_directed_pickup.c:302 pickup_exec: No target channel found for 107 at from-internal.

[2014-09-07 12:44:16] NOTICE[5266][C-00000009]: app_directed_pickup.c:302 pickup_exec: No target channel found for 107 at PICKUPMARK

I can successfully pick up that extension when it is ringing alone i.e. outside the ring group:

[2014-09-07 12:45:00] NOTICE[5268][C-0000000b]: app_directed_pickup.c:203 pickup_by_exten: SIP/107-00000012 pickup by SIP/101-00000013

Here is the code I am using:

[app-blfpickup]
include => app-pickup-custom
exten => _[x]-cisco-serviceuri-blfpickup-.,1,Macro(user-callerid,)
exten => _[x]-cisco-serviceuri-blfpickup-.,n,Set(PICKUP_EXTEN=${AMPUSER})
exten => _[x]-cisco-serviceuri-blfpickup-.,n,Pickup(${EXTEN:29}&${EXTEN:29}@PICKUPMARK)
exten => _[x]-cisco-serviceuri-blfpickup-.,n,Hangup

; Strip the x-cisco-serviceuri- prefix
exten => _[x]-cisco-serviceuri-.,1,Goto(${EXTEN:19},1)

Apologies if I have missed something obvious here and thanks for your time


> [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.11.0.patch, gareth-11.2.1-dndbusy.patch, gareth-1.8.14.0.patch, gareth-documentation-url.txt, 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 was sent by Atlassian JIRA
(v6.2#6252)