Summary:ASTERISK-06719: Park ignores the extension argument passed to it
Reporter:opsys (opsys)Labels:
Date Opened:2006-04-06 14:41:29Date Closed:2006-04-10 12:33:42
Versions:Frequency of
Description:If I dial 700 in a context that has parkedcalls included the Parking system offers me up the next available space.

However if I have say:
exten => 770X,Park(${EXTEN:1}
and I dial 703.

I expect the call to be parked on 703. So far on all versions tested, 1.2.1 - 1.2.5 the application simply ignores the argument sent and auto-parks.

The documentation states that you can specify a parking space. Or am I reading it wrong.

Comments:By: Andrey S Pankov (casper) 2006-04-06 17:25:56

As I read it you need to dial 'parkext' to park a call. It will be parked according to the strategy specified in 'findslot => next|first' on a slot in the 'parkpos' range.

Where do you see a bug here? Please use asterisk-users list or Digium forum or voip-info.org wiki to ask support questions. Thanks.

By: opsys (opsys) 2006-04-06 19:32:30

CASPER, I understand what you are saying, But this will cause confusion going forward.  The Doc below shows an exten argument. I understood it to mean that I could specify the parking space.

If this is not the case and NEVER will be, we should remove the (exten) from the Documentation.

-= Info about application 'Park' =-

Park yourself

Park(exten):Used to park yourself (typically in combination with a supervised
transfer to know the parking space). This application is always
registered internally and does not need to be explicitly added
into the dialplan, although you should include the 'parkedcalls'

By: Andrey S Pankov (casper) 2006-04-06 20:45:49

> and I dial 703.
or 7703?

I do not have enough time to look deeper into the code in park_exec, but it does process extension passed. Maybe a bug in how it does it...

By: opsys (opsys) 2006-04-06 20:53:33

I used 7703 so as to not 'confuse' the range in feature.conf.

So this should park in space 703.
exten=> 7703,1,Park(${EXTEN:1})

By: Andrey S Pankov (casper) 2006-04-10 12:10:13

Did you have some time to revise the code in park_exec()?

By: opsys (opsys) 2006-04-10 12:14:20

I was planning on working on it today. Did you see anything that I should be looking for? My asterisk flag was set to "NO WAY" by my wife this weekend so I was unable to even look at it. :-)

By: BJ Weschke (bweschke) 2006-04-10 12:27:24

It's not park_exec for Park(exten). It's park_call_exec which has the following comment:

       /* Data is unused at the moment but could contain a parking
          lot context eventually */

opsys is correct. The application description here is incorrect.

By: BJ Weschke (bweschke) 2006-04-10 12:33:41

app documentation error corrected.