Summary:	ASTERISK-01159: 'p' and 'd' flags mutually exclusive with x100p but not ztdummy
Reporter:	brook davis (mrgoby)	Labels:
Date Opened:	2004-03-04 19:27:44.000-0600	Date Closed:	2011-06-07 14:05:16
Priority:	Major	Regression?	No
Status:	Closed/Complete	Components:	Applications/app_meetme
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	With an x100p and wcfxo/zaptel driver loaded, the 'd' and 'p' flags appear to be mutually exclusive.  Moreover, the order of the flags appears to determine the resulting behaviour.  Placing the 'p' flag first will cause an invalid conference error, placing the 'd' first will create the room, but I cannot leave on pressing '#'.  I can leave the conference with a static room, however.  My meetme.conf file has a single room defined, with a blank line at the end of the file(though i've tried with/without the blank line).   I double checked, and this same scenario works as I would expect on a different, but similar, machine using the ztdummy driver, I can both create a dynamic conference and leave it. I have attatched the lsmod info, like i said, I'm not completely hip with zaptel drivers yet, The x100p works as I would expect, is detected by ztcfg correctly, and I've not had any problems with it, and though I'm not an expert, I believe it is installed correctly.  I am running all of this on a dell power-edge running redhat... the asterisk install is fairly current 0.7.2 , a CVS checkout about a month old now... please let me know if I can provide further information.   ****** ADDITIONAL INFORMATION ****** The only entry in /var/log/asterisk/messages that I see that might be relevant is: Mar  3 23:03:12 NOTICE[90124]: Don't know what to do with control frame -1 and Mar  3 23:03:00 WARNING[8192]: parse error: No category context for line 5 of musiconhold.conf lsmod Module                  Size  Used by    Not tainted wcfxo                   9280   1 zaptel                178784   4  [wcfxo] autofs                 13332   0  (autoclean) (unused) e1000                  60288   1 ipt_REJECT              4024   6  (autoclean) iptable_filter          2412   1  (autoclean) ip_tables              15096   2  [ipt_REJECT iptable_filter] mousedev                5588   0  (unused) keybdev                 2976   0  (unused) hid                    22340   0  (unused) input                   5920   0  [mousedev keybdev hid] usb-ohci               21608   0  (unused) usbcore                78944   1  [hid usb-ohci] ext3                   70912   5 jbd                    51988   5  [ext3] -- meetme.conf [rooms] conf => 1000 ;only static room (this is a blank line) -- Please let me know if you require additional information.  dodecaphonic@hotmail.com Thankyou For Asterisk !!
Comments:	By: brook davis (mrgoby) 2004-03-04 19:32:14.000-0600 SideNote: I realized I had a typo in my MeetMe.conf that was commenting out the conference context. I deleted the semi-colon that was causing the warning regarding the conference context, however, this did not resolve the problem. By: twisted (twisted) 2004-04-06 01:29:20 I attempted to reproduce with latest cvs-head, and was unable to reproduce the problem.  Make sure that if you are calling a dynamic confrence you are doing so as exten => x,1,MeetMe(xxxx|dp) not specifying a confrence number should be ok, if you're not mapping an extension to a confno.   Unable to reproduce, using latest zaptel and latest -head.  Re-Open bug if updating to latest zaptel and latest cvs has no effect.