[cisco-voip] [Nortel-list] international dialing
Brian D. Browne
brianb at ct2k.com
Tue Apr 6 12:40:20 EDT 2010
From: Brian D. Browne <brianb at ct2k.com>
To: nortel-list at tgrace.com
Cc: francois.lasalle at stratosglobal.com; afeinberg at hersheypa.com; cisco-voip at puck.nether.net
Sent: Tue, April 6, 2010 2:00:46 AM
Subject: [Nortel-list] international dialing
Finally posting after much anguish over this problem...
Well folks, after more than a week of of online research into this problem of the Meridian 1 mysteriously stripping the digits "011" from international calls, I found this post from Al Feinberg (of the Nortel-List) describing the very same problem I have been experiencing. Thank God for the posts below which allows me to put this problem to rest. I have come to the conclusion that the problem, really is in the way that Nortel implemented NI2 on the Meridian 1. My post is going to be a it long, but please bear with me.... a bit. I have seen a significant number of people (in a number of forums ie Tek-Tips, PBX info, and even in the Cisco VOIP mailing list posting on this very problem)
As described in detail by Al Feinberg( below), the problem is that with an ISDN PRI circuit programmed for NI2 the M1 mysteriously strips out the "011" on out going international calls. To keep things simple, I bypassed the NARS/BARS software on the Meridian 1 by dialing an access code (7180) to directly access the route. I programmed the call type on the PRI route as NATL (after first trying ctyp - unkwn) and made three types of calls. The first two 1-305-679-2118 and 679-2118 went through flawlessly. When I dialed 011-55-44-6792118 or whatever number I dial with a 011 prefix, the system would output the number without the 011.
This was first encountered on a CS1000 rls 4.0 system at a customer of mine. Previously the customer was using ISIG (nortel's implementation of QSIG), but after the carrier did an upgrade of their softwitch (maker unkown), their QSIG wouldn't work with Nortel's ISIG. (the D-channel wouldn't even come up), so we moved to NI2. With NI2, the D-channel synched up very quickly and we are able to make 1+ and local calls without any problems but the 011 calls fail due to the "011" digit stripping.
I replicated the problem back in my lab by setting up an CS1000 Opt.11 C rls 3.4 with two TMDI cards in it. One went to a cisco 3640 running CME (Call Manager Express) programmed for NI2 with a dial peer configured to terminate on an FXS port with 0116792118 and the other PRI went to an Avaya definity GS3 PBX also configure for NI2.
The call setup messages from the meridian 1 to both switches (Cisco and Avaya) show that the "011" being stripped. Since I was directly accessing the route, and there was no NARs/BARS DMI to complicate things, I can only conclude that the problem is with the Nortel switch. What re-inforces this point of view also, is the fact that I could take the identical circuit from the cisco 3640 gateway (which was previously connected to the Nortel switch) and connect it to the Avaya switch (without altering any programming, and it should be noted that I used official documents from both Cisco and Avaya's interoperability labs to setup the connections) and the Avaya switch could call the Cisco 011556792118 number.
Below is my programming and the output of my Nortel D-channel messaging. This is with the call type configured as unknwn in the RDB. Similar results were obtained with the Call type configured as NATL. Dchannel 3 went to the Avaya and D-Channel 16 went to the Cisco 3640. Output shown is for the calls to the Avaya. Route access code is 7180. Note that the Call detail record shows the number that was dialed, while the D-channel msgo shows what the M1 actually dials out in the initial address message (IAM).
TYPE RDB
CUST 00
DMOD
ROUT 25
DES PRICARD6
TKTP TIE
NPID_TBL_NUM 0
ESN NO
RPA NO
CNVT NO
SAT NO
RCLS EXT
VTRK NO
DTRK YES
BRIP NO
DGTP PRI
ISDN YES
MODE PRA
IFC NI2
SBN NO
NCNA YES
NCRD YES
CHTY BCH
CTYP UKWN
INAC NO
CPFXS YES
CPUB OFF
DAPC NO
BCOT 0
INTC NO
DSEL VOD
PTYP PRI
AUTO YES
ACMP NO
DNIS NO
IANI NO
ICOG IAO
SRCH LIN
TRMB NO
STEP
ACOD 7180
TCPP NO
PII NO
TARG 01
CLEN 1
BILN NO
OABS
INST
ANTK
SIGO STD
MFC NO
ICIS YES
OGIS YES
PTUT 0
TIMR ICF 512
OGF 512
EOD 13952
NRD 10112
DDL 70
ODT 4096
RGV 640
GTO 896
GTI 896
SFB 3
NBS 2048
NBL 4096
TFD 0
DTD NO
SCDT NO
2 DT NO
DRNG NO
CDR YES
INC YES
LAST YES
TTA YES
ABAN YES
CDRB YES
QREC YES
OAL YES
AIA YES
OAN NO
OPD YES
NDP EXC 0
CDRX NO
NATL YES
SSL
CFWR NO
IDOP NO
MUS NO
PANS YES
FRL 0 0
FRL 1 0
FRL 2 0
FRL 3 0
FRL 4 0
FRL 5 0
FRL 6 0
FRL 7 0
TTBL 0
ATAN NO
PLEV 2
OPR NO
ALRM NO
ART 0
SGRP 0
CCBA NO
AACR NO
ADAN DCH 3
CTYP TMDI
CARD 06
PORT 1
DES pricard6
USR PRI
DCHL 6
OTBF 32
PARM RS232 DTE
DRAT 64KC
CLOK EXT
IFC NI2
ISDN_MCNT 300
CLID OPT0
CO_TYPE STD
SIDE USR
CNEG 1
RLS ID **
RCAP COLP
OVLR NO
OVLS NO
T310 120
T200 3
T203 10
N200 3
N201 260
K 7
BSRV NO
ADAN DCH 16
CTYP TMDI
CARD 08
PORT 1
DES OPT11PRITEST
USR PRI
DCHL 8
OTBF 32
PARM RS232 DTE
DRAT 64KC
CLOK EXT
IFC NI2
ISDN_MCNT 300
CLID OPT0
CO_TYPE STD
SIDE USR
CNEG 1
RLS ID **
RCAP COLP
OVLR NO
OVLS NO
T310 120
T200 3
T203 10
N200 3
N201 260
K 7
BSRV NO
DCH 3 UIPE_OMSG CC_SETUP_REQ REF 0000002F CH 6 23 TOD 13:22:32 CK 0B9782F4
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:5502 NUM PLAN: PRIVATE TON: UNKNOWN
CALLED #:6792118 NUM PLAN: PRIVATE TON: UNKNOWN
DCH 3 UIPE_IMSG CC_PROCEED_IND REF 0000002F CH 6 23 TOD 13:22:32 CK 0B978373
DCH 3 UIPE_IMSG CC_SETUP_CONF REF 0000002F CH 6 23 TOD 13:22:48 CK 0B97F6EF
N 056 00 5502 A025023 03/23 13:22:48 00:00:02.0 71806792118
&
& 000 01
DCH 3 UIPE_IMSG CC_DISC_IND REF 0000002F CH 6 23 TOD 13:22:50 CK 0B98089E
CAUSE: #16 - NORMAL CALL CLEARING
DCH 3 UIPE_OMSG CC_RELEASE_REQ REF 0000002F CH 6 23 TOD 13:22:50 CK 0B9808A6
DCH 3 UIPE_IMSG CC_RELEASE_CONF REF 0000002F CH 6 23 TOD 13:22:50 CK 0B9808FF
DCH 3 UIPE_OMSG CC_SETUP_REQ REF 00000030 CH 6 23 TOD 13:23:36 CK 0B996F43
N 057 00 5502 T025023 03/23 13:23:36 00:00:00.0 71800115966962611738
&
& 000 01
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:5502 NUM PLAN: PRIVATE TON: UNKNOWN
CALLED #:5966962611738 NUM PLAN: PRIVATE TON: INTL
DCH 3 UIPE_IMSG CC_PROCEED_IND REF 00000030 CH 6 23 TOD 13:23:36 CK 0B996FC5
DCH 3 UIPE_IMSG CC_DISC_IND REF 00000030 CH 6 23 TOD 13:23:36 CK 0B996FD2
CAUSE: #17 - USER BUSY
DCH 3 UIPE_OMSG CC_RELEASE_REQ REF 00000030 CH 6 23 TOD 13:23:36 CK 0B996FDA
DCH 3 UIPE_IMSG CC_RELEASE_CONF REF 00000030 CH 6 23 TOD 13:23:36 CK 0B997031
DCH 3 UIPE_OMSG CC_SETUP_REQ REF 00000031 CH 6 23 TOD 13:24:08 CK 0B9A6B6C
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:5502 NUM PLAN: PRIVATE TON: UNKNOWN
CALLED #:13056792118 NUM PLAN: PRIVATE TON: UNKNOWN
DCH 3 UIPE_IMSG CC_PROCEED_IND REF 00000031 CH 6 23 TOD 13:24:08 CK 0B9A6BF6
DCH 3 UIPE_IMSG CC_SETUP_CONF REF 00000031 CH 6 23 TOD 13:24:10 CK 0B9A7F5E
DCH 3 UIPE_IMSG CC_DISC_IND REF 00000031 CH 6 23 TOD 13:24:14 CK 0B9A9D1E
N 058 00 5502 A025023 03/23 13:24:11 00:00:04.0 718013056792118
&
& 000 01
CAUSE: #16 - NORMAL CALL CLEARING
DCH 3 UIPE_OMSG CC_RELEASE_REQ REF 00000031 CH 6 23 TOD 13:24:14 CK 0B9A9D27
DCH 3 UIPE_IMSG CC_RELEASE_CONF REF 00000031 CH 6 23 TOD 13:24:14 CK 0B9A9DA9
Below is the original post by Al Feinberg of the Nortel-list as well as a similar post from Sam Hodgeman over at the Cisco-VOIP mailing list.
Thanks to all the posters and the responders for sharing your thoughts on this problem. Although, I am not over joyed with the final outcome, reading your posts has proven to be very instructive and helpful. Thanks again.
Brian D. Browne
Inter-Caribbean Networking Solutions Ltd.
1-868-679-2118
1-868-679-2548
1-868-679-8919
brianb at ct2k.com
cns at ct2k.com
"Live long and prosper.....but do it with kindness and compassion" - Spock and Browne
-----Original
Message-----
From: nortel-list-bounces at tgrace.com
[mailto:nortel-list-bounces at tgrace.com]
On Behalf Of
AFeinberg at hersheypa.com
Sent:
Thursday, May 14, 2009 3:51 PM
To:
Mailing list for Northern Telecom related issues
Subject:
Re: [Nortel-list] international dialing
That's
weird that you say that.
We
just left AT&T as our LD carrier and moved to Level 3.
We
were told that because they use DMS250 switch for LD, they don't
support
NI2. Their local switch was Lucent 5ESS and does support NI2.
We
also had trouble dialing internationally after we switched. The
carrier
didn't see 011, though we didn't strip it. I built a DMI to
insert
011 and added to the RDB and it worked. I still don't understand
where
the digits went.
Where
is the "type of number" because on the call trace, I do see
International,
but the 011 was gone.
Thanks!
Al
Al
Feinberg
Telecommunications
Analyst
Hershey
Entertainment & Resorts
27
West Chocolate Avenue
Hershey,
PA 17033
Telephone
717-508-1598
Fax
717-520-5785
Email: afeinberg at hersheypa.com
"Proudly
Committed To Our Legacy of Excellence"
From: "Hannah, Patrick" <phannah at thenetwerk.net>
To: Mailing list for Northern Telecom related issues
<nortel-list at tgrace.com>
Date: 05/14/2009 03:09 PM
Subject: Re: [Nortel-list] international
dialing
Sent by: nortel-list-bounces at tgrace.com
I
seem to recall with NI2 (and maybe speficially with a DMS switch) that
if
you send the Type of Number as International there is no need to call
411.
I've
found it easier to change the Type of Number to Unknown and prefix
with
011. I've not done this on Nortel but have on Avaya and it works
like
a charm.
On
Tue, May 12, 2009 at 1:55 PM, <AFeinberg at hersheypa.com> wrote:
We just installed new Level 3 PRI's (legacy
wiltel)
Getting carrier message, can't complete the
call.
Traced call, we don't see the 011 intl code,
however the RLI doesn't
have
DMI assigned.
DCH monitor only shows the phone number, not
the international code
011.
We added a DMI table and assigned to the RLI
and successfully
completed
the
call.
What else would strip the first three digits
if not a DMI table
assigned
to
the route list? We could do this on AT&T
last week with the same RLI.
Thanks!
Al
Al Feinberg
Telecommunications Analyst
Hershey Entertainment & Resorts
27 West Chocolate Avenue
Hershey, PA 17033
Telephone 717-508-1598
Fax 717-520-5785
Email: afeinberg at hersheypa.com
"Proudly Committed To Our Legacy of
Excellence"
Post from Cisco-Voip mailing list describing the same problem of the Nortel M1 stripping 011 digits..
Hi all,
I am working on using Cisco 24xx IP-IADs connected
to PBX NI2 PRIs.
With NI2 on these particular PBXs - Nortel
Meridian - the user dials the
leading zero, but the PBX strips it out. Instead,
it includes a special
IE in the ISDN setup message of "Operator
Services Access Requested."
The usual debug ISDN q931 trace doesn't show any
sign of recognizing
this IE, nor of recognizing the call as anything
but ISDN/National.
Is there a different trace/debug parameter that
would show the
individual ISDN IEs? Assuming this IE is
recognized by the IOS, how does
one tell the box what to do with these calls? In
our case, most calls
are transformed into SIP calls directed to a
Broadsoft SIP gateway, but
I don't see how the IE is mapped to the SIP
message.
Any insight would be appreciated.
- Sam Hodgeman
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20100406/ae4619b7/attachment.html>
More information about the cisco-voip
mailing list