[asterisk-dev] meetme and zap pseudo

Clod Patry cpatry at gmail.com
Wed Feb 28 08:09:52 MST 2007


hi guys,
Im running a lot of conferences in one machine and start to think, why
meetme is always looking for zap/pseudo.
Since, im running thru ztdummy and i didnt load chan_zap.so, im always
getting such warnings:

    -- AGI Script Executing Application: (MeetMe) Options: (2005|MpT)
  == Parsing '/etc/asterisk/meetme.conf': Found
[Feb 28 09:48:32] WARNING[15870]: channel.c:3020 ast_request: No channel
type registered for 'zap'
[Feb 28 09:48:32] WARNING[15870]: app_meetme.c:727 build_conf: Unable to
open pseudo channel - trying device
[Feb 28 09:48:32] WARNING[15870]: channel.c:3020 ast_request: No channel
type registered for 'zap'
    -- Created MeetMe conference 1021 for conference '2005'
    -- <SIP/64.15.69.138-082ef280> Playing 'conf-onlyperson' (language 'fr')

But, the conference works perfectly (as far that I know).


What are the zap uses for exactly?
I saw the ast_conference has these 2 members:
        struct ast_channel *chan;               /*!< Announcements channel
*/
        struct ast_channel *lchan;              /*!< Listen/Record channel
*/

Even if im not using zap/pseudo, i still can get MOH (option M).

In scenario like that example, do we agree zap/pseudo is totally useless?

Based on that code:
cnf->chan = ast_request("zap", AST_FORMAT_SLINEAR, "pseudo", NULL);
[... few condition here ...]
cnf->lchan = ast_request("zap", AST_FORMAT_SLINEAR, "pseudo", NULL);

it just duplicate the warning in the CLI.

So both the chan and lchan are requesting a pseudo, but why exactly?
After that explanation, maybe we could write something with flags, and do
these ast_request() only when really needed?

Also, even if these ast_request() got no chan (like my scenario), it just
continue, so what's the point exactly?

There's also the variable using_pseudo which could help to control if we're
using the pseudo channel.

ls -l /dev/zap/
total 0
crw-rw---- 1 root     dialout  196, 254 2007-02-20 19:38 channel
crw-rw---- 1 root     dialout  196,   0 2007-02-20 19:38 ctl
crw-rw---- 1 root     dialout  196, 255 2007-02-20 19:38 pseudo
crw-rw---- 1 root     dialout  196, 253 2007-02-20 19:38 timer
crw-rw---- 1 asterisk asterisk 196, 250 2007-02-20 19:38 transcode

(im running 1.4.0 on that box)

Thanks, for letting me understand that zap stuff in meetme.


-- 
Clod Patry
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-dev/attachments/20070228/efce9a36/attachment-0001.htm


More information about the asterisk-dev mailing list