unable to write frame to channel: sucess

[enjay]

Hey All,

I know this topic has been beaten half to death though I've isolate the problem down to a response I receive back from a Cisco gateway. Any time I get a BUSY number I get a response back from the cisco and I begin getting flooded with the "unable to write frame to channe: success" warnings until I "soft hangup Local/whateverline". Any ideas on that?

Here is a snippet

Code: Select all

 == Manager 'sendcron' logged on from 127.0.0.1
    -- Executing MeetMe("Local/8600054@default-2f50,2", "8600054") in new stack
       > Channel Local/8600054@default-2f50,1 was answered.
    -- Executing AGI("Local/8600054@default-2f50,1", "agi://127.0.0.1:4577/call_log") in new stack
    -- AGI Script agi://127.0.0.1:4577/call_log completed, returning 0
    -- Executing Dial("Local/8600054@default-2f50,1", "SIP/cisco/12464284760||o") in new stack
    -- Called cisco/12464284760
    -- Got SIP response 486 "Busy here" back from 172.18.0.2
    -- SIP/cisco-094f2bf8 is busy
  == Everyone is busy/congested at this time (1:1/0/0)
    -- Executing Hangup("Local/8600054@default-2f50,1", "") in new stack
  == Spawn extension (default, 12464284760, 3) exited non-zero on 'Local/8600054@default-2f50,1'
    -- Executing DeadAGI("Local/8600054@default-2f50,1", "agi://127.0.0.1:4577/call_log") in new stack
    -- AGI Script agi://127.0.0.1:4577/call_log completed, returning 0
    -- Executing DeadAGI("Local/8600054@default-2f50,1", "agi://127.0.0.1:4577/VD_hangup--HVcauses--PRI-----NODEBUG-----17-----BUSY----------") in new stack
    -- AGI Script agi://127.0.0.1:4577/VD_hangup--HVcauses--PRI-----NODEBUG-----17-----BUSY---------- completed, returning 0
Nov 29 18:49:46 WARNING[11062]: app_meetme.c:1546 conf_run: Unable to write frame to channel: Success
Nov 29 18:49:46 WARNING[11062]: app_meetme.c:1546 conf_run: Unable to write frame to channel: Success
Nov 29 18:49:46 WARNING[11062]: app_meetme.c:1546 conf_run: Unable to write frame to channel: Success
Nov 29 18:49:46 WARNING[11062]: app_meetme.c:1546 conf_run: Unable to write frame to channel: Success
Nov 29 18:49:46 WARNING[11062]: app_meetme.c:1546 conf_run: Unable to write frame to channel: Success
Nov 29 18:49:46 WARNING[11062]: app_meetme.c:1546 conf_run: Unable to write frame to channel: Success
Nov 29 18:49:46 WARNING[11062]: app_meetme.c:1546 conf_run: Unable to write frame to channel: Success
Nov 29 18:49:47 WARNING[11062]: app_meetme.c:1546 conf_run: Unable to write frame to channel: Success
Nov 29 18:49:47 WARNING[11062]: app_meetme.c:1546 conf_run: Unable to write frame to channel: Success
Nov 29 18:49:47 WARNING[11062]: app_meetme.c:1546 conf_run: Unable to write frame to channel: Success
Nov 29 18:49:47 WARNING[11062]: app_meetme.c:1546 conf_run: Unable to write frame to channel: Success
Nov 29 18:49:47 WARNING[11062]: app_meetme.c:1546 conf_run: Unable to write frame to channel: Success
Nov 29 18:49:47 WARNING[11062]: app_meetme.c:1546 conf_run: Unable to write frame to channel: Success
Nov 29 18:49:47 WARNING[11062]: app_meetme.c:1546 conf_run: Unable to write frame to channel: Success



[mflorell]

Asterisk version?

Is this with manual dial, auto-dial or both?

[enjay]

Sorry I know the drill


