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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Cannot make international calls

Status
Not open for further replies.

cjtucker1976

Technical User
Sep 7, 2006
72
US
we occasionally have this issue and we are a non-profit and get hit with a pretty hefty service call when this happens- but it happens so often so any how- to help would be appreciated.

We cannot make any international calls- get a fast busy. The last time it happened the tech said he "assigned DMI 17 to insert 011 on international calls to RLI 17 " Any help on how could check this? what module to check? I called out carrier and they said to contact pbx vendor.
 
LD 86
REQ prt
CUST 0
TYPE rlb
RLI 17

look at the output from what you have said you will see DMI 17 assigned

same load
REQ prt
CUST 0
TYPE dgt
DMI 17

here you should see
DEL 0 (delete no leading digits)
INST 011
CTYP xxxx (This would be NCHG=no change to type of number (TON), UKWN= TON Unknown, or INTL= TON International)

If you are inserting the 011 I would expect it to be UKWN, usually when you have TON International the carrier doesn't require the 011 (but this is not always the case).

Another thing you can do is in LD 96
. stat dch
. enl msgi x (enable inbound messaging against the D-Channel (add all the numbers seen on the previous STAT))
. enl msgo x (enable outbound messaging against the DCH's)
. enl mon tty (enable the output of the messages to display on your terminal)

make the call and you should see the outbound SETUP message and also reason for failure coming back in. You can post results back in here if you need help interpreting
 
Also, look for the FRL assigned in Step 1 of bignose21's instructions.

Then go to LD 87 and

REQ prt
CUST 0
TYPE nctl
NRNG 0 7

Typically the NCOS and FRL will match but review printout to double check.
If FRL from Step 1 was 5 - check to see what NCOS it matches.

Then, print out your telephone and make sure that the NCOS assigned is equal to or lower than 5 (or whatever was assigned in Step 1)
 
Then, print out your telephone and make sure that the NCOS assigned is equal to or lower than 5 (or whatever was assigned in Step 1)

***Should be equal to or greater than 5****
 
Sorry I cannot remote into the terminal so I had to got terminal and take pics and type. I tried the suggested step s and still get fast busy when dialing international. below it output

LD 86
REQ prt
CUST 0
FEAT RLB
RLI 17

ENTR 0
LTER NO
ROUT 10
TOD 0 ON 1 ON 2 ON 3 ON
4 ON 5 ON 6 ON 7 ON
VNS NO
CNV NO
EXP NO
FRL 6
DMI 17
FCI 0
FSNI 0
SBOC NRR
IDBB DBD
IOHQ NO
OHQ NO
CBQ NO

ISET 0
NALT 5
MFRL 6
OVLL 0

REQ PRT
CUST 0
FEAT DGT
DMI 17

DMI 17
DEL 0
INST 011
CTYP UKWN

LD 87
PRT
CUST 0
TYPE NCTL
NRNG 6

NCOS 6
EQA NO
FRL 6
RWTA NO
NSC NO
OHQ NO
CBQ NO
SPRI 0
MPRI 0
PROM 0
TOHQ NONE

LD 96
ENL MSGO 2


DCH 2 OMSG SETUP RED 00000014 CH 28 20 TOD 10:42:35
CALLING#:215XXXXXXX NUMPLAN: E163/NATIONAL (UNKNOWN)
CALLED #:011441926499555 NUM PLAN:E163/INTERNATIONAL (UNKNOWN)

DCH 2 OMSG RELEASE REF 00000014 CH 2 28 20 TOD 10:42:35
DCH 2 OMSG DISC REF 00000015 CH 2 28 20 TOD 10:43:07
CAUSE :NORMAL CALL CLEARING

 
NCOS 6

I also tried from other phones that are set to NCOS 6 and still get fast busy
 
Its not NCOS as you wouldn't have seen the outbound setup message if there was any barring in effect.

Did you enable MSGI and MSGO on DCH 2 as you only posted the outgoing (MSGO) messages.

LD 96
STAT MON

if the fail is incoming from the carrier something like "Invalid number format" it might be the carrier is not liking the TON International mixed with you also sending the 011.
 
ok will dO- tried again results below. appreciate your help.

DCH 2 OMSG SETUP RED 00000014 CH 28 20 TOD 10:53:10
CALLING#:215XXXXXXX NUMPLAN: E163/NATIONAL (UNKNOWN)
CALLED #:011441926499555 NUM PLAN:E163/INTERNATIONAL (UNKNOWN)

DCH 2 IMSG CALLPROC REF 00000017 CH 2 28 23 TOD 10:53:10
DCH 2 IMSG DISC . REF 00000017 CH 2 28 23 TOD 10:53:10
CAUSE :UNASSIGNED NUMBER

DCH 2 OMSG RELEASE REF 00000017 CH 2 28 20 TOD 10:53:10
DCH 2 IMSG REL COMP REF 00000017 CH 2 28 23 TOD 10:53:10




 
So i guess you dial 901144xxxx is 9 the ac1
Ld 86
Req prt
Cust 0
Type esn

If it is
Ld 90
Req prt
Cust 0
Feat net
Tran ac1
Type all

Find the match closest to your numer less the ac1 so may just be 011 as spn etc.
Confirm the RLI that is associated with that number.

If it is 17 as you think as a test try removing the 011 from your DMI
 
I've rang the UK number OK over this side of the pond using (0)1926499555.

Therefore you need to follow the steps from the beginning as we have been trying to help you solve the problem.

I'm assuming that you dial from the phone an access code such as "9"?. If so, then the full number from the phone would probably be
9011441926499555
We in the UK use "00" for international calls, but it's usually "011" in NA. The Meridian phone system will most likely be using a SPN of 011 and this will be found in LD 90.

Something like this below.

>LD 90
REQ PRT
CUST 0
FEAT NET
TRAN AC1
TYPE SPN

SPN

SPN 011
FLEN 16
ITOH NO
RLI 1
SDRR NONE
ITEI NONE

If that doesn't work, then just press "enter" at the SPN prompt to print out all the SPN's in case "0" or "01" is used.

Then follow the steps in LD 86 by printing out the RDB and DGT to find out if any conversion is done.

Personally, I'd print off all your networking information as suggested in my first reply so that you can find out the whole picture of waht is dialled.


Firebird Scrambler

Nortel & Avaya Meridian 1 / Succession & BCM / Norstar Programmer

Website = linkedin
 
BTW in the original post you mentioned that the tech added 011 to the DMI as it was not going to PRI. This is usually the prompts at the bottom of the NET_DATA say INTL set to 011 would mean that if the call has a TON of international the 011 is removed from the call. So in affect the tech has added the 011 making the call 01101144xxxxxx then the NET_DATA removes 011 leaving 01144xxxxx. If the carrier does not accept 44xxxxxxx TON INTL then you would be better removing the 011 from the NET_DATA.

But for now as Firebird says you would be best served establishing the routing of the call and make sure you are looking at the right bits. The normal format to pass a number would be:

44xxxxxx TON INTL
01144xxxxx TON UKWN

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top