xen

Discussion in 'General' started by j2l, Jun 27, 2007.

  1. j2l

    j2l

    Joined:
    Jun 26, 2007
    Messages:
    8
    Likes Received:
    0
    Did you worked out zaptel timer on Xen?

    This is mandatory to have meetme and other FreePBX functions working properly.

    That's the main problem on any Asterisk virtual appliance.

    It is feasible according to some people, but AFAIK, there's no public information about it.
     
  2. lek

    lek Guest

    Hmmm... I'm not pretty sure but We have released a new zaptel-xen package compiled against the xen kernel in the 0.8.4-beta2 version.

    Could you give us more info about this topic?
     
  3. j2l

    j2l

    Joined:
    Jun 26, 2007
    Messages:
    8
    Likes Received:
    0
    I posted a reply to this post but I can<t see it.

    BTW, I confirm it doesn<t work in xen:
    [Jul 11 14:32:55] VERBOSE[2746] logger.c: -- Executing [990@from-internal:6] Goto("SIP/100-092b1f58", "STARTMEETME|1") in new stack
    [Jul 11 14:32:55] VERBOSE[2746] logger.c: -- Goto (from-internal,STARTMEETME,1)
    [Jul 11 14:32:55] VERBOSE[2746] logger.c: -- Executing [STARTMEETME@from-internal:1] MeetMe("SIP/100-092b1f58", "990||") in new stack
    [Jul 11 14:32:56] VERBOSE[2746] logger.c: == Parsing '/etc/asterisk/meetme.conf': [Jul 11 14:32:56] VERBOSE[2746] logger.c: Found
    [Jul 11 14:32:56] VERBOSE[2746] logger.c: == Parsing '/etc/asterisk/meetme_additional.conf': [Jul 11 14:32:56] VERBOSE[2746] logger.c: Found
    [Jul 11 14:32:56] WARNING[2746] chan_zap.c: Unable to open '/dev/zap/pseudo': No such file or directory
    [Jul 11 14:32:56] ERROR[2746] chan_zap.c: Unable to dup channel: No such file or directory
    [Jul 11 14:32:56] WARNING[2746] app_meetme.c: Unable to open pseudo channel - trying device
    [Jul 11 14:32:56] WARNING[2746] app_meetme.c: Unable to open pseudo device
    [Jul 11 14:32:56] VERBOSE[2746] logger.c: -- Playing 'conf-invalid' (language 'en')
     
  4. j2l

    j2l

    Joined:
    Jun 26, 2007
    Messages:
    8
    Likes Received:
    0
    I though I subscribed to this post, sorry that I didn't replied before.

    some asterisk features relies on 1000ms timing coming from zaptel PCI card or ztdummy.
    xen cannot share a physical card among virtual appliances (especially for timing!).
    ztdummy didn't seem to work out-of-the-box in virtual appliances and needed FIX.

    A long time ago, some guys tweaked it enough on Linux V-server to make it work at http://www.telephreak.org/papers/vpa/

    callweaver.org (asterisk fork) kicked out zaptel timing, I didn't try it as a virtual appliance.

    I'm not tech enough to tell what, where, how to change zaptel.

    keep me informed, a PM to check if subscribing works for me.
     
  5. j2l

    j2l

    Joined:
    Jun 26, 2007
    Messages:
    8
    Likes Received:
    0
  6. j2l

    j2l

    Joined:
    Jun 26, 2007
    Messages:
    8
    Likes Received:
    0

Share This Page