Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations dencom on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Tenant partitioning

Status
Not open for further replies.

bparr

Technical User
Feb 11, 2009
25
US
I have a small tenant partition with a single T1 trunk and a range of DIDs. When the new tenant was created, I thought I was told that any station that has a 2 in the TN field, would direct any outbount calls to the trunk for that tenant which also has a 2 in the TN field.

I have created some new stations in that tenant but the calls are going out the trunks for the old tenant.

What am I missing?
 
Check your COR's, if they have a different time of day chart, the COR could be using a different route number... which could be programmed to use different trunks.

display COR - note the time of day chart number
list ars analysis -- find the closest match to the dialed number, check the route pattern column.. it should have a p then a number. This is your partition number.
display partition-route-table x -- x being the partition number in the previous step. The partition number is the route index number on the page. The time of day chart number is the column number (PGN 1 is time of day chart 1) Where they meet on the chart is the route number.
display route-pattern x ---- x being the route number in the previous step. The route pattern screen will show you which trunk the call used.

If you use locations, you'd use the list ars analysis location x --- x being your location

A shorts cuts:
list ars route-chosen xxxxxxxxxx
list ars route-chosen location x xxxxxxxxxxx

Also, tenant.. the change tenant command controls tenant items.

Wildcard
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top