IP Telephony - NBX
1751970 Members
4709 Online
108783 Solutions
New Discussion юеВ

Re: V3000 Locking up

 
helper_1
Advisor

V3000 Locking up

V3000A running R6_5_22 with memory upgrade.  System was showing signs of corrupt database as in the way of voice mail ports have same extension numbers and when attempting to clean up unused profiles, system would stop responding.  Modified extension numbers to remove duplicate extension numbers.  When I say stop responding, GUI not responding and voice mail ports would hangup on caller attempting to retrieve voice mail after entering password. System also running 15 member ACD.

 

Database was rebuilt from scratch on new hard drive.  Only part of database imported to new hard drive were dial plan and license backup.  New hard drive was put into existing system.

 

Current issue, system continues to lock up and now showing the following on the com port of the NBX system.

 

socket: Error #         55
socket: Error #         55
socket: Error #         55
socket: Error #         55

v3000->
v3000->
v3000->0x269441a4 (tNetTask): arpresolve: can't allocate llinfo0x269441a4 (tNetT
ask): arpresolve: can't allocate llinfo0x269441a4 (tNetTask): arpresolve: can't
allocate llinfo0x269441a4 (tNetTask): arpresolve: can't allocate llinfoDisabling
 logging

 

Could this be a processor or bad memory?  How can we figure out what the issue is?

 

 

13 REPLIES 13
bosoxfan
Trusted Contributor

Re: V3000 Locking up

hi.

the best way is when the "freeze" occurs, do an "i" command. This will show the state of the tasks.

Are any tasks SUSPENDED? (other than the debugger task)

if so, you should do an nbxSaveCore and open a case.

The "socket error 55" means that we ran out of buffers.. This could be the innocent victim because something else got suspended.

Also, you mention that user would log into their voicemail, enter password and then get disconnected. Is this when the system freezes? We had issues on 6.5.22 with this. You can check if this is your issue by doing an "i" command and look for a "2d" in the PID column of the nbxVMAxxx tasks.

We do have a P03 patch out that fixes a lot of issues, including the voicemail one mentioned above. This may also fix your issue. I would install that first.

You can get this by going to the ftp site , gso.3com.com, user: customer, pass:cases.

Go to /download/P03 patches. Grab the patch for the V3000 and the release notes to see how to install the patches.

Hope this helps!

bosoxfan
Trusted Contributor

Re: V3000 Locking up

Just learned that the gso.3com.com ftp site may be going away very soon.

The patches are also on

ftp.usa.hp.com

login: nbx123

password: Welcome2

in the /P03 Patches folder

helper_1
Advisor

Re: V3000 Locking up

Will all of the software (ie. NBX voice softwares and applications) be available on the new site?

 

Also have another issue with this.  I am seeing the following error pop up quote a bit.

 

UI Display : feature Id not handled

 

What is this telling me?

helper_1
Advisor

Re: V3000 Locking up

By the way....that error is appearing in the NBossLog only on one extension.

 

1020:125346:0480 Call           W connect - Conference request but no conference address was reserved                                                     
1020:130349:0692 Call           W connect - Conference request but no conference address was reserved                                                     
1020:130948:0115 NBSetBus1051   E 1051 : UI Display : feature Id not handled                                                                              
1020:130948:0403 NBSetBus1051   E 1051 : UI Display : feature Id not handled                                                                              
1020:130948:0653 NBSetBus1051   E 1051 : UI Display : feature Id not handled                                                                              
1020:130948:0865 NBSetBus1051   E 1051 : UI Display : feature Id not handled                                                                              
1020:130949:0076 NBSetBus1051   E 1051 : UI Display : feature Id not handled                                                                              
1020:130949:0269 NBSetBus1051   E 1051 : UI Display : feature Id not handled                                                                              
1020:131032:0365 Call           W connect - Conference request but no conference address was reserved                                                     
1020:131311:0711 Call           W connect - Conference request but no conference address was reserved                                                     
1020:131349:0307 Transfer       W 1025 : OtherParty's extension= 1032                                                                                     
1020:131350:0365 Transfer       W 1000 : OtherParty's extension= 1010                                                                                     
1020:131708:0403 Call           W connect - Conference request but no conference address was reserved                                                     
1020:132002:0442 Call           W connect - Conference request but no conference address was reserved                                                     
1020:132103:0173 Call           W connect - Conference request but no conference address was reserved     
bosoxfan
Trusted Contributor

Re: V3000 Locking up

All of the software will be available on another HP Networking site for all contract customers.

 

Regarding the "feature ID not handled", x1051 is hitting a feature that is not known.  Someone could just be hitting the feature button and then any digits.

 

Hope this helps !

helper_1
Advisor

Re: V3000 Locking up

Is this what you are talking about with the "2d" in the PID?

nbxInetD     d6b5a8       230affc4 100 PEND        108bddc 230afbf4        2b0001     0
nbxVMAA0   d6d4a8       2310eb98 100 PEND        11352f2 230fad70              37     0
nbxVMAA1   d6d4a8       2309ae68 100 PEND        11352f2 23081988   3d0002     0
nbxVMAA2   d6d4a8       2306ae38 100 PEND        11352f2 23055178   3d0004     0
nbxVMAA3   d6d4a8       2303a958 100 PEND        11352f2 2302a578   3d0002     0
nbxVMAA4   d6d4a8       22ff9180 100 PEND        11352f2 22fdfcc8                  37     0
nbxVMAA5   d6d4a8       22fcad98 100 PEND        11352f2 22fb34c8      3d0002     0
nbxVMAA6   d6d4a8       22f9a8b8 100 PEND        11352f2 22f87ac0      3d0002     0
nbxVMAA7   d6d4a8       22f6ad38 100 PEND        11352f2 22eafc28      3d0004     0
nbxVMAA8   d6d4a8       22e9acf8 100 PEND        11352f2 22e81818     3d0002     0
nbxVMAA9   d6d4a8       22e6ab20 100 PEND        11352f2 22e55e10             37     0
nbxVMAA10  d6d4a8       22e25820 100 PEND        11352f2 22e2a588  3d0004     0
nbxVMAA11  d6d4a8       22e0a648 100 PEND        11352f2 22ddfb58    2b0001     0
nbxVMAA12  d6d4a8       22dcac30 100 PEND        11352f2 22db4160   2b0001     0
nbxVMAA13  d6d4a8       22d9ac18 100 PEND        11352f2 22d88758   3d0002     0
nbxVMAA14  d6d4a8       22d6a2b8 100 PEND        11352f2 22d3fab8                0     0
nbxVMAA15  d6d4a8       22d2ab90 100 PEND        11352f2 22d124b0               0     0

bosoxfan
Trusted Contributor

Re: V3000 Locking up

This is different.. where you see the "37" would be the "2d". Also, the PC number would be different from the other vm tasks. In this case, they are the same.
Helper1
Visitor

Re: V3000 Locking up

I am looking for applications for the V3000 such as CDR, DSA, TAPI, CALL ASSISTANT and the such.  Where can I find these since the gso.3com.com has been taken down?

merlin215
Valued Contributor

Re: V3000 Locking up

You need to open a case . Then we can put them on a one time download site for you .