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

route-to vector command failing

Status
Not open for further replies.

a1bandit

Technical User
Jun 30, 2004
16
0
0
US
I have built a vector that uses a route-out command to route to an external LD number. If I call the LD number from my phone it works fine. When I call the VDN it disconnects me. The VDN has the same COR that I have. I did a list trace from my phone when calling the VDN because it gives more info than just tracing the Vector.
Here is what I get:


172.16.254.105:39908 uid:0x8bd9
13:15:20 ring vector 93 cid 0xae7
13:15:20 dial 91801599 route:ARS
13:15:20 ring trunk-group 1 cid 0xae7
13:15:20 dial 918015995898 route:ARS
13:15:20 route-pattern 3 preference 1 cid 0xae7
13:15:20 seize trunk-group 1 member 83 cid 0xae7
13:15:20 Setup digits 18015995898
13:15:20 Calling Number & Name NO-CPName
13:15:20 denial event 1166: Unassigned number D1=0x8bd9 D2=0x1
13:15:20 idle trunk-group 1 member 83 cid 0xae7

I notice the Denial Event 1166 but can't find much info on it as it relates to the Unassigned number. My trunks are PRI. One other interesting tidbit is if the route-to number is to a local number it works fine. I am not sure where the hangup is. Any help would be appreciated.
 
The problem is when you have an incoming toll-free number over ISDN facilities and you try to tandem a call out over the same ISDN facilities. There is a component of the ISDN message set that carries call-type information. What we have to do is create a new Network Specific Facility indicator that deletes the originating call type. Typically we use 'strip3' with a nsf of 3. This new nsf is used on the outbound routing of all toll-free numbers. Deleting it has no affect on any other calls.

Kevin

display isdn network-facilities
NETWORK-FACILITIES
Facility Facility
Name Type Coding Name Type Coding
sub-operator 0 00110 mega800 1 00010
operator 0 00101 megacom 1 00011
outwats-bnd 1 00001 inwats 1 00100
sdn 1 00001 wats-max-bnd 1 00101
accunet 1 00110 lds 1 00111
i800 1 01000 multiquest 1 10000
strip3 3


display route-pattern 13
Pattern Number: 13

Grp. FRL NPA Pfx Hop Toll No. Delted IXC
No. Mrk Lmt List Digits Digits
1: 9 2 704 1 user 2: user
3: user
4: user 5: user 6: user
BCC VALUE TSC CA-TSC ITC BCIE Service/Feature BAND No. Numbering LAR
0 1 2 3 4 W Request Dgts Format
Subaddress
1: y y y y y n n bothept strip3 none
 
I created the strip3 facility and added it to my route but got an error inidicating it's only for CBC trunks (Call by Call I'm assuming) which I don't have. Did I miss something?
 
I added the NSF strip3 and when I tried to add it to my route pattern it indicated it was only for CBC trunk groups (Call by Call I'm assuming).

Am I missing something else?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top