Re: [asterisk-dev] Bridge not in Stasis application

Abhay Gupta Thu, 20 Feb 2020 04:42:43 -0800

In case of issue manager event of BridgeDestroy does not come and as seen it never enters the destroy_bridge() function .

[Feb 20 15:33:07] DEBUG[25464] http.c: HTTP Request URI is /ari/bridges/1029
[Feb 20 15:33:07] DEBUG[25464] http.c: match request [ari/bridges/1029] with handler [httpstatus] len 10
[Feb 20 15:33:07] DEBUG[25464] http.c: match request [ari/bridges/1029] with handler [phoneprov] len 9
[Feb 20 15:33:07] DEBUG[25464] http.c: match request [ari/bridges/1029] with handler [static] len 6
[Feb 20 15:33:07] DEBUG[25464] http.c: match request [ari/bridges/1029] with handler [ari] len 3
[Feb 20 15:33:07] DEBUG[25464] http.c: Match made with [ari]
[Feb 20 15:33:07] DEBUG[25464] res_ari.c: Finding handler for bridges/1029
[Feb 20 15:33:07] DEBUG[25464] res_ari.c: Finding handler for bridges
[Feb 20 15:33:07] DEBUG[25464] res_ari.c: Checking ari applications: Didn't match bridges
[Feb 20 15:33:07] DEBUG[25464] res_ari.c: Checking ari deviceStates: Didn't match bridges
[Feb 20 15:33:07] DEBUG[25464] res_ari.c: Checking ari asterisk: Didn't match bridges
[Feb 20 15:33:07] DEBUG[25464] res_ari.c: Checking ari recordings: Didn't match bridges
[Feb 20 15:33:07] DEBUG[25464] res_ari.c: Checking ari sounds: Didn't match bridges
[Feb 20 15:33:07] DEBUG[25464] res_ari.c: Checking ari endpoints: Didn't match bridges
[Feb 20 15:33:07] DEBUG[25464] res_ari.c: Checking ari events: Didn't match bridges
[Feb 20 15:33:07] DEBUG[25464] res_ari.c: Checking ari playbacks: Didn't match bridges
[Feb 20 15:33:07] DEBUG[25464] res_ari.c: Checking ari bridges: Explicit match with bridges
[Feb 20 15:33:07] DEBUG[25464] res_ari.c: Finding handler for 1029
[Feb 20 15:33:07] DEBUG[25464] res_ari.c: Checking bridges bridgeId: Matched wildcard.
[Feb 20 15:33:07] DEBUG[25464] res_ari.c: No explicit handler found for 1029. Using wildcard bridgeId.
[Feb 20 15:33:07] DEBUG[25464] bridge.c: Bridge 1029: telling all channels to leave the party
[Feb 20 15:33:07] DEBUG[25464] bridge.c: Bridge 1029: dissolving bridge with cause 16(Normal Clearing)
[Feb 20 15:33:07] DEBUG[25464] bridge.c: Bridge 1029: queueing action type:13 sub:1001

In case where it is successfully deleted

[Feb 20 15:34:30] DEBUG[29018] bridge.c: Bridge 1013: telling all channels to leave the party

[Feb 20 15:34:30] DEBUG[29018] bridge.c: Bridge 1013: dissolving bridge with cause 16(Normal Clearing)

[Feb 20 15:34:30] DEBUG[29018] bridge.c: Bridge 1013: queueing action type:13 sub:1001

[Feb 20 15:34:30] DEBUG[4070][C-000019bf] bridge.c: Bridge 1013: actually destroying stasis bridge, nobody wants it anymore

[Feb 20 15:34:30] DEBUG[29018] http.c: HTTP keeping session open. status_code:204

[Feb 20 15:34:30] DEBUG[4070][C-000019bf] bridge.c: Bridge 1013: calling stasis bridge destructor

[Feb 20 15:34:30] DEBUG[4070][C-000019bf] bridge.c: Bridge 1013: calling simple_bridge technology stop

[Feb 20 15:34:30] DEBUG[4070][C-000019bf] bridge.c: Bridge 1013: calling simple_bridge technology destructor

Regards,

Abhay Gupta

From: Joshua C. Colp
Sent: 19 February 2020 19:46
To: Asterisk Developers Mailing List
Subject: Re: [asterisk-dev] Bridge not in Stasis application

On Wed, Feb 19, 2020 at 10:08 AM Abhay Gupta <[email protected]> wrote:

Hi,

We are getting a problem where bridge get shows the bridge but on delete gives the message “Bridge not in Stasis application” and we cannot add any channels to the bridge .

But when we issue the POST command again to create the bridge then it is successfully created & we are able to successfully delete it . The logs are shown here :-

Step 1:- try to delete an extension

curl -X DELETE http://192.168.1.250:8088/ari/bridges/1014?api_key=asterisk:asterisk
{"message":"Bridge not in Stasis application"}

Step 2:- try to check the extension

curl -X GET http://192.168.1.250:8088/ari/bridges/1014?api_key=asterisk:asterisk
{"id":"1014","technology":"simple_bridge","bridge_type":"mixing","bridge_class":"stasis","creator":"Stasis","name":"","channels":[],"creationtime":"2020-02-18T09:30:59.528+0530","video_mode":"talker"}

Step 3:- try to add/create an extension

curl -X POST http://192.168.1.250:8088/ari/bridges/1014?api_key=asterisk:asterisk
{"id":"1014","technology":"simple_bridge","bridge_type":"mixing","bridge_class":"stasis","creator":"Stasis","name":"","channels":[],"creationtime":"2020-02-19T17:37:14.624+0530","video_mode":"talker"}

Step 4:- try to delete extension after POST extension

curl -X DELETE http://192.168.1.250:8088/ari/bridges/1014?api_key=asterisk:asterisk

Step 5:- try to check extension after delete extension

curl -X GET http://192.168.1.250:8088/ari/bridges/1014?api_key=asterisk:asterisk
{"message":"Bridge not found"}

I am not able to find the sequence of events that lead to this issue .

You'd need to examine the Asterisk log with debug on to see the specific execution flow and when things are occurring and why. That would narrow down the scenario and what is going on.

Joshua C. Colp

Asterisk Technical Lead

Sangoma Technologies

Check us out at www.sangoma.com and www.asterisk.org

-- 
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --


asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev

Re: [asterisk-dev] Bridge not in Stasis application

Reply via email to