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

Tue Aug 4 11:30:33 CDT 2015

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

Ben Hughes edited comment on ASTERISK-13145 at 8/4/15 11:29 AM:
----------------------------------------------------------------

Sorry to be a pain but i'm just wondering if you could shed some light on the Park function? 

I'm running the patch under a FreePBX system and so far have managed to work out every associated problem with adding it onto the FreePBX generated dialplan apart from this, the document has been a great help!

I'm running the normal freepbx parking module and I have it configured that when a call timeouts back to the original parking extension it prepending to the callerid which parking slot it has come from. Now when I do a transfer to the parking extension without using the park key all is well and the call will timeout back to the parking extension with the prepended callerid, if I use the Park button then it will call the parking extension straight back rather than going through the additional dialplan to alter the callerid.

The bit I can't work out is that making a call to the parking extension is only calling Park() just as the dialplan does for an XML park command but the timeout logic seems to be different and I can only assume this is due to how the patch handles the XML request? Or is it purely based on the dialplan and i'm missing some magic freepbx does somewhere.

When I park the call I can see that the logged extension to timeout to is different between the two method, a transfer to the parking extension will display that it will timeout back to s at from-internal (which doesn't really seem to exist hence I think i'm missing something). Whereas the park button will show going back to whichever extension parked the call @from-internal hence bypassing the cid alterations.

Sorry to pollute with this but i've spent a few days on and off and not really got any closer.

edit: Just to add if I do a directed blf park on a line key it seems to work as just transferring to the parking extension.

was (Author: bmh.01):
Sorry to be a pain but i'm just wondering if you could shed some light on the Park function? 

I'm running the patch under a FreePBX system and so far have managed to work out every associated problem with adding it onto the FreePBX generated dialplan apart from this, the document has been a great help!

I'm running the normal freepbx parking module and I have it configured that when a call timeouts back to the original parking extension it prepending to the callerid which parking slot it has come from. Now when I do a transfer to the parking extension without using the park key all is well and the call will timeout back to the parking extension with the prepended callerid, if I use the Park button then it will call the parking extension straight back rather than going through the additional dialplan to alter the callerid.

The bit I can't work out is that making a call to the parking extension is only calling Park() just as the dialplan does for an XML park command but the timeout logic seems to be different and I can only assume this is due to how the patch handles the XML request? Or is it purely based on the dialplan and i'm missing some magic freepbx does somewhere.

When I park the call I can see that the logged extension to timeout to is different between the two method, a transfer to the parking extension will display that it will timeout back to s at from-internal (which doesn't really seem to exist hence I think i'm missing something). Whereas the park button will show going back to whichever extension parked the call @from-internal hence bypassing the cid alterations.

Sorry to pollute with this but i've spent a few days on and off and not really got any closer.

> [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.17.0.patch, cisco-usecallmanager-11.17.1.patch, cisco-usecallmanager-11.18.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 Back, Call Back, Join Calls, Mallicious Call ID and Quality Reporting Tool.
> Also included is Application Server Events used by non-USECALLMANAGER phones (Call Forward and Do Not Disturb only).
> *Important:* Read the documentation at http://docs.acsdata.co.nz/asterisk-cisco to see the additional configuration options required for the phones to operate correctly.

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