Howto:A Fallback Scenario: Difference between revisions

From innovaphone wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 10: Line 10:


==Example==
==Example==
This is an example for a fallback scenario with an ACD Server, which is registered at a Gateway with the extension 9. Normally you call the 9222  to reach someone in the sales department. The ACD Server usually alarms the appropriate sales person. In case the connection to the ACD Server is lost the CFNR takes effect and routes the call to a waiting queue. To intelligently forward the call, the PBX uses the extension 222 and the PBX appends this extension to the CFNR Number. In this case the CFNR number is 8 and the call is transferred to the sales waiting queue (8222).
There are sometimes questions about special routing based on the number length at a innovaphone gateway.
Yes, this is possible.


[[Image:A_fallback_scenario_01.png]]
Let's start from the following call scenario. Call numbers are sent without leading zeros or ISDN Type of Number (TON). We must therefore decide on the basis of the CGPN (Calling Party Number) number length whether we
*    we have a CGPN of less than 10 digits we must prefix 0
*    we have a CGPN of 10 or more digits we must prefix 00
Our provider is connected by BRI1 to the trunk. We use GW1 to register to the trunk object inside the PBX.


==Configuration==
==Configuration==
The configuration is simple. You just have to create a CFNR at the object that might fail and a matching extension that receives the call in a fallback case.
The first step is to create a route from the BRI1 interface to the MAP interface. In this "Force Enblock" is activated. In my example, with 4 seconds waiting time for the next digit to wait for overlap dialing from the trunk before the number length is checked in the routing.


The appending of a number works with a Trunk Line, User object or Call Broadcast object as well.
Next, a second map is created in the route to check if the CGPN has 10 digits or more. Source is BRI1 and destination is the MAP interface. The checkmark "Verify CGPN" is set to check the CGPN.


Under "CGPN Maps" in Map 2, a rule is created, with which it is checked whether the CGPN has at least 10 digits. In this case a 00 is set before the CGPN. This is done by entering 10 points (one point for a number) in "Number In" and a 00 in "Number Out" (.......... -> 00). Otherwise the routing continues.


Next, a third map is created in the route to check whether a 00 is already prefixed. If not, a 0 is prefixed. Source is again the BRI1 interface and destination is again the MAP interface. The checkmark "Verify CGPN" is set to check the CGPN.
Under "CGPN Maps" in Map 3, two rules have to be created.
1. Check whether the CGPN already begins with 00 (00 -> 00). In this case, nothing is changed and routing continues.
2. If the CGPN not started with a 00, a 0 is set before the CGPN (-> 0) and routing continues.
This should provide the following routing for the adaptation of the CGPN:
[[Image:Call_routing_number_length.png]]


<!-- == Related Articles == -->
<!-- == Related Articles == -->


[[Category:Howto|{{PAGENAME}}]]
[[Category:Howto|{{PAGENAME}}]]

Revision as of 17:44, 29 August 2017

Applies To

This information applies to

  • All Innovaphone devices with PBX functionality
  • V9 HF12 and up


Example

There are sometimes questions about special routing based on the number length at a innovaphone gateway. Yes, this is possible.

Let's start from the following call scenario. Call numbers are sent without leading zeros or ISDN Type of Number (TON). We must therefore decide on the basis of the CGPN (Calling Party Number) number length whether we

  • we have a CGPN of less than 10 digits we must prefix 0
  • we have a CGPN of 10 or more digits we must prefix 00

Our provider is connected by BRI1 to the trunk. We use GW1 to register to the trunk object inside the PBX.

Configuration

The first step is to create a route from the BRI1 interface to the MAP interface. In this "Force Enblock" is activated. In my example, with 4 seconds waiting time for the next digit to wait for overlap dialing from the trunk before the number length is checked in the routing.

Next, a second map is created in the route to check if the CGPN has 10 digits or more. Source is BRI1 and destination is the MAP interface. The checkmark "Verify CGPN" is set to check the CGPN.

Under "CGPN Maps" in Map 2, a rule is created, with which it is checked whether the CGPN has at least 10 digits. In this case a 00 is set before the CGPN. This is done by entering 10 points (one point for a number) in "Number In" and a 00 in "Number Out" (.......... -> 00). Otherwise the routing continues.

Next, a third map is created in the route to check whether a 00 is already prefixed. If not, a 0 is prefixed. Source is again the BRI1 interface and destination is again the MAP interface. The checkmark "Verify CGPN" is set to check the CGPN.

Under "CGPN Maps" in Map 3, two rules have to be created. 1. Check whether the CGPN already begins with 00 (00 -> 00). In this case, nothing is changed and routing continues. 2. If the CGPN not started with a 00, a 0 is set before the CGPN (-> 0) and routing continues.

This should provide the following routing for the adaptation of the CGPN:

Call routing number length.png

Retrieved from "https://wiki.innovaphone.com/index.php?title=Howto:A_Fallback_Scenario&oldid=47751"