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

Call Forward Unconditional problem on ATM16

Status
Not open for further replies.

teletomi

Vendor
Aug 31, 2013
276
PH
Hi all, I have an IPO V2 9.0.5.. I also have ATM16.. I set all incoming group ID of ATM16 to 1. And in the ICR, line group ID 1 has a destination to operator (ext 200). The operator has 1416 phone with button 8 configured to Forward unconditional to huntgroup of 519. The problem is, when the fwd unconditional is on, and incoming call hit the ports 1-8 of ATM16, the call always go to operator. But when the call comes from port 9-16 of ATM16, forward unconditional is working. Please help.
 
Hi everyone.. Seeking your great expertise.. Please help..
 
Hi everyone..Any help will do..Appreciate your great expertise..
 
It can't be a collective group (200 is typically the main group) also forward group calls must be ticked, if it's not a group.....who knows? :)


 
Is hunt group 519 forwarding the call off-site? If so, each line needs to have trunk-to-trunk transfer enabled (which is disabled by default).
 
Hi amriddle01 and Telecomboy. Thanks for your comments. Really appreciate it! HG 519 is just a standard HG with two extensions. But I think this is a kind of bug on R9 SP5. Here are what I did on my troubleshooting:

Test 1:

*ATM16 is patched in on expansion port 1 of control unit

-on navigation pane, ticked Control unit. Deleted ATM16.
-on navigation pane, ticked Line. Deleted all analogue trunks of ATM16.
-save and reboot.
-patched in ATM16 on expansion port 6 (vacant) of control unit.
-save and reboot.

*after rebooting, noticed that there are no Line Appearance ID labeled on every trunks of ATM16 (It should be automatically assigned right?) but left if blank anyway.

-configured all incoming line group ID of ATM16 to 1.
-configured ICR of LG ID:1 and destination is operator (ext 200)
-turned ON FWD UNCOND which is configured on button 8 of operator's phone (1416)
-patched in a sample analog trunk in port 1 of ATM16.
-called the trunk and fwd uncond is working.
-Repeat the procedure on all ports of ATM16 and confirmed fwd uncond is working.

Test 2:

-on navigation pane, ticked Control unit. Deleted ATM16.
-on navigation pane, ticked Line. Deleted all analogue trunks of ATM16.
-save and reboot.
-repatched ATM16 back in expansion port 1 of control unit.
-save and reboot.
-noticed again that there are no Line Appearance ID labeled on every trunks of ATM16 but leave it blank anyway.
-configured all incoming line group ID of ATM16 to 1.
-turned ON FWD UNCOND which is configured on button 8 of operator's phone (1416)
-patched in a sample analog trunk in port 1 of ATM16.
-called the trunk and fwd uncond is working.
-Repeat the procedure on all ports of ATM16 and confirmed fwd uncond is working.

Test 3:

-sent my original config to control unit.
-save and reboot.
-turned ON FWD UNCOND which is configured on button 8 of operator's phone (1416)
-patched in a sample analog trunk in port 1 of ATM16.
-called the trunk and fwd uncond is not working again.
-Repeat the procedure on all ports of ATM16 and confirmed fwd uncond is working only on ports 9-16 but not on ports 1-8.

Test 4:

-deleted all descriptions of "Telephone Number" (Line>analogue trunk>Line Setting tab;Telephone Number) of every analogue trunk of ATM16
-save
-repeat the test, but still fwd uncond is still not working on ports 1-8 only.

Test 5:

-Tried to delete the Line Appearance ID of port 1 of ATM16.
-save and reboot.
-patched in a sample analog trunk in port 1 of ATM16.
-called the trunk and fwd uncond is working.
-Repeat the procedure on all ports of ATM16 and confirmed fwd uncond is not working only on ports 2-8.

Test 6:

-Tried to delete the Line Appearance ID of ports 1-8 of ATM16.
-save and reboot.
-patched in a sample analog trunk in port 1 of ATM16.
-called the trunk and fwd uncond is working.
-Repeat the procedure on all ports of ATM16 and confirmed fwd uncond is working on all ports.

Findings:
-Leaving the Line Appearance IDs of ports 1-8 blank make fwd uncond working.
-But Line Appearance IDs are definitely needed and must be configured on the buttons of operator's phone (1416) to monitor the status trunks which is one of the requirements of the customer.


What do you think experts? Need to upgrade to 9.1?

 
Why are customers always so keen on using line appearance keys? What are they afraid of missing exactly?

If it's busy, it's busy. If it rings, answer it.

Just for the sake of argument, try with your original config:
-remove LA's
-add 2 or more CA's
-see what happens.
 
Hi NLPeterK, thanks for your comments. Already did that but issue still persist. I also created a ticket to Avaya support regarding the issue and waiting for their recommendation. I'll updated you all once available.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top