Transition to Elastix, IAX trunk: * Elastix

Discussion in 'General' started by pilcheck, Aug 28, 2009.

  1. pilcheck

    Joined:
    Aug 24, 2009
    Messages:
    2
    Likes Received:
    0
    Hello Everyone!

    I am currently in the process of connecting two boxen via IAX2 from plain Asterisk to Elastix

    I've been digging through Elastix without Tears, this forum, and google, but keywords aren't my strong point as it turns out. This issue needs to be pounded into my head in a different fashion.

    Alright, I have a feeling I'll be a regular on this board so Let me get the situation explained firmly before the questions roll around.

    Over time I've learned asterisk mostly through the cli. I have maintained the company's network and phone systems now
    for well over over a year, and tackled a variety of modifications since.
    I feel comfortable in the command line, but I feel like I'd be wasting the bulk of Elastix's functionality.
    (okay, okay, I put a few test lines in iax_custom and it didn't work - you caught me)
    Our call center(~15 seats used) currently uses another open-source call center solution, but I wish to seek an alternative.
    Thats where I found Elastix. Now that I'm caught up on most of my projects, I want to revamp the call center.

    We have two servers, both Ubuntu.
    Asterisk 1.2.23 (the_Q@.20)
    and our Call Center - currently using another call center solution
    Asterisk 1.2.24 (Ferengi@.21)
    I'll be adding Elastix
    Elastix current/1.5.2ish? (Elastix@.19)

    All calls enter into the_Q(.20) via PRI.
    This server also handles calls to the Admin side of the office, A few IVR's, but most the numbers (25 of them)
    trunk via IAX to Ferengi(.20) and enter our call center. All phones are Polycoms.
    In the call center all calls enter appropriate queue (a meetme conf, rather) with MOH until an agent answers.
    Straight forward, to me at least.

    So i have a few test lines I'm looking to hook up from the_Q(.20) to Elastix(.19) via IAX.
    I believe I'm having difficulty dechiphering the web interface from the cli.

    On the_Q(.20) all IAX trunks are friend, and would like to keep it that way if possible
    [testtrunk]
    type=friend
    username=elastixiax
    secret=--------
    auth=plaintext
    host=10.0.10.19
    context=616REALNUM
    qualify=yes
    trunk=yes

    On Elastix(.19) I have a IAX2 trunk set up as follows:
    [all fields are blank unless noted here]
    Dial Rules:3xxx <= thats the next discussion.
    Trunk Name: testrunk
    PEER Details:
    host=10.0.10.20
    auth=plaintext
    username=elastixiax
    secret=--------
    type=friend
    qualify=yes
    trunk=yes
    context=616REALNUM

    I created an extension in extensions_custom of:
    [616REALNUM]
    exten => s,1,Dial(SIP/3002)

    But I don't even get an answer on the Elastix side.
    Here is the output from an attempted call on the_Q
    -- Accepting call from '616THECELL' to '616REALNUM' on channel 0/2, span 4
    -- Executing Gosub("Zap/74-1", "all-incoming|start|1") in new stack
    -- Executing Answer("Zap/74-1", "") in new stack
    -- Executing Return("Zap/74-1", "") in new stack
    -- Executing Set("Zap/74-1", "DNID=616REALNUM") in new stack
    -- Executing Goto("Zap/74-1", "iaxtoElastix|start|1") in new stack
    -- Goto (iaxtoElastix,start,1)
    -- Executing Answer("Zap/74-1", "") in new stack
    -- Hungup 'Zap/74-1'
    -- Channel 0/1, span 4 got hangup request, cause 16

    The phones do boot correctly (and THATS half the battle with Polycoms!)
    and are registered in the endpoint manager.

    I'm over thinking/missing something simple and I could use another viewpoint.

    -Pilcheck
     
  2. rafael

    Joined:
    May 14, 2007
    Messages:
    1,454
    Likes Received:
    1
    I think it might be a bug. Did you update the Elastix server with yum?
     

Share This Page