Signal Server commands - 2004p1 and 3904s missing caller list

[robakabobbo]

Hello. I am in need of how to use the commands to check my signaling server. I have had a few reports of 3904s and 2004p1s down. I read on some other threads that its most likely caused by the signaling server , one of them not being the leader. What commands should I use to check this? Also if this is the issue, how would I correct this?

Thanks in advance

 

[Tacosoup]

Login to the signaling via command line:


appstart pd status (checks current status)

appstart pd restart

This will not interrupt service


** Proofread carefully to see if you any words out.

 

[robakabobbo]

[*******@sigserver2 ~]$ appstart pd status
pd is stopped
[*******@sigserver2 ~]$ appstart pd restart
[ OK ]
[ OK ]
Synchronizing the system host database file [ OK ]
Stopping PD: PD is already stopped. [ OK ]
Application 'pd' was not started (possibly not configured).
[******@sigserver2 ~]$ appstart pd status
pd is stopped
[********@sigserver2 ~]$
What is PD? would this be causing my issue?

 

[Tacosoup]

PD is personal directory
Try checking SigServer 1 ( I noticed that is SigServer 2)
It only has to work on one SigServer

** Proofread carefully to see if you any words out.

 

[robakabobbo]

[*****@sigserver1 ~]$ appstart pd status
pd (pid 6309) is running...
[*****@sigserver1 ~]$

So I must be looking at a different issue. We had a power issue monday, and out vendor was here monday looking at it while doing other work. Coincidence I thought that it may be this issue.

 

[Tacosoup]

They can be kind of funky. I had a site where the PD worked on phones registered to SS1, but not on SS2.
I finally moved the phones over to SS1 and rebooted SS2 to get it working again

** Proofread carefully to see if you any words out.

 

[robakabobbo]

We've had this issue before but it was an all or nothing. Our support vendor has had to look at it twice within 3 months. So if i wanted to reboot this remotely, like from home, how can i do this, like if i were to do it at night with no one being here, if you don't mind me asking

 

[Tacosoup]

Just type the command "reboot" and it will ask you if you are sure (Y/N) and enter Y
You can do the SigServers one at a time, moving the phones to the SigServer you are not rebooting with the command
disiTPS
(This does a courtesy force over)

disTPS
(No courtesy)

If you type "help" you can scroll through the commands on the SigServer

maintadmin/bin has the TPS commands
systemadmin/bin has reboot

Also if you have SIP trunks you will want to do disVTRK to move those over from SS1 to SS2





** Proofread carefully to see if you any words out.

 

[gwebster]

FWIW, the SS has nothing to do with M3904. If you have M3904 "down", then it is not caused by SS issues.