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.

only able to receive one inbound call at a time

Discussion in '3CX Phone System - General' started by maso, May 29, 2008.

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

    Joined:
    May 29, 2008
    Messages:
    6
    Likes Received:
    0
    Hi,

    I have a setup as follows:

    sip.internode.on.net --> 3cx on a server --> snom handsets

    My voip account has 4 channels and i can make 4 outbound calls concurrently. I can receive 1 call, but any subsequent inbound calls are received by my providers voice mail system. I have spoken to my voip provider and they claim the system is set up correctly at their end.

    I have the Voip line registered in 3cx as a generic line, stun is on and seems to be working.

    I would post from the logs but there is nothing to see after the first connection.
     
  2. ktikoft

    Joined:
    Jun 22, 2007
    Messages:
    59
    Likes Received:
    0
    Hi this is probably the general settinsg ports to use for external calls Under General.

    Also check these ports are open on your firewall.

    I would suspect you will find there is some port blocking going on.

    BTW
    I am using The Engin Business Service with no problems for 10 months
    15 Grandstream Phones,
    Old HP server early model 2.8 xeon running DC, Exchange, Rightfax, DNS and backup software

    I looked at nodefone but the price was not compentitve. I looked at MyNetFone as well but they did not support G711 and i wanted the highest quality calls.
     
  3. maso

    Joined:
    May 29, 2008
    Messages:
    6
    Likes Received:
    0
    I have the Sip Port under general settings on 5060 - should this be a single port or a range? The firewall test reports all is working.
     
  4. ktikoft

    Joined:
    Jun 22, 2007
    Messages:
    59
    Likes Received:
    0
    Two things "ports to use" for external calls and also 5060 is only the starting port. The next call will come in on 5061 etc etc.

    Also open up your firewall a bit to allow all traffic from internode to the server, you can lock it down later
     
  5. maso

    Joined:
    May 29, 2008
    Messages:
    6
    Likes Received:
    0
    ok, i have turned off the firewall and port forwarded all ports from sip.internode.on.net to the server. still no luck receiving more than one call at a time
     
  6. archie

    archie Well-Known Member
    3CX Support

    Joined:
    Aug 18, 2006
    Messages:
    1,299
    Likes Received:
    0
    Any logs?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  7. maso

    Joined:
    May 29, 2008
    Messages:
    6
    Likes Received:
    0
    Hi archie,

    Hmm, its' out of office hours here and i was able to connect two incoming calls. Must be something to do with my ring group...sorry to waste both of your time and thanks for the help.
     
  8. maso

    Joined:
    May 29, 2008
    Messages:
    6
    Likes Received:
    0
    Ugh! The message was changed on the voip providers message service I and mistook it for the 3cx voicemail. Did not get two lines in at all.

    archie, if you are still interested here are the logs:

    22:11:38.831 MediaServerReporting::SetRemoteParty [MS210003] C:4.2:Answer provided. Connection(transcoding mode):127.0.0.1:7008(7009)
    22:11:38.831 MediaServerReporting::SetRemoteParty [MS210000] C:4.2:Offer received. RTP connection: 127.0.0.1:42010(42011)
    22:11:38.831 CallLeg::setRemoteSdp Remote SDP is set for legC:4.2
    22:11:34.987 CallLeg::eek:nConfirmed Session 110 of leg C:4.1 is confirmed
    22:11:34.831 CallCtrl::eek:nLegConnected [CM503007]: Call(4): Device joined: sip:104@127.0.0.1:5070;rinstance=7864e06928271a63
    22:11:34.831 LineCfg::getInboundTarget [CM503011]: Inbound out-of-office hours' rule for LN:10000 forwards to DN:800
    22:11:34.815 CallCtrl::eek:nLegConnected [CM503007]: Call(4): Device joined: sip:0290432448@203.2.134.1:5060
    22:11:34.815 MediaServerReporting::SetRemoteParty [MS210003] C:4.1:Answer provided. Connection(transcoding mode):150.101.202.229:9006(9007)
    22:11:34.815 MediaServerReporting::SetRemoteParty [MS210001] C:4.2:Answer received. RTP connection: 127.0.0.1:42010(42011)
    22:11:34.799 CallLeg::setRemoteSdp Remote SDP is set for legC:4.2
    22:11:32.190 Extension::printEndpointInfo [CM505001]: Ext.104: Device info: Device Identified: [Man: 3CX Ltd.;Mod: 3CX VoIP Client;Rev: 1] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CX Phone v5.1] Transport: [sip:192.168.1.1:5060]
    22:11:32.190 CallCtrl::eek:nAnsweredCall [CM503002]: Call(4): Alerting sip:104@127.0.0.1:5070;rinstance=7864e06928271a63
    22:11:31.893 CallCtrl::eek:nSelectRouteReq [CM503004]: Call(4): Calling: HuntGrp:800@[Dev:sip:103@192.168.1.108:2051;line=wkya7tfs]
    22:11:31.893 CallCtrl::eek:nSelectRouteReq [CM503004]: Call(4): Calling: HuntGrp:800@[Dev:sip:102@192.168.1.103:2051;line=ofjz9ilm]
    22:11:31.893 CallCtrl::eek:nSelectRouteReq [CM503004]: Call(4): Calling: HuntGrp:800@[Dev:sip:101@192.168.1.109:2051;line=ux83x3v1]
    22:11:31.893 CallCtrl::eek:nSelectRouteReq [CM503004]: Call(4): Calling: HuntGrp:800@[Dev:sip:100@192.168.1.110:2051;line=zjgu9kmt]
    22:11:31.893 MediaServerReporting::SetRemoteParty [MS210002] C:4.2:Offer provided. Connection(transcoding mode): 127.0.0.1:7008(7009)
    22:11:31.877 CallCtrl::eek:nSelectRouteReq [CM503004]: Call(4): Calling: HuntGrp:800@[Dev:sip:104@127.0.0.1:5070;rinstance=7864e06928271a63]
    22:11:31.877 CallCtrl::eek:nSelectRouteReq [CM503010]: Making route(s) to [sip:800@FGI00.fgi.local:5060]
    22:11:31.877 MediaServerReporting::SetRemoteParty [MS210000] C:4.1:Offer received. RTP connection: 203.2.134.1:25650(25651)
    22:11:31.877 CallLeg::setRemoteSdp Remote SDP is set for legC:4.1
    22:11:31.877 Line::printEndpointInfo [CM505003]: Provider:[node] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] Transport: [sip:192.168.1.1:5060]
    22:11:31.877 LineCfg::getInboundTarget [CM503011]: Inbound out-of-office hours' rule for LN:10000 forwards to DN:800
    22:11:31.862 CallCtrl::eek:nIncomingCall [CM503001]: Call(4): Incoming call from anonymous@(Ln.10000@node) to [sip:800@FGI00.fgi.local:5060]
    22:11:31.581 LineCfg::getInboundTarget [CM503011]: Inbound out-of-office hours' rule for LN:10000 forwards to DN:800
    22:11:31.549 CallLeg::eek:nNewCall [CM500002]: Info on incoming INVITE:
    INVITE sip:0290432448@150.101.202.229:5060;rinstance=561fbb58dc7e2e5c SIP/2.0
    Via: SIP/2.0/UDP 203.2.134.1:5060;branch=z9hG4bK9ds2g300a0t1rdo3b241.1
    Max-Forwards: 9
    Contact: [sip:anonymous@203.2.134.1:5060;transport=udp]
    To: [sip:0290432448@sip.internode.on.net;user=phone]
    From: "Anonymous"[sip:anonymous@anonymous.invalid];tag=1172109904-1212063093920-
    Call-ID: BW214133920290508629475702@203.2.134.129
    CSeq: 441158225 INVITE
    Accept: multipart/mixed, application/sdp
    Allow: ACK, BYE, CANCEL, INFO, INVITE, OPTIONS, PRACK, REFER, UPDATE, NOTIFY
    Supported: 100rel
    Content-Length: 0
     
  9. archie

    archie Well-Known Member
    3CX Support

    Joined:
    Aug 18, 2006
    Messages:
    1,299
    Likes Received:
    0
    I see no problem, call has been established to 3CX VoIP client (supposedly) which is located on PBX server.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  10. maso

    Joined:
    May 29, 2008
    Messages:
    6
    Likes Received:
    0
    Signed with engin this morning and no problems. Internode are looking into it.
     
  11. ktikoft

    Joined:
    Jun 22, 2007
    Messages:
    59
    Likes Received:
    0
    Engin work out of the box one of the reasons we went with them the other is cost. For Autralia they are cheap but not the cheapest :)
     
Thread Status:
Not open for further replies.