Howto:Config size Limitations: Difference between revisions

From innovaphone wiki
Jump to navigation Jump to search
m (Reverted edits by Slu (Talk); changed back to last version by Sga)
(revert correct version)
Line 1: Line 1:
<!-- Keywords: config line size lenght length configline alias maximum number max config conf line relay maximum characters maps routes how many routes maximum routes maximum maps limitations restrictions -->
<!-- Keywords: config line size lenght length configline alias maximum number max config conf line relay maximum characters maps routes how many routes maximum routes maximum maps limitations restrictions -->
=Limitations=
=Limitations=


There are various global restrictions in the config size:
Sometimes, in large scenarios, there are configurations that can exceed some limits. This is to be considered in a concept planning.<br />
In most cases, problems with the limitations are simple conceptual errors and can be resolved by a different configuration.


* the total size of "config change" commands must not exceed 29kB
If you have any problems with the concept development, or problems with understanding, please feel free to contact [mailto:presales-at-innovaphone-dot-com our presales team]
 
==Global==
* the total line length must not exceed 20kB (for v11r2 and earlier versions the limit is 8kB)
* the total line length must not exceed 20kB (for v11r2 and earlier versions the limit is 8kB)
* the number of whitespace separated strings (words) on a config line must not exceed 1024
* the number of whitespace separated strings (words) on a config line must not exceed 1024


There are some special restrictions in the config size:
==Gateway layer==
* the total size of "config change" commands must not exceed 29kB
 
==Interfaces==
* No more than 32 alias entries are allowed on one Gatekeeper/Registrar interface.
* No more than 32 alias entries are allowed on one Gatekeeper/Registrar interface.
==PBX Objects==
* No more than 6 Hardware IDs on a PBX Object are possible.
* No more than 6 Hardware IDs on a PBX Object are possible.
* No more than 32 conditions (only/only not) in a single CFx are possible
: If more conditions are needed, we recommend moving the logic to an external XML script that interprets the CGPN and forwards the call if necessary. See [http://wiki.innovaphone.com/index.php?title=Category:Sample sample scripts]


So if there is a problem, you can try to use shorter aliases, leave out redundant informations. Nevertheless, it is ugly.
=Weak Scenarios and better Solutions=


Online Calculator of bytes on String - https://mothereff.in/byte-counter
==Many Routes and Number Mappings in the routing engine==
It is not recommended to create very large configurations in the routing engine.
Instead, we recommend an assessment of the necessary concept and a sustainable solution.


=Weak Scenarios and alternative Solutions=
Examples:
*[[Course12:Advanced_-_E164_PBX_Setups|E164 Setup]] - use global structured numbering plan
*[[Howto:Create_an_ACD_Routepoint_with_external_Call_Distribution_Logic|Howto: external ACD Routepoint logic]] - use external call-distribution logic via Vociemail Object
*[[Howto:Central_SIP_trunk_with_multiple_subscriber_numbers]] - use an additional PBX and GW-interfaces to map subscriber numbers to internal extensions
*separate Node with CFU's - use an additional Node for CFU's with Trunk Object and activated ''Discard received diverting No''


==Many number mappings in the routing engine==
=Tools=
Use PBX Features instead:
*Online Calculator of bytes on String - https://mothereff.in/byte-counter
*[[Course12:Advanced_-_E164_PBX_Setups|E164 Setup]]
*[[Howto:Create_an_ACD_Routepoint_with_external_Call_Distribution_Logic|Howto: external ACD Routepoint logic]]
*separate Node with CFx's
* [[Howto:Central_SIP_trunk_with_multiple_subscriber_numbers]] - uses an additional PBX and GW-interfaces to map subscriber numbers to internal extensions

Revision as of 16:20, 14 June 2018


Limitations

Sometimes, in large scenarios, there are configurations that can exceed some limits. This is to be considered in a concept planning.
In most cases, problems with the limitations are simple conceptual errors and can be resolved by a different configuration.

If you have any problems with the concept development, or problems with understanding, please feel free to contact our presales team

Global

  • the total line length must not exceed 20kB (for v11r2 and earlier versions the limit is 8kB)
  • the number of whitespace separated strings (words) on a config line must not exceed 1024

Gateway layer

  • the total size of "config change" commands must not exceed 29kB

Interfaces

  • No more than 32 alias entries are allowed on one Gatekeeper/Registrar interface.

PBX Objects

  • No more than 6 Hardware IDs on a PBX Object are possible.
  • No more than 32 conditions (only/only not) in a single CFx are possible
If more conditions are needed, we recommend moving the logic to an external XML script that interprets the CGPN and forwards the call if necessary. See sample scripts

Weak Scenarios and better Solutions

Many Routes and Number Mappings in the routing engine

It is not recommended to create very large configurations in the routing engine. Instead, we recommend an assessment of the necessary concept and a sustainable solution.

Examples:

Tools