NI2 Local Outbound Help

[bizzaro]

I am in the process of changing Carriers and PRI configurations. The new configuration is using NI2 connected to a DMS. We have several sites that were converted and are up and working with the same configuration. On my last implementation, when making outbound local calls, I get a fast busy. The only workaround is to configure a dmi on the route that deletes 0, inserts 0, but has ctyp set for nxx. I did not have to do this with the other 10 sites. I do notice a difference when watching the d-channel messages between a working site, the new site with dmi, and new site without dmi.
If you look at the following, you will see the failed call has an originating clid of 10 digits instead of 7. I compared clids, net_data, route data block and d-channel configurations. Any ideas?

Successful from other location
DCH 3 UIPE_OMSG CC_SETUP_REQ REF 00000102 CH 11 23 TOD 12:55:10
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:879xxxx NUM PLAN: E164 TON: LOCL
CALLED #:285xxxx NUM PLAN: E164 TON: LOCL


Failed from new location
DCH 35 UIPE_OMSG CC_SETUP_REQ REF 0000000D CH 35 23 TOD 10:22:58
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:xxx642xxxx NUM PLAN: E164 TON: NATL
CALLED #:642xxxx NUM PLAN: E164 TON: NATL


Successful from new location with dmi in place
DCH 35 UIPE_OMSG CC_SETUP_REQ REF 00000011 CH 35 23 TOD 10:26:44
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:642xxxx NUM PLAN: E164 TON: LOCL
CALLED #:642xxxx NUM PLAN: E164 TON: LOCL

 

[johnpoole]

look at the dsel value, if it's vod and needs to vce it can cause that problem.. the opposite of that is true also, it was very common in earlier rel;s, and i've seen several post lately with the same response

john poole
bellsouth business
columbia,sc

 

[bizzaro]

I have tried 3vce and now vod. Same results. I have it working both ways in other offices, without issues. What causes the messaging to be "TON: NATL" instead of "TON:LOCL"?

 

[janaya]

This is done in LD 86 when you build your RLB tables. With some LECs using NI2 you will need to set a DGT option even if you don't have to delete/insert digits and in CTYP put NPA or NXX or UKWN.

What the LEC is looking for is something to designate the call a "PUBLIC" call, or an E164 dial protocol.

You might not see it on other switches, because the LEC CO switch might not need it. As the LEC CO's upgrade most NI2 configurations will change to this.

I find that in most bigger metro areas I am having to use the DMI table now.

Hope this exlpains.

John

 

[johnpoole]

another thing to check, ld 96 stat serv.. some ni2 offices will not process calls without service msgs..

john poole
bellsouth business
columbia,sc