Howto:Config size Limitations: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| 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= | ||
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. | |||
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 | ||
==Relay== | |||
* 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. | ||
=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 relay routing engine. | |||
Instead, we recommend an assessment of the necessary concept and a sustainable solution. | |||
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'' | |||
== | =Tools= | ||
*Online Calculator of bytes on String - https://mothereff.in/byte-counter | |||
* | |||
Revision as of 12:31, 18 April 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
Relay
- 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.
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 relay routing engine. Instead, we recommend an assessment of the necessary concept and a sustainable solution.
Examples:
- E164 Setup - use global structured numbering plan
- 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
Tools
- Online Calculator of bytes on String - https://mothereff.in/byte-counter