Tac not working engage tone.displayed all config

[Arvindsunny]

trunk

Group Number: 1 Group Type: isdn CDR Reports: y
Group Name: Colt Courbevoie COR: 1 TN: 1 TAC: #90
Direction: two-way Outgoing Display? n Carrier Medium: PRI/BRI
Dial Access? y Busy Threshold: 25 Night Service:
Queue Length: 0
Service Type: public-ntwrk Auth Code? n TestCall ITC: rest
Far End Test Line No:
TestCall BCC: 4



cor

FRL: 7 APLT? y
Can Be Service Observed? n Calling Party Restriction: all-toll
Can Be A Service Observer? y Called Party Restriction: none
Time of Day Chart: 1 Forced Entry of Account Codes? n
Priority Queuing? n Direct Agent Calling? n
Restriction Override: none Facility Access Trunk Test? y Restricted Call List? n Can Change Coverage? n
Unrestricted Call List: 1 2 3 4 5 10
Access to MCT? y Fully Restricted Service? n
Group II Category For MFC: 7 Hear VDN of Origin Annc.? y
Send ANI for MFE? n Add/Remove Agent Skills? y
MF ANI Prefix: Automatic Charge Display? n
Hear System Music on Hold? y PASTE (Display PBX Data on Phone)? n
Can Be Picked Up By Directed Call Pickup? y
Can Use Directed Call Pickup? y
Group Controlled Restriction: inactive

List trace station

12:52:30 G711A ssff ps:20
rgn:1 [10.208.16.195]:41430
rgn:1 [10.208.16.52]:2080
12:52:32 dial #90
12:52:32 term trunk-group 1 cid 0x4d6
12:52:32 dial #90
12:52:32 seize trunk-group 1 member 20 cid 0x4d6
12:52:32 Setup digits
12:52:32 Calling Number & Name 174310288 NO-CPName
12:52:32 denial event 1218: Invalid IE contents D1=0x863a D2=0x280764
12:52:32 idle trunk-group 1 member 20 cid 0x4d6
12:52:35 TRACE COMPLETE station 331288 cid 0x4d6

 

[AvayaTier3]

You cannot TAC dial ISDN trunks

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

39 years Bell, AT&T, Lucent, Avaya
Tier 3 for 29 years and counting
[URL unfurl="true"]http://bshtele.com[/url]

 

[Arvindsunny]

You can tac dial isdn trunks but it will not work unless both ends of the trunk are on Avaya equipment.


do mean that my ISP (telecom opter) should use avaya and i should have avay device to use tac

 

[Smovk]

I successfully TAC to public ISDN provider and also to several different PBX (Siemens, Ericsson, AASTRA, Tenovis, IPO).
I have done it from all CM versions. Configurations was almost the same for all connections (some different setting for public,qsig or tie trunks).
Here is one example of ISDN tie trunk to AASTRA

DIAL PLAN ANALYSIS TABLE
Location: all Percent Full: 9

Dialed Total Call Dialed Total Call Dialed Total Call
String Length Type String Length Type String Length Type
* 3 fac
*6 4 dac
---------------------------------------------------------
TRUNK GROUP

Group Number: 100 Group Type: isdn CDR Reports: y
Group Name: AAstra COR: 995 TN: 1 TAC: *605
Direction: two-way Outgoing Display? n Carrier Medium: PRI/BRI
Dial Access? y Busy Threshold: 255 Night Service:
Queue Length: 0
Service Type: tie Auth Code? n TestCall ITC: rest
Far End Test Line No:
TestCall BCC: 4


TRUNK PARAMETERS
Codeset to Send Display: 6 Codeset to Send National IEs: 6
Max Message Size to Send: 260 Charge Advice: none
Supplementary Service Protocol: c Digit Handling (in/out): overlap/enbloc
Digit Treatment: Digits:
Trunk Hunt: cyclical
Digital Loss Group: 13
Incoming Calling Number - Delete: Insert: Format:
Bit Rate: 1200 Synchronization: async Duplex: full
Disconnect Supervision - In? y Out? n
Answer Supervision Timeout: 0
Administer Timers? n CONNECT Reliable When Call Leaves ISDN? n
XOIP Treatment: auto Delay Call Setup When Accessed Via IGAR? n
CPN to Send for Redirected Calls: redirecting

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

