On Sat, 2009-09-12 at 00:22 -0500, Josh Patten wrote: > FYI my plan was to migrate my sipX installation to a new server (HP > DL-360 G5 8 cores 16 GB RAM) when 4.0.2 came out so I could install it > on 64 bit CentOS so I can be prepared for when I start to get into 500+ > extensions (I am curious why there are only 32 bit ISO's available). I > first upgraded my existing server according to the wiki and that went > without a hitch. > > To migrate the server to the new hardware I used the backup-restore > method of moving the server and while that worked for the most part > there were a few things I had to move manually (mainly custom stuff, but > device firmware files didn't move over), which is not a big deal. The > part that caused me 3 hours of hair pulling was sipXbridge. No matter > what I did I couldn't seem to get media going on the call. As soon as I > picked a ringing call up, either inbound or outbound, one of the sides > would terminate the call, no audio passed. > > During the latter half of the second hour of pulling on my hair, it > occured to me that I'd been down a similar path with sipXbridge before, > and what I did to fix the issue was re-run sipxecs-setup and re-enter > all the original configuration values. So I did that again for this > issue and it fixed the problem. > > In retrospect I believe it was an SSL certificate problem as that is > what I traced it down to last time, but I'm not terribly concerned about > it now that it's working.
Did you use the same hostname on the new server as you'd used on the old one? The hostname is in the certificates, and in several other places, but moving certificates from one machine to another should work if the hostnames are the same. _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
