No VOIP Resource, what voip resource? Please help

[9mmgeek]

This is killing me. We even called Avaya and paid for an hour with a credit card and they were no help.
CM 3.1.2 on 8700s. G650 at the main site and G700s at the remotes.

This is from a disp event denials. I see the same thing happen with a list trac on the attendant console but it does not always happen. They end up with one way calls and dropped calls.

Event Event Event Event First Last Evnt
Type Description Data 1 Data 2 Occur Occur Cnt
2049 No VOIP Resource A 53 06/15/08:11 06/15/08:11 2
2371 IGC:Exch no common codec 400A7800 400B7833 06/15/08:11 06/15/08:11 1

I have done all the list measures in asa and sh voip at the MGs on the G700s and I dont see any shortage of DSPs. These sites work most of the time so I cant believe there is a codec problem. I believe data1 on the 2049 is the MG. In this case A=10. I cant figure out the 53 or either data for the 2371. It is not an IP address in our network. The documents dont show any data1 or 2 for these denial events. Man this is frustrating. The real kicker is that I see the events happen at night when people call in to check their voicemail. Definitely not a peak time. They may be the only activity in the entire nationwide phone system.

Can anyone give me a clue where to look?

 

[9mmgeek]

Could this be the IPSI? Is there something in the IPSI that limits the number of VoIP connections?

 

[kjrnec]

Could you post your configs for these Gateways?

 

[9mmgeek]

Thats a lot of stuff. You mean the MG config on the media servers or the config in the MG?

 

[9mmgeek]

These are two MGs in a stack that gets the problem pretty often.

MEDIA GATEWAY
Number: 3 IP Address: 10 .2 .56 .13
Type: g700 FW Version/HW Vintage: 25 .43 .0 /4
Name: Houston_MG1 MAC Address: 00:04:0d:6f:95:3b
Serial No: 05J206801407 Encrypt Link? y
Network Region: 13 Location: 13
Registered? y Controller IP Address: 10 .0 .31 .19
Recovery Rule: 2 Site Data:
Slot Module Type Name
V1: S8300 ICC MM
V2: MM717 DCP MM
V3: MM710 DS1 MM
V4: MM717 DCP MM

V8:
V9: gateway-announcements ANN VMM


MEDIA GATEWAY
Number: 4 IP Address: 10 .2 .56 .15
Type: g700 FW Version/HW Vintage: 25 .43 .0 /6
Name: Houston_MG2 MAC Address: 00:04:0d:f8:fd:95
Serial No: 061648603329 Encrypt Link? y
Network Region: 13 Location: 13
Registered? y Controller IP Address: 10 .0 .31 .19
Recovery Rule: 2 Site Data:
Slot Module Type Name
V1: MM717 DCP MM
V2: MM717 DCP MM
V3: MM717 DCP MM
V4: MM711 ANA MM

V8:
V9:

MG-003-1(super)# sh mg li

SLOT TYPE CODE SUFFIX HW VINTAGE FW VINTAGE VOIP FW
---- ------ ----- ------ ---------- ----------- -------
v0 G700 DAF1 C 04 25.43.0(A) 77
v1 ICC S8300 B 4 1 N/A
v2 DCP MM717 A 2 9 N/A
v3 DS1 MM710 A 5 21 N/A
v4 DCP MM717 A 3 9 N/A

MG-003-1(super)# sh voip v0

VOIP ENGINE PARAMETERS
---------------------------------------------------------
Slot Number : v0
Current IP Address : 10.2.56.14
Static IP Address : 10.2.56.14
DHCP Used : No
DSP Firmware Version: 77
MAC Address : 00-04-0D-70-15-3B
Fault Status : No Fault Messages
Additional Status : No Status Messages

CURRENT STATE
---------------------------------------------------------
In Use : 3 of 64 channels, 120 of 1920 points (6.3% used)
DSPs State : In use
Admin State: Release

MG-003-1(super)# sh mgc

CALL CONTROLLER STATUS
-------------------------------------------
Registered : YES
Active Controller : 10.0.31.19
H248 Link Status : UP
H248 Link Error Code: 0x0

CONFIGURED MGC HOST
---------------------
10.0.31.19
10.0.31.14
10.0.31.15
10.2.56.12


MG-004-2(super)# sh mg li

SLOT TYPE CODE SUFFIX HW VINTAGE FW VINTAGE VOIP FW
---- ------ ----- ------ ---------- ----------- -------
v0 G700 DAF1 C 06 25.43.0(A) 77
v1 DCP MM717 A 2 9 N/A
v2 DCP MM717 A 3 9 N/A
v3 DCP MM717 A 3 9 N/A
v4 ANA MM711 A 27 73 N/A

