Lucent Definity connected to Siemens Realitis Isdx usig Q931

[mckevis]

Hi There

I have an ISDX CLI I/F connected to a Lucent DS1 I/F set up as a 30 Channel Q931 all is working well with calls routing both ways using routing patterns.
I can,t seem to use the Dial access Code eg 116 on the Lucent ie get a Denial Event when I list Trace Tac 116.
If I connect 2 DS1 cards Back To Back with the same settings I can dial the Tacs ok which indicates the issue is on the ISDX .
Below are traces from both switches and the Trunk Form on the Lucent

Isdx TRQM DLI 0410

]Call From 77502 on Lucent to 2516 on ISDX

?> 0410 - 08 002:0:2D90 SETUP
sending complete
bearer capability (003) 90 90 A3
chan id (003) 10100001 10000011 001
progress ind (002) 81 83
disp (014) Steve Mckevitt
calling p.n (006) A1 77502
called p.n (008) A1 7902516
31/01/13 11:25:36
< 0410 - 08 002:1:2D90 CALL PROC
chan id (003) 10101001 10000011 001
31/01/13 11:25:37
< 0410 - 08 002:1:2D90 ALERT
chan id (003) 10101001 10000011 001
31/01/13 11:25:39
< 0410 - 08 002:1:2D90 CONN
chan id (003) 10101001 10000011 001
connected number (006) 00 A3 2516
31/01/13 11:25:39
> 0410 - 08 002:0:2D90 CONN ACK
31/01/13 11:25:43
> 0410 - 08 002:0:2D90 DISC
cause (002) type=81 value=016
31/01/13 11:25:43
< 0410 - 08 002:1:2D90 REL
31/01/13 11:25:43
> 0410 - 08 002:0:2D90 REL COM


XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX


Result of TRQM when Tac 116 dialed on Lucent

> 0410 - 08 002:0:3192 SETUP
bearer capability (003) 90 90 A3
chan id (003) 10100001 10000011 001
progress ind (002) 81 83
disp (014) Steve Mckevitt
calling p.n (006) C9 77502
called p.n (001) 80
31/01/13 11:27:56
< 0410 - 08 002:1:3192 REL COM
cause (002) type=81 value=028

Trace on Trunk Tac 16 on Lucent
11:32:43 dial 116
11:32:43 term trunk-group 16 cid 0x218
11:32:43 dial 116
11:32:43 seize trunk-group 16 member 1 cid 0x218
11:32:43 Calling Number & Name 77502 Steve Mckevit
11:32:43 denial event 1186: ISDN invalid numbr format D1=0x4a D2=0x96011c
11:32:43 idle trunk-group 16 member 1 cid 0x218
11:32:44 idle station 77502 cid 0x218


TRUNK GROUP Form on Lucent

Group Number: 16 Group Type: isdn CDR Reports: y
Group Name: Isdx mg 81 code 709 q931 COR: 93 TN: 1 TAC: 116
Direction: two-way Outgoing Display? n Carrier Medium: PRI/BRI
Dial Access? y Busy Threshold: 99 Night Service:
Queue Length: 0
Service Type: tie Auth Code? n TestCall ITC: unre
Far End Test Line No:
TestCall BCC: 4
TRUNK PARAMETERS
Codeset to Send Display: 0 Codeset to Send National IEs: 6
Max Message Size to Send: 260 Charge Advice: none
Supplementary Service Protocol: c Digit Handling (in/out): overlap/overlap
Digit Treatment: Digits:
Trunk Hunt: ascend
Digital Loss Group: 13
Calling Number - Delete: Insert: Numbering Format:
Bit Rate: 1200 Synchronization: async Duplex: full
Disconnect Supervision - In? y Out? y
Answer Supervision Timeout: 20



TRUNK FEATURES
ACA Assignment? n Measured: both Wideband Support? n
Internal Alert? y Maintenance Tests? y
Data Restriction? n NCA-TSC Trunk Member:
Send Name: y Send Calling Number: n
Used for DCS? n
Suppress # Outpulsing? n Numbering Format: private
Outgoing Channel ID Encoding: preferred UUI IE Treatment: service-provider

Replace Restricted Numbers? n
Replace Unavailable Numbers? n

http://www.tek-tips.com/threadminder.cfm?pid=690

Send Connected Number: y

Send UUI IE? y
Send UCID? n
Send Codeset 6/7 LAI IE? y Ds1 Echo Cancellation? n



SBS? n Network (Japan) Needs Connect Before Disconnect? n



any thoughts please
Thanks steve

 

[fataldata]

I'm on North American standards so we don't use E1's but on my ISDN trunks we cannot use TAC codes to directly access them for testing. To test individual members on our system we have to setup a separate trunk with just the member we wish to test.

 

[fataldata]

On a different note however the denial event I get is not the same as the one you posted. If this is possible on your system you may try altering the trunk Numbering Format which looks like it has no entry on your post.

list trace station 8996 Page 1

LIST TRACE

time data

07:23:33 tone-receiver 14AXX01 cid 0x10a8
07:23:33 active station 8996 cid 0x10a8
07:23:34 dial 8068
07:23:34 term trunk-group 114 cid 0x10a8
07:23:34 dial 8068
07:23:34 seize trunk-group 114 member 16 cid 0x10a8
07:23:34 Calling Number & Name xxxxxx8996
07:23:34 denial event 1190: No circ/chan avail D1=0x8308 D2=0x280222
07:23:34 idle trunk-group 114 member 16 cid 0x10a8
07:23:35 idle station 8996 cid 0x10a8

 

