conference error on vicidial demo

[emel_punk]

HI
Thanks for all the help you guys been giving to me.
last days i was making a simple demo with outbound routes and worked very well.
the first demo was on a single local machine.


now ive decide to do some integrations with another aplications and put a new VICIDIAL into vmware. and when i try to log an agent for some inbound campain, the vicidial do send the call to an agent. but something happens and this is the output in asterisk:

-- Executing [8600051@default:1] MeetMe("SIP/201-00000003", "8600051|F") in new stack
== Parsing '/etc/asterisk/meetme.conf': Found
== Parsing '/etc/asterisk/meetme-vicidial.conf': Found
[Dec 22 17:41:47] WARNING[4487]: app_meetme.c:829 build_conf: Unable to open pseudo device
-- <SIP/201-00000003> Playing 'conf-invalid' (language 'en')
== Spawn extension (default, 8600051, 1) exited non-zero on 'SIP/201-00000003'


i checked the meetme-vicidial.conf and vicidial.conf and they are ok. my conference rooms are there. i also dialed directly to de conference 8600051 and the same error. invalid conference.

SO any ideas whats happening?

[williamconley]

when you post, please post your entire configuration including (but not limited to) your installation method and vicidial version with build.

this IS a requirement for posting along with reading the stickies (at the top of each forum) and the manager's manual (available on EFLO.net, both free and paid versions)

You should also post: Asterisk version, telephony hardware (model number is helpful here), cluster information if you have one, and whether any other software is installed in the box. If your installation method is "from scratch" you must post your operating system and should also post the .iso version from which you installed your original operating system.

Similar to This:
Vicibox X.X from .iso | Vicidial X.X.X Build XXXX | Asterisk X.X.X | Single Server | No Digium/Sangoma Hardware | No Extra Software After Installation
________
is this VMware vicidial box clustered to your other box? if so: what installation method did you use for the clustering?

if it's not clustered, be sure the ip address has not been altered since installing the machine, and verify the ip address of the meetme room in the vicidial_conferences configuration screen and be sure your timing device (be it a dummy or a real one) is installed.

can you dial that conference from a phone registered on that box?

[emel_punk]

OK

1) vicibox redux v3.0.9 |vicibox server 3.0 | asterisk1.4.38 |single server |no digium\sangoma hardware
2) vmware is not clustered. just a simple vmplayer.
3) so ztdummy is not load, i guess is by the fact that dahdi is on it.
4) th ip hasnt been changed since instalatioin.
5) i checked the ip server of teh meetme rooms. and also checked the meetme*.conf files and the rooms are there ,.
6) when i dial directly the conference from a phone happens the same.


let me know if i left something.

[williamconley]

Did you use 64 bit or 32 bit? (which is why i recommend using the name of the .iso to identify your installation, it contains this information)

[emel_punk]

32 bits

[williamconley]

Hm. The latest Redux installation we have is 3.0.6 (in VMWare, that is). Worked nicely on VMWare server 2.0.2.

[emel_punk]

So you mean ... try to install 3.0.6 into my vmware?

[williamconley]

Well, we have VMware server 2.0.2 and redux 3.0.6 installed cleanly. Can't say it'll work for you, technically, but at least it's possible.

I suppose it's possible that there has been a change in the repository of a few packages since then, and one could be killing your install. In that case, 3.0.6 won't solve the problem.

[williamconley]

Code: Select all

lsmod|grep dahdi


[emel_punk]

all rigth ill download 3.0.6 and try .
thanks for all dude