term attendant-group 1 cid 0x239

[CarlosPrex]

Hi
Customer has an old Definity R9.5 system running with no problems.

DS1 trunk group has DIGIT TREATMENT: insertion, DIGITS: 9* and ARS DIGIT CONVERSION TABLE REPLACING STRING to ext. 150 working since installed.

Today all incoming calls instead of going to ext 150, go to ext. 605, which is declared as NIGHT DESTINATION on CHANGE LISTED DIRECTORY NUMBERS
Customer says he formerly had attendant 302D, but since 5 years ago it was replaced for a 1408 digital phone with no problem on incoming calls.

11:34:46 Calling party trunk-group 10 member 2 cid 0x239
11:34:46 Calling Number & Name NO-CPNumber TRONCAL DIGIT
11:34:46 tone-receiver 01A0205 cid 0x239
11:34:46 active trunk-group 10 member 2 cid 0x239
11:34:47 dial 9*5
11:34:47 term attendant-group 1 cid 0x239
11:34:47 dial 605
11:34:47 busy station 605 cid 0x239
11:34:48 idle trunk-group 10 member 2 cid 0x239


I noticed that TERM ATTENDANT-GROUP 1 on the trace, I don´t know why calls are being treated that way instead of the ARS DIGIT CONVERSION TABLE
System Time is correct.

Any help would be highly appreciated.

 

[G van Hamburg]

I think there is a diable night-service command for that. Perhaps the system was rebooted? disp init-causes will give you more on that. But it can cause the system to go in night service.

Freelance Certified Avaya Aura Engineer

 

[smokinjoe2938]

Agreed sounds like it is in night service