Hi all,
Having difficulties setting up the remote Audix over a DCS-link.
In software release 9.5 we see that the choice that the book describes is not available. For setting up the huntgroup we can choose rem-vm but not rem-audix what the book tell us to do.
Our DCS-link is up and running, at least we can make phonecalls over the link. If the remote location dials the Audix he is recognised by the system (CLI is arriving in the IntuityAudix because he can press pound instead of his number+pound).
Appendix B in the IP- and Networking book isn't very clear. Why the heck must Avaya use all types of links in their example. Somewhere we must be missing the clue.
Our Intuity is configured over LAN as link 1.
I think our problems lies in the Communications Processor Channels. That part is confusing us.
When tracing the calls we see a message that the Audix is not available and we get busy-tone.
Anyone any idea..
Thanks in advance,
John
Having difficulties setting up the remote Audix over a DCS-link.
In software release 9.5 we see that the choice that the book describes is not available. For setting up the huntgroup we can choose rem-vm but not rem-audix what the book tell us to do.
Our DCS-link is up and running, at least we can make phonecalls over the link. If the remote location dials the Audix he is recognised by the system (CLI is arriving in the IntuityAudix because he can press pound instead of his number+pound).
Appendix B in the IP- and Networking book isn't very clear. Why the heck must Avaya use all types of links in their example. Somewhere we must be missing the clue.
Our Intuity is configured over LAN as link 1.
I think our problems lies in the Communications Processor Channels. That part is confusing us.
When tracing the calls we see a message that the Audix is not available and we get busy-tone.
Anyone any idea..
Thanks in advance,
John