MG-004-2(super)# sh voip v0

VOIP ENGINE PARAMETERS
---------------------------------------------------------
Slot Number : v0
Current IP Address : 10.2.56.16
Static IP Address : 10.2.56.16
DHCP Used : No
DSP Firmware Version: 77
MAC Address : 00-04-0D-F8-FD-96
Fault Status : No Fault Messages
Additional Status : No Status Messages

CURRENT STATE
---------------------------------------------------------
In Use : 2 of 64 channels, 60 of 1920 points (3.1% used)
DSPs State : In use
Admin State: Release

MG-004-2(super)# sh mgc

CALL CONTROLLER STATUS
-------------------------------------------
Registered : YES
Active Controller : 10.0.31.19
H248 Link Status : UP
H248 Link Error Code: 0x0

CONFIGURED MGC HOST
---------------------
10.0.31.19
10.0.31.17
10.0.31.15
10.2.56.12

 

[kjrnec]

Isn't this the same issue you posted an few months ago? In that thread someone asked for the ip-network-region configs.

http://www.tek-tips.com/viewthread.cfm?qid=1605178&page=9

 

[phoneguy55]

This is happening on the the remote G700? If so, then post the ip routes for the G700.

sho ip route voip v0
sho ip route mgp
sho ip route static

 

[9mmgeek]

kjrnec, yes it is the same problem. It has not been resolved and my rep it taking a hit. In that post he didn't ask for the configs but told me to check them. The data fields are not IP addresses in the 2371 event so most of that response didn't apply.

Many of the calls that are failing are coming in their local PRI and the attendant cannot hear them or it drops when she is trying to transfer it to someone in the same tenant/location. This site is entirely digital but since the media servers are at a different location and the MGs are on IP connect links there are still voip resources in play but not many.

I know where you are going with the route questions but you need to understand that this has been working for over 4 years and works now most of the time. Nothing has changed in 14 months other than adding phones and new locations. So initially I thought I might actually be hitting limits in the DSP resources but I cannot see any evidence of that happening. Since it is happening at multiple locations, all connected to the same media servers, I focused on the media servers and the medpros at the main site. But the problem seems to clear up for a while if I reset the voip engine and MGP at the remote location. The next day it will appear again but usually at a different site.

MG-003-1(super)# sh ip route mgp

DESTINATION MASK GATEWAY INTERFACE (F/C/U)
--------------- --------------- --------------- ---------- -----------
0.0.0.0 0.0.0.0 10.2.56.1 motfec0 (3/2/50178)
10.2.56.0 255.255.255.0 10.2.56.13 motfec0 (101/0/0)

MG-003-1(super)#
MG-003-1(super)# sh ip route mgp
MG-003-1(super)# sh ip route voip v0

DESTINATION MASK GATEWAY
--------------- --------------- ---------------
0.0.0.0 0.0.0.0 10.2.56.1
10.2.56.0 255.255.255.0 10.2.56.14

MG-003-1(super)#
MG-003-1(super)# sh ip route static

DESTINATION MASK GATEWAY
--------------- --------------- ---------------
0.0.0.0 0.0.0.0 10.2.56.1

MG-003-1(super)#

MG-004-2(super)# sh ip ro mgp

DESTINATION MASK GATEWAY INTERFACE (F/C/U)
--------------- --------------- --------------- ---------- -----------
0.0.0.0 0.0.0.0 10.2.56.1 motfec0 (3/2/49711)
10.2.56.0 255.255.255.0 10.2.56.15 motfec0 (101/0/0)

MG-004-2(super)# sh ip route voip v0

DESTINATION MASK GATEWAY
--------------- --------------- ---------------
0.0.0.0 0.0.0.0 10.2.56.1
10.2.56.0 255.255.255.0 10.2.56.16

MG-004-2(super)# sh ip route stat

DESTINATION MASK GATEWAY
--------------- --------------- ---------------
0.0.0.0 0.0.0.0 10.2.56.1

MG-004-2(super)#

 

[kjrnec]

I sympathize with your issue since I've been battling IPSI failures ever since our system was installed last year. But have you tried posting on other Avaya sites besides this one?

I would post the link to the site I use the most but don't know the rules about competing websites.

 

[phoneguy55]

Your IP routes look good. Have you upgraded the firmware on everything? Also, you said your running CM3.1.2 might have to go to 3.1.5 to rule that out.

 

[AvayaTier3]

what is the fw on your medpro in the g650?
can IP phones in the g700's call to stations or trunks in the g650?

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

