Jump to content

Migrated to Vmware and trunk will not come up.


bruce
 Share

Recommended Posts

We've been running Snomone one on a physical server now for about 2 years with no issues. It's running under ubuntu 10.10.

 

I've needed to migrate this to a new server and to upgrade the version of snomone to the newest.

 

So. I've run up a Debian 7 under VMware. Installed the newest version of snomone as per instructions on the wiki.

 

I backed up my config on the old server, imported to the new. Everything came right up.

 

We run dual nics, one internal one external just fyi. Tried to migrate over and our voip trunk will not come up. Constantly gets a 408 error.

 

Upon some more testing found out that running tcpdump shows that when I click register in the admin interface I get 0 traffic on my external nic, hence its not even trying to register and im getting a 408.

 

Am I barking up the wrong tree here trying to get this to run in a vm? Is there something with snomone that I have to set different to make it work. I've verified all network level stuff and it all works. Same settings throughout. The only difference is a new version of snom and the fact that its in a vm.

 

Any help here would be appreciated.

 

Thanks

Bruce

Link to comment
Share on other sites

I would suspect a problem with iptables on the system. I don't think this is a issue with VM. Can phones register and for example call the mailbox? The other thing is if the DNS server is setup properly, check /etc/resolv.conf.

 

I thought the same thing. Iptables is accept on all. Resolv.conf is set to same dns servers as old server. I can get everywhere on the internet.

 

What I did find out is.

 

If I do a tcpdump on the external interface and click register its nothing. Its almost like snomone cannot see the interface. I have completely removed the trunk and re set it up.

 

In addition I thought it might be an issue with using Debian 7 since it just came out. So I reverted back to debian 6. Same thing.

 

That's where I'm at now.

 

Thanks

Bruce

Link to comment
Share on other sites

If you have multiple interfaces, check your IP configuration. What does "ifconfig", "route" and "iptables -L" produce? We are using Debian 6.0.5.

IFconfig is exactly like the old. I can verify that working. 1 external interface with gateway, 1 internal with no gateway. That works.

 

route is correct. Default route goes out where it should. Verified all internet connectivity.

 

I actually totally removed iptables just to get that out of the way.

 

I did a tcpdump on port 5060 testing with 1 phone to see if it registers.

 

 

09:35:19.933261 IP 192.168.1.228.2048 > 192.168.1.188.sip: SIP, length: 657

09:35:23.943406 IP 192.168.1.228.2048 > 192.168.1.188.sip: SIP, length: 657

 

I see the phone ( 228 ) communicating with the snom server ( 188 ) but it will not register.

Link to comment
Share on other sites

Hmm. Does the PBX bind to port 5060? "netstat -anp|grep pbxctrl" will show you that. Can you log into the web interface and check if there phone IP address was blacklisted?

tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 1564/pbxctrl

tcp 0 0 0.0.0.0:5060 0.0.0.0:* LISTEN 1564/pbxctrl

tcp 0 0 0.0.0.0:5061 0.0.0.0:* LISTEN 1564/pbxctrl

tcp 0 0 0.0.0.0:389 0.0.0.0:* LISTEN 1564/pbxctrl

tcp6 0 0 :::443 :::* LISTEN 1564/pbxctrl

tcp6 0 0 :::5060 :::* LISTEN 1564/pbxctrl

tcp6 0 0 :::5061 :::* LISTEN 1564/pbxctrl

tcp6 0 0 :::389 :::* LISTEN 1564/pbxctrl

udp 0 0 0.0.0.0:57260 0.0.0.0:* 1564/pbxctrl

udp 0 0 0.0.0.0:50368 0.0.0.0:* 1564/pbxctrl

udp 0 0 0.0.0.0:5060 0.0.0.0:* 1564/pbxctrl

udp 0 0 0.0.0.0:69 0.0.0.0:* 1564/pbxctrl

udp 0 0 0.0.0.0:39894 0.0.0.0:* 1564/pbxctrl

udp 0 0 0.0.0.0:161 0.0.0.0:* 1564/pbxctrl

udp6 0 0 :::5060 :::* 1564/pbxctrl

udp6 0 0 :::69 :::* 1564/pbxctrl

udp6 0 0 :::51935 :::* 1564/pbxctrl

udp6 0 0 :::34826 :::* 1564/pbxctrl

udp6 0 0 :::161 :::* 1564/pbxctrl

unix 2 [ ] DGRAM 6602 1564/pbxctrl

 

Ip of phone is explicitly allowed so its not being blacklisted..

 

192.168.1.228.2048 > 192.168.1.188.5060: [udp sum ok] SIP, length: 393

CANCEL sip:100@192.168.1.188;user=phone SIP/2.0

Via: SIP/2.0/UDP 192.168.1.228:2048;branch=z9hG4bK-lkiuetlkl4em;rport

From: "Bruce Markey" <sip:100@192.168.1.188>;tag=hgg0cykxhj

To: <sip:100@192.168.1.188;user=phone>

Call-ID: 3c2670553252-3omuupi3eb9o

CSeq: 1 CANCEL

Max-Forwards: 70

Reason: SIP;cause=487;text="Request terminated by user"

Proxy-Require: buttons

Content-Length: 0

 

Thats what a -vv tcpdump shows me. Still no registration.

Link to comment
Share on other sites

Oh... Well if you move your license to a new server then you have to reset the license from the snomone.com portal. Log in, then go to you account, your licenses and reset the license. Please not that you can do this only one time. Licenses are bound to one specific server, and the reset is supposed to be there when that server hardware fails. If you virtualize the server now, chances are good that you never have to do that again (VM are forever, no matter what the host hardware is looking like).

Link to comment
Share on other sites

Oh... Well if you move your license to a new server then you have to reset the license from the snomone.com portal. Log in, then go to you account, your licenses and reset the license. Please not that you can do this only one time. Licenses are bound to one specific server, and the reset is supposed to be there when that server hardware fails. If you virtualize the server now, chances are good that you never have to do that again (VM are forever, no matter what the host hardware is looking like).

 

*insert cursing here* Cannot believe all this was due to a license issue. And I only noticed it because I happened to look at one of the text files buried in the snomone dir.

 

THanks for all the help.

 

Bruce

Link to comment
Share on other sites

Yea we added that reset button to make server moves possible in version 5. We should "advertise" this more... (maybe also on the status screen of the PBX)

 

Well im still on 4.5, with a snom blue license. So I should have no issue once I actually install the correct version now?

Link to comment
Share on other sites

I guess I'll close this thread with the following thought. I just got off the phone with snom/vodia and must say I'm completely put off by their business tactics.

 

I have a server about to go down and they cannot offer any way to transfer my license to a different mac address UNLESS we pay to upgrade. That is some really bad customer service right there.

 

I'm now left trying to justify the cost of upgrading just to deal with this. I can't even move the NIC since it's legacy PCI.

 

Totally dissatisfied customer.

Link to comment
Share on other sites

Ah... Well snom version 4 licenses did not feature server moves huh.gif. The price for snom ONE blue was very aggressive to put it this way.

 

We did see the problem. Obviously it is not acceptable for us that customers or resellers use the same license on multiple servers. Having to go through every single installation and verify that a server move is legal is not practical and frustrating for everybody. That's why the license reset was added to the V5 license scheme. This is a 24/7 automated service with clear rules and there are no questions asked.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...