Replace Restricted Numbers? n
Replace Unavailable Numbers? n
Send Connected Number: n
Hold/Unhold Notifications? n
Send UUI IE? y Modify Tandem Calling Number: no
Send UCID? n
Send Codeset 6/7 LAI IE? y Ds1 Echo Cancellation? n

Apply Local Ringback? n
Show ANSWERED BY on Display? y
Network (Japan) Needs Connect Before Disconnect? n


----------------
SIGNALING GROUP

Group Number: 100 Group Type: isdn-pri
Associated Signaling? y Max number of NCA TSC: 0
Primary D-Channel: 002V516 Max number of CA TSC: 0
Trunk Group for NCA TSC:
Trunk Group for Channel Selection: 100 X-Mobility/Wireless Type: NONE
TSC Supplementary Service Protocol: c
ETSI CCBS Support: both-directions

-----------------
DS1 CIRCUIT PACK

Location: 002V5 Name:
Bit Rate: 2.048 Line Coding: hdb3

Signaling Mode: isdn-pri
Connect: pbx Interface: network
TN-C7 Long Timers? n Country Protocol: etsi
Interworking Message: PROGress
Interface Companding: alaw CRC? n
Idle Code: 11111111
DCP/Analog Bearer Capability: 3.1kHz

T303 Timer(sec): 4
Disable Restarts? n

Slip Detection? n Near-end CSU Type: other

Echo Cancellation? n


and trace:
list trace tac *605 Page 1
list trace tac *605 Page 1

LIST TRACE

time data

00:53:53 TRACE STARTED 07/05/2012 CM Release String cold-00.1.510.1-19528
00:54:05 dial *605
00:54:05 term trunk-group 100 cid 0x11e2
00:54:05 dial *605
00:54:05 seize trunk-group 100 member 16 cid 0x11e2
00:54:05 Setup digits
00:54:05 Calling Number & Name 8497 test
00:54:05 dial *605
00:54:05 seize trunk-group 100 member 16 cid 0x11e2
00:54:09 idle station 8497 cid 0x11e2

 

[AvayaTier3]

Digit Collection
The intention of the ISDN PRI specifications is that all digits be collected and sent
in the SETUP message for a call. This is not an absolute requirement, however.
Two methods exist for collecting digits on ISDN PRI calls, as follows:
n ISDN PRI calls routed by networking software collect all digits and send
them in the SETUP message.
n ISDN PRI calls made by dialing a trunk access code do not collect the
digits. Instead, the SETUP message is sent without the digits. The digits
are then sent in-band as with non-ISDN calls.
G2.2 does not support the use of trunk access code dialing on ISDN PRI trunks.
The primary problem with TACs on G2.2 systems is that all digits must be dialed
before expiration of the T310 layer 3 timer (10 seconds) otherwise the call will be
torn down. Thus, this limits the number of switches you can cut through within the
allotted time. G2.2 systems block ISDN PRI calls that try to use a trunk access
code to dial the call.
G3V2 systems support trunk access code dialing on ISDN PRI trunks that are not
call by call trunks or nodal services trunks. When a G3V2 system receives a
SETUP message with no digits, it returns a PROGRESS message, which
suppresses the layer 3 timers. Thus, for calls dialed with trunk access codes to
be guaranteed to work, all switches in the call path must be G3V2s (or G1s or
G3V1s).
For calls routed with AAR or ARS, G3V2 systems implement digit collection by
automatically collecting all digits before trunk seizure for all calls in a pattern
starting with the first ISDN preference encountered. For example, if the third
preference in a pattern is the first occurrence of an ISDN trunk group, all digits
will not be collected before trunk seizure for calls on the first two preferences. All
digits will be collected before trunk seizure starting with calls on the third
preference and continue for all subsequent preferences regardless of whether
they are ISDN trunk groups. Thus, if you want to collect all digits before trunk
seizure on some non-ISDN calls, you can administer the first preference of a
pattern as an ISDN trunk group containing no members. All calls on subsequent
preferences will have all digits collected before trunk seizure. This administration
is done in the routing pattern form. There are both advantages and
disadvantages to administering the patterns this way, however, as follows:

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

39 years Bell, AT&T, Lucent, Avaya
Tier 3 for 29 years and counting
[URL unfurl="true"]http://bshtele.com[/url]