[Home]

Summary:ASTERISK-07179: [patch] pressing DTMF features while prompts are playing cause havoc on the console
Reporter:Vadim Berezniker (kryptolus)Labels:
Date Opened:2006-06-15 11:25:24Date Closed:2006-09-28 11:20:10
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Applications/app_meetme
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) asterisk.log
( 1) asterisk2.log
( 2) asterisk3.log
( 3) meetme.diff
Description:Join a conference with at least one other user. While joining, keep pressing * to enter the menu. At a certain point, you will get the following message repeated many times:

chan_sip.c:2555 sip_write: Asked to transmit frame type 64, while native formats is 4 (read/write = 64/4)

I haven't found the perfect timing, but you can reproduce this issue without constantly pressing star. It seems if you hit * at the end/right after the "you will now be placed in the conference" or "there are N users" in the conference you will hit this issue.
Comments:By: Serge Vecher (serge-v) 2006-06-15 11:28:21

1) Make sure your logger.conf has the following line:
  console => notice,warning,error,debug
2) restart Asterisk
3) at cli enter 'set debug 4'
4) reproduce the problem, capture all console output and post here as an attachment. thanks

By: Vadim Berezniker (kryptolus) 2006-06-15 11:56:42

I attached a log for the following scenario:
Enter menu, press star again and press star again at the end of the "Invalid choice" message. I can reproduce this almost every time.

By: Serge Vecher (serge-v) 2006-06-15 12:47:12

hmmm, need to dig a little deeper herem since we are using SIP clients. At cli, please enter 'set debug' after set debug 4. An add the sip trace to this bug. Thanks a lot.

By: Vadim Berezniker (kryptolus) 2006-06-15 13:21:36

Called the conference and pressed * at the end of the "you will now be placed in the conference" message and immediately got the errors.

By: Serge Vecher (serge-v) 2006-06-15 13:47:52

sorry, forgot to mention, verbose needs to be set to 4 as well.

By: Vadim Berezniker (kryptolus) 2006-06-16 08:06:20

I can reproduce it every time now.
Press * while the "There are N people in the conference" is playing.
Then press * again at the end of the "You will now be placed in the conference" messsage. Something might be happening to the channel when the first message is skipped.



By: Serge Vecher (serge-v) 2006-06-16 09:47:21

ugh ... mpg123 -- it's off-topic to this bug, but I would remove that thing from your system. It is not recommended for use on a production system. Convert all your mp3 to either gsm or a/alaw format -- your Asterisk will thank you.

Moving this to 'acknowledged' for a developer to look at (asterisk3.log)

By: Serge Vecher (serge-v) 2006-06-16 09:50:37

by the way, is there any "breakage" beside the console being flooded with messages, like distorted audio or what not?

By: Vadim Berezniker (kryptolus) 2006-06-16 09:54:59

Everything seems to be working fine even with the warnings.

By: Vadim Berezniker (kryptolus) 2006-06-23 13:06:14

ah... the meetme app is missing ast_stopstream calls all over the place

By: Vadim Berezniker (kryptolus) 2006-06-23 13:24:39

With those calls in place, the problem goes away.

By: Serge Vecher (serge-v) 2006-06-23 13:27:58

kryptolus: do you want to get a disclaimer on file and get those changes submitted as a patchfile?

By: Vadim Berezniker (kryptolus) 2006-06-23 13:30:14

Yeah, I'll try to do that once i'm off work.

By: Serge Vecher (serge-v) 2006-06-28 13:00:32

kryptolus: need your patch here, as well as confirmation of sending a disclaimer.

By: Vadim Berezniker (kryptolus) 2006-07-05 08:05:20

Sorry for the delay.
I submitted the disclaimer on Friday.

By: Serge Vecher (serge-v) 2006-07-05 12:25:17

ok, please upload the patch too. Here is the howto  http://www.asterisk.org/developers/Patch_Howto

By: Vadim Berezniker (kryptolus) 2006-07-05 12:27:38

Forgot to attach it.

By: Serge Vecher (serge-v) 2006-08-08 11:31:04

oops, missed this one. Ready for review.

By: Joshua C. Colp (jcolp) 2006-09-28 11:20:10

Fixed in 1.2 as of revision 43891, 1.4 as of revision 43893, and trunk as of revision 43894. Thanks!