Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Magix to IPO shortcodes for dialing out?

Status
Not open for further replies.

IPhello

Programmer
Aug 13, 2005
205
US
This could be a long one.

Magix R2.1 tied to and IPO 3.2(54) 406V2, via a PtoP in the same room (crossover cable).

Currently I have this setup as a PRI going 5ess on the IPO side and Magix-PBX and the Magix side. The IPO has a PRI from the LEC coming into it and the other of course going to the Magix on a dual PRI card.

Everything works except for dialing out on the Magix. All incoming call route perfectly. If I create an incoming call route such as this;

Line Group:2 "This is the line from the Magix"
Incoming number:95555555 "Number dialed in the Magix"
Destination:95555555

Call will go out just fine. If I use ANYTHING else, it just dies and will not pass. I have to put in the excat number that I am dialing. I see it in Monitor and can't figure out why it doesn't just match up with the default shortcodes to dial out. Can someone give me a tip or kick me in the head or something to wake me up.

Unfortunately it has to be this way as the LEC SUCKS here and will not fix their screw up for 3 days. I don't want to give the LEC'S name, but if you were to guess Qwest you might be right.

 
I think what you will need to do is create a incomming call route with wild cards in it. I think i did one with 9xxxxxxxxxx and no destination. It gave me an error but allowed me to dial out. I am sure thee is a bette way to create it but i think this may work. I put 11 x's in there but you could do 9 and 10x's as well.
 
You can't have an incoming call route without a destination. The Manager will not let it happen.
 
A little more information. In the Monitor I see the number coming in, then it strips the number and puts in the destination. It does not pass the number on through.

3993059mS CMTARGET: LOOKUP CALL ROUTE:51 type=2 called_party=8755254 sub= calling=5152435626 in=1 complete=1
3993059mS CMTARGET: SET BESTMATCH:51 length 7 vs 0 match=98755254 dest=98755254
3993059mS CMTARGET: LOOKUP INCOMING CALL ROUTE:51, calling party is 5152435626. Using destination 98755254
3993059mS CMTARGET: ADD TARGET:51 number=98755254 type=100 depth=1 nobar=1 setorig=1
3993060mS CMTARGET: SYS SC:51 98755254 3 8755254 sc=type=Dial3K1 code=[9]N;, num=N
3993060mS CMTARGET: LCR NOT MATCHED:51 (cpn=8755254)
3993060mS CMTARGET: DIAL LINE:51 GROUP=0 SUCCESS=1
3993060mS CMTARGET: LOOKUP CALL ROUTE:51 returned 1


3905383mS CMTARGET: LOOKUP CALL ROUTE:49 type=2 called_party=2627686 sub= calling=7133 in=1 complete=1
3905384mS CMTARGET: SET BESTMATCH:49 length 0 vs 0 match= dest=[9]N
3905384mS CMTARGET: LOOKUP INCOMING CALL ROUTE:49, calling party is 7133. Using destination [9]N
3905384mS CMTARGET: ADD TARGET:49 number=[9]N type=100 depth=1 nobar=1 setorig=1
3905384mS CMTARGET: SYS SC:49 [9]N 5 N sc=type=Dial3K1 code=[9]N;, num=N
3905385mS CMTARGET: LCR NOT MATCHED:49 (cpn=N)
3905385mS CMTARGET: DIAL LINE:49 GROUP=0 SUCCESS=1
3905385mS CMTARGET: LOOKUP CALL ROUTE:49 returned 1

In the first trace you can see it working when I have the shortcode as the destination of 98755254 and it works. If I don't have a shortcode for the 92627686, it tries to follow the path of the [9]N; shortcode which would make sense, but it strips the number and just passes N.
 
Put 10 x's in the incoming number field and 9# in the destination
 
Just did that before I checked here and it worked.

I used

LG:2
ICR:xxxxxxxx
Destination: #
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top