Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

Register Log in
  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

IP500V2 Release 9 to Server Edition Virtual

Status
Not open for further replies.
VTTD1870

VTTD1870

Technical User
Dec 31, 2008
213
US
Had customer running on release 9 on IP500V2. Moved to Virtual machine sever Edition. SIP Trunks won't register. Had them coming in on LAN2 on IP500V2. Have same configure on Virtual but not working.
 
Sort by date Sort by votes
You need to be more specific as your info is lacking that :)
But configuring a SIP trunk on a server edition is nothing different to be honest.
I would have exported the trunk as binary and imported it on the server edition.
This way the settings could not have been changed.
Did the IP address change perhaps?


BAZINGA!

I'm not insane, my mother had me tested!

 
Upvote 0 Downvote
I think we have some sort of routing issue. Have SIP coming in on LAN2. Cannot even ping from LAN2 to SIP Provider's gateway IP address on router 5 feet away.
 
Upvote 0 Downvote
I think you do.
What does your IP route look like?

BAZINGA!

I'm not insane, my mother had me tested!

 
Upvote 0 Downvote
Customer moved from one location to another. Is it possible to roll back to original virtual machine before an changes were made to the configuration? Would that affect the SSID?
 
Upvote 0 Downvote
SSID depends on IP addresses and hostname but you can check that in the manual.
Hostname does change it for sure.

BAZINGA!

I'm not insane, my mother had me tested!

 
Upvote 0 Downvote
SID depends on time zone also!

Sadly until today I got no answer if there are other Informations it depends on.

Once Avaya support desk wanted me to reinstall a virtual primary server. I asked if they guarantee that I get the same SID again so that licences will still work and from that point the support guy didn't want to give me a GO. So no one knows for sure? I think I will try it in our lab. Install, configure, delete the machine. Install and configure a new one on another host with same IPs and host names and time zone.

Two hours of work but useful to know what's possible or not.

Reinstall from scratch and wait one or two days for a license swap because you get a new SID is not an option. Especially in bigger Serber Edition solutions.
 
Upvote 0 Downvote
I feel like there is a problem in routing. I cannot get sip trunks going on the customer's vm. I brought a R210 from our lab, I cannot get the sip trunksgoingon that either. However, I have no problem making the sip trunks work on our IP500 V2.
 
Upvote 0 Downvote
In SSA I can ping lan1 address to lan2 address and the system that can successfully register sip trunks. I cannot ping from lan1 to lan2 on either of the server deployments.
 
Upvote 0 Downvote
Did you set up the relations of Linux network interfaces (eth0/eth1) and IPO interfaces (LAN1/LAN2) in Web Management correct?
 
Upvote 0 Downvote
Does the system have the correct gateway?
Lan1 and Lan2 have the same gateway but you route your traffic with an IP route if lan2 needs a different gateway ofcourse.


BAZINGA!

I'm not insane, my mother had me tested!

 
Upvote 0 Downvote
The network interfaces in web control look correct and they have the same gateway. The route we built in the lab ip500v2 is the same as the one built in the server.
 
Upvote 0 Downvote
In sysmon it appears as though the sip invite is being initiated from lan1 instead of lan2.
 
Upvote 0 Downvote
Eth0: 192.168.42.1 255.255.255.0 192.168.42.254
Eth1: 192.168.16.5 255.255.255.0 192.168.42.254

Ip route for sip (lan2):192.168.16.1 (sip gateway) from 192.168.16.5 (lan2)
 
Upvote 0 Downvote
But 42.254 is not a valid gateway for a 16.x addressed device, it can't work like that :)

 
Upvote 0 Downvote
On site with VTTD1870. We have the same IP address built on our demo unit and the SIP trunks come up right away. Should we still change this .254 address?
As far as the Linux network relation from eth/0 and eth/1 to LAN 1/ LAN 2, do we need to set up the sub interface section in the web portal?
 
Upvote 0 Downvote
The gateway is correct I imagine, but a 16.x device can't have a 42.x address as its gateway with a 24 bit mask, it needs a gateway in the same range....:)

 
Upvote 0 Downvote
Followed all of your collected advice and it paid off. Tried a few things and the SIP trunks have successfully registered. Thank you very much. That's the good news. The bad news is that we had an Avaya Engineer in the system last night (supposedly to help) and I believe he flipped the LAN1 and LAN2 settings on the IPO and did a reboot. We are now unable to communicate with 192.168.42.1. We can only talk on 192.168.16.5 which is not what we need. Is there a way for us to figure out what change he made and how to reverse it?
 
Upvote 0 Downvote
What is your IP range internally? Why does the IP you programme over important? :)

 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

DigitalG
  • Question
Upgrade path virtual server edition VMware from 11.1.3.2 to 12.1 1
Replies
5
Views
561
OmegaStar
OmegaStar
finest
  • Locked
  • Question
Alternative SBC to ASBCE - Server Edition (we have both physical server and server edition virtual)
Replies
3
Views
899
Fr0gg3r - MaartenS
Fr0gg3r - MaartenS
finest
  • Locked
  • Question
VM Pro License > Server Edition Virtual
Replies
1
Views
711
MrFooF
MrFooF
NYSTECH
  • Locked
  • Question
IP Office Migrating from Metal server to Virtual server
Replies
5
Views
511
biv343
biv343
DigitalG
  • Locked
  • Question
Server edition Uplift to Select editon 1
Replies
3
Views
564
JoConnex
JoConnex

Part and Inventory Search

Sponsor

Back
Top