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

Configuring Embedded PRI on SX-200 ICP 1

Status
Not open for further replies.

southwell

IS-IT--Management
Nov 17, 2010
37
US
Hello,
I am running a version 5.0.0.18 on a SX200 ICP MX. I’ve following all of the programming per tech docs for installing a embedded PRI. It is programmed and installed in the system. It is synced to the PRI interface from the provider and all appears to be fine looking at the status in the maintenance terminal. It is connected to an Adtran 908e.

I have programmed the mod digit table with *4000*6*4

All of the settings in form 13 and 42 are all set correctly. DTMF was said to be ON in one tech doc and OFF in another. Either way does not make a difference.

Form 15 is programmed with N=4 M=0 X=blank CDN=7
Form 13 T1 E&M programmed to WINK incoming and outgoing.
It is connecting to a DMS100 switch. Framing is ESF and Line coding is B8ZS. PRI Capability Voice: Speech
Form 44 is programed to PRI module. bay 4 slot 2
A stratum 3 clock is also onboard.

Form 26 ARS programming is the same as our old LS trunks which are still in service. I routed my cell phone 5551212 QTY to Follow = 0 to the route and number to which the PRI trunk groups are in as well as the mod digit table.

Anytime I dial out my cell phone (or any number when I change it in form 26 to the proper route for PRI) I get a fast busy immediately. Before I call the provider I wanted to ask if it may be in our system configuration. It doesn’t even look like it is trying while monitoring in maintenance.

Below is the mitel maintenance terminal showing the status of the link. Also below that is the Adtran info that they gave me.

It is also a dynamic PRI but I don’t know if the system even notices the difference. I cannot test the inbound calls because they have not ported over the numbers yet, but apparently we can test outbound I was told.

Any help would be appreciated.

DSTi : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 SYNC : yes
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 SLIP : 0
DSTo : 00 80 81 00 00 80 03 00 00 02 FF 00 01 02 18 03 BPV : 0
A9 83 82 00 00 03 80 00 00 00 00 00 00 00 00 00 XS1 : 0
XCTL : inact
CSTi : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 52 RxYLW : no
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 8KHZ : 1
CSTo : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 B8ZS : yes
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 TxYLW : no
CCS : yes
TRK Tx TxA TxB TxPD Rx RxA RxB RxPD LPBK DAC SRCE MODE MCW: 01010010
1 00 0 0 000 80 0 0 00 no 675 4/2/ 0 AUTO MST: 00000000

Adtran:
pri 1 is UP
Description: pri 1
Switch protocol: Nortel DMS100
Signaling role: network (NT) b-channel-restarts enabled
Ringing signal: provide inband ringing signal to calling TE
Calling-party override: if no Caller ID
Calling-party presentation: allowed
Calling-party number: 9042843505
digits transferred 4
ISDN name-delivery: disabled
progress indicator #8 in alerting message: enabled
progress indicator #2 in connect message: disabled
progress indicator #1 in setup message: disabled
progress indicator #3 in setup message: disabled
progress indicator location: public
resource-selection: automatic
RLT: disabled
Connected interface: t1 0/3 tdm-group 1
Channel status 123456789012345678901234
.......................D
Legend: - = Unallocated . = Inactive
A = Active B channel B = Backup D channel
D = Active D channel M = Maintenance
R = Restart
42408 packets input, 201871 bytes, 0 no buffer
0 runts, 2 giants, 0 throttles
3 input errors, 0 CRC, 1 frame
2 abort, 0 discards, 0 overruns
42410 packets output, 201523 bytes, 0 underruns
 
turn dtmf off
start type wink
bay location = isdn (form 53)

NO GOOD DEED GOES UNPUNISHED!
 
RE: I have programmed the mod digit table with *4000*6*4

What are the programmed values for: (Form 42 Link Descriptor Options)
- Outgoing bearer capability selection - {default = Fixed Voice}
- Outgoing NSF Selection - {default = Fixed -default}
- Outgoing caling party number restriction - - {default = Fixed allow for voice}

If the above items are still default then you should program the Mod Table as: *4*6*4

If they are set to Call by Call then the *4000*6*4 is valid.


**********************************************
What's most important is that you realise ... There is no spoon.
 
on a 200ICP with embedded PRI, call by call would have a mod digit entry of *400*6*4. only 2 zeros not 3 like on on a 3300 or like on a PRI card.
or go fixed as was suggested

(the middle zero is not an option)
 
It was setup to default like kwbMitel suggested and I changed the mod digital table to the above *4*6*4. It ended up being a problem with the Adtran router from the provider as well.

