not able to connect to officemanager

[martinipenburg]

we are not able to connect to office manager. we use version 1.12. we use in our network a different router as the uc500 maybe this causes the connection to fail. the error message on screen is:

unable to connect to uc500.

hereunder te content of the logfile:

22:Apr:2011 14:26:39 -vService| Er CiscoDeviceDiscoveryModule::mUcInfo: Slot 0: UC500 Mainboard 1FE, 8FE POE, Stacking FE, MOH, Port adapter Port adapter is analyzed Port adapter insertion time unknown Hardware Crypto Engine Details: The CHIP id is 0x10003 The SEC revision no is 0x1 EEPROM contents at hardware discovery: PCB Serial Number : FOC142320NM Hardware Revision : 1.0 Top Assy. Part Number : 800-32871-01 Board Revision : C0 Deviation Number : 0 Fab Version : 03 RMA Test History : 00 RMA Number : 0-0-0-0 RMA History : 00 Processor type : AD Hardware date code : 0 Chassis Serial Number : FHK142677K9 Chassis MAC Address : c84c.7504.3f00 MAC Address block size : 32 CLEI Code : TBD0000000 Product (FRU) Number : UC540W-BRI-K9 Part Number : 73-12691-01 Version Identifier : V01 EEPROM format version 4 EEPROM contents (hex): 0x00: 04 FF C1 8B 46 4F 43 31 34 32 33 32 30 4E 4D 40 0x10: 05 60 41 01 00 C0 46 03 20 00 80 67 01 42 43 30 0x20: 88 00 00 00 00 02 03 03 00 81 00 00 00 00 04 00 0x30: 09 AD 83 00 00 00 00 C2 8B 46 48 4B 31 34 32 36 0x40: 37 37 4B 39 C3 06 C8 4C 75 04 3F 00 43 00 20 C6 0x50: 8A 54 42 44 30 30 30 30 30 30 30 CB 92 55 43 35 0x60: 34 30 57 2D 42 52 49 2D 4B 39 20 20 20 20 20 82 0x70: 49 31 93 01 89 56 30 31 00 D9 04 40 C1 C2 CB FF BRI Voice IO Card: EEPROM contents at hardware discovery: Hardware Revision : 4.0 PCB Serial Number : FOC14185RX6 Part Number : 73-10882-04 Board Revision : C0 RMA Test History : 00 RMA Number : 0-0-0-0 RMA History : 00 Deviation Number : 0 Product (FRU) Number : VOICE IO CARD Top Assy. Part Number : 800-28186-03 CLEI Code : Version Identifier : V02 EEPROM format version 4 EEPROM contents (hex): 0x00: 04 FF 40 05 62 41 04 00 C1 8B 46 4F 43 31 34 31 0x10: 38 35 52 58 36 82 49 2A 82 04 42 43 30 03 00 81 0x20: 00 00 00 00 04 00 88 00 00 00 00 CB 8D 56 4F 49 0x30: 43 45 20 49 4F 20 43 41 52 44 C0 46 03 20 00 6E 0x40: 1A 03 C6 8A 20 20 20 20 20 20 20 20 20 20 89 56 0x50: 30 32 20 FF FF FF FF FF FF FF FF FF FF FF FF FF 0x60: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 0x70: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF PVDM Slot 0: 64-channel (G.711) Voice/Fax PVDMII DSP SIMM PVDM daughter card Hardware Revision : 4.0 Part Number : 73-8541-05 Board Revision : C0 Deviation Number : 0 Fab Version : 04 PCB Serial Number : FOC14225N8Y RMA Test History : 00 RMA Number : 0-0-0-0 RMA History : 00 Processor type : 00 Product (FRU) Number : PVDM2-64 Version Identifier : V01 EEPROM format version 4 EEPROM contents (hex): 0x00: 04 FF 40 03 EC 41 04 00 82 49 21 5D 05 42 43 30 0x10: 88 00 00 00 00 02 04 C1 8B 46 4F 43 31 34 32 32 0x20: 35 4E 38 59 03 00 81 00 00 00 00 04 00 09 00 CB 0x30: 88 50 56 44 4D 32 2D 36 34 89 56 30 31 20 D9 02 0x40: 40 C1 FF FF FF FF FF FF FF FF FF FF FF FF FF FF 0x50: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 0x60: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 0x70: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF VIC Slot 0: 3rd generation - FXS DID Voice daughter card (4 port) Hardware Revision : 1.0 Top Assy. Part Number : 800-27473-03 Board Revision : C0 Deviation Number : 0 Fab Version : 01 PCB Serial Number : RMA Test History : 00 RMA Number : 0-0-0-0 RMA History : 00 Product (FRU) Number : VIC3-4FXS/DID Version Identifier : V01 CLEI Code : TBD Longitudinal Calibration : 01 10 10 AA 81 10 10 7B 8D 10 10 84 3A 10 10 7A 65 EEPROM format version 4 EEPROM contents (hex): 0x00: 04 FF 40 05 1B 41 01 00 C0 46 03 20 00 6B 51 03 0x10: 42 43 30 88 00 00 00 00 02 01 C1 8B 20 20 20 20 0x20: 20 20 20 20 20 20 20 03 00 81 00 00 00 00 04 00 0x30: CB 8D 56 49 43 33 2D 34 46 58 53 2F 44 49 44 89 0x40: 56 30 31 20 D9 02 40 C1 C6 8A 54 42 44 20 20 20 0x50: 20 20 20 20 D3 11 01 10 10 AA 81 10 10 7B 8D 10 0x60: 10 84 3A 10 10 7A 65 FF FF FF FF FF FF FF FF FF 0x70: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF VIC Slot 1: VIC2 - BRI-NT/TE Voice daughter card (2 port) Hardware Revision : 1.1 Top Assy. Part Number : 800-21861-03 Board Revision : C0 Deviation Number : 0-0 Fab Version : 02 PCB Serial Number : RMA Test History : 00 RMA Number : 0-0-0-0 RMA History : 00 Product (FRU) Number : VIC2-2BRI-NT/TE Version Identifier : V02 CLEI Code : CNUIAVZAAA EEPROM format version 4 EEPROM contents (hex): 0x00: 04 FF 40 00 51 41 01 01 C0