36 years Bell, AT&T, Lucent, Avaya
Tier 3 for 26 years and counting

http://bshtele.com

 

[Mitch672]

I Notice you are running a fairly old MGP release (25.43.0) with the very latest VoIP MM760 firmware (FW077). I might try upgrading the MGP to the latest, I beleive it is backward cmpatible with CM 3. Also, it wouldn't hurt to upgrade your sysem to CM 3.1.5, and also load the latest CM 3.1.5 patches on the main and on the LSPs as well. Yes, I know its a lot of work to do all of that updating, but this is what AVAYA will also suggest to you. I would start with just the MGP firmware on the 2 G700's, and see how that goes. Also, the TN2302AP/TN2602AP firmware at the main site might also come into play, but not for DS1 calls within that gateway to DCP phones in the same gateway (but might if they are in the other G700)

Your best bet is to check the firmware compatability page at support.avaya.com and see what is recomended. Again, CM 3.1.5 was released to address issues with previous CM 3 releases...


Mitch

AVAYA Certified Expert

 

[Mitch672]

http://support.avaya.com/css/appman...ownloads/P0001/3.1.x/C20090710154815434625607

Compatabilty Word document:
ftp://ftp.avaya.com/incoming/Up1cku9/tsoweb/CM_SW_FW_Compatibility_Matrix.doc

page 22 is about CM 3.1.2




Mitch

AVAYA Certified Expert

 

[Mitch672]

it does look like 25.43.0 is the recomended version for CM3, so my recomendation would be to examine the IP Network Regions, and see if you have some "misconfiguration" possibly in the "ip-codecs" specified possibly between regions.. also the CM 3.1.5 upgrade could not hurt, but to make a difference, you would have to upgrade all of yor LSPs first, then the main site (LSP's can be running a higher version, but you won't notice any operational difference until the main site is upgraded)



Mitch

AVAYA Certified Expert

 

[9mmgeek]

Thanks for all the suggestions.

My medpros are on fw 118 and I have 120 ready to load, waiting for the ok, but there is nothing in the release notes that indicates it fixes anything like this.

The 25.43.0 FW for the MGs is the highest recommended with CM3.1.2.

I am starting to wonder about time slots in my g650 port network at the main site. Most of my phones are digital but they are on G700s that are IP connected to the media server through the clans, medpros,and IPSI in the G650. The different docs I have found are extremely hard to follow when calculating the capacity and load.

I have relied on the list meas blockage command to tell me if there is a problem with time slots. I don't know if that is enough. Here is an example showing yesterday's peak. I know we had an event at 1420 hours and this shows yesterdays peak at 1000 hours. Is there a better way to check time slot usage?
BLOCKAGE STUDY REPORT

Meas Time Division Multiplexed(TDM) Port Network(PN) Link
PN Hour Usage Peg Peak Blockage Time-slots Usage Peg Peak Blockage

1 1000 1853 1670 70 0 0 0 0 0 0

 

[9mmgeek]

BTW, the idea of going to 3.1.5 would be nice but it takes big $$$. They wouldn't even consider it unless Avaya said there was bug that was fixed in the new version.

 

[Mitch672]

how does it take "big money" you can download the ISO image, stage it yourself, and actually perform the upgrades yourself. It's a minor dot release, not a major release, it doesn't require any license.

You can use "MagicDisc" to mount an ISO image, then use any TFTP Server (there is one on the CD image under "PC Software"), then copy the image to each S8300 and each server on your network, and upgrade them 1 at a time... DO the LSPs first. don't forget to "Make Upgrade permanent" after you get each one done and apply the CM 3.1.5 service packs, if you forget the old version will go active on a reboot..

Here is the CM 3.1.5 ISO image, you can download...

http://support.avaya.com/css/appmanager/public/support/Downloads/P0001/3.1.x/C2009071016361659625570

Mitch

AVAYA Certified Expert

 

[9mmgeek]

Mitch,

I never heard of this. I thought everything was a release and needed a license, and I never thought Avaya would let you have anything without a charge! Are you saying this is like the firmware updates?

 

[phoneguy55]

Are you saying this is like the firmware updates?

We'll its a little more complex then a firmware upgrade. But yes its, free. The only thing your gaining is bug fixes and not new features.

 

[Mitch672]

Yes, and you certainly seem to have some "bugs", which is why I recomended you upgrade to the most recent release of CM 3.1, which is CM 3.1.5

There are instructions on how to do it on the AVAYA website, or if you have an AVAYA Business Partner, you could have them do one of your S8300LSPs, and take notes, once you see how it's done, it's really not a big deal...



Mitch

AVAYA Certified Expert