Asterisk 1.2.13
VICI - Latest SVN
Manual Dial Mode (have not tested auto-dial yet).

[mflorell]

This shouldn't happen with auto-dial mode since the calls are not sent to the meetme room if they are busy in auto-dial mode. As for the warnings, that's probably something that you should post as a bug on the digium bug tracker.

[enjay]

Just a follow up on this I noticed that its not when I get ANY busy its when I get specific BUSY back..

All busy's that show the Local/Phonenumber work fine (i.e)

Code: Select all

  == Spawn extension (default, 12464328071, 3) exited non-zero on 'Local/12464328071@default-350a,2'
    -- Executing DeadAGI("Local/12464328071@default-350a,2", "agi://127.0.0.1:4577/call_log") in new stack
    -- AGI Script agi://127.0.0.1:4577/call_log completed, returning 0
    -- Executing DeadAGI("Local/12464328071@default-350a,2", "agi://127.0.0.1:4577/VD_hangup--HVcauses--PRI-----NODEBUG-----17-----BUSY----------") in new stack
    -- AGI Script agi://127.0.0.1:4577/VD_hangup--HVcauses--PRI-----NODEBUG-----17-----BUSY---------- completed, returning 0



  == Spawn extension (default, 12464227476, 3) exited non-zero on 'Local/12464227476@default-50ad,2'
    -- Executing DeadAGI("Local/12464227476@default-50ad,2", "agi://127.0.0.1:4577/call_log") in new stack
    -- AGI Script agi://127.0.0.1:4577/call_log completed, returning 0
    -- Executing DeadAGI("Local/12464227476@default-50ad,2", "agi://127.0.0.1:4577/VD_hangup--HVcauses--PRI-----NODEBUG-----17-----BUSY----------") in new stack
    -- AGI Script agi://127.0.0.1:4577/VD_hangup--HVcauses--PRI-----NODEBUG-----17-----BUSY---------- completed, returning 0


Its when I receive a BUSY back with the conference ID in it that I get the errors, why would I get a busy back in this form?

Code: Select all

  == Spawn extension (default, 12464379299, 3) exited non-zero on 'Local/8600051@default-3f9f,1'
    -- Executing DeadAGI("Local/8600051@default-3f9f,1", "agi://127.0.0.1:4577/call_log") in new stack
    -- AGI Script agi://127.0.0.1:4577/call_log completed, returning 0
    -- Executing DeadAGI("Local/8600051@default-3f9f,1", "agi://127.0.0.1:4577/VD_hangup--HVcauses--PRI-----NODEBUG-----17-----BUSY----------") in new stack
    -- AGI Script agi://127.0.0.1:4577/VD_hangup--HVcauses--PRI-----NODEBUG-----17-----BUSY---------- completed, returning 0
Dec  7 18:35:20 WARNING[23819]: app_meetme.c:1541 conf_run: Unable to write frame to channel: Success
Dec  7 18:35:20 WARNING[23819]: app_meetme.c:1541 conf_run: Unable to write frame to channel: Success
Dec  7 18:35:20 WARNING[23819]: app_meetme.c:1541 conf_run: Unable to write frame to channel: Success
Dec  7 18:35:20 WARNING[23819]: app_meetme.c:1541 conf_run: Unable to write frame to channel: Success
Dec  7 18:35:20 WARNING[23819]: app_meetme.c:1541 conf_run: Unable to write frame to channel: Success
Dec  7 18:35:20 WARNING[23819]: app_meetme.c:1541 conf_run: Unable to write frame to channel: Success


[mflorell]

This is in auto-dial mode?

I don;t know how a BUSY would be put through in Auto-dial mode unless for some reason an Answer signal is sent first, although I have never seen this I suppose it is possible.

[enjay]

Yup in Auto Dial mode...

[mflorell]

Can you see in the Asterisk CLI if an Aswer signal was sent on that line before the BUSY was sent?

What kind of trunks does this happen on?