Remote office has high volume of dropped calls or dead air

Discussion in '3CX Phone System - General' started by orl1jps, May 24, 2010.

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

    Joined:
    May 24, 2010
    Messages:
    2
    Likes Received:
    0
    We are using 3cx Server in our Chicago location. We have about 40 users using Linksys SPA 2102 ATAs at this location. We rarely get dropped calls or dead air. We have a remote office setup in Texas with 12 extensions using Linksys SPA 2102 ATAs and 2 3cx soft phones. This remote location gets a large volume of dropped calls. All extensions get good calls also just there is roughly a 30% dropped call ratio.
    Our network setup is.

    Chicago
    Server resides here
    Line speed is 19MB down 9MB up
    Public IPs using NAT
    All Netgear QOS gigabyte switches

    Texas
    Line speed is 19MB down 4MB up
    1 100mb switch

    We have lots of calls that come in and so the log files are a little busy. Here is where I think this issue is in the log file. The calls come into queue 800 and the extension that had the dead air or dropped call was ext 710. If you notice you will see what appears to be the call going to ext 707 and 710 at the same second? All help greatly appreciated.



    Kindly Place all server logs in code and /code, this time it has been done for you - MFM
    Code:
    15:39:35.171|.\Target.cpp(430)|Log2||Target::makeOneInvite:[CM503025]: Call(10460): Calling Queue800:710Ext.710@[Dev:sip:710@98.200.121.175:5076]<br>
    15:39:35.296|.\CallLeg.cpp(268)|Log2||CallLeg::onFailure:[CM503003]: Call(10460): Call to sip:707@173.15.29.187 has failed; Cause: 487 Request Terminated; from IP:98.200.121.175:5092<br>
    15:39:35.311|.\CallLeg.cpp(268)|Log2||CallLeg::onFailure:[CM503003]: Call(10460): Call to sip:710@173.15.29.187 has failed; Cause: 486 Busy Here; from IP:98.200.121.175:5076<br>
    15:39:35.311|.\SLServer.cpp(794)|Log5|MediaServer|MediaServerReporting::SetRemoteParty:[MS210002] C:10460.6:Offer provided. Connection(transcoding mode): 173.15.29.187:9128(9129)<br>
    15:39:35.311|.\Target.cpp(430)|Log2||Target::makeOneInvite:[CM503025]: Call(10460): Calling VoIPline:@(Ln.10021@100 YMC Main 6303261610)@[Dev:sip:322002508@sbc.voipdnsservers.com:5060]<br>
    15:39:35.358|.\SLServer.cpp(762)|Error1|MediaServer|MediaServerReporting::RTPReceiver:[MS105000] C:10408.2: No RTP packets were received:remoteAddr=127.0.0.1:40830,extAddr=0.0.0.0:0,localAddr=127.0.0.1:7328<br>
    15:39:35.624|.\CallLeg.cpp(123)|Log5||CallLeg::onNewCall:[CM500002]: Info on incoming INVITE:
    INVITE sip:Q437@127.0.0.1:5060 SIP/2.0
    Via: SIP/2.0/UDP 127.0.0.1:40600;branch=z9hG4bK-d8754z-c640b6178974da2d-1---d8754z-;rport=40600
    Max-Forwards: 70
    Contact: <sip:437@127.0.0.1:40600;rinstance=036cee649ddbc7ae>
    To: <sip:Q437@127.0.0.1:5060>
    From: <sip:18017289936@127.0.0.1:5060>;tag=1e18c749
    Call-ID: MGY0ZmMzMmI0YTY0MjViMTg2ODMwYmJiYTU3NWJjZjA.
    CSeq: 2 INVITE
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO
    Proxy-Authorization: Digest username="437",realm="3CXPhoneSystem",nonce="414d535c020b750749:7aa6efc8212506b727e74071d0331b64",uri="sip:Q437@127.0.0.1:5060",response="565327e053514258773c626a8d68bf43",algorithm=MD5
    Supported: replaces
    User-Agent: 3CX Queue
    Content-Length: 0
    
    Jamie Smith
     
  2. mfm

    mfm Active Member

    Joined:
    Mar 4, 2010
    Messages:
    641
    Likes Received:
    2
    Hi,

    The log files show a normal call flow. To diagnose such an issue you need to purchase support contract. If you already have a support contract then please open a ticket with the full support logs and a wireshark capture.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Thread Status:
Not open for further replies.