Legacy Dev Forum Posts

 View Only

Sign Up

Back to discussions
Expand all | Collapse all

Change trunk_outboundIdentity_callingAddress via API

  • 1.  Change trunk_outboundIdentity_callingAddress via API

    Posted 06-05-2025 18:03

    Lloyd | 2022-06-13 02:25:30 UTC | #1

    One of our customers has a requirement to change their outbound CLI on a daily basis. They have purchased a group of numbers to use for this & I'm looking at how to automate this process for them by making an API request every morning at 1am.

    Testing in our lab, I can get the current trunk settings: GET: /api/v2/telephony/providers/edges/trunkbasesettings/{trunkBaseSettingsId}

    Which returns a JSON object with all the settings

    In the returned object I do the following:

    1. remove the *version* number property
    2. change the value stored in *properties.trunkoutboundIdentitycallingAddress.value.instance* from +649xxx1234 to +649xxx6789

    I then perform a PUT: /api/v2/telephony/providers/edges/trunkbasesettings/{trunkBaseSettingsId}

    this returns a 200/Ok

    But in the response document it shows the previous version and also shows the previous trunkoutboundIdentitycallingAddress value (+649xxx1234) not my new one.

    If I I take the exact same updated object and paste it in to the API Explorer however, and perform the same PUT: /api/v2/telephony/providers/edges/trunkbasesettings/{trunkBaseSettingsId}

    Then the response contains an *incremented version* & the *trunkoutboundIdentitycallingAddress* shows as being my new one (+649xxx6789)

    So little confused as how to proceed with this one, so any guidance appreciated

    tim.smith | 2022-06-13 19:54:44 UTC | #2

    Lloyd, post:1, topic:15104
    1. change the value stored in *properties.trunkoutboundIdentitycallingAddress.value.instance* from +649xxx1234 to +649xxx6789

    I then perform a PUT: /api/v2/telephony/providers/edges/trunkbasesettings/{trunkBaseSettingsId}

    this returns a 200/Ok

    But in the response document it shows the previous version and also shows the previous trunkoutboundIdentitycallingAddress value ( +649xxx1234 ) not my new one.

    This doesn't sound right. A 200 OK indicates the request was handled successfully with no errors, which definitely isn't the case. Please open a case with Genesys Cloud Care to report that the API is reporting success but not performing the operation it was given.

    system | 2022-07-14 19:54:48 UTC | #3

    This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.

    This post was migrated from the old Developer Forum.

    ref: 15104



Related Content