Genesys Cloud - Main

 View Only

Sign Up

  Thread closed by the administrator, not accepting new replies.

  • 1.  BYOC Carrier - Diversion Header

    Posted 10-24-2022 02:45
    No replies, thread closed.
    Hi All

    We have enabled Diversion header under 'Diversion Method'  in Trunk settings to as per our Carrier SIP Trunk requirements.

    config

     

     

     

     

    1. This works as intended when an External User A calls PureCloud user 'B' , diverted to External user C

     

    Diversion: sip:+61xxxxxxxx@10.47.17.50;user=phone;reason=deflection

     

    1. However, there is an issue when the A-party is another local user.

     

    i.e Local User A Calls PureCloud user 'B' , diverted to External user C,  the diversion header is populated with the user extension. This does not meet our SIP Trunk provider requirements causing a call failur

     

    sip:2502@10.47.17.50;user=phone;reason=deflection

     

     

    How can we enforce the DID to be used in this scenario (as per scenario 1)


    #Implementation
    #SIP/VolP
    #Telephony

    ------------------------------
    David Ragon
    Ethan Global Pty Ltd (t/a Ethan)
    ------------------------------


  • 2.  RE: BYOC Carrier - Diversion Header

    Posted 10-28-2022 19:34
    No replies, thread closed.
    If User B have both DID and Ext number, you need to update the user profile and set the DID number to "Primary Voice".

    The DID number has to be a valid number from your SIP provider.

    ------------------------------
    Paulo Mesquita
    Vodafone New Zealand Limited
    ------------------------------

    Original Message


Related Content