Voicemail hunt-group is busy

[moev99]

I have an issue which has plagued me for days. I am trying to do a first-time setup of an IA770 on an s8300 system (it's the version that comes with CM4.0). This is a standalone setup, so it should be straightforward.

I followed the 58 page PDF in the document titled “Avaya IA 770 INTUITY AUDIX Messaging Application Release 4.0. Administering Media Servers to Work with IA 770” to the best of my ability. Page 45 states “call the hunt group for messaging” from the station that you configured, and you should hear a greeting “Welcome to AUDIX”. I don’t. I get a BUSY signal

From the examples, I followed it exactly with a few modifications. My extension ranges are 7 digits (not 4), and the range is from 4002020 to 4002059.

Only 4002022 and 4002040 are setup as stations right now. I've assigned 4002057 to be the voicemail hunt-group. When I call it from 4002040, I get a busy signal.

(192.168.4.104 = phone; 192.168.4.7 = voip IP address)

"list trace station 4002040" reveals:
16:36:13 active station 4002040 cid 0x3f
16:36:13 G711MU ssff ps:20 rn:1/1 192.168.4.104:2566 192.168.4.7:2050
16:36:13 xoip: fax:Relay modemff tty:US 192.168.4.7:2050 uid:0x16
16:36:15 call-forwarding
16:36:15 term hunt-group 99 cid 0x3f
16:36:15 dial 34002057 route:AAR
16:36:15 busy hunt-group 99 cid 0x3f
16:36:17 idle station 4002040 cid 0x3f

"list trace tac 199" revealed no information.

I've tried rebooting, and these commands as well:

busyout trunk 99 ; release trunk 99
busyout signaling-group 99; release signaling-group 99

I'll try to keep my settings as compact as possible. I think that these are the relevant pieces.

dialplan analysis
1 3 dac
3 1 fac
9 1 fac
feature access-codes
AAR code: 3
ARS code: 9
system-parameters features
QSIG/ETSI TSC Ext: 4002059
QSIG path replace: 4002058
unknown numb internal? y max length: 7
node-names ip
msgserver 192.168.4.4
procr 192.168.4.4
ip-interfaces procr
ip: 192.168.4.4 enable eth: y
signaling-group 99
near node: procr (port 1720)
far node: msgserver (port 1720)
trunk group for NCA TSC: 99
trunk group for channel selection: 99
trunk-group 99
COR: 1
TAC: 199
Sig Group: 99
serv type: tie
ars digit-conversion 1
match:4 min:7 max:7 del:0 net:ext conv:y
aar digit-conversion 1
match:4 min:7 max:7 del:0 net:ext conv:y
route-pattern 99
grp:99 FRL:0 DCS:n IXC:user
y y y y y n y none rest ... rehu
aar analysis 4
4002057 min:7 max:7 route:99 calltype:aar ANI:n
public-unknown-numbering 7
len:7 extcode:4 trk grp:99 cpn_len:7
hunt-group 99
grp name: msgserver
grp ext: 4002057
grp type: ucd-mia
COR: 1
Message Center: qsig-mwi
voicemail number: 4002057
routing digits (aar/ars): 3
coverage path 2
Point1: h99
machine:
name: s8300c (hostname, 192.168.4.4 in /etc/hosts)
ext length: 7
community id: 1
start ext: 4002020
end ext: 4002059
station 4002040
COR: 1
Coverage Path 1: 2
LWC reception: spe LWC activation: y
MWI served user type: qsig-mwi
subscriber 4002040:
name: 4002040 locked?: n Password:
COS: class00 switch number: 1


Should the IP of procr = IP of msgserver?
There are no stations defined for the QSIG extensions, and from my reading, I'm under the impression that they shouldn't be. However, they should be in the "extension range". What else should I do to try to troubleshoot this?

Thanks!

 

[DJPlaZma]

A couple things to check first:

1) Is the link up between the Audix and the switch?
2) Is the connection type set correctly in the Audix? (DCIU, IP, etc)


-DJ PlaZma
Single-Handedly Keeping the 80s Alive!

http://www.PlaZmaRadio.com

http://plazmaradio.serveroom.us:9652/listen.pls

 

[moev99]

Thanks DJPlazma.

Perhaps I should be posting in a different forum, but I know that definity's audix setup is similar. The CM4.0 software was installed with IA770 audix on the same box (the s8300c). Thus, I would assume that there is no DCIU link that would require setting up, and that CM4 should be able to talk to audix since it's on the same box. Please correct me if I'm wrong, as I'm willing to try anything.

By the way, running "systat" shows the critical pieces are up:
CommunicaMgr 59/59 UP SIMPLEX
Messaging 1/ 1 UP SIMPLEX

Cheers.

 

[definityman]

Hi moev99. what about ip-network regions and ip-coded sets ?

I have done several IA770 install starting from cm 2 to cm 3.1.4 and as long as i know , the IA770 has to be on network region 1 with codec set using g.711 MU .

Hope this helps

 

[moev99]

Thanks.

ip-network regions is setup exactly like in the PDF:

ip-network-region 1
MEDIA PARAMETERS Intra-region IP-IP Direct Audio: yes
Codec Set: 1 Inter-region IP-IP Direct Audio: yes
UDP Port Min: 2048 IP Audio Hairpinning? n

src dst codec direct Total Video Dyn
rgn rgn set WAN WAN-BW-limits Norm Prio Shr Intervening-regions CAC IGAR
1 1 1
1 2

ip-codec-set 1
Audio Silence Frames Packet
Codec Suppression Per Pkt Size(ms)
1: G.711MU n 2 20


signalling-group 99
Far-end Network Region: 1


I just tried changing these to y and restarted everything, but i still get a busy signal:
Direct IP-IP Audio Connections? y
Enable Layer 3 Test? y

 

[bsmo]

moev99,

What does a 'status trunk' say ?

The IP address of the Audix is different of the procr one. You should go to the maintenance webpage, select 'configure server' and go thru all the settings. On the page were you define the IP for the S8300 there should be also a field where you put the IP for the IA770. If it's empty fill it in and continue to make sure all settings are correct. After this reboot the S8300.

 

[moev99]

Wow. you've solved my problem!

I added a new IP for IA770 in the "configure server", and I now see the IP in "dummy0". Sadly, I originally had it configured this way through the AIW wizard, but the route for my subnet went through dummy0, so I lost communication with the subnet, and I couldn't ping any system on my subnet. (of course, I could have manually removed the route ).

However, doing this afterward in the Management interface, I no longer have this routing conflict, and my subnet is routed through eth1.

Anyways, to make a long story short, I get the "welcome to audix" prompt now! Thanks to all of you.