No Signaling Server Present In Node (?)

[robl3000]

On a recently re-commissioned lab system (CS1000E 7.6), I tried to add updated phone firmware via Element Manager. EM informs me that "There are no Signaling Servers present in IP Telephony Node 100 configured in Call Server 10.99.100.31" on the IP Firmware Page.

This is odd, as Element Manager is running on my one and only Signaling Server. If I view "System » IP Network » IP Telephony Nodes » Node Details", it shows Node 100, it shows the Call Server IP 10.99.100.31, and Associated Signaling Servers & Cards lists the signaling server.

It may well be something I missed during the install, as this is my first 7.6 system that I built. Previous lab system was 5.5 on an SSC with ISP1100 VxWorks Signaling Server, so the newer architecture is a little less familiar.

New system is a small system, SA, single MGC, CPPM VxWorks Call Server, 1 UCM -- basically the bare minimum. It is running 7.65 with all patches and SP (for CS, Linux base, and UCM) as of late May 2014.

Any pointers as to what I might have missed or how to correct the issue?

Thanks!

==================================
<INSERT SIGNATURE HERE>

 

[robl3000]

Additional information, with the exception of the IP Firmware update, the rest of the system seems to be working as expected. It shows my Signaling Server as the node leader. I have a couple phones registered. "Personal Directory" works on the phones. Element Manager seems to be talking to the Call Server as I can make changes in EM and it's pushing those changes to the CS.



==================================
<INSERT SIGNATURE HERE>

 

[KCFLHRC]

I would go into the Node configuration, look at it, do a save and transfer, and then restart applications.

 

[KCFLHRC]

I would also look at what's deployed on that SS

 

[robl3000]

Thanks for the suggestion, but it doesn't seem to be the answer. I saved / re-transfered, then restarted the applications. Same error presents itself when accessing the IP Firmware page.

The signaling server reports it is deployed with: SIP Line, LTPS, Gateway (SIP/H323), PD, Presence Publisher, IP Media Services. Enabled applications are: LTPS & PD.

[pre]Node ID : 100
Node Master : Yes
Up Time : 0 days, 2 hours, 27 mins, 42 secs
TN : 000 00 00 00
Server Type : Signaling Server
Platform Type : VMware
TLAN IP Addr : 10.99.101.41
ELAN IP Addr : 10.99.100.41
Election Duration : 15
Wait for Result time : 31
Master Broadcast period : 30
===== Node Master =====
Server Type Platform TN TLAN IP Addr
Signaling Server VMware 000 00 00 00 10.99.101.41
Next timeout : 10 sec
AutoAnnounce : 1
Timer duration : 60 (Next timeout in 59 sec)
====== Registered node elements ======
Num Server Type Platform ELAN MAC TLAN IP ELAN IP
001 Signaling Server VMware XX:XX:XX:XX:A7:ED 10.99.101.41 10.99.100.41
TN = 000 00 00 00
UpTime = 000 02:27:42
NumOfSets = 8
NumOfCensusTimeout = 0
====== All elements in node configuration are registered ======


Active Call Server type = CS 1000E
Active Call Server S/W Release = 765P
Supported Features: CorpDir UserKeyLabel VirtualOffice UseCSPwd 2001P2 2004P2 2002P2 PD/RL/CL QoS Monitoring NAT Traversal ACF IP ACD 1150 NextGen Phones IP Phones 1200
Call Server Main: ip = 10.99.100.31, ConnectID = 0x8b83128, BroadcastID = 0x8b7d308, Link is up
Call Server Redundant: ip = 137.135.128.254, ConnectID = 0x8b83228, BroadcastID = 0x0, Link is in TBD state
Call Server Signaling Port = 15000
Call Server Broadcast Port = 15001
Broadcast PortID = 0x8b836e0
RUDP portID = 0x8b83770
Tcp Link state = up
Tcp Signaling Port: 15000
Tcp socket fd: 22
Tcp msgs sent: 862
Tcp msgs recd: 11508
[/pre]



==================================
<INSERT SIGNATURE HERE>

 

[KCFLHRC]

There is a place in deployment where you have to associate the Call Server with the Signal Server for EM to work properly. I bet that never happened. I believe I would undeploy and redeploy what I needed instead of all that other stuff they have deployed.