Re: [Asterisk-Users] Re: Call parking from legacy PBX over PRI??
On Friday 12 May 2006 17:38, Steven wrote: > Does anyone have a version that talks back during the transfer like Park() > does? ParkAndAnnounce can do this, can you not specify the correct channel? Also, I added a feature to ParkAndAnnounce which is now part of trunk which gives the variable ${PARKEDAT} to the announced channel. -A. ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[Asterisk-Users] Re: Call parking from legacy PBX over PRI??
I did a test with ParkAndAnnounce and the call back is not going to fly here. Does anyone have a version that talks back during the transfer like Park() does? I piggybacked off of another feature request in the bug system that is very similar. http://bugs.digium.com/view.php?id=6953 I hope doing so is not a problem. -- -- Steven http://www.glimasoutheast.org "C F" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] Use a macro that uses the ParkAndAnnounce application and set the return context there. On 5/11/06, Steven <[EMAIL PROTECTED]> wrote: > I have an issue with call parking and hope there is some undocumented feature > for this. ;-) > > We are replacing our legacy PBX with asterisk, but to save money over time > (handsets and network), I am trying to maintain the use > of our legacy PBX. > Asterisk extensions can not use the call parking features (not usable over > trunk cards) of the old PBX, so I have to get the old > PBX > to use asterisk's. > > Problem: > If I park a cal from an asterisk extension, it works fine. > If I park a call from Legacy PBX extension, It will not call back the proper > extension and will make all extensions on our old PBX > ring. > The issue is that the call parking feature retains the cannel to reconnect on > timeout. > This is fine for SIP, because the cannels includes the destination. > On a ZAP PRI trunk, it retains ZAP/25, which only makes it call back the old > PBX, not an extension. > My front desk is still on the Legacy PBX. > > Two hopes: > 1. The call parking feature can be changed to reconnect to the caller ID of > the parker instead of the channels ID. > or > 2. I can set a timeout extension (front desk) for all parked calls. This > would be acceptable, because most users either just use > hold or a blind transfer. It is normally only the front desk that parks > calls and even if a user did, the front desk can handle > their timeout. > > > > > features.conf: > [general] > parkext => 5400; What ext. to dial to park > parkpos => 5401-5409 ; What extensions to park calls on > context => parkedcalls ; Which context parked calls are in > parkingtime => 120 ; Number of seconds a call can be parked for (default is > 45 seconds) > > -- > -- > Steven > > http://www.glimasoutheast.org > > > > > > ___ > --Bandwidth and Colocation provided by Easynews.com -- > > Asterisk-Users mailing list > To UNSUBSCRIBE or update options visit: >http://lists.digium.com/mailman/listinfo/asterisk-users > ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[Asterisk-Users] Re: Call parking from legacy PBX over PRI??
Here is a CLI of the problem: Here is a CLI of the problem: == Timeout for Zap/47-1 parked on 5401. Returning to park-dial,Zap/47,1 -- Executing Dial("Zap/47-1", "Zap/47||t") in new stack == Everyone is busy/congested at this time (1:0/0/1) -- Hungup 'Zap/47-1' Zap/47-1 could be any of 200 phones and the Legacy PBX doesn't know what to do with the call, so it comes back as busy. -- -- Steven http://www.glimasoutheast.org "Steven" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] >I have an issue with call parking and hope there is some undocumented feature >for this. ;-) > > We are replacing our legacy PBX with asterisk, but to save money over time > (handsets and network), I am trying to maintain the use > of our legacy PBX. > Asterisk extensions can not use the call parking features (not usable over > trunk cards) of the old PBX, so I have to get the old > PBX to use asterisk's. > > Problem: > If I park a cal from an asterisk extension, it works fine. > If I park a call from Legacy PBX extension, It will not call back the proper > extension and will make all extensions on our old PBX > ring. > The issue is that the call parking feature retains the cannel to reconnect on > timeout. > This is fine for SIP, because the cannels includes the destination. > On a ZAP PRI trunk, it retains ZAP/25, which only makes it call back the old > PBX, not an extension. > My front desk is still on the Legacy PBX. > > Two hopes: > 1. The call parking feature can be changed to reconnect to the caller ID of > the parker instead of the channels ID. > or > 2. I can set a timeout extension (front desk) for all parked calls. This > would be acceptable, because most users either just use > hold or a blind transfer. It is normally only the front desk that parks > calls and even if a user did, the front desk can handle > their timeout. > > > > > features.conf: > [general] > parkext => 5400; What ext. to dial to park > parkpos => 5401-5409 ; What extensions to park calls on > context => parkedcalls ; Which context parked calls are in > parkingtime => 120 ; Number of seconds a call can be parked for (default is > 45 seconds) > > -- > -- > Steven > > http://www.glimasoutheast.org > > > > > > ___ > --Bandwidth and Colocation provided by Easynews.com -- > > Asterisk-Users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users > ___ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users