[mattKnight]

If I read your trace from the ISDX correctly

You are dialling 2516 and the ISDX is receiving 7902516

The denial event suggests that you have an invalid number... Is 7902516 a vlaid number on the ISDX

Can you trace a direct dialled call to the 2516 number?



Take Care

Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.

 

[mckevis]

Hi Both

Firstly many thanks for the feedback,
firstly Fataldata, I have tried changing the Number Format on the Lucent and this makes no difference, Matt 7902516 is a correct number on the Isdx .
Not sure if I explained myself correctly but I can dial over the circuits both ways with no issues by using the uniform dial plan and AAR to route path using Trunk Group 16 , but it would be convenient to use the TAC code on the Lucent if possible ie 116.

Below is the TRQM trace on 0410 on the ISDX when a TAC code is dialed from the Lucent and you see that the called party number on siezure is 80 not sure where these digits are generated from and by looking at the 2 traces there is a difference between the calling p n number in that on the failed call you get (calling p.n (006) C9 77502 )and on the successful call you get (calling p.n (006) A1 77502).
FAILED CALL TRACE ON ISDX USING TAC CODE ON LUCENT
> 0410 - 08 002:0:3192 SETUP
bearer capability (003) 90 90 A3
chan id (003) 10100001 10000011 001
progress ind (002) 81 83
disp (014) Steve Mckevitt
calling p.n (006) C9 77502
called p.n (001) 80
31/01/13 11:27:56
< 0410 - 08 002:1:3192 REL COM
cause (002) type=81 value=028

SUCCESSFUL CALL TO ISDX USING UNIFORM DIAL PLAN ETC

?trqm 0410
04/02/13 10:19:05
> 0410 - 08 002:0:63AB SETUP
sending complete
bearer capability (003) 90 90 A3
chan id (003) 10100001 10000011 001
progress ind (002) 81 83
disp (014) Steve Mckevitt
calling p.n (006) A1 77502
called p.n (008) A1 7902516
04/02/13 10:19:05
< 0410 - 08 002:1:63AB CALL PROC
chan id (003) 10101001 10000011 001
04/02/13 10:19:05
< 0410 - 08 002:1:63AB ALERT
chan id (003) 10101001 10000011 001
04/02/13 10:19:08
> 0410 - 08 002:0:63AB DISC
cause (002) type=81 value=016
04/02/13 10:19:08
< 0410 - 08 002:1:63AB REL
04/02/13 10:19:08
> 0410 - 08 002:0:63AB REL COM

I can dial the TACS on the ISDX with no issues and also Direct Trunk Select on the ISDX .
If I connect Trunk group 16 to Trunk Group 15 Back to Back on the Lucent I can dial the TACS ok

Hope this is clearer.

Regards

 

[mattKnight]

This here is your problem

> 0410 - 08 002:0:3192 SETUP
<snip>
calling p.n (006) C9 77502
called p.n (001) 80
31/01/13 11:27:56
< 0410 - 08 002:1:3192 REL COM
cause (002) type=81 value=028

<snip>
calling p.n (006) A1 77502
called p.n (008) A1 7902516

Using the TAC, you are sending the calling-party-number as Type-of-number Subscriber and Number-plan-type private (indicated by C9)
you are also sending the Called-party-number as Type-of-number unknown and Number-plan-type unknown (indicated by 80)

Using UDP etc,
you are sending the both the calling-party-number and called-party-number as Type-of-number National and Number-plan-type ISDN (indicated by A1)


This is confirmed by the denial event code denial event 1186: ISDN invalid numbr format

I suspect that changing Suppress # Outpulsing? n Numbering Format: private
to Suppress # Outpulsing? n Numbering Format: public

and maybe
Calling Number - Delete: Insert: Numbering Format:
to
Calling Number - Delete: Insert: Numbering Formatub-unk



Take Care

Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.

 

[mckevis]

Hi Matt made the changes you highlighted but still not working dialing the TAC the TRQM message on the ISDX has changed as below though .
I also tried different combinations of
Calling Number - Delete: Insert: Numbering Formatub-unk

Thanks

Steve




04/02/13 12:19:26
> 0410 - 08 002:0:77B5 SETUP
bearer capability (003) 90 90 A3
chan id (003) 10100001 10000011 001
progress ind (002) 81 83
disp (014) Steve Mckevitt
calling p.n (006) A1 77502
called p.n (001) 80
04/02/13 12:19:26
< 0410 - 08 002:1:77B5 REL COM
cause (002) type=81 value=028

 

[mattKnight]

>Calling Number - Delete: Insert: Numbering Formatub-unk

I can see the difference in the
> calling p.n (006) A1 77502

But the CalledPN is still the same. You can change the call type from other places (like the route pattern, AAR or ARS) but not it seems from the trunk group.

You might find it more productive to tweak the settings on the ISDX to accept different formats from the Avaya - but is it really worth it for TAC dial access?

Calling Number - Delete: Insert: Numbering Formatub-unk affect inbound numbers only - so it is irrelevant here.




Take Care

Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.

 

[mckevis]

Hi Matt

I agree with you been like this for years now, so no big deal but was more from interest ( never take a drum apart to see what makes the noise LOL ), anyway tomorrow I will be connecting 4 of these ccts to a Server with ISDN i/f cards ( no details as yet to make of server etc ) which is going handle the calls from and back to the Lucent so I am sure I maybe here if any issues etc.

Many thanks for your help though appreciate it

Steve