[asterisk-users] Asterisk 22.214.171.124 connectivity to Avaya SM (Thomas Peters)
viljoens at verishare.co.za
Thu Feb 28 00:18:05 CST 2019
What is your IVR box's domain name in Linux?
With a hostname of, for example, "mcts.org" do you have a line like this in /etc/hosts:
in your /etc/hosts?
Additionally, in /etc/asterisk/asterisk.conf, is there a line
that is -uncommented- and contains the string you need to the right of the @ e. g.
The immediate above just a shot in the dark but could affect how your IVR box identifies itself.
If the Linux system host name of the IVR machine is not "mcts.org" maybe you can change the machine's name via (for Centos 7 at least - if you have NetworManager running):
nmcli general hostname mcts.org
systemctl restart systemd-hostnamed
and then reboot the machine which implies also restarting asterisk.
If I remember right this will cause the Asterisk instance to identify itself as
"mcts.org" sip:mcts.org at mcts.org:0;tag=...
>From asterisk.conf |
From nmcli general hostname mcts.org
Might still not solve your precise issue but might be a step in the right direction??
>We have a brand-new Avaya phone system in place and we will be cutting over to it in late March 2019.
> * We have an Asterisk 13.3.2 server with no phones registered to it, acting as a PSTN gateway. Calls come into it and get distributed to other Asterisk boxes with phones.
> * If a call comes in from the provider marked as having been dialed as xxx-xxx-6711 (those are digits, not a pattern) it gets routed to the IVR box
> * The IVR box runs Asterisk 126.96.36.199 and a custom IVR.
>Where we have to get to:
> * The new Avaya Session Manager has to have a working SIP trunk to the IVR so it can pass calls that come into xxx-xxx-6711 to it.
>What the problem is:
> * I don't fully understand what's going on here, neither how it works now, nor what I need to do to make Avaya's SM happy.
More information about the asterisk-users