Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Issues with Upgrade to R11.0.4 9

Status
Not open for further replies.

pyoung85

Technical User
Feb 13, 2016
25
CA
We recently upgraded an IP Office from R.9.1.7 to 11.0.4. We passed from 9.1 to 10.0 and finally 11.
Following the first upgrade to R10 I noticed the IP Office wasn't responding well. I started a continuous ping on the IP Office. I would get delayed responses of 20 ms to 5000 ms and 1/3 of the ping's would timeout.

This IP Office has approx 50 digital phones and another 50 IP phones at various locations. They would slowly come back on one after another. The PBX seemed stabilized after everyone has been connected (more or less 20 minutes).

Two days later we had to reboot the PBX to change a combo card that has been defect for the past 2 weeks. Following this reboot, the PBX would go through the same process I mentioned but would NEVER stabilize. We tried formatting and recreating the SD Card. We tried to power on the IP Office and plug in one card at a time. Once all cards and the DS expansion module all proved to be working fine, we tried plugging in one phone at a time. After all proved to be fine, we tried plugging in the PRI. Next we plugged in the WAN which contains only SIP lines. So far everything is up and running fine. We have a laptop in LAN 1 monitoring the system. We waited a bit with calls going in and out and everything is fine.

We plugged in LAN 1 to the local network, which also has the Voicemail Pro server, XIMA Chronicall + Multimedia server and +-50 IP Phones in various locations. All hell broke loose. At this point we do understand the IP Office is loaded with requests but nothing has been added recently and it never acted this way. The only new factor is the XIMA multimedia server but at this point I had all XIMA services turned off to limit the requests.

So we installed a new IP Office 500 V2 cabinet. Right away the IP Office responds with reasonable delays (1ms to 4 or 5ms) but the IP Phones took approximately 20 minutes to come back online one after another. At this point we're certain the IP Office network card was faulty and the issue is resolved.

Come in the next day and surprise we have some new issues. Voicemail isn't always answering, and if it does the sound cuts off halfway. No DTMF is supported once in the Voicemail. So we restarted the Voicemail Pro service. Issue resolved. A few hours later, the client mentions digital phones can no longer dial out. When they press on digits, nothing appears on the screen. If they press very slowly, the digits will go through.

So we now proceed to downgrade from R11.0.4 to 11.0.2. We read about different numerous issues online concerning 11.0.4. After this downgrade we come back to point A. The IP Office responds only 2/3 of the time with major delays. It takes approximately 30 minutes or so for everything to come back online. Yet after 30 minutes it all seems stable. For now...

The only errors we can see in the Sys monitor are the following :
ERR: Vil Cafeteria Terminal PGO Response !OK:(0x1)
TFTP Write:: Too many retries (from 0.0.0.0, 49597, to 4207) file=deltaconfig/svmail1/CHqoAZFPD9irGpRmDx8u6JbzCCinHJADCyeqGZK4020

Any ideas ?
 
We recently ran into a similar issue and it ended up being the customers network. Something on the network (still don’t know what) was over loading the IP500 with DHCP requests which cause major latency and in turn, poor QOS. Post a monitor trace.
 
I have done about thirty upgrades to 11SP4 due to the need for Equinox or J179/K1x5 phones and had no network issues at all.
Said that i think you have a network issue where R9.1 had no problem with.
So my advice is to solve the network problem, use VLANs for Voip and connect the Voice VLAN to LAN2.
Our rule is to deploy VLANs if there are more than 20 IP Phones to be or going to be used now or in the future.
It avoids many voice related issues.
 
We do suspect this is a network-related issue. However this is not our network and we have limited access. The client's IT has done preliminary troubleshooting and says there is nothing out of the ordinary on this network.

The phones are all in VLAN'S depending on what location they are at. Again, not our network, I can't see or validate anything other than the fact that they are able to communicate with one another and no routes seem to be missing.

