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

[BastianM (JIRA)]

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

BastianM commented on ASTERISK-13145:
-------------------------------------

Hi Gareth,

Your latest patch has been incredibly useful. The patch in combination with the instructions from Sean Simpson were invaluable in getting several 9971's up and running here. My setup is:

- Latest FreePBX: (asterisk 11.0.1 and freepbx 2.11)  http://downloads.freepbxdistro.org/ISO/FreePBX-1.1100.211.63-x86_64-Full-1353367890.iso
- Your 11.0.1 patch applied.
- Custom device states enabled
- edits to extensions_custom.conf as per here: http://pastebin.com/1wjrCpTP based on your comment from Nov 2.

I have a couple of issues. 

The first is surely related to the new presence system in Asterisk 11. with the extensions_custom.conf I've attached I'm getting the following errors:

[2012-11-27 15:08:47] WARNING[19951][C-00000001] func_presencestate.c: Unknown presence state value NOT_INUSE
[2012-11-27 15:08:47] WARNING[19951][C-00000001] func_presencestate.c: Invalid arguments to PRESENCE_STATE

If I change CustomPresence back to Custom in lines 17 and 22 I get:

[2012-11-27 15:27:26] WARNING[20060][C-00000001] func_presencestate.c: The PRESENCE_STATE function can only set CustomPresence: presence providers.

What's missing is the DND animation and the status light. 

The second issue is that video is not working. Before giving any more details on this problem, can you let me know if the 11.0.1 patch was video enabled please?

I'd be really grateful if you can help me out.

Kind regards,

Bastian 



                
> [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.0.1.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, 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
For more information on JIRA, see: http://www.atlassian.com/software/jira