Genesys Casual

 View Only

Sign Up

  • 1.  3 outbound regex rules per external trunk

    Posted 20 days ago

    Do we know why Genesys only allows 3 address transformations in the trunk? We will have more then 3 area codes soon. 


    #General

    ------------------------------
    Edward Gonzales
    ------------------------------


  • 2.  RE: 3 outbound regex rules per external trunk

    Posted 17 days ago

    As far as I know, the limit of three Address Transformations is a platform design decision rather than a SIP or carrier limitation.

    If you expect to manage more than three area codes, one option could be to simplify the transformation logic by using regular expressions when possible, or to split the routing across multiple trunks if the design allows it.

    Another approach would be to submit a Product Idea if this limit is becoming a common operational constraint, especially for organizations managing multiple numbering plans.

    I'm interested to know if anyone from Genesys can share whether this is a technical limitation or a configurable platform limit.



    ------------------------------
    Luis Antonio Padilla Yee
    na
    ------------------------------



  • 3.  RE: 3 outbound regex rules per external trunk

    Posted 16 days ago

    Thanks, we are good for now but are maxed out and don't like having a limit. I guess we can split more off to another trunk if needed. I haven't seen anyone else complain yet so maybe i am the only one maxed out. 



    ------------------------------
    Edward Gonzales
    ------------------------------

    Original Message


  • 4.  RE: 3 outbound regex rules per external trunk

    Posted 16 days ago
    Edited by Raphael Poliesi 16 days ago
    Hi Edward,
     
    Based on the documentation, the current limit of three address transformations per trunk is a platform limitation.
     
    Using more advanced regular expressions can sometimes help consolidate multiple rules into a single transformation, although that can also make the expressions harder to read and maintain. If you need more than three independent transformation rules, the practical workaround today is to split the routing across multiple trunks.
     
    I also found there's already an existing Idea requesting that this limit be increased to a configurable value:
     
    https://genesyscloud.ideas.aha.io/ideas/CERTNG-I-1913
     
    Although the use case described there is multiple divisions requiring different transformations, it addresses the same platform limitation. If it aligns with your needs, I'd recommend adding your vote and sharing your use case in the comments.
     
    Since you've already reached this limit, it's also worth checking the comments on that Idea. You may find other customers facing the same challenge, and adding your scenario can help demonstrate the demand for this enhancement.



Related Content