Call Parking - Some help Please

to answer your first question, yes that is setup correctly. The only way to acheive the second question is to alter the C code of asterisk, as dialplan is no longer involved in that process. Is it the alert-info you wish to alter or the CALLERID(name) ? either way would have to modify the parking functions themselves.

Thanks Erik,

I would like to do either - append PK- to the CLI coming back to the parkee or add alert-info ringtonename into the SIP message so it is a different ringtone for returning calls.

I may take a look at the source later as this is a bit of a show stopper for this company. They park calls constantly and when it's not picked up they need to know its a parked call..

Thanks for your time.

Regards
Brian

in single tenant you *might* be able to make use of this feature setting in features.conf

;comebacktoorigin = yes
; Whether to return to the original calling extension upon parking
; timeout or to send the call to context 'parkedcallstimeout' at
; extension 's', priority '1' (default is yes).


the trick then would be to set your headers in this context, but knowing who to ring back would be a challenge unless you always want to ring back the same extension.

another option is to not use the default parking as defined by including 'parkedcalls' but rather make your own parking design based on the use of the Park() application. You'd still have to include parkedcalls but your parking extension would be some other macro extension number. If you want to keep 700 you'd have to then alter features.conf to declare a different parkext value. from here you can specify both the return context and return extension. Your custom code could include something like


[somecustomcontext]
exten => _X.,1,SIPAddHeader(Alert-Info: )
exten => _X.,n,Goto(from-inside-redir,${EXTEN},1)


Erik,

Many thanks. I am going to see them on Monday and will spend sometime working through your suggestions.

Thanks again.

Regards
Brian