IP Routing FAQ

What is IP Routing?

The originating Service Provider generates a dip to check if there is an IP routing call record.

From there, based on the information gained from the dip, the originating Service Provider determines if an IP routing arrangement with the Service Provider for the IP endpoint is in place by looking into the Route link Data Feed.

If so, a fully qualified domain name (FQDN) that points to the IP endpoint is utilized to make a direct connection with the terminating Service Provider

If someone owns an endpoint FQDN, but are not a carrier or RespOrg, how do they enable it with SOMOS?

They would need to have a RespOrg manage the FQDN on their behalf.  You must be a RespOrg to add an FQDN to the system

How many FQDNs can a RespOrg have as an option at a time?

For example, knowing that I can only pick 2 to route to and the second would only work if the first one was down, can I have a list of 100 to choose from at a given time?

There is not currently a limit on how many FQDNs a RespOrg can have access to.

Also, how does the OSP know if the first route is down? Do they have to have some monitoring in place, or is this something SOMOS is pinging to check and then routelink tells the route?

 When the OSP attempts to pass the call they would receive back an “unavailable” response or something similar.  This would let them know if the FQDN was down. RouteLink does not do any monitoring of FQDNs in the system.