The only addition to this network was a XIMA Chronicall Multimedia server. This is only deployed for the web chat so no SIP user has been created by XIMA and calls SHOULD be treated as they were to the best of my knowledge. Issues seemed to occur a day or so before this installation. Is it related ? Very hard to tell for now given that I wasn't able to assist during the installation process of this new server. We're looking into it and will keep this possibility in mind. However, the day where we tested everything I had turned off all XIMA Chronicall services to limit requests to the IP Office and it barely helped.

I would like to post a better monitor trace but I don't see any errors. What filters would you suggest I use ?
Interface packets In, Out and Queue give me nothing. If we add all H323, of course, we see all the IP Phone registrations. SIP does show me all packets on the SIP trunk. Then again nothing but the two errors I mentioned in the original post. There must be some filters I don't understand properly that will give us more information.
 
We have upgraded IP Office 500v2 from R9.1.12.0 (build 213) to R 11.0.4.0.0 (build 74).
The IPO configuration is with around 120 IP phones and IPO is acting as a DHCP Server also to the IP phones. With the existing R9.1.12 the IPO is working properly.

After successful upgrade to R 11.0.4 we are facing with the same problem, the IPO became very unstable
and the ping is with delayed response, and with timeout. The IP office then never become stable until remove whole network from LAN1, reboot IPO and connect directly to LAN1 with my PC.
To make operational again we have to downgrade to R9.1.12

The errors captured with System Monitor during IPO was on R11.0.4 are:

3528748mS ERR: !RRQ --- Extn 6607 is registering with a legacy default password!
13:54:41 3528749mS PRN: SSITreeSystemInfoNode::EventVoIPExtensionRegistrationAlarm()





 
3528748mS ERR: !RRQ --- Extn 6607 is registering with a legacy default password!

I guess the default password is an empty one. Earlier releases had been forgiving against lower password policies while the newer releases aren't.

I suggest to set stronger extension passwords for all IP extensions and register the phones with that new password. Best you do that (along with phone firmware updates) before you upgrade the IPO.

Need some help with IP Office? CLI based cale blocking: SCN fallback over PSTN:
 
I have define pass code for every IP extension for H.323 registration, the status of IP Office is the same.
There is no error "ERR: !RRQ --- Extn xxxx is registering with a legacy default password!" any more
Even I went to IPO R10.1 and the IPO is unstable and nonfunctional

I have noticed the log in the monitor log, not show as error

GRQ --- RAS reaches the max capacity of 20; Endpoints registered: 5


 
I had the same behaviour of IP Office by Upgrading vom 9.1.12 to 11.0.2 last week.
At the second attempt today I changed the LAN2 IP adress, where the H.323 phones are connected and started the upgrade again.
After that I checked the security settings and disabled "blocked default endpoint passwords" or something like that in english language and configured in IP Office manager in System-Telephony-Telephony tab the options "force complexity of registration code".
Then changed the LAN2 adress settings to previous value and restarted.

IP Office is getting very unstable (long ping return times, timeouts) - sysmon is sometimes showing entries like
[tt] 05:29:56 1017156mS RES5: CLog MemObjs=3767 FreePoolMem(Objs)=1848(33) TotalMem=212800 StringsTotalMem=345800
05:29:56 1017166mS H323Evt: GK: Unregister endpoint xxx NA_5d1453db567b7ee5 for extension 4804 reason 6 urq_reason 3
05:29:57 1018551mS H323Evt: GK: Send URQ
05:29:57 1018552mS H323Evt: Recv: RegistrationRequest 10.11.0.148:49301 on 1; Endpoints registered: 1; Endpoints in registration: 14, tpkt user: 00000000
05:29:57 1018553mS H323Evt: e_H225_AliasAddress_dialedDigits alias
05:29:57 1018553mS H323Evt: found number <4881>
05:29:57 1018553mS H323Evt: RRQ --- CallSigProtocol is H323AnnexL_P. Go for Avaya 4600IP phone
05:29:57 1018553mS H323Evt: RRQ --- Treat this as a forced login, the phone was probably rebooted (same_cs_addr 1)
05:29:57 1018553mS H323Evt: GK: Unregister endpoint xxx NA_5d14541401ca0e35 for extension 4881 reason 4 urq_reason 3
05:29:57 1018553mS PRN: Task CMRtEngine waiting on Call Model Semaphore held by CM
05:29:58 1019941mS H323Evt: RRQ --- Register extn 4881 using product IP_Phone, version 6.6506, id xxx NA_5d1454574f676d07
05:29:58 1019942mS H323Evt: RASSRV: GetAlternate GK list returns <none>

