app_meetme.c: Unable to write frame to channel Local/8600051

[amkoldn]

Hi All,

I've installed minimal version of CentOS Linux 5.9 then I installed
Goautodial From Scratch CentOS 64bit (CentOS 5.9)

Then Upgraded PHP 5.1 to PHP 5.3

I've created Carrier, Campaign, List then loaded list with Leads

CallCenter*CLI>sip show registry
Asterisk Call Manager/1.0
Response: Success
Message: Authentication accepted

Response: Follows
Privilege: Command
ActionID: 603181dcafaf8a8b99db20ed54b9ea28
Host Username Refresh State Reg.Time
sip myprovider com:5060 myuser 105 Registered Sat, 16 Mar 2013 19:20:24
--END COMMAND--

CallCenter*CLI>sip show peers
Asterisk Call Manager/1.0
Response: Success
Message: Authentication accepted

Response: Follows
Privilege: Command
ActionID: 4ef14e7069657ffc40fc39f4f44a432d
Name/username Host Dyn Nat ACL Port Status
8003/8003 (Unspecified) D N 0 UNKNOWN
8002/8002 (Unspecified) D N 0 UNKNOWN
8001/8001 80.80.47.201 D N 38788 OK (61 ms)
vtvoip/myuser 67.73.169.132 N 5060 OK (5 ms)
4 sip peers [Monitored: 2 online, 2 offline Unmonitored: 0 online, 0 offline]
--END COMMAND--


As soon as agent001 tries to make a call "Dial Next" I get:
[2013-03-16 20:04:29] WARNING[12844] app_meetme.c: Unable to write frame to channel Local/8600051@default-5b69,2
[2013-03-16 20:04:29] WARNING[12844] app_meetme.c: Unable to write frame to channel Local/8600051@default-5b69,2

And on the Agent side I get:

DIAL ALERT:
Call Rejected: CONGESTION
Cause: 0 - Unspecified. No other cause codes applicable.


I hope you can give me hint what is going wrong with my system.

Thanks in advance.
Amko

[williamconley]

1) Welcome to the Party!

2) You are going to an awful lot of effort to avoid installing Vicibox or Goautodial ... is there a reason not to use the .iso?

3) I believe Gardo expects a more "robust" CentOS instead of a barebones, although this may not be related to your problem.

4) It sounds like your meetme audio is failing. Either because meetme is broken or because the channel disappeared or never arrived. Check to see if your meetme rooms work by having two different agents dial 8600051 without logging in. See if they can talk to each other in that meetme room to validate meetme functionality.

5) Check your firewall (turn it off for testing) as I've had the firewalls cause issues similar to this from time to time.

6) Please describe In Detail how this error occurred. For instance: When the agent logged in, did they hear "you are the only person in this conference"?

7) Show CLI output from the actual happening. Something may have happened before the error you show which caused the error you show. We don't need 3000 lines of unrelated code, but perhaps more than One Line would be useful.

When you are debugging a problem like this, often SIP debugging is useful. It is arcane and tedious to read, but often contains the key to the flaw.

Happy Hunting

[amkoldn]

Hi William,

First of all thanks for your attempt to help me.
I've tried to follow your instructions and this is outcome of my debugging:
I've disabled firewall in this way:

# service iptables save
# service iptables stop
# chkconfig iptables off


Asterisk realtime logs:
[2013-03-17 19:40:36] WARNING[2664] app_followme.c: No follow me config file (followme.conf), so no follow me
[2013-03-17 19:59:18] VERBOSE[2664] logger.c: [2013-03-17 19:59:18] Asterisk Ready.
[2013-03-17 19:59:20] NOTICE[17671] chan_sip.c: Peer '8001' is now Reachable. (52ms / 2000ms) # X-Lite Client
[2013-03-17 19:59:20] NOTICE[17671] chan_sip.c: Peer 'vtvoip' is now Reachable. (4ms / 2000ms) # My Voip Provider

Step by step of what I did:

RE:Please describe In Detail how this error occurred. For instance: When the agent logged in, did they hear "you are the only person in this conference"?

Yes I hear "you are the only person in this conference"?