Now the when you call one of the DIDs during night 1 service (hunt # 300 vmail ports) it goes to "please enter your mailbox number" instead of the main auto att greeting. Is a * being entered somewhere or do I need to change something in the COS?

Also the SMDR displays the incoming DID digits (4) in the beginning and end of the data string. And no name of the person or business is displayed on the display sets or SMDR during ringing the set or after pickup it is still the number. On the LS trunks it displayed the Calling Name ID. Is it possible to have it programmed the same way and is this something the service provider must enable?


ISDN Trunks Class of Service.
• Enable ANI/DNIS Trunk COS option 811 to display CLID (the caller's number) and DDI (the number the caller dialed) on incoming trunks.
• Enable Incoming Trunk Call Rotary COS option 801.
• Enable Incoming Trunk No Dial Tone COS option 701.
• Enable Limited Wait for Dial Tone COS Option 802.
• Enable SMDR - Record ANI/DNIS COS Option 814 to allow CLID digits to appear in SMDR reports for Incoming calls.
• Enable SMDR - Extended Record, COS Option 246, to allow the calling name to appear in SMDR reports for Incoming calls.
• Enable SMDR - Overwrite Buffer Option 702 if SMDR - Record Incoming Calls Option 806 is Enabled.
Note: Ensure that COS Option 800 (ANI Applies) is NOT enabled in the class of service of the ISDN trunks.

Set & Station Class of Service
• Enable Display ANI/DNIS Information COS option 502 and Display ANI Information Only COS option 613 to allow display of CLID digits on display telephones.
• Enable COS option 503, Enable Calling Name Display, to allow the display of the calling name.
• Enable SMDR - Overwrite Buffer COS option 702.
• DISABLE Outgoing Trunk Callback COS option 236.
• DISABLE Outgoing Trunk Campon COS option 237.

Thank you very much for your help.
 
RossBC- There are 3 fields for call by call and therefore up to 3 zeros in the ModDig. It has been this way on the 200 for quite some time. Are you saying this has changed recently?

**********************************************
What's most important is that you realise ... There is no spoon.
 
KWB - I can only assume you always use fixed (or don't use the embedded PRI card) as this has been this way since the embedded PRI(T1) card came out - release 3.
as per KBA 06-5106-00047

If the system is running a PRI card or an ISDN Gateway and the database gets converted to a 200 ICP, there are some database changes to take note of if these devices are being replaced by the embedded PRI.
If you are using call by call, the PRI card has 3 entries for call by call. If they are not programmed as fixed, you have to insert digits into the modified digit table. The embedded PRI has only 2 call by call selections. This means one of the 0's will have to be removed from the modified digit table in order for the outgoing calls to work properly.

If you are using call by call and CPN to the network, the following information may be in the digits to insert portion of the modified digit table. *4000*6*4. If this is the case, then the outgoing calls will not work.
If this is changed to *4*600*4, calls will work.
Also note that form 42 descriptor must also be set to ESF for the framing parameter. PRI cards and gateways have this value at D4.
This is being corrected on the 3.1 software load, so the embedded PRI will not care which order it received these digits.


Southwell - try this, as per this KBA (Knowledge base article)

Description/Symptoms
Outside callers could be answered by voice mail requesting to enter their password.


Body/Solutions
COS option 502 is enabled by default in the EMEM cos of the ICP. Option 613 should also be enabled to prevent the voice mail from mis-interpreting DNIS digits as an internal extension number. It will also allow the user to hear the envelope information of a voice mail should a call be forwarded to voice mail. If envelope information is not desired, you may disable option 502 and 613 without issue.

I know you were getting a prompt for a mailbox, not a password, but if the VM is seeing it as an internal call and it doesn't match a mailbox, it will ask for the mailbox. escpecially if you are only getting 4 digit DNIS.
 
RossBC - Actually no - although I do not work as much with SX200's I always use call by call and I have never used less than 3 zero's on an embedded PRI card.

In fact I'm building one right now for a Hotel. I let you know what I find out.

**********************************************
What's most important is that you realise ... There is no spoon.
 
Ross - Thank you enabling option 613 in the vmail COS fixed the issue.

I'm still have a problem getting the CNID Calling name ID to work. Is this an option that much be enabled in the COS? I have enabled option 503 Enable CLASS name but don't know if this is required.

Are there settings in the circuit descriptors that need to be changed? Debounce timer is at 100ms. Or anything else is the ISDN COS like wait for network name? If not it is possible that the provider is not sending the calling name ID.

On an outgoing PRI trunk is it not possible to display the trunk name like an outgoing LS trunk would display LINE 12 instead of the dialed number which is currently displayed "95551212"

Thanks again for you help. I'm new to ISDN as you can see.
 
there are a number of things that can affect it, and yes, the Telco may not be sending the name.
make sure COS 502 is also enabled.
what type of CO, NI1 or NI2?
what type of phone are you receiving the call on? one with soft keys?
do you see the number?
we often don't get name display here unless the caller is using the same Telco we are. If you use your own PRI to call yourself, do you see the name then?
there are a couple of KBA's that tell you how to turn on L2/L3 trace and see if the incoming call has name display depending on the protocol
 
Ross - Thanks for you help. ISDN name delivery on the providers router was not turned on. It is working now. It is DMS100 but it only show's the number unless it is on the same network as our telco.

As for the outgoing line display versus the dialed number display something that can be changed when dialing out on ISDN trunks? eg "95551212" versus LINE 12
 
sorry, I forgot to comment on that.
I am unaware of a way to modify that. I assume you are wanting to know the trunk # for troubleshooting purposes?
I wonder what would happen if you put it on hold and then pressed the superkey and then the held line. it might say which trunk was in use, or it might just show the number dialed again.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top