Server Failure & Call Limit Reached

Discussion in '3CX Phone System - General' started by Bassackwards, Dec 14, 2010.

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

    Joined:
    Jul 21, 2010
    Messages:
    8
    Likes Received:
    0
    Hi All.

    I'm having a problem that I can't seem to figure out and don't see a solution on the forums. Here is my setup.

    3CX ( 3cx-win-PRO-16-w-upgrade ) @ IP 10.10.20.20
    SIP Trunk Provider is Speakeasy ( 10 total )
    Edgemark VOIP Gateway @ 10.10.20.1

    3CX registers to an EdgeMark VOIP Gateway - provided by Speakeasy. The Edgemark device registers with their servers. Everything works find for weeks on end and then the system will go on the fritz. I can only make 1 call ( in or out ). If a call is already in progress, I get a busy ( call limit reached ). Rebooting the 3CX system does not fix the problem. Having speakeasy reboot the Edgemark or power cycling the Edgemark fixes the problem. What am I not seeing here?

    The systemtrace log will show this:

    Code:
    08:19:24.472|.\Dialog.cxx(370)|Debug8|Resip|::ResipLogger:Dialog::dispatch: SipResp: 503 tid=672a5645421ae623 cseq=INVITE contact=4088341422@10.10.20.20:5060 / 1 from(wire)
    08:19:24.472|.\Dialog.cxx(640)|Debug8|Resip|::ResipLogger:Dialog::dispatch  --  Created new client invite sessionSipResp: 503 tid=672a5645421ae623 cseq=INVITE contact=4088341422@10.10.20.20:5060 / 1 from(wire)
    08:19:24.472|.\InviteSession.cxx(76)|Debug8|Resip|::ResipLogger:^^^ InviteSession::InviteSession 0361A518
    08:19:24.472|.\ClientInviteSession.cxx(735)|Trace5|Resip|::ResipLogger:Failure:  error response: SipResp: 503 tid=672a5645421ae623 cseq=INVITE contact=4088341422@10.10.20.20:5060 / 1 from(wire)
    08:19:24.472|.\InviteSession.cxx(2561)|Trace5|Resip|::ResipLogger:Transition UAC_Start -> InviteSession::Terminated
    08:19:24.472|.\InviteADS.cpp(122)|Trace5||InviteADS::onFailure:Failure from <sip:5104492999@10.10.20.1:5060> to "4088341422"<sip:4088341422@10.10.20.1:5060>;tag=ed1f4558
    08:19:24.472|.\CallLeg.cpp(299)|Trace5||CallLeg::onFailure:Session 104532 has failed in leg C:612.2 ; cause=503 Call limit exceeded; from IP:10.10.20.1:5060
    08:19:24.472|.\CallLeg.cpp(300)|Log2||CallLeg::onFailure:[CM503003]: Call(612): Call to sip:5104492999@10.10.20.1:5060 has failed; Cause: 503 Call limit exceeded; from IP:10.10.20.1:5060
    08:19:24.472|.\DevsMgr.cpp(464)|Debug2||DevsMgr::setDevBusyStatus:Device (537739866) is used in 1 calls: [606]
    08:19:24.472|.\Route.cpp(40)|Trace5||??:~Route=Dev:sip:9000014041@10.10.20.1:5060
    08:19:24.472|.\Target.cpp(30)|Trace5||??:~Target=VoIPline:5104492999@(Ln.10000@Speakeasy.net)
    08:19:24.472|.\CallEvents.cpp(536)|Trace5||StatusEventHolder::StatusEventHolder:StatusNotification:C=612,L=2,Status=OnHook,Skip=0
    08:19:24.472|.\CallEvents.cpp(568)|Debug2||StatusEventHolder::StatusEventHolder:Issue: [pres:10000;2;call;49439]
    08:19:24.472|.\CallEvents.cpp(174)|Trace5||FireStatusEvent:Ignored:612.2 (OnHook)
    08:19:24.472|.\SLAIface.cpp(639)|Debug2||??:SLA: 10000#0 'idle' -> 'idle'
    08:19:24.472|.\InviteADS.cpp(228)|Trace5||InviteADS::onTerminated:Terminated from <sip:5104492999@10.10.20.1:5060> to "4088341422"<sip:4088341422@10.10.20.1:5060>;tag=ed1f4558; reason: Error
    08:19:24.472|.\CallEvents.cpp(591)|Trace5||StatusEventHolder::StatusEventHolder:StatusNotification:C=612,L=2,Status=OnHook,Skip=0
    08:19:24.472|.\CallEvents.cpp(619)|Debug2||StatusEventHolder::StatusEventHolder:Issue: [pres:10000;2;call;49440]
    08:19:24.472|.\CallEvents.cpp(174)|Trace5||FireStatusEvent:Ignored:612.2 (OnHook)
    08:19:24.472|.\CallLeg.cpp(681)|Trace5||CallLeg::onTerminated:Session 104532 terminated; 503 Call limit exceeded; from IP:10.10.20.1:5060
    08:19:24.472|.\CallLeg.cpp(1811)|Trace5||CallLeg::terminateTargets:Reason: SIP ;cause=503 ;text="Call limit exceeded"
    08:19:24.472|.\Call.cpp(1134)|Trace5||Call::Terminated:Removing leg C:612.2
    08:19:24.472|.\Call.cpp(264)|Trace5||Call::remLeg:Removing leg C:612.2
    08:19:24.472|.\Call.cpp(284)|Trace5||Call::remLeg:Legs count: 1
    08:19:24.472|.\Call.cpp(1139)|Trace5||Call::Terminated:Legs count: 1
    08:19:24.472|.\InviteSession.cxx(82)|Debug8|Resip|::ResipLogger:^^^ InviteSession::~InviteSession 0361A518
    08:19:24.472|.\Dialog.cxx(244)|Debug8|Resip|::ResipLogger:Dialog::~Dialog() 
    08:19:24.472|.\DialogSet.cxx(123)|Debug8|Resip|::ResipLogger: ********** DialogSet::~DialogSet: YTQ3NmM2MjExMDkyZWM4ZmUzOWE3ZTMzZDVlZjdhNmE.-ed1f4558*************
    08:19:24.472|.\InviteADS.cpp(56)|Trace5||InviteADS::destroy:InviteADS::destroy:1348
    08:19:24.472|.\CallLeg.cpp(1776)|Trace5||CallLeg::~CallLeg:~CallLeg(612.2)
    08:19:24.472|.\SLAIface.cpp(639)|Debug2||??:SLA: 10000#0 'idle' -> 'idle'
    08:19:24.472|.\CallCtrl.cpp(556)|Trace5||CallCtrl::onRerouteReq:RerouteReq
    08:19:24.472|.\CallCtrl.cpp(569)|Trace5||CallCtrl::onRerouteReq:Forwarding call (prev. target = <sip:95104492999@10.10.20.20>), cause: Server Failure
    08:19:24.472|.\CallCtrl.cpp(579)|Debug2||CallCtrl::onRerouteReq:Current call diversion path:{}
    08:19:24.472|.\Call.cpp(974)|Log2||Call::RouteFailed:[CM503016]: Call(612): Attempt to reach <sip:95104492999@10.10.20.20> failed. Reason: Server Failure
    08:19:24.472|.\Call.cpp(535)|Log2||Call::DoEndCall:[CM503020]: Normal call termination. Reason: Server Failure
    08:19:24.472|.\CallEvents.cpp(536)|Trace5||StatusEventHolder::StatusEventHolder:StatusNotification:C=612,L=1,Status=OnHook,Skip=0
    08:19:24.472|.\CallEvents.cpp(568)|Debug2||StatusEventHolder::StatusEventHolder:Issue: [pres:1422;2;call;49441]
    08:19:24.472|.\CallEvents.cpp(185)|Trace5||FireStatusEvent:Reported(Delete):612.1 (OnHook)
    08:19:24.472|.\DnsUtil.cxx(145)|Trace5|Resip|::ResipLogger:local hostname does not contain a domain part FM-3CX
    08:19:24.504|.\ServerInviteSession.cxx(454)|Trace5|Resip|::ResipLogger:UAS_Offer: reject(500)
    08:19:24.504|.\Helper.cxx(375)|Debug8|Resip|::ResipLogger:Helper::makeResponse(SipReq:  INVITE 95104492999@10.10.20.20 tid=7299654b cseq=INVITE contact=1422@10.10.20.84:5060 / 102 from(wire) code=500 reason=
    08:19:24.504|.\Dialog.cxx(1067)|Debug8|Resip|::ResipLogger:Dialog::makeResponse: 
    
    SIP/2.0 500 Server Internal Error
    Via: SIP/2.0/UDP 10.10.20.84:5060;branch=z9hG4bK7299654b
    To: <sip:95104492999@10.10.20.20>;tag=3e7f2635
    From: "1422"<sip:1422@10.10.20.20>;tag=001646d29992082e2a9c8999-76c9c149
    Call-ID: 001646d2-9992009c-0ddb97ed-40557401@10.10.20.84
    CSeq: 102 INVITE
    Content-Length: 0
    
    
    08:19:24.504|.\InviteADS.cpp(272)|Trace5||InviteADS::onReadyToSend:SendMsg from <sip:95104492999@10.10.20.20>;tag=3e7f2635 to "1422"<sip:1422@10.10.20.20>;tag=001646d29992082e2a9c8999-76c9c149
    08:19:24.504|.\Extension.cpp(1154)|Debug2||Extension::notifyDI:Ext.1422: sip:1422@10.10.20.84:5060;transport=udp, Call(612)
    08:19:24.504|.\Extension.cpp(1171)|Debug2||Extension::notifyDI:Call(612): DlgID:612-1397, entry state: 0
    08:19:24.504|.\Extension.cpp(1328)|Debug2||Extension::notifyDI:Call(612): DlgID:612-1397, exit state: 3
    08:19:24.504|.\DialogUsageManager.cxx(866)|Debug8|Resip|::ResipLogger:SEND: 
    
    SIP/2.0 500 Server Internal Error
    Via: SIP/2.0/UDP 10.10.20.84:5060;branch=z9hG4bK7299654b
    To: <sip:95104492999@10.10.20.20>;tag=3e7f2635
    From: "1422"<sip:1422@10.10.20.20>;tag=001646d29992082e2a9c8999-76c9c149
    Call-ID: 001646d2-9992009c-0ddb97ed-40557401@10.10.20.84
    CSeq: 102 INVITE
    User-Agent: 3CXPhoneSystem 9.0.14795.0
    Warning: 499 FM-3CX "Server Failure"
    Content-Length: 0
    Any help would be appreciated. Thanks!

    Brian
     
  2. mfm

    mfm Active Member

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

    What version of 3CX are you using, and are you sure that you have not reached you call limit. It might be that your calls are sticking for some reason.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. Bassackwards

    Joined:
    Jul 21, 2010
    Messages:
    8
    Likes Received:
    0
    3cx is @ v9 SP4 ( will be updating to SP5 this weekend ). This particular issue has been happening since my original installation of v 9 ( base install without any updates/SP's ). I've had at least 8 concurrent calls going on many times before without issue. It seems 3CX is breaking down the calls just fine. I'm in a small 20 person office, I can usually tell when people are on the phone and look at the 3CX extension status - as far as I can tell, 3CX is reporting correctly. I guess if call breakdown is the issue, it must be with the Edgemark device. Is there a log file that shows the status of this?

    3CX shows only 1 call in progress and still tells me that I've reached my limit. The strange thing:
    " cause=503 Call limit exceeded; from IP:10.10.20.1:5060 "

    Is 3CX telling me that 10.10.20.1 ( the Edgemark VOIP gateway ) is reporting that IT has reached its limit? When having this problem, I open a ticket with Speakeasy ( my Data/SIP trunk provider ) and every time they tell me that everything looks normal. Unfortunately, I don't have any management rights to the Edgemark device so I can't login to the web admin to see whats going on. If 3CX was reporting that it was reaching it's limit, wouldn't it say
    " cause=503 Call limit exceeded; from IP:10.10.20.20:5060 " ( 10.10.20.20 being the IP of the 3CX server )
    OR
    " cause=503 Call limit exceeded; from IP:127.0.0.1:5060 "??
     
  4. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,869
    Likes Received:
    304
    The fact that re-booting the gateway clears the problem, AND that the 3CX log shows the gateway IP is what is reporting that a call limit has been reached, pretty much points to the gateway being the problem.

    If it was supplied by your provider then you should be talking to them about getting you a replacement. Yours seems to have a fault.
     
Thread Status:
Not open for further replies.