[2013-03-17 20:05:03] VERBOSE[22308] logger.c: [2013-03-17 20:05:03] == Manager 'sendcron' logged off from 127.0.0.1
[2013-03-17 20:05:06] VERBOSE[22264] logger.c: [2013-03-17 20:05:06] > Channel SIP/8001-00000000 was answered.
[2013-03-17 20:05:06] VERBOSE[22653] logger.c: [2013-03-17 20:05:06] -- Executing [8600052@default:1] MeetMe("SIP/8001-00000000", "8600052|F") in new stack
[2013-03-17 20:05:06] VERBOSE[22653] logger.c: [2013-03-17 20:05:06] == Parsing '/etc/asterisk/meetme.conf': [2013-03-17 20:05:06] VERBOSE[22653] logger.c: [2013-03-17 20:05:06] Found
[2013-03-17 20:05:06] VERBOSE[22653] logger.c: [2013-03-17 20:05:06] == Parsing '/etc/asterisk/meetme-vicidial.conf': [2013-03-17 20:05:06] VERBOSE[22653] logger.c: [2013-03-17 20:05:06] Found
[2013-03-17 20:05:06] VERBOSE[22653] logger.c: [2013-03-17 20:05:06] -- Created MeetMe conference 1023 for conference '8600052'
[2013-03-17 20:05:06] VERBOSE[22653] logger.c: [2013-03-17 20:05:06] -- Playing 'conf-onlyperson' (language 'en')
[2013-03-17 20:05:07] VERBOSE[22706] logger.c: [2013-03-17 20:05:07] == Parsing '/etc/asterisk/manager.conf': [2013-03-17 20:05:07] VERBOSE[22706] logger.c: [2013-03-17 20:05:07] Found
[2013-03-17 20:05:07] VERBOSE[22706] logger.c: [2013-03-17 20:05:07] == Manager 'sendcron' logged on from 127.0.0.1

As soon as "Dial Next" is clicked I get this error:


[2013-03-17 20:10:06] WARNING[25532] app_meetme.c: Unable to write frame to channel Local/8600052@default-8d77,2
[2013-03-17 20:10:06] WARNING[25532] app_meetme.c: Unable to write frame to channel Local/8600052@default-8d77,2

When I press on "Hang Up"

