Signaling server 4.5

[wcmyers3]

My issue is simple. When our signaling server reboots, the Virtual DCH never establishes on its own. We always have to completely reload the sig server from the CD to get it to work again. I have other sites that don't require this. I have tried DCHmenu from the sig server command line and it doesn't work at all. We replaced the server and the 2nd one does the same thing. This site was fine until we moved it to another building and had to change all of the IP information. Any ideas?

 

[pronei]

I would rebuild the DCH before I'd rebuild the SS.

 

[allenmac]

Have you made sure that the D-Channel is set to automatically recover in LD 96?

ld 96
DCH000
.stat dch
DCH 050 : OPER EST ACTV AUTO DES : H323
.


If your D-Channel does not have the 'AUTO' designation, you will need to manually establish after an outage.

 

[tnphoneman]

When you reload are you reinstalling all the patches?

Signature===========================================
Artificial Intelligence Is No Match for Natural Stupidity.

The latest survey shows that 3 out of 4 people make up 75% of the population.

The original point and click interface was a Smith & Wesson.

Red meat is not bad for you, it is the green fuzzy meat that is bad.

 

[Triton101]

As suggested above in LD 96 on the PBX (call server) with virtual dch, I would go with that first.....

__________________________________________________________
Find a job you love and you'll never work a day in your life. - Confucius

 

[johnpoole]

rebuild the d and download the card.. and why does it need to reboot? if i need to boot here more then once a year it would be a problem... unlike mr gates toys, if built right and maintained a reboot is not that common

john poole
bellsouth business
columbia,sc

 

[allenmac]

I agree with johnpoole.

I have 12 ISP1100s in my inventory, and I have never had to rebuild any of them. If you are convinced that the problem is in a particular server, then re-partition the hard drive, and rebuild it from scratch.

Always keep up to date with PEPs as well. I have seen some strange things cleared up with a MDP refresh.

 

[bignose21]

I would take a good look at your config if all your problems started after you redid the IP.

Start at CS active host, mask, route has an update database been done.

Then the Sig server on the install menu you only need to do basic SS config only, do your changes boot up delete old node if its still there retrieve new node, finish setup of new node (add extra SS and VGMC/MC32s) save and transfer reboot Leader. Then boot up your VGMC's and followers (as long as you don't change the Host name of the Leader the Follower SS don't need touching).

 

[esoare]

are you stil there wcmyers3?
es

 

[wcmyers3]

Ok, we found the issue. After rebuilding the node in Element manager to change the IP information, this was the setting that was set to NONE. We changed it to H323 and it worked. We had to reboot the signaling server to get the DCH to come up again, but to test it, we rebooted again and it established on its own. Thanks for all the help!
This setting is under Node Configuration, and signaling server properties.

Enable IP Peer Gateway (Virtual Trunk TPS)-H.323 only