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

[Andrey Zharkov (JIRA)]

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

Andrey Zharkov commented on ASTERISK-13145:
-------------------------------------------

Hello.

I have problem with DeviceState in extension status.

I have configured 3 accounts on my cisco 7965 phone. Account 100 is on primary line and accounts 101 and 103 on lines 2 and 3. 
After first registration of phone i have no problems with DeviceState in extension status.
pbx*CLI> core show hints
Location                  Hints                           DeviceState     PresenceState   Watchers
100 at extensions            SIP/100,SIP/100                 Idle            Available       0 
101 at extensions            SIP/101,SIP/101                 Idle                            1 
103 at extensions            SIP/103,SIP/103                 Idle                            1 
199 at extensions            SIP/199,SIP/199                 Idle            Available       1 
4 hints registered

When i restart phone using "sip notify cisco-restart 100" the next thing happening.
pbx*CLI> sip notify cisco-restart 100
Sending NOTIFY of type 'cisco-restart' to '100'
    -- Unregistered SIP '100'
    -- Unregistered SIP '101'
    -- Unregistered SIP '103'
    -- Registered SIP '100' at 10.10.10.107:51972
    -- Registered SIP '101' at 10.10.10.107:51972
    -- Registered SIP '103' at 10.10.10.107:51972
pbx*CLI> core show hints
Location                  Hints                           DeviceState     PresenceState   Watchers
100 at extensions            SIP/100,SIP/100                 Idle            Available       0 
101 at extensions            SIP/101,SIP/101                 Unavailable                     1 
103 at extensions            SIP/103,SIP/103                 Unavailable                     1 
199 at extensions            SIP/199,SIP/199                 Idle            Available       1 
4 hints registered

The DeviceState of extensions 101 and 103 is Unavailable.
After second attempt of registration (600 seconds) account 100 correctly registers and extensions 101 and 103 changing to idle.
If i place a call to extensions 101 or 103 (before second registration) device state also changes to idle.
I found this problem on both versions 11.25.0 and 13.15.0
What could cause problem with DeviceState on extensions 101 and 103?
Thanks in advance

> [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
>            Assignee: Gareth Palmer
>         Attachments: 00_READ_ME_FIRST.txt, cisco-usecallmanager-11.25.0.patch, cisco-usecallmanager-13.15.0.patch, dialtemplate.xml, featurepolicy.xml, SEP000000000000.cnf.xml, softkeys.xml
>
>
> This patch provides support for Cisco 6900, 7900, 8800 and 9900 series phones using the SIP firmware.
> Available features are: Busy Lamp Field, Off Hook Notification, Call Forward, Do Not Disturb, Huntgroup Login, Call Park (Notify and Monitor), Server-Side Ad-Hoc Conference, Conference List, Kick and Mute/Unmute, Multi-Admin Conference, Multiple Lines via Bulk Register, Immediate Divert, Call Recording, Restart or Reset via CLI, Call Pickup Notification, Call Back, Join Calls, Mallicious Call ID, Quality Reporting Tool and Fail-over/Fail-back.
> Also included is Application Server Events used by non-USECALLMANAGER phones (Call Forward and Do Not Disturb only).
> *Important:* Read the documentation at [http://usecallmanager.nz] to see the additional configuration options required for the phones to operate correctly.



--
This message was sent by Atlassian JIRA
(v6.2#6252)