22:Apr:2011 14:26:39 -vService| Er CiscoDeviceDiscoveryModule::mCueGw: 10.1.10.2

22:Apr:2011 14:26:39 -vService| Er CiscoDeviceDiscoveryModule::Start of table

22:Apr:2011 14:26:39 -vService| Er CiscoDeviceDiscoveryModule::Dest[0.0.0.0], Mask[0.0.0.0], Policy[0], NextHop[10.45.1.254]

22:Apr:2011 14:26:39 -vService| Er CiscoDeviceDiscoveryModule:: IfIdxex[2] Type[4] Proto[3] Age[104178] NextHopAS[0] M1[20] M2[-1] M3[-1] M4[-1] M5[-1]

22:Apr:2011 14:26:39 -vService| Er CiscoDeviceDiscoveryModule::Dest[10.1.10.0], Mask[255.255.255.0], Policy[0], NextHop[10.45.1.1]

22:Apr:2011 14:26:39 -vService| Er CiscoDeviceDiscoveryModule:: IfIdxex[2] Type[4] Proto[3] Age[908] NextHopAS[0] M1[1] M2[-1] M3[-1] M4[-1] M5[-1]

22:Apr:2011 14:26:39 -vService| Er CiscoDeviceDiscoveryModule::Dest[10.45.1.0], Mask[255.255.255.0], Policy[0], NextHop[10.45.1.104]

22:Apr:2011 14:26:39 -vService| Er CiscoDeviceDiscoveryModule:: IfIdxex[2] Type[3] Proto[2] Age[104181] NextHopAS[0] M1[20] M2[-1] M3[-1] M4[-1] M5[-1]

22:Apr:2011 14:26:39 -vService| Er CiscoDeviceDiscoveryModule::Dest[10.45.1.104], Mask[255.255.255.255], Policy[0], NextHop[127.0.0.1]

22:Apr:2011 14:26:39 -vService| Er CiscoDeviceDiscoveryModule:: IfIdxex[1] Type[3] Proto[2] Age[104181] NextHopAS[0] M1[20] M2[-1] M3[-1] M4[-1] M5[-1]

22:Apr:2011 14:26:39 -vService| Er CiscoDeviceDiscoveryModule::Dest[10.255.255.255], Mask[255.255.255.255], Policy[0], NextHop[10.45.1.104]

22:Apr:2011 14:26:39 -vService| Er CiscoDeviceDiscoveryModule:: IfIdxex[2] Type[3] Proto[2] Age[104181] NextHopAS[0] M1[20] M2[-1] M3[-1] M4[-1] M5[-1]

22:Apr:2011 14:26:39 -vService| Er CiscoDeviceDiscoveryModule::Dest[127.0.0.0], Mask[255.0.0.0], Policy[0], NextHop[127.0.0.1]

22:Apr:2011 14:26:39 -vService| Er CiscoDeviceDiscoveryModule:: IfIdxex[1] Type[3] Proto[2] Age[104199] NextHopAS[0] M1[1] M2[-1] M3[-1] M4[-1] M5[-1]

22:Apr:2011 14:26:39 -vService| Er CiscoDeviceDiscoveryModule::Dest[169.254.0.0], Mask[255.255.0.0], Policy[0], NextHop[10.45.1.104]

22:Apr:2011 14:26:39 -vService| Er CiscoDeviceDiscoveryModule:: IfIdxex[2] Type[3] Proto[3] Age[104168] NextHopAS[0] M1[20] M2[-1] M3[-1] M4[-1] M5[-1]

