Tuesday, August 28, 2018

Verizon SIP requires VPN and public IP range?

I’m at the beginnings of a project to migrate a call platform over to our network and have come across a weird one. One of the SIP carriers is Verizon, there is a p2p link between Verizon and one of our routers, with a vpn pointing towards verizon(not at the p2p ip, just routed towards them), and the LAN subnet associated with this setup is a public range, assigned by Verizon, but not routable over the internet.

I’ve never seen this before and have scheduled a call with Verizon for the end of the week to see why we have it set up this way.

Anyone seen similar before? I’ve never seen VPN’s pointing to a sip endpoint when on a private circuit, and definitely never been told we have to use their ip range on the lan



No comments:

Post a Comment