I have setup an ARI application the same way the “getting started” documentation states. I’m using the swagger UI to do my testing.
Using swagger and ARI I can setup a bridge. I can create channels to either internal SIP extensions or through external SIP trunks to a real phone number. Then I can add the channels to the bridge (mixing type) and the channels are able to speak to each other.
The problem is that if I only use external SIP channels then when the second channel is added to the bridge, both lines are hung up. I’ve done this using my home phone and my cell phone.
If I have an internal SIP extension connected to the bridge then everything works. I’ve tried one extension and one or more external phone numbers and it works fine.
To be a bit more clear on what exactly I’m doing…
In the “create a new channel (originate)” UI on Swagger I use an endpoint of SIP/101 for what I call the “internal channel.” This exists in the “from-internal” context but I do not specify it here as it does not appear to be needed. I also set the app (name) and timeout and hit “Try it out!”. All works fine. Extension 101’s phone rings.
I then do the same for the external channels except the only difference is the endpoint syntax. In this case I use SIP/[phone number]@from-trunk. “from-trunk” is the context I have setup for my sip-trunk. I do this once (or twice to a second phone number) and the phone rings and I pick it up.
Then I use the id’s that were generated from the create channel function and use that to add to my bridge that I’ve already created. This all works fine and the 3 channels are able to talk to each other.
The problem arises if I do not include the SIP/101 channel. Just the SIP/[phone number]@from-trunk. If I only use this type of endpoint then when I add them both to the bridge, the lines disconnect.
Any ideas? Very much appreciate any insight here.