Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

IX Workplace and SIP trunks Issue

IX Workplace and SIP trunks Issue

IX Workplace and SIP trunks Issue

Hello All,

I’m hoping someone here can assist with this issue I seem to be having.

I have a customer running an IP Office on R11. firmware. They are using SIP trunks and IP desk phones (J series). I have configured both LAN ports, LAN1 is using 192.168.125.X/24 and LAN2 is 10.170.150.x/16. LAN1 is used for all the IP phones and LAN2 is used to communicate to the outside world. The VM Pro is a Windows box configured with both networks as well using the 10 network to communicate with IP Office.

The customer was using One-X but was having issues with it so I decided to move them over to IX Workplace.

The issue is, for some reason, the SIP trunks want to use LAN1 even though I tell them to use LAN2. If I disable LAN1’s “SIP Trunk Enable” button, the SIP trunks go down.

The original FQDN was sending packets to both the IP Office and to the One-X server for One-X Mobile. But with IX Workplace you don’t use the One-X Server anymore and all traffic is sent to the IP Office directly.

The Customers firewall is using dual 1:1 NAT and they have forwarded all the necessary ports for IX Workplace to the IP Office except for ports 5060 & 5061 because if they change that route the SIP trunks go down.

IX Workplace works perfect from inside the company via the Wi-Fi network using the new FQDN but when we try to connect from outside the company, via cell network, it will not connect. This is due to the port forwarding rules, which I know.

I’m looking for a suggestion for my next steps. As everything I have thought of, does not seem to work.

RE: IX Workplace and SIP trunks Issue

Use the same interface for IX Workplace and SIP trunk. The trunk only uses the Interface information (Topology) of the chosen LAN interface. The interface used to send SIP packets is chosen based on the routing table.

If you get information about the IP addresses of the provider's SIP infrastructure you can also setup individual routes to those IPs to send the SIP packets.

IP Office remote service
IP Office certificate check
CLI based call blocking
SCN fallback over PSTN

RE: IX Workplace and SIP trunks Issue

Thank you derfloh. Will see if I get the customers IT guy to make the changes

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close