Howto:Config size Limitations: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 23: | Line 23: | ||
*[[Howto:Create_an_ACD_Routepoint_with_external_Call_Distribution_Logic|Howto: external ACD Routepoint logic]] | *[[Howto:Create_an_ACD_Routepoint_with_external_Call_Distribution_Logic|Howto: external ACD Routepoint logic]] | ||
*separate Node with CFx's | *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 10:43, 18 April 2018
Limitations
There are various global restrictions in the config size:
- the total size of "config change" commands must not exceed 29kB
- 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
There are some special restrictions in the config size:
- No more than 32 alias entries are allowed on one Gatekeeper/Registrar interface.
- No more than 6 Hardware IDs on a PBX Object are possible.
So if there is a problem, you can try to use shorter aliases, leave out redundant informations. Nevertheless, it is ugly.
Online Calculator of bytes on String - https://mothereff.in/byte-counter
Weak Scenarios and alternative Solutions
Many number mappings in the routing engine
Use PBX Features instead:
- E164 Setup
- 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