Jump to content

Adding IP into account - API seems broken


Gagan

Recommended Posts

Hello

Have been trying to add single//multiple ips in account   but post/put all  give error

 

"data": {
        "ips%2E0": {
            "not_found": {
                "message""ip not found",
                "value""85.215.197.153"
            }

 

Can others shed more light..

 

Thanks

 

 

 

Link to comment
Share on other sites

Hello,

i just sent part of response..

Complete response

{
    "data": {
        "ips%2E0": {
            "not_found": {
                "message""ip not found",
                "value""85.215.197.153"
            }
        }
    },
    "error""400",
    "message""validation error",
    "status""error",
    "timestamp""2023-10-30T17:39:00Z",
    "version""4.3.140",
    "node""k0ktGBIJ38vMxQeOH7Q1cQ",
    "request_id""45e2bffb1b17d996adceb1500d95aa4a",
 
Edited by Gagan (see edit history)
Link to comment
Share on other sites

  • 2600Hz Employees

Indeed, you have the "request_id" value now! Grep your logs to see what the server did and perhaps it will suggest what went wrong.

Also, as an aside, it is generally advisable to strip things like the "auth_token" value. All to easy to accidentally leak access to a cluster that way.

Link to comment
Share on other sites

Hello,

Just need to be more clear .. will this IP API work for solution i am looking to achieve.

 

a user account on kazoo , if adds his Asterisk IP in account.

Now , he wishes to place Outbound calls from his asterisk via his kazoo account, so he sets up a trunk for our kazoo ip and calls are auto routed based on call routing by kazoo and his account billed ( as he has authenticated his ip in account).

 

Thanks

 

 

 

Link to comment
Share on other sites

  • 2600Hz Employees

If you want to have an existing PBX route through KAZOO, create it either using the "connectivity" API or as a "device". "Connectivity" configs use a backend service call trunkstore, most suitable for pure SIP trunking. If you want callflow features available before routing to/from your PBX, creating it as a "device" makes sense.

The "ips" API is probably not what you want, in this case.

Link to comment
Share on other sites

×
×
  • Create New...