Solved: PAP2 -> Obi110 dial plan
mrjoe:
Hi ianobi,
Tried that, no luck.
I think this is saying if a call comes through from the PAP2 that is prefixed with **7 (remove **7) use vg7's digit map and put the call through vg7.
Quote
{pap2>(<**7:>(Mvg7)):vg7}
I'm lost for digit maps! :)
ianobi:
Your last post is correct. We are saying the same thing in different ways. What is in Mvg7? Maybe there is a problem there.
ianobi:
My attempt to prepend codes to incoming calls was wrong. Here is why:
Call originating from Phone Port or Auto Attendant: This is a two stage process. Stage one: The DMP (Digit Map Processor) compares the number with the rules in the Phone Port or Auto Attendant Digit Map, then executes the best matched rule. This may transform the number by say adding a code such as **1. Transforming is most often done using Mpli. Stage two: The DMP takes the number from stage one and compares it to the rules in the Phone Port or Auto Attendant OutBoundCallRoute. It looks at rules from left to right and executes the first rule that matches the number from stage one. The number may be further transformed here by say removing a code such as **1 before sending the number out on the appropriate trunk.
Call coming into Obi through X_InboundCallRoute: This is a one stage process. The DMP compares the incoming number with the rules in X_InboundCallRoute. It looks at rules from left to right and executes the first rule that matches the number. The number may be further transformed here by say removing a code such as **1 before sending the number out on the appropriate trunk. The DMP then stops, no further processing takes place.
In effect the X_InboundCallRoute acts the same as the Phone Port or Auto Attendant OutBoundCallRoute. If we wish to prepend codes to incoming numbers, then we must do it before they reach the Obi. In your case you do it in the pap2.
mrjoe:
Thanks ianobi,
Where did you see that?
In all sincerity, that makes a mighty lot of sense.
It really should work that way.
The only problem is....
The PAP2's dial plan will not affect any calls going out in that way. All it will do is block calls that do not match it for example if it says (xx.) it will stop **x from going through.
It seems to use Mli all the way.
ianobi:
The Obi Admin Guide tries to explain it, but as usual it took RonR to give us a clear idea of how it all works.
I do not know how the pap2 dial plan works. The best way forward is to look at the OBi Call History to see in what format numbers are coming into the OBi from the pap2. Then the OBi will apply the rules in X_InboundCallRoute and Call History will show the result.
It looks like the pap2 and the OBi are doing exactly what they are supposed to do, but maybe not what you want them to do :)
Navigation
[0] Message Index
[#] Next page
[*] Previous page