SIP Trunk Delivery Question
-
We usually purchase a our DID's trough a provider like Flowroute and send the SIP traffic to a separate public IP on our internet connection and route it to our 3cx server from there. We have a site where a decent internet connection wasn't available so the ISP is going to give us a SIP trunk that is delivered via a T1.
The provider will put in an adtran as their CPE and then is planning on giving us an internal 192 based IP to attach to our IP PBX. Our IP PBX is 3cx and will run as VM on HyperV 2012. We planed to do a external non shared NIC for the SIP connection and a External managed by the host NIC for the PBX. Will this work? Or is the fact they are giving us a non routable out of their CPE just causing my brain to lock up. It's seems foreign to get a 192 address for a service, I was expecting a routable public IP.
-
@NETS said:
It's seems foreign to get a 192 address for a service, I was expecting a routable public IP.
You don't want routable. Remember there is no Internet involved here, so using routable public IPs would be wasteful as they could not overlap with "real" ones, yet could not be connected to the Internet.
This is purely a private networking service, so you want private IPs. What they are doing is totally correct.
-
You will likely connect the new Adtran to your LAN just like another router coming onto it. So your PBX doesn't need any special configuration other than having a route entered to know to look to the Adtran for addresses on that subnet.
-
How should we configure our Hyper Virtual Switch?
- NIC 1 for the SIP on 192.168.3.2 (Not shared with the host)
2 NIC 2 for the PX on 192.168.1.2 (our normal internal range)
Since it's pure SIP we shouldn't have to worry about STUN over their router correct?
- NIC 1 for the SIP on 192.168.3.2 (Not shared with the host)
-
@NETS said:
Since it's pure SIP we shouldn't have to worry about STUN over their router correct?
Correct
-
Welcome to MangoLassi, by the way!
-
@NETS said:
- NIC 1 for the SIP on 192.168.3.2 (Not shared with the host)
2 NIC 2 for the PX on 192.168.1.2 (our normal internal range)
Yup, that's fine. You can do it that way. Or you can have the routers handle it and only have one NIC on the PBX. Works both ways. Depends how you want to handle it.
- NIC 1 for the SIP on 192.168.3.2 (Not shared with the host)
-
Thanks,
I've followed you on SW and your blog and this is another great IT resource. It' helps me sleep and night knowing there's fellow IT people that I can bounce things off of when I hit a wall. Hopefully I can help a few others out as well.
-
Hopefully you find a lot of good resources here. It's very active and friendly.
-
This post is deleted!