[2013-03-17 20:10:06] VERBOSE[26046] logger.c: [2013-03-17 20:10:06] == Parsing '/etc/asterisk/manager.conf': [2013-03-17 20:10:06] VERBOSE[26046] logger.c: [2013-03-17 20:10:06] Found
[2013-03-17 20:10:06] VERBOSE[26046] logger.c: [2013-03-17 20:10:06] == Manager 'sendcron' logged on from 127.0.0.1
[2013-03-17 20:10:06] VERBOSE[25532] logger.c: [2013-03-17 20:10:06] == Spawn extension (default, 8600052, 1) exited non-zero on 'Local/8600052@default-8d77,2'
[2013-03-17 20:10:06] VERBOSE[25532] logger.c: [2013-03-17 20:10:06] -- Executing [h@default:1] DeadAGI("Local/8600052@default-8d77,2", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----0---------------") in new stack
[2013-03-17 20:10:06] VERBOSE[25532] logger.c: [2013-03-17 20:10:06] -- AGI Script agi://127.0.0.1:4577/call_log--HVcauses ... ---------- completed, returning 0
[2013-03-17 20:10:06] VERBOSE[26048] logger.c: [2013-03-17 20:10:06] == Parsing '/etc/asterisk/manager.conf': [2013-03-17 20:10:06] VERBOSE[26048] logger.c: [2013-03-17 20:10:06] Found
[2013-03-17 20:10:06] VERBOSE[26048] logger.c: [2013-03-17 20:10:06] == Manager 'sendcron' logged on from 127.0.0.1


##########################################################################################################################

RE:Check to see if your meetme rooms work by having two different agents dial 8600051 without logging in.

Yes they both 8001/8002 can hear eachother well.

[2013-03-17 20:32:03] VERBOSE[10281] logger.c: [2013-03-17 20:32:03] == Manager 'sendcron' logged off from 127.0.0.1
[2013-03-17 20:32:05] VERBOSE[17671] logger.c: [2013-03-17 20:32:05] -- Registered SIP '8002' at 80.80.47.239 port 63116
[2013-03-17 20:32:05] VERBOSE[17671] logger.c: [2013-03-17 20:32:05] -- Saved useragent "X-Lite release 4.5 stamp 69607" for peer 8002
[2013-03-17 20:32:05] NOTICE[17671] chan_sip.c: Peer '8002' is now Reachable. (41ms / 2000ms)

[2013-03-17 20:32:07] VERBOSE[10671] logger.c: [2013-03-17 20:32:07] == Manager 'sendcron' logged off from 127.0.0.1
[2013-03-17 20:32:30] VERBOSE[10788] logger.c: [2013-03-17 20:32:30] -- Executing [8600051@default:1] MeetMe("SIP/8002-00000006", "8600051|F") in new stack
[2013-03-17 20:33:13] VERBOSE[10788] logger.c: [2013-03-17 20:33:13] == Spawn extension (default, 8600051, 1) exited non-zero on 'SIP/8002-00000006'
[2013-03-17 20:33:13] VERBOSE[10788] logger.c: [2013-03-17 20:33:13] -- Executing [h@default:1] DeadAGI("SIP/8002-00000006", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----0---------------") in new stack
[2013-03-17 20:33:13] VERBOSE[10788] logger.c: [2013-03-17 20:33:13] -- AGI Script agi://127.0.0.1:4577/call_log--HVcauses ... ---------- completed, returning 0

[2013-03-17 20:37:44] VERBOSE[32305] logger.c: [2013-03-17 20:37:44] == Spawn extension (default, 8600051, 1) exited non-zero on 'SIP/8001-00000005'
[2013-03-17 20:37:44] VERBOSE[32305] logger.c: [2013-03-17 20:37:44] -- Executing [h@default:1] DeadAGI("SIP/8001-00000005", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----0---------------") in new stack
[2013-03-17 20:37:44] VERBOSE[32305] logger.c: [2013-03-17 20:37:44] -- AGI Script agi://127.0.0.1:4577/call_log--HVcauses ... ---------- completed, returning 0
[2013-03-17 20:37:56] VERBOSE[14069] logger.c: [2013-03-17 20:37:56] -- Executing [8600051@default:1] MeetMe("SIP/8001-00000007", "8600051|F") in new stack
[2013-03-17 20:37:56] VERBOSE[14069] logger.c: [2013-03-17 20:37:56] == Parsing '/etc/asterisk/meetme.conf': [2013-03-17 20:37:56] VERBOSE[14069] logger.c: [2013-03-17 20:37:56] Found
[2013-03-17 20:37:56] VERBOSE[14069] logger.c: [2013-03-17 20:37:56] == Parsing '/etc/asterisk/meetme-vicidial.conf': [2013-03-17 20:37:56] VERBOSE[14069] logger.c: [2013-03-17 20:37:56] Found
[2013-03-17 20:37:56] VERBOSE[14069] logger.c: [2013-03-17 20:37:56] -- Created MeetMe conference 1023 for conference '8600051'
[2013-03-17 20:37:56] VERBOSE[14069] logger.c: [2013-03-17 20:37:56] -- Playing 'conf-onlyperson' (language 'en')
[2013-03-17 20:38:01] VERBOSE[14125] logger.c: [2013-03-17 20:38:01] == Parsing '/etc/asterisk/manager.conf': [2013-03-17 20:38:01] VERBOSE[14125] logger.c: [2013-03-17 20:38:01] Found

Thanks,
Amko

[williamconley]

[2013-03-17 20:05:06] VERBOSE[22653] logger.c: [2013-03-17 20:05:06] -- Playing 'conf-onlyperson' (language 'en')
[2013-03-17 20:05:07] VERBOSE[22706] logger.c: [2013-03-17 20:05:07] == Parsing '/etc/asterisk/manager.conf': [2013-03-17 20:05:07] VERBOSE[22706] logger.c: [2013-03-17 20:05:07] Found
[2013-03-17 20:05:07] VERBOSE[22706] logger.c: [2013-03-17 20:05:07] == Manager 'sendcron' logged on from 127.0.0.1

As soon as "Dial Next" is clicked I get this error:


[2013-03-17 20:10:06] WARNING[25532] app_meetme.c: Unable to write frame to channel Local/8600052@default-8d77,2

There is 5 minutes between these two items. Something happened in between that caused the channel to fail. Is the agent on this call on the same physical network as the server?

Have you tested this within a few seconds of login, and what were the results?

Have you considered installing from an .iso image? Vicibox.com and goautodial both have .isos that make installation simple. Then you can spend your time making $$ instead of learning Linux.

Also, I was interested in hearing whether the agents could hear each other when in the same meetme room ... could they?

[amkoldn]

5 min. because I've spend time in extracting logs and deletening unnecessary lines
Agents were able to hear eachother.
I would still like to understand/troubleshoot this error instead of trying to install new system.
Maybe my voip provider which is from Betamax family is not allowing me to make call?

[amkoldn]

I've installed Goautodial locally from .iso and I'm experiencing the same issue.

At this point I think my carrier is not configured well maybe.
Would you mind checking if is ok?

Code: Select all

Carrier ID:   dialnow

Registration String:   
register => username:password@sip.dialnow.com:5060/username

Account Entry:   
[dialnow]
disallow=all
allow=g729
allow=gsm
allow=ulaw
type=friend
username=username
secret=password
host=sip.dialnow.com
dtmfmode=rfc2833
context=trunkinbound
qualify=yes
insecure=very
fromuser=username

Dialplan Entry:
exten => _9387.,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _9387.,2,Dial(SIP/${EXTEN:1}@dialnow,,tTo)
exten => _9387,3,Hangup

I'm trying to call Bosnia country code +387

Thanks

[williamconley]

before you were experiencing an issue with a meetme room. now you are experiencing an issue with your carrier?

show cli output from a single call attempt. not 3000 lines of unrelated code, LOL, just the code from the moment of the attempt to the moment of failed/terminated call.

also worthy of note: if you have not installed g729, take it out of the "allow" section of your account entry. for troubleshooting you should only be using ulaw anyway

[amkoldn]

Hi William and thank you

I was just guessing that Carrier was an issue and your comment:
re: also worthy of note: if you have not installed g729, take it out of the "allow" section of your account entry. for troubleshooting you should only be using ulaw anyway

Solved the problem I've done as you suggested and problem is now solved thanks for your patience and help.

[williamconley]

Good job posting details

Now go make some $$