Genesys Cloud - Main

 View Only

Sign Up

  Thread closed by the administrator, not accepting new replies.

  • 1.  What kind of trunk config we have to do to retrieve original DNIS of an inbound call in case of Call redirection/diversion at carrier/TSP.

    Posted 06-22-2023 08:38
    No replies, thread closed.
    Dear Team,
     
    Greetings. Kindly guide me, how to retrieve original DNIS(customer Dialed digits) of an inbound call using custom trunk config.
     
    Scenario:  A customer having ANI "A" is dialing  "D" number, Telephony service provider is forwarding/redirecting the traffic from "D" number to "E" number which is configured under Genesys cloud for inbound calls.
     
    Whenever I receives a call on "E" number,  I could see the ANI is "A" which is perfect but the "DNIS" is showing "E" (I am expecting a DNIS as "D" here, which my customer actually dialed).
     
    I could see SIP traces from my TSP in the below given format.  I want  DNIS value for this call, which is reflecting under "Diversion" field below. 
     
    ===========================================
     
    INVITE sip:destination@example.com SIP/2.0
     
     
    From: <sip:source@example.com>
     
    Call-ID: 1234567890
     
    CSeq: 1 INVITE
     
    Diversion: <tel:DNIS@example.com>;reason=unconditional Content-Length: 0
     
    ========================================
     
     
    I could see "Diversion Method" has been set to "From" in my org's External Trunk config. will it help if I change it to "First Diversion Header" ? 
     
    Or please let me know, is there any other way-out. Can we create a new trunk with such custom config to get the original DNIS.
     
     Thanks in advance...!!!

    #PlatformAdministration
    #SystemAdministration
    #Telephony

    ------------------------------
    Devanand Gawande
    Capgemini Brasil
    ------------------------------


  • 2.  RE: What kind of trunk config we have to do to retrieve original DNIS of an inbound call in case of Call redirection/diversion at carrier/TSP.

    Posted 06-22-2023 16:25
    No replies, thread closed.

    The usual way of doing this is to set up multiple "E" numbers and have a 1:1 forwarding match. So, customer dials "D1" and you see "E1" as the DNIS. You then use that number in automation (Architect etc.) or reports.

    Alternatively, just port the numbers to Genesys Cloud Voice.

    I'm working with a customer at the moment who is migrating from method 1 to method 2 right now!



    ------------------------------
    Paul Simpson
    Eventus Solutions Group
    ------------------------------



  • 3.  RE: What kind of trunk config we have to do to retrieve original DNIS of an inbound call in case of Call redirection/diversion at carrier/TSP.

    Posted 06-27-2023 14:25
    No replies, thread closed.

    This is a big gap when you use BYOC. The "alternative" to go direct to Genesys is not always practical or viable.

    We have same challenge with customers with 1000s DDIs where we want to direct from service provider to Genesys (via our/BYOC trunks). Ideally, to a small range of numbers which can then allow the originating DDI to be accessible (Avaya supports this) independently in the interaction / flows.

    IMHO the trunk configuration should allow this processing and carry property through to DID config and Genesys environment.



    ------------------------------
    Simon Brown
    Maintel Europe Limited
    ------------------------------

    Original Message


  • 4.  RE: What kind of trunk config we have to do to retrieve original DNIS of an inbound call in case of Call redirection/diversion at carrier/TSP.

    Posted 06-28-2023 04:04
      |   view attached
    No replies, thread closed.

    Thanks a lot for your reply, Yes I agree that Avaya allows DNIS override, on their voice switch as well as on their SBC. could you please plz let us know whether below given changes will work or not to get the original DNIS. I can try this with separate trunk. Actually I am planning to set up Org level redundancy and I dnt want to configure lots of ,DID umbers in the backup Org. just want to go with one number as a landing pad for all client calls. inside the architect I will segregate the clients on the basis of DNIS. like, we have Call.CustomerDialedNumberOriginal.

    Trunk>External Trunk>Inbound>>Identity Type>>change it from "From" to First Diversion Entry (Pfa snapshot).



    ------------------------------
    Devanand Gawande
    Capgemini Brasil
    ------------------------------

    Original Message


Related Content