pmealey

I have been working towards getting my video conferencing system to work over ISDN (supplied via a TN556C card in my switch) and as suggested in some other threads, my issue is now with my long distance carrier. They will not support the bandwidth requirements for video, but I want to keep them for voice calls. My idea is to use 1010xxx dialing from my video conferencing system to select a LD carrier that will handle video calls, but I have been unable to get it to work.
I dial 1010xxx-1-123-1234567 and I receive a "you must dial a 1 before the area code when you dial this number" message. The 1 is there when I dial, but it must be disappearing somewhere along the way. Here is my ars analysis:

ARS DIGIT ANALYSIS TABLE
Location: all Percent Full: 13

Dialed Total Route Call Node ANI
String Min Max Pattern Type Num Reqd
1010xxx 18 18 4 fnpa n


Here is route pattern 4:

Pattern Number: 4
Grp FRL NPA Pfx Hop Toll No. Inserted DCS/ IXC
No Mrk Lmt List Del Digits QSIG
Dgts Intw
1: 2 3 612 1 n user
2: n user
3: n user
4: n user
5: n user
6: n 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 y as-needed bothept none
2: y y y y y n n rest none
3: y y y y y n n rest none
4: y y y y y n n rest none
5: y y y y y n n rest none
6: y y y y y n n rest none


I have also attached the above switch setting information in a text file because the text gets reformatted a bit in these posts and sometimes becomes hard to read.
I have a Definity G3csi V11 switch.

I would appreciate any suggestions. Thanks.

Attached Files

1010info.txt (2.5 KB, 8 views)

liquidvw

Can you make a test call whiel running a list trace on the first data module. Then post your list trace. That may help.

PBXtech.info

 

stubborne

"I dial 1010xxx-1-123-1234567 and I receive a "you must dial a 1 before the area code when you dial this number" message."

You're dialing '9' (or your FAC) 1st, right? 9-1010xxx-1-123-1234567

__________________
Stu

stubborne

I see via your trace you did...
10:35:47 tone-receiver 01A0203 cid 0x31
10:35:47 active station 223 cid 0x31
10:35:48 dial 91010288
10:35:48 term trunk-group 2 cid 0x31
10:35:48 dial 9101028819259246000
10:35:48 route-pattern 4 preference 1 cid 0x31
10:35:48 seize trunk-group 2 member 21 cid 0x31
10:35:48 Setup digits 1010218819259246000
10:35:48 Calling Number & Name NO-CPNumber NO-CPName
10:35:48 Proceed trunk-group 2 member 21 cid 0x31

Notice in the setup digits string a '1' was inserted after the 2? Try Prefix Mark = 0 or 4 in the route pattern.

__________________
Stu

pmealey

I tried setting pfx mrk to both 0 and 4 and I received a fast busy. Earlier in the week I had left the pfx mrk blank and gotten a fast busy also, but I then asked my local provider to trace the call and they said that the only difference that they saw between my "regular" long distance calls and my 1010 calls was that there was an additional network transit message sent with the 1010 calls (I don't know what that means). If we assume that this network transit message is also the problem with prefix marks of 0 and 4, then what to do about it?
I have included list traces of calls made with prefix marks of 0 and 4 and also a "regular" long distance call. The regular call uses route pattern 3, but it has the same settings as the route pattern 4 listing I included in my original post (with a pfx mrk of 1).

with prefix mark = 0:
21:01:06 dial 91010288
21:01:06 term trunk-group 2 cid 0x1e9
21:01:13 dial 9101028819259246000
21:01:13 route-pattern 4 preference 1 cid 0x1e9
21:01:13 seize trunk-group 2 member 22 cid 0x1e9
21:01:13 Setup digits 101028819259246000
21:01:13 Calling Number & Name NO-CPNumber NO-CPName
21:01:13 Proceed trunk-group 2 member 22 cid 0x1e9
21:01:13 denial event 1164: ISDN call reject D2=CV D1=0x17 D2=0x880429
21:01:13 idle trunk-group 2 member 22 cid 0x1e9

with prefix mark = 4:
20:55:06 dial 91010288
20:55:06 term trunk-group 2 cid 0x1e2
20:55:16 dial 9101028819259246000
20:55:16 route-pattern 4 preference 1 cid 0x1e2
20:55:16 seize trunk-group 2 member 22 cid 0x1e2
20:55:16 Setup digits 101028819259246000
20:55:16 Calling Number & Name NO-CPNumber NO-CPName
20:55:16 Proceed trunk-group 2 member 22 cid 0x1e2
20:55:16 denial event 1164: ISDN call reject D2=CV D1=0x17 D2=0x880429

"regular" long distance call
21:01:59 dial 91925924
21:01:59 term trunk-group 2 cid 0x1e9
21:01:59 dial 919259246000
21:01:59 route-pattern 3 preference 1 cid 0x1e9
21:01:59 seize trunk-group 2 member 22 cid 0x1e9
21:01:59 Setup digits 19259246000
21:01:59 Calling Number & Name NO-CPNumber NO-CPName
21:01:59 Proceed trunk-group 2 member 22 cid 0x1e9
21:02:00 Alert trunk-group 2 member 22 cid 0x1e9
21:02:03 active trunk-group 2 member 22 cid 0x1e9


Thanks

oozenoz

If they are referring to the 'network specific facility' information element, this is required by the ISDN spec.

Check out this post:

Denial event 1164 ISDN call reject


Can get the decoded printout of the d-channel messages from your local carrier, from SETUP thru to the RELEASE COMPLETE?

__________________
- calvin

PBXtech.info

 

pmealey

Thanks!! That worked.
I left the pfx mrk blank and added sdn to the service/feature field in the ch route-pattern screen and all is well.

Best regards,
Pat

oozenoz

sweet! :D

one quick question, in doing some research I found that for SDN calls, the numbering plan information (which identifies the number type format to the CO switch) is supposed to be set to 'private' - what is yours set for?

__________________
- calvin

pmealey

If you are referring to the numbering plan field on the ch route-pattern screen, then mine is blank. The book says that blank means E.164(1).
I changed it from blank to lev0-pvt and when I dialed a 1010 number I got a message saying "that it was unnecessary to dial a zero when dialing this number" (what zero?).
Since it seems to work with a blank, should I worry about what the documentation says?

oozenoz

There's a reason why you would get that message - but is it worth digging into since what you have is working? One man's opinion - changing your programming just to match the documentation increases the probability that you will be doing one or more of the following:

a) pulling an all-nighter to fix what you have broken;
b) sweating profusely as you try to explain to your boss why you did what you did to break your system;
c) posting your resume on Monster.

I follow documentation as closely as possible, unless I really understand what those settings are for and feel absolutely confident in changing them - or just downright stupid.

I'll leave you with this thought:

"Documentation is like *** - when it's good, it's very, very good. When it's bad, it's better than nothing."

__________________
- calvin