[asterisk-bugs] [JIRA] (ASTERISK-24609) Features DTMF parking to an existing custom parkinglot with no 'parkext' defined results in silent failure

[Rusty Newton (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-24609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rusty Newton updated ASTERISK-24609:
------------------------------------

    Description: 
h1. Scenario

A custom parkinglot exists in res_parking.conf configuration as follows:
{noformat}
[acustomlot]
;parkext = 800
context => acustomlot_park
parkpos => 801-850
findslot => next
{noformat}

In features.conf the parkcall feature is activated:
{noformat}
[featuremap]
parkcall => #72 
{noformat}

h1. The failure

* SIP Channel A dials Channel B, using the 'Kk' Dial options
* After the call is established, the user for Channel A dials the parkcall feature code.
* Nothing happens, the call remains established, but the call is not parked. No parking related debug is seen with verbose or debug channels up to 5.

h1. What do we do!

Obviously this only seen with a user configuration error, but the issue is there was no debug to indicate what was going on. Fortunately someone else helped me spot the missing parkext option. We should probably have a warning or notice saying that we can't find the park extension to dial even though the feature code is detected. I know the feature code is detected because *if I comment out the custom parking lot completely* then we do see debug as follows:
{noformat}
[Dec 11 16:45:29] WARNING[25860][C-00000002]: parking/parking_bridge_features.c:492 parking_park_call: Cannot Park SIP/6001-00000004: lot acustomlot unknown
{noformat}

  was:
h1. Scenario

A custom parkinglot exists in res_parking.conf configuration as follows:
{noformat}
[acustomlot]
;parkext = 800
context => acustomlot_park
parkpos => 801-850
findslot => next
{noformat}

In features.conf the parkcall feature is activated:
{noformat}
[featuremap]
parkcall => #72 
{noformat}

h1. The failure

* SIP Channel A dials Channel B, using the 'Kk' Dial options
* After the call is established, the user for Channel A dials the parkcall feature code.
* Nothing happens, the call remains established, but the call is not parked. No parking related debug is seen with verbose or debug channels up to 5.

h1. What do we do!

Obviously this is a configuration error. The issue is there was no debug to indicate what was going on. Fortunately someone else helped me spot the missing parkext option. We should probably have a warning or notice saying that we can't find the park extension to dial even though the feature code is detected. I know the feature code is detected because *if I comment out the custom parking lot completely* then we do see debug as follows:
{noformat}
[Dec 11 16:45:29] WARNING[25860][C-00000002]: parking/parking_bridge_features.c:492 parking_park_call: Cannot Park SIP/6001-00000004: lot acustomlot unknown
{noformat}


> Features DTMF parking to an existing custom parkinglot with no 'parkext' defined results in silent failure
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-24609
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24609
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/General, Features/Parking, Resources/res_parking
>    Affects Versions: SVN, 13.0.2
>         Environment: SVN-branch-13-r429379
>            Reporter: Rusty Newton
>            Severity: Minor
>
> h1. Scenario
> A custom parkinglot exists in res_parking.conf configuration as follows:
> {noformat}
> [acustomlot]
> ;parkext = 800
> context => acustomlot_park
> parkpos => 801-850
> findslot => next
> {noformat}
> In features.conf the parkcall feature is activated:
> {noformat}
> [featuremap]
> parkcall => #72 
> {noformat}
> h1. The failure
> * SIP Channel A dials Channel B, using the 'Kk' Dial options
> * After the call is established, the user for Channel A dials the parkcall feature code.
> * Nothing happens, the call remains established, but the call is not parked. No parking related debug is seen with verbose or debug channels up to 5.
> h1. What do we do!
> Obviously this only seen with a user configuration error, but the issue is there was no debug to indicate what was going on. Fortunately someone else helped me spot the missing parkext option. We should probably have a warning or notice saying that we can't find the park extension to dial even though the feature code is detected. I know the feature code is detected because *if I comment out the custom parking lot completely* then we do see debug as follows:
> {noformat}
> [Dec 11 16:45:29] WARNING[25860][C-00000002]: parking/parking_bridge_features.c:492 parking_park_call: Cannot Park SIP/6001-00000004: lot acustomlot unknown
> {noformat}



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