Dismiss Notice
We would like to remind you that we’re updating our login process for all 3CX forums whereby you will be able to login with the same credentials you use for the Partner or Customer Portal. Click here to read more.

Error 12289 - Inbound Calls

Discussion in '3CX Phone System - General' started by Overwatch, Jul 20, 2012.

Thread Status:
Not open for further replies.
  1. Overwatch

    Joined:
    Jan 24, 2012
    Messages:
    8
    Likes Received:
    0
    Hello 3CX'ers!

    I posted on the forums several months ago when I first began a trip into replacing our existing ancient Norstar PBX with 3CX. It has gone swimmingly with very little problems in which I am over the moon about and thankful to this community for. Little issues have cropped up here and there but I've been able to sort them out and the whole VoIP system is happy as larry.

    Though there is one problem that we've had for a while now that I just can't seem to nail down with it being intermittent and I can't seem to recreate the problem. After sitting watching the logs I've managed to catch the problem in action and have copied the logs into this post below.

    The problem I seem to be having is that some incoming calls are not passed on to a Ring Group and instead are just left ringing constantly.

    If anybody has an idea as to what the problem may be I'd greatly appreciate any input. From what I can understand it seems that the call is either not being passed on to the Ring Group or is being diverted down another PSTN Trunk?

    If any more information is required I'd be more than happy to acquire it!

    3CX Server IP: 192.168.0.9
    Grandstream GWX4104 PSTN Gateway IP: 192.168.0.14
    GWX-4104 Trunks: 10000, 10001, 10002 and 10003
    Extension Number for Ring Group to pass calls to: 800

    The Event Log states:
    7/20/2012 10:42:59AM WARNING 12289 Device 10002@(Ln.10002@GWX4104) Had no available trunk(s) for Call(604)

    The Activity Log states:
    10:43:15.748 Currently active calls - 1: [598]
    10:43:01.513 [CM503008]: Call(555): Call is terminated
    10:42:59.747 [MS210000] C:604.1:Offer received. RTP connection: 192.168.0.14:5008(5009)
    10:42:59.747 Remote SDP is set for legC:604.1
    10:42:59.747 [CM503020]: Normal call termination. Reason: Disabled by Inbound Rule
    10:42:59.747 [CM503019]: Call(604): Rejected! Line is 'Busy' because number of simultaneous calls per line 10002@(Ln.10002@GXW-4104) is limited by Administrator
    10:42:59.747 [CM503012]: Inbound office hours rule (unnamed) for 10002 forwards to DN:800
    10:42:59.747 Looking for inbound target: called=10000++; caller=10002
    10:42:59.747 [CM500002]: Info on incoming INVITE:
    INVITE sip:10000++@192.168.0.9 SIP/2.0
    Via: SIP/2.0/UDP 192.168.0.14:5064;branch=z9hG4bK95f6b0438f9484b6
    Max-Forwards: 70
    Contact: <sip:10002@192.168.0.14:5064;transport=udp>
    To: <sip:10000++@192.168.0.9>
    From: <sip:10002@192.168.0.9>;tag=b6548b7497c389d2
    Call-ID: 2c630ea264025a06d9b7a8237d111004@192.168.0.14
    CSeq: 19546 INVITE
    Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, OPTIONS, INFO, SUBSCRIBE, UPDATE, PRACK
    Proxy-Authorization: Digest username="10002",realm="3CXPhoneSystem",algorithm=MD5,uri="sip:10000++@192.168.0.9",nonce="414d535c0619b92319:9d4da50f2cc7fc3f4173a35130e22254",response="64f1818658901e1db8e337d9127a6305"
    Supported: replaces, timer, path
    User-Agent: Grandstream GXW4104 (HW 2.0, Ch:1) 1.3.4.10
    P-Asserted-Identity: "" <sip:unknown@192.168.0.9>
    Content-Length: 0


    Thank you,
    Mark
     
  2. lneblett

    lneblett Well-Known Member

    Joined:
    Sep 7, 2010
    Messages:
    2,086
    Likes Received:
    65
    In 3cx, how many simultaneous calls do you have the gxw set to handle in pstn device? Try setting the gxw to 4. you did not indicate which version of 3cx (11, 10, 9, etc.) you have. Many set the gxw to 1 thinking that this is the correct paramet based upon how 3cx presented the setup screen in versions prior to 11. I think they made the screen more relative in 11 and eliminated some of the confusion.
     
  3. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    11,119
    Likes Received:
    330
    Without seeing all of your trunk set-up...
    This line would seem to indicate that you have the gateway trunk group set for a certain number of simultaneous calls, and there is an attempt to exceed that so the call was rejected.


    It's telling you (the administrator), that it is because of a setting you have defined. If you are using all four trunks on your gateway, be sure that you have that parameter, in the trunk group, set to four (incoming/outgoing). That would be the first thing to look into.
     
  4. Overwatch

    Joined:
    Jan 24, 2012
    Messages:
    8
    Likes Received:
    0
    Sorry about the delay and thank you for such a prompt response guys!
    We're currently running version Version 10 with an 8-Simultaneous Call license.

    Within the Ports/Trunks menu I have 4 lines set up for the GWX-4104 ranging from 10000, 10001, 10002, and 10003 as mentioned.
    Each trunk has 1 simultaneous call, the problem I have doesn't relate to one specific trunk (10002 in the above example) as I get this randomly on any trunk.

    I think this may be the problem Ineblett, I read the simultaneous calls on a "Per trunk/line" basis. And with it being a PSTN line... It can only have one call per physical line.

    I'll make some alterations and get back to you! Though sadly it will not be until Monday - But again, thank you both for your help!
     
  5. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    11,119
    Likes Received:
    330
    A while back, someone was having a similar problem with a gateway and simultaneous calls. I may be mistaken, but it seemed that even set at the one call per one trunk, it required that be increased to two. It did not make a lot of sense, logically, but I believe it did eventually work for them. I'll try to do some digging and see if I can find that post.
     
  6. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    11,119
    Likes Received:
    330
    There is this post, but there might also be some others dealing with the Grandstream in particular, as well..
    http://www.3cx.com/forums/strange-issue-with-incoming-calls-11992.html
     
  7. gschwab

    gschwab New Member

    Joined:
    Mar 21, 2012
    Messages:
    131
    Likes Received:
    0
    I have a Grandstream GXW 4108 and I had to set up outbound rules to direct the outgoing calls to ports.
    Route 1: 10001 prepend 991
    Route 2: 10002 prepend 992 etc.
    set my simultaneous calls to 8 everywhere
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  8. lneblett

    lneblett Well-Known Member

    Joined:
    Sep 7, 2010
    Messages:
    2,086
    Likes Received:
    65
    Yes, setting it to 4 for the gxw and then 2 per line if running v10 will do the trick. If you get the chance to go to V11, you might consider that too as 3cx seems to have cleaned that screen up. The prepend of 991, 992, etc. To the dial string is not needed unless you specifically want to stipulate the trunk an outbound call is to use.

    I have one client with 2 companies using one instance of 3cx then I split the gxw4108 so that one company would only use certain ports so as to maintain their proper caller-id and the other company used the other ports using the same method for the same reason. I used separate extension ranges for each and then assigned them to groups whereupon the outbound rules were established accordingly.
     
  9. Overwatch

    Joined:
    Jan 24, 2012
    Messages:
    8
    Likes Received:
    0
    Good morning folks,

    Thank you very much for the helpful comments!
    Having checked through the logs and done a few test calls - So far, so good! It seems to have sorted it. I would have been scratching my head for a while longer if not for you all - I'll see how it goes throughout the rest of the day and report back later.

    You have my deepest gratitude!

    I think it may be an idea for me to upgrade to V11 soon!
     
Thread Status:
Not open for further replies.