Zap Channel DID problem solved (hack)

Discussion in 'General' started by vtofa, Oct 31, 2008.

  1. vtofa

    Oct 21, 2008
    Likes Received:
    This is a hack, and there is probably a better way to go about this, but I got my Zap DIDs this working by doing this:

    If you need Zap Channel DIDs to work in Elastix 1.3, do this:

    Add the necessary Zap Channel DIDs in unembedded FreePBX

    Edit /usr/sbin/genzaptelconf and change line 46 to context_lines=from-zaptel

    Go to the Elastix web interface, System, Hardware Detection, checkmark "Replace file zapata.conf", click "Detect New hardware"

    Once detection finishes, edit /etc/asterisk/zapata.conf and change context=from-pstn to context=from-zaptel

    Restart asterisk, and DIDs should work.

    Hopefully this helps.

  2. nachogomez

    Sep 11, 2008
    Likes Received:
    Well, I had to do something similar because the Zap DIDs wasn't working. I had to edit the zapata-channels.conf and set the callerid to something specific, so the Inbound Route is assigned using the caller id and not the DID.

    This is another hack and I think it should be easier to accomplish without editing files manually...

Share This Page