Line partitions

Unanswered Question
Apr 17th, 2009

Today, I have a line partition for every location. All locations can call other locations. If I reduced my line partitions to 5. (5 different PRIs) Do you see any issues?

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Chris Deren Sun, 04/19/2009 - 06:57

I've seen some partners/customers implement solutions this way where they create line partition for each site without thinking about possible impact/limitations this can have.

I would never recommend this as SIP or JTAPI applications are not partition aware, which means as soon as you start using those apps you'll have issues.

Unless you have a requirement to block siteA users from calling siteB users (never seen anyone wanting to do it), there is no point of creating separate partitions, simply create global partition that all DNs are assigned to.

Typically the reason to do this is to achieve 4 digit dial plan with 4 digit extensions and have a TP that prefixes digits, again the proper way to achieve variable length dial plan is by making the extensions unique (i.e. 8 digits) in global partitions and having site specific TPs that strip the site codes instead of prefixing.

HTH,

Chris

thomuff Mon, 04/20/2009 - 11:39

Chris, You hit it on the head. That is why I am reducing it to five partitions instead of one in the event that the last 4 digits are duplicates. and we are not blocking siteA from siteB. I do have two special locations where the public can reach the phones so unless someone logins the phone. The phone lines are in a local calling search space. Thank you! Tom

Actions

This Discussion