ValetParkCall

this does not work with valetparking, I have not heard back from a client that requested this in the new 1.6.1.x parking if it worked using the multi-parkinglot options. I had to set the options in local-extensions-tenant

exten => 701,hint,park:701@parkedcalls-tenant

he was supposed to setup his BLF and tell me if it lit up when a call parked.. i never heard back. I even emailed 3 times but still havent heard a peep.

Got the following when the call timed out, looks like the call tried to ring back to the default context. Any thoughts?

-- Stopped music on hold on SIP/Roseburg_Telica-ac0c8440
== Starting SIP/Roseburg_Telica-ac0c8440 at from-inside-RioNetworks,Roseburg_Telica,1 failed so falling back to exten 's'
== Starting SIP/Roseburg_Telica-ac0c8440 at from-inside-RioNetworks,s,1 still failed so falling back to context 'default'
[Jan 12 00:06:29] WARNING[23093]: pbx.c:2437 __ast_pbx_run: Channel 'SIP/Roseburg_Telica-ac0c8440' sent into invalid extension 's' in context 'default', but no invalid handler

thats not what that says

first it tried

Roseburg_Telica,1 failed so falling back to exten 's'

then it tried 'default'

something is wrong with the script you used as it identified your extension as

SIP/Roseburg_Telica

instead of SIP/somenumber-Roseburg_Telica

Ok, so if I blind transfer the call to park it will try to ring back the trunk rather then the extension I transferred it from. Makes sense now.

dependign on your script and the phone.. some phones dont blind transfer .. they call something known as a 'blonde transfer' a blind transfer but it really isnt. Only when BLINDTRANSFER gets set in channel variables does atrue blind transfer occur.

We have been experiencing a slightly different MoH experience.

We are using a multi-slot per tenant script.

1.Polycom phone receives call
2.Polycom presses transfer, MoH starts playing for the caller
3.Polycom dials feature code and hears the parking slot
4.Polycom completes the transfer, MoH stops for the caller

The caller is parked, but the music stops, the caller is wondering what is going on.

Is this the same with everyone?

-Matt

there is no MOH channel built into valetparking, the author refuses to answer email even when the email consists of 'here is the patch file so that it will continue to compile on asterisk 1.4.24 and higher'.

"there is no MOH channel built into valetparking"

That is too bad, seems to make it unusable. I think most callers will assume they have been hung up on when the music stops suddenly. The person doing the parking will need to explain to the caller not to hang up when the music stops.

-Matt

Looking at the source for Valet Park I see refernces to music on hold, i.e.

/* Start music on hold */
ast_moh_start(pu->chan, ast_strlen_zero(chan->musicclass) ? "default" : chan->musicclass, NULL)

Not a C programmer but will post to the asterisk users list to see if anyone found a workaround.

-Matt

do you have time to do testing?

in your musiconhold.conf file what exists under

[default] ?

Erik...heading out, will look it up when I get back this afternoon.

Thanks.

try the change i just made to your script and see if it makes any difference.

Updated the test box with the new script and it did not work.

I added a [default] section to the musiconhold.conf file, restarted asterisk and that solved it. It does not give any custom a tenant might have music but it is 100% better than silence.

I am glad one of us can read what that c code means!

-Matt

In reading this thread I'm not sure if valetparking is still the way to go or if asterisk now does what we want natively. I'm using the newest version of asterisk and was a little surprised to see references to need a third party app but this thread perhaps suggests that is no longer necessary?

depends on which branch you are running

I'm using the newest version (1.6.2.2). Straight up stock.

1.6.2.x is still bug ridden and not supported

1.6.2.2 , 1.6.1.14 , 1.6.0.22 are the exact same age.. so just saying 'newest' doesn't really mean shit.

1.4.29 is the newest version of the 1.4 branch (long term release)
1.6.0.22 is the newest version of the 1.6.0 branch
1.6.1.14 is the latest version of the 1.6.1 branch
1.6.2.2 is the latest version of the 1.6.2 branch

Well that may explain my other issue with "reload" as well.

The fact that 1.6.2.2 is essentially developmental isn't all that clear I guess from:

http://www.asterisk.org/asterisk-versions

What is considered the latest stable version then?

From earlier in the thread I'm guessing the parking stuff is only in the newer releases.

Ok, I think I've figured this versioning thing out in asterisk so we've installed 1.6.1.14 rather than 1.6.2.2 We're using 1.6.1.14 specifically to use the multi-tenant parking stuff.

This post has been very useful and I've got parking set up and it appears to be working. I'm able to park calls, they get hold music and the parked calls will time out after the specified times. What is not working is I'm not able to unpark the calls.

My understanding of the process is this:

To park a call you transfer the call to the parking extension. In my case I'm using 700. It parks the call on one of the parking spots and then returns the slot #. In my case it returns 701.

To unpark I thought you just dialed that extension 701 and it would pick the call back up. However, that is not working. Do I need to do more.

Here is what I've done:

In features.conf:

[parkinglot_tenant]
context => parkedcalls-tenant
parkext => 700
parkpos => 701-710
parkingtime => 180
findslot => next

In sip.conf:

Added "parkinglot=parkedcalls-tenant" to each of the extensions.

In extensions.include:

Added "include => parkedcalls-tenant" to [from-inside-redir-tenant]