********** SysMonitor v11.0.0.2.0 build 23 [connected to 10.10.100.70 (xxx NA)] **********
05:30:01 1022726mS H323Evt: Recv: RegistrationRequest 10.11.0.147:49307 on 1; Endpoints registered: 1; Endpoints in registration: 14, tpkt user: 00000000
05:30:01 1022726mS H323Evt: e_H225_AliasAddress_dialedDigits alias
05:30:01 1022727mS H323Evt: found number <4882>
05:30:01 1022727mS H323Evt: RRQ --- CallSigProtocol is H323AnnexL_P. Go for Avaya 4600IP phone
05:30:01 1022727mS H323Evt: RRQ --- Treat this as a forced login, the phone was probably rebooted (same_cs_addr 1)
05:30:01 1022727mS H323Evt: GK: Unregister endpoint xxx NA_5d14542238120c63 for extension 4882 reason 4 urq_reason 3
05:30:03 1024111mS H323Evt: RRQ --- Register extn 4882 xxx product IP_Phone, version 6.6506, id xxx NA_5d14545b31174c31
05:30:03 1024112mS H323Evt: RASSRV: GetAlternate GK list returns <none>

********** contact lost with 10.10.100.70 at 05:30:08 27/6/2019 - reselect = 35 **********
******************************************************************[/tt]

 
Did these actions with IPO resolved your issue or not ?
 
sorry that this was not clear from my post: no, the problem persisted and we had to downgrade.
 
Thank you, but we only use Avaya 1608-I IP phones firmware 1.3110 and 5 1408 phones on this location.

 
When register all IP phones one by one in IP Office the IPO is stay stable with all IP phones registered.
But when reboot IPO, and after that the IPO is unstable and ping to it is with timeouts.

In the IPO system monitor there are logs:

18:30:53 108397mS H323Evt: Recv GRQ from 192.168.2.70:49304
18:30:53 108397mS H323Evt: GRQ --- RAS reaches the max capacity of 20; Endpoints registered:
18:30:53 108398mS H323Evt: Recv GRQ from 192.168.2.76:49303
18:30:53 108398mS H323Evt: GRQ --- RAS reaches the max capacity of 20; Endpoints registered: 1
18:30:53 108399mS H323Evt: Recv GRQ from 192.168.2.167:49309
18:30:53 108399mS H323Evt: GRQ --- RAS reaches the max capacity of 20; Endpoints registered: 1
18:30:53 108400mS H323Evt: Recv GRQ from 192.168.2.62:49303
18:30:53 108400mS H323Evt: GRQ --- RAS reaches the max capacity of 20; Endpoints registered: 1
18:30:53 108401mS H323Evt: Recv GRQ from 192.168.2.58:49308
18:30:53 108401mS H323Evt: GRQ --- RAS reaches the max capacity of 20; Endpoints registered: 1

It seems this is connected with IPO crashing after rebooting. I never meet before this limitation "RAS reaches the max capacity of 20", and where I can find this RAS limitation described in the IP Office documentation ?

 
DO NOT USE 11.0.4 on control units if it is a server edition then its ok. there are issues with system settings that are usually a reboot save being changed during standard merge saves. Screwed with me on SIP registrar setting be turned off.

Stick with 11.0.2 until 11.0.5 comes out next week or so.
 
I did not mentioned before, actually I have been try with R11.0.2 and after upgrade the IPO had same behavior.
 
Has anyone had a problem with digital extensions?

Our ones have started to become very slow and unresponsive.
 
SIP DECT LINES D100 require sip registrar enabled and it doesnt use sip extensions

 
Well, just create a SIP extension and the problem is solved until they fix it.

"Trying is the first step to failure..." - Homer
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top