22:Apr:2011 14:26:39 -vService| Er CiscoDeviceDiscoveryModule::Dest[224.0.0.0], Mask[240.0.0.0], Policy[0], NextHop[10.45.1.104]

22:Apr:2011 14:26:39 -vService| Er CiscoDeviceDiscoveryModule:: IfIdxex[2] Type[3] Proto[2] Age[104181] NextHopAS[0] M1[20] M2[-1] M3[-1] M4[-1] M5[-1]

22:Apr:2011 14:26:39 -vService| Er CiscoDeviceDiscoveryModule::Dest[255.255.255.255], Mask[255.255.255.255], Policy[0], NextHop[10.45.1.104]

22:Apr:2011 14:26:39 -vService| Er CiscoDeviceDiscoveryModule:: IfIdxex[2] Type[3] Proto[2] Age[104199] NextHopAS[0] M1[1] M2[-1] M3[-1] M4[-1] M5[-1]

22:Apr:2011 14:26:39 -vService| Er CiscoDeviceDiscoveryModule::End of table

22:Apr:2011 14:26:46 -UC Comm| &R UC5XX version = 15.1(2)T2, Uptime = 1 week, 1 day, 22 hours, 10 minutes, Details = Cisco UC540W-BRI-K9 (MPC8358) processor (revision 0x100) with 249856K/12288K bytes of memory. Processor board ID FHK142677K9 MPC8358 CPU Rev: Part Number 0x804A, Revision ID 0x20 14 User Licenses 10 FastEthernet interfaces 2 ISDN Basic Rate interfaces 2 terminal lines 1 Virtual Private Network (VPN) Module 4 Voice FXS interfaces 1 Voice MoH interface 1 802.11 Radio 1 cisco service engine(s) 128K bytes of non-volatile configuration memory. 254464K bytes of ATA CompactFlash (Read/Write) License Info: License UDI: ------------------------------------------------- Device# PIDSN ------------------------------------------------- *0 UC540W-BRI-K9 FHK142677K9 Configuration register is 0x2102 UC540#

22:Apr:2011 14:26:55 -vService| Er CiscoDeviceDiscoveryModule::Upgrade: Checking for OM upgrade, current version: 1.12.20.00, build: Dec 20 2010 - 09:31:36

22:Apr:2011 14:27:33 -UC Comm| &R handleIOSCallHistoryPrompt: received timeout, rx buffer: "Telephony call-legs: 491 SIP call-legs: 3 H323 call-legs: 0 Call agent controlled call-legs: 0 Total call-legs: 494 There are 494 call records, displaying to console may impact the performance of the gateway it is suggested that output be redirected to flash or disk. Do you still want to continue display to console? [yes/no]"

22:Apr:2011 14:27:33 -UC Comm| &R Error when waiting for IOS Init Event : handleIOSCallHistoryPrompt: received timeout, rx buffer: "Telephony call-legs: 491 SIP call-legs: 3 H323 call-legs: 0 Call agent controlled call-legs: 0 Total call-legs: 494 There are 494 call records, displaying to console may impact the performance of the gateway it is suggested that output be redirected to flash or disk. Do you still want to continue display to console? [yes/no]"

[Brandon Buffin]

Can you ping the UC500? Does your other router have a route to it?

Brandon

[martinipenburg]

yes we can ping and yes we have a route from the default gateway to the UC500

[David Trad]

Hi Martin,

Firstly was this system configured using CCA version 3 or is this a CLI based system?

OM is connecting to the system, but since this is the first time looking at the logs I am still trying to discern if there are any errors displayed, none yet found though

What happens if you connect the PC directly to the UC and try to log into it that way? Does it work then??

You 100% have a route to it because it probes the machine and gets all the information of it, but the logs do not appear to show any errors but that is because I am an untrained eye to the OM logs, I can read CCA logs now (Well at least I think I can).

I'll keep looking over the log and see if anything sticks out, but whilst looking into it can you please plug a system directly into the UC540 and see if that works please?

OH and make sure you have the latest version of Adobe flash player and Adobe AIR, and be very very careful of the latest Adobe update, it seems to corrupt previous installation and you have to do a re-install of it.

Cheers,

David.

[martinipenburg]

Hi David,

thanks for answering and looking in the case. after further going thrue the logs i find the cause. this was because we enabled call history and the history database was more than 480 records. i suppose that office manger opens in the background the show tech voice command to collect system information but the sh tech voice command holds because of the 480 records limit.

after decreasing the database en rebooting the device the log was quite small and officemanger was able to start and function normally.

thanks again for helping!

regards,

martin

[David Trad · Accepted solution]

Hi Martin,

I am glad to hear it

Today I have learnt something new myself today which is always a good thing

If the problem is no longer, then can you please mark the thread of as answered, this can help those out who use search terms to look for the same or similar problems.

Cheers,

David.