Can dial 1+ but not 011 on PRI

[jlk53]

This is a continuation of my last thread. This job is throwing everything at me. The 81C has 2 PRI's, each going to a different carrier. On the one I am installing, I can make all types of calls except 011 calls. I can make 011 calls on the other PRI. When I look at my DCH messaging I see all the digits going except the 011. That is why the call is not going thru. I see the 011 going on the other route. I have compared and can find no difference except they are set up as TIE and mine is DID. The IFC is NI2. Any thoughts why I would not be sending the 011. Thanks

 

[johnpoole]

the rlb is sending 011 to the right route? if so is one route vce and the other vod? that can cause problems.. where does the 011 go, reorder? and ld 90/86 are the same?

john poole
bellsouth business
columbia,sc

 

[GHTROUT]

The order in which to troubleshoot is

In LD90, what RLI does SPN 011 point to (or, if no 011 exists, what RLI does SPN 0 point to)

Now tht you know the RLI, you know the Trunk Route(s) from the LD86 ENTR responses. LD86 ROUT = the Trunk Route.

As for TIE vs. DID - if a call from a user or from another TIE route is to end up on the public network - in other words, ring a phone outside of your PBX - the route delivering that call from the PBX to the outside world should never be TIE. If the TIE signaling is required, the routew should be built at DID.... This because TIE is unaeffected by most CLS and Disconnect Control restrictions











~

http://www.GHTROUT.com/

 

[jlk53]

Hi Guys, here is a little more information. At this point I am not using ESN. I dial the ACOD for both routes when testing. Both routes are set to VOD. On my route the ACOD is 59. when I dial 5901161396694916, I see 61396694916 being sent down the DCH. The 011 is stripped like part of the ACOD. When I do the same on the other route with ACOD of 69 I see 01161396694916 on the DCH. Any futher thoughts?

 

[johnpoole]

is the far end interface the same switch? and compare net_data between the two sites..

john poole
bellsouth business
columbia,sc

 

[jlk53]

All is the same on both ends. I discovered that if I put a DMI entry to insert 011 for any 011 calls, the call goes thru and you see the second 011 going down the DCH. Strange one but it works so I will leave it. Thanks for all the help.

 

[johnpoole]

in reply to your last thread, either your cdb or rdb is stripping those digits.. look at options in the cdb.. you can dial the number so it's in ld 90, it goes out on the right route so 86 is clean, you don't have a dgt in either switches rlb.. so it's not broke but it doesn't work.. cdb or PATCH

john poole
bellsouth business
columbia,sc

 

[johnpoole]

just had a thought, there is a place in 87? where you define the limits of ac1 and 2, you can allow or deny npa, nxx and spn, check that.. tomorrow i will try to find it in my 81 and post.. worth a thought

john poole
bellsouth business
columbia,sc

 

[jlk53]

any luck finding where you define limits of AC1 and AC2?

 

[jlk53]

After reviewing the CDB I have found this, but have no idea and could not locate what it means. Not sure if it has any bearing on why I cannot dial 011 form 1 of the T1's. Can anyone help?

FTR_DATA
**DAPC**PREFIX TABLE NO: 00 **
UNKN**INTL**NATL**ESPN**LOCL**ELOC**ECDP**
UNKN*
E164* 00 0
PRIV*
E163* 00 0
TELX*
X121*
NATL*

 

[FDM816]

jlk53 UNKN is unknown, intl is international, natl is national. If you are set as NI2 the CO is looking for you to tell the switch whether the call in unknown, international or national. If you send unknown and pass the 011 the call will go thru. If you are set as international and send 011 the call will be blocked by the Central Office. What type of CO switch are you connected to? If it is a Nortel DMS they will block the hell out of your calls if not setup properly in the isdn setup message. So if you are able to debug your setup message and see in there that the call was setup with intl and you send 011 it will get block. If you are sending natl with 011 you will get blocked. If you send unknown and have 011 it should go thru. ISDN national 2 is very particular.
If you can not debug your d-channel then any CO tech should be able to put on a d-ch analyzer and look at the setup message to tell you what is wrong. The CO should see the called number plan as isdn telephony rec e164 and the number type unknown, international, national but the pbx has to set the call up correctly. If all else fail numbering plan type unknown type of number unknown and make sure to send the 011

 

[johnpoole]

try a stat serv in 96

john poole
bellsouth business
columbia,sc

 

[jlk53]

Sorry for the delay but was off for a bit. Once again, thanks for the information. Still confused as to wwher I se the call type. Here is a sample of the DCH messaging. The calls complete fine for local and 1+. It is the 011 that is not sent on the DCH. Any further help is apreciated.

DCH 2 UIPE_OMSG CC_SETUP_REQ REF 00000017 CH 19 23 TOD 15:08:38
PROGRESS: ORIGINATING END IS NOT ISDN
CALLED #:6771020 NUM PLAN: E164

DCH 2 UIPE_IMSG CC_PROCEED_IND REF 00000017 CH 19 23 TOD 15:08:38

DCH 2 UIPE_IMSG CC_PROGRESS_IND REF 00000017 CH 19 23 TOD 15:08:40
PROGRESS: INBAND INFO OR PATTERN IS AVAIL

DCH 2 UIPE_IMSG CC_SETUP_CONF REF 00000017 CH 19 23 TOD 15:08:56

DCH 2 UIPE_OMSG CC_DISC_REQ REF 00000017 CH 19 23 TOD 15:09:00
CAUSE: #16 - NORMAL CALL CLEARING

DCH 2 UIPE_IMSG CC_RELEASE_IND REF 00000017 CH 19 23 TOD 15:09:00