Paging multiple IP phones problems

[phantomiii]

I've tried to setup a Page All for my IP phones. I have a group of about 100 phones, mixture of 5610, 5602, and 5620's, with a majority the 5602. All the codec's are G.711 U-Law. According to Avaya and my own monitoring, a page call from an IP phone to a group of IP phones will only use 1 VCM resource if the codec's are all set the same.

What happens is... I make the page call, the first 2 seconds of my page goes through, then all the IP phones lockup and the phone I was paging on locks too. After about 15 seconds, the phone I paged from recovers, but all the other IP phones are off hook with a phantom page call. Upon looking in monitor, all the IP phones have become unregistered.

I have to go to every phone and hang it up, and it becomes registered and back to normal.

I've upgrade from 3.1.5602 to 3.1.65 to see if that would fix it, but the same problems occurs. I can page a group of IP phones with 10 just fine. Anyone else have problems or suggestions with this?

 

[magix2kewl]

I was also having similar problems with this issue. Some of the fix seemed to be duplicate entires in the hunt group and user form. If an extension was in twice it would grab an extra VCM and lock it up. Later no vcm's would be available and all paging would die. Also problems with users named incorrectly such as punctuation like Dr. the period throwing it off.

 

[ipofficedude]

I have had this escalated for several months now with AVAYA see:

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

 

[phantomiii]

Thanks for the response magix2kewl and ipofficedude.

I do not have any duplicate users, no punctuation in any of the names, no duplicate members in the huntgroup, etc...

Hmmm, I have direct media path checked and Extreme Network switches with Layer 2/3 QoS mechanisms in place.

ipofficedude wrote:

"I have also since noted:
CQ25911 IP office paging appears to be causing some sort of indefinite packet storm with IP phones."

-Yeah, I thought upgrading to 3.1.65 would fix this one, but it didn't. Any other ideas or suggestions? Are you just waiting to see if 3.2 will fix it? Or does Avaya acknowledge the problem with that many IP phones?

 

[magix2kewl]

ipoffice dude - replied to your thread

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