Phantom digits inserted in a PRI

[Bunkerman]

I have an 81C connected to a Cisco 2851 using a T1 PRI. I'm sending 96240XX DN's for the Cisco to use. I set up DSC 96240 so that all 96240XX numbers are routed to this PRI.
The problem is when you dial 96240XX, three digits are inserted in front of the number. when I call from an outside commercial number a 100 is inserted. When I call from a phone on the 81C, a 103, 104, 105, or 107 is inserted, depending on what phone you call from.
I don't know where these digits are coming from and I need to get rid of them. They cause the wrong number to be sent to the Cisco 2851. Can anyone shed light?
Note that the PRI leaves the 81c through a Cisco 3800 series router over a DS-3 to a Cisco 3800 then to the Cisco 2851 at the distant end..

 

[911guru]

This is TCOS (Traveling Class of Service) and is due to the fact that the signalling is set to ESN5. Set the Signalling to STD and you will be fine.

911Guru

http://pbx-e911.com

 

[911guru]

That's the SIGO prompt in the Route Data BLock, by the way.
Sorry forgot to mention that!

911Guru

http://pbx-e911.com

 

[tnphoneman]

Good catch.

Signature===========================================
Artificial Intelligence Is No Match for Natural Stupidity.

The latest survey shows that 3 out of 4 people make up 75% of the population.

The original point and click interface was a Smith & Wesson.

Red meat is not bad for you, it is the green fuzzy meat that is bad.

 

[Bunkerman]

That sure was it. Thank you very much, I don't think I could have found that in the book. I thought the tcos was only one digit and didn't interfer with the dialed digits.
I couldn't delete the digits with DMI but the Cisco could to make a call go thru. Now we don't have to worry about it.

 

[911guru]

I used to remember what each digit was.

The last one I know for sure is NCOS.
The middle one was Customer (i think)
The first one might be the PNI

Anyone??

911Guru

http://pbx-e911.com

 

[tnphoneman]

I think the ncos is a 2 digit field to account for 0 to 99.

Signature===========================================
Artificial Intelligence Is No Match for Natural Stupidity.

The latest survey shows that 3 out of 4 people make up 75% of the population.

The original point and click interface was a Smith & Wesson.

Red meat is not bad for you, it is the green fuzzy meat that is bad.

 

[911guru]

Good point. So do you agree the first is the PNI?

911Guru

http://pbx-e911.com

 

[tnphoneman]

First digit is the TGAR of the set.

Signature===========================================
Artificial Intelligence Is No Match for Natural Stupidity.

The latest survey shows that 3 out of 4 people make up 75% of the population.

The original point and click interface was a Smith & Wesson.

Red meat is not bad for you, it is the green fuzzy meat that is bad.

 

[Bunkerman]

The TGAR of the sets I was calling from is 2. I remember the PNI being 1 in the RDB.

 

[911guru]

Duh!

I'm sitting here next to 3 CS1000 systems! Why am I guessing!?

The last 2 digits are definitely NCOS. Good call TN. Here is an example of a call with NCOS 0 and NCOS 99:

PROGRESS: ORIG ADDR IS NOT ISDN 
CALLING #:5556507        NUM PLAN: E164/SUBSCRIBER (NXX)/LOCL 
CALLED  #:[!]100[/!]911         NUM PLAN: PRIVATE/UNKNOWN (UNKNOWN) 

PROGRESS: ORIG ADDR IS NOT ISDN 
CALLING #:5556507        NUM PLAN: E164/SUBSCRIBER (NXX)/LOCL 
CALLED  #:[!]199[/!]911         NUM PLAN: PRIVATE/UNKNOWN (UNKNOWN)

Changing the TGAR to 5 and the PNI to 2 did not change the first digit of 1. Now I am intrigued! Thinking about it it HAS to be a single digit entity. That rules out customer (I'm in CUST 0 anyway) and PNI can be a 5 digit number.

Can't be TARG on the Route as that can be more than 1 there, and I see nothing else in either the TNB or RDB that it could be.

This is going to drive me nuts. Time to dig out the old notebooks.

911Guru

http://pbx-e911.com