Location Based Routing

When you use Location Based Routing, the Location Number is defined on the cabinet and/or gateway, and IP Network Region.
Whatever device the station is connected or registered to determines which ARS table is used for routing.
With Location Based Routing you don't have to use Partitioning.

If you wanted to continue using Partitioning, and depending on your switch version, there is a Special Application available, SA9050, that increases the Partition Tables up to 32. If you don't have that and still need to use partitioning for some reason with the location based routing, you could start sharing Partition Group Numbers. For example, for CORs with Partition Group 1 you could use p1-p100 for routes on the ARS tables for one location, and p101 to p200 on the ARS tables for routes for another location.

So for digital phones that's easy to determine, the location defined on the port network it is connected to is the location routing it will use.

So if I build a new location and define the cabinets with location 9, add a location ars ana table for location 9, then all digital phones connected to that cabinet will use the location 9 ars ana table.

From what you stated, IP phones will rely on the ip-network-mapping, so a phone that registers with the system from the range defined in the ip-network-mapping will look at the network region defined and use the location defined in the network region.

For remote IP users this is an issue because the IP phone or application can register to any of the CLANs in our PNs at any of our locations. IP Agent this was "resolved" by allowing the application to configure your emergency number (either extension or other telephone number). But it looks like One-X Agent doesn't have this?

- Stinney

Quoting only proves you know how to cut and paste.

If a site is currently using the ALL location for routing, does it retain a copy of that table locally in the S8300 for LSP purposes?

- Stinney

Quoting only proves you know how to cut and paste.