We are using Meridian 81C and 61C Release 24 and MLink 5.
Here is a basic overview of the setup:
We have two 81C Meridians and one 61C. 61C is connected to the second 81C Meridian. Is it possible to route a call using IR from the first 81C to and agent on the 61C in one step?
I heard that it might be possible to setup a second 81C, so that when a call with a particular access code came to it, it would automatically forward that call to a different PBX. So, PBXwise, you would have a call transferred from PBX1 to PBX2 to PBX3, but since the transfer between PBX1 and PBX2, as well as PBX2 and PBX3 will be done via PBXs, Genesys will not know about it. So, for Genesys, it will look like a call transferred directly from PBX1 to PBX3.
Can this be done?
The only other way I can think of is by using attach data where we would select and write the TargetSelect on PBX1, transfer the call to PBX 2, where IR would take that call and then route the call to the agent on PBX3 specified in the attach data. I do not really like this kind of approach.
No problems. The meridians can be configured to retranslate any call to another destination. You can use a coordinated dial plan or use access codes to identify the trunks to use.
As Roli suggested, it works well with IR, as IR tells the tserver were the call is waiting the fully qualified targrt name (DN@tserver). The external router functionality within the tserver then realizes that the call is for an external tserver, and contacts the remote tserver to ask for an external route point. The ExtRP is reserverd and then the initial tserver transfers the call to the external route point. When the call arrives at the routepoint, the attached data and conn ID is updated and the tserver then completes the transfer to the target destination.
So, the tservers work fine, you only have to make sure your PBX’s are configured okay to route the call through to the target switch. One thing that you may have to watch is the external route point timeout config. If this is too short, the ExtRP may be released before the call actually arrives. (Watch for this if you are routing calls via the PSTN..)
So, you mean, if I have three switches, connected like 1>2>3, and I have ERP on each switch, then as long as we know the access code for each switch, the EventRouteRequest issued by a TServer on a first switch will be replied by the IR as AgentID(Switch 3)@StatServer, and then the first TServer will route call to a switch #2 TServer, which in turn will route a call to switch#3 TServer and connect it to the agent on the switch#3 ?
So, if access code for switch number one is 1000, for switch #2 2000, and switch #3 3000 then switch #1 will issue GetExternalAccessNumber to switch #2, will receive 3000, then somehow KNOW that it has to actually route it to switch#2 via 2000 and then let TServer on switch #2 redirect the call to TServer#3?!!! I am sure I am misunderstanding something here!
The remote tserver on switch 3 tells the tserver on switch 1 to use ERP 3000. Switch has a dial plan that routes the dialed number (3000) to Switch 2. Switch 2 looks at the dialed number and uses its dial plan to route the call to Switch 3. The call arrives on the ERP 3000 on switch 3 and the External Router function of tserver associates the attached data etc with the call.