Added "include => parkedcalls-tenant" to [from-inside-restricted-redir-tenant]

All that seems to work but I'm not sure what I'm missing to be able to then pick up the parked calls.

did you substitute _tenant_ with the actual tenant name?

you also need to add this to every extension

parkinglot=parkedcalls-tenant

this is done in the box so that the extra arguement populates in sip.conf for that extension

Yes I replaced tenant name with "tenant" for the purpose of this posting but in the config I have the tenant name.

I did add "parkinglot=parkedcalls-tenant" to each of the extensions for this tenant in sip.conf (see above).

I did not do this in the GUI though. I did it for the first one and then manually added it for the others.

That part I think is working because I see:

-- Added extension '700' priority 1 to parkedcalls-tenant (0xb620a430)

for each of the extensions.

Also:

-- Including context 'parkedcalls-tenant' in context 'from-inside-restricted-redir-tenant'
-- Including context 'parkedcalls-tenant' in context 'from-inside-redir-tenant'

I can clearly see the parked call in the right place:

voice*CLI> parkedcalls show
Num Channel (Context Extension Pri ) Timeout
*** Parking lot: default
701 SIP/101-tenant-0000000d (from-inside-redir-tenant s 1 ) 174s
*** Parking lot: parkinglot_ tenant
---
1 parked call in total.

I just can't get them back out of parking once they are in there.

i think you meant to say that you can clearly see its NOT parked in the right place.. because its in the lot labled 'default' not the lot labled parkinglot_tenant

when you park the call the CLI will say .. parked blah blah in 701@parkinglot_tenant

change
parkinglot=parkedcalls-tenant

to

parkinglot=parkinglot_tenant

then issue a reload and try again

Thanks much.

This seems to be working just fine now.

I've been using valet parking for a while and I'm noticing that asterisk restarts when dialing the park extension and then hanging up when a call is already parked. This is the message that appears in the logs right before the crash.

[Feb 15 09:50:07] NOTICE[27864] channel.c: No/unknown event '0' on timer for 'SIP/2349-LindaSewellMD-c81a38f0'?

Here are my park and unpark scripts, let me know if anyone has run into this before.
[rio-park]
exten => s,1,Macro(tl-set-myvariables)
exten => s,n,Set(TIMEOUT=${ARG1})
exten => s,n,GotoIf($["${TIMEOUT}" != ""]?park)
exten => s,n,Set(TIMEOUT=360)
exten => s,n(park),ValetParkCall(auto|${tenant}|${TIMEOUT}|${MYEXTENSION}|1|from-inside${TL_DASH}${tenant})

[rio-unpark]
exten => s,1,ValetUnParkCall(${MACRO_EXTEN:${ARG1}}|${tenant})

i think this crash goes away in 1.4.29 but at the expense of a dtmf issue that is getting worked.

Tried it on my lab system running 1.4.29 and got the same result. I have a ticket open with Diguim to see if we can nail this down.

if they give you a patch to the app_valetparking.c i want a copy :) the code is non-maintained.

hi

multi tenant park slots are working fine for me under asterisk 1.6.1.18
Now I'm just wondering about having parkext for each tenant

here is my feature.conf

[general]
;parkext => 7000
parkpos => 701-704
context => parkedcalls
parkingtime => 180
transferdigittimeout => 3
courtesytone = beep
xfersound = beep
xferfailsound = beeperr

[parkinglot_elp]
parkext => 8000
context => parkedcalls-elp
parkpos => 7001-7010
findslot => next

[parkinglot_thirdlane]
context => parkedcalls-thirdlane
parkpos => 7001-7010
parkext => 9000
findslot => next

I have 2 issues
- first, to update general parkext, I have to restart Asterisk service, reload is not enough

- if I call 8000 with elp phone, I hear, I'm sorry this is not an available extension, if I call 7000, my call is parked

any idea how to update parkext ?
thanks

well i'd be willing to bet you didnt park them in the tenant specific context. do you have CLI output of the 'parkedcalls show' command that proves the they parked in parkinglot_elp ?

do you have the properly included

include => parkedcalls-elp

do not uncomment the parkext for default.. you need to keep it there. There is really no reason to have different parking extensions for each tenant.. its the parkinglot= setting in sip.conf that determines the lot REGARDLESS of what extension you dial to park :)

Here is the CLI command result
cis1*CLI> parkedcalls show
Num Channel (Context Extension Pri ) Timeout
*** Parking lot: parkinglot_elp
7001 SIP/1012-elp-00000049 (from-inside-elp 1 ) 154s
*** Parking lot: default
*** Parking lot: parkinglot_thirdlane

in my sip.conf, I have
[1010-elp]
parkinglot=parkinglot_elp

and the same for all extensions of ELP tenant

what about the

include => parkedcalls-elp in the from-inside-tenant flavors of context? One for each security level (restricted, emergency, unrestricted)

would you care if 7000 was the parking extension regardless of what tenant did the parking? For me it seems easier if I knew everyone dialed 700 to park a call, would make support easier.

I added the include in from-inside-redir-tenant and from-inside-restricted-redir-tenant sections and from-inside-internal-redir-tenant, same result
then I tried to add it in all tenant section, nothing more

for sure we'll keep 7000 for all tenants, but just trying to figure out how to do it if one day a customer asks it