dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
1
share rss forum feed

DBOD

join:2012-10-17
reply to VexorgTR

Re: [CallCentric] Recommended settings for 3CX can be problemati

I just saw this in the 3CX server activity log. It doesn't bode well. Not sure of the source of the issue yet. Will let it run for another hour.

14-Nov-2012 09:27:49.540 Call to T:Line:10001>>18003454344@[Dev:sip:1777XXXXXXX@bypass0.callcentric.com] from L:369.1[Extn:602] failed, cause: Cause: 500 Network Failure/INVITE from 204.11.192.135:10123
14-Nov-2012 09:27:49.540 [CM503003]: Call(C:369): Call to has failed; Cause: 500 Network Failure/INVITE from 204.11.192.135:10123

Iscream
Premium
join:2009-02-17
New York, NY
kudos:6
Reviews:
·Verizon FiOS
I don't think those lines [you mentioned above] are relevant somehow to the setup in question - this is just a "regular" 500 Network Failure, could happen due to many different reasons (this event isn't good by itself, but happens - could be network connectivity issue or even something on our side which prevented the call from progressing properly).

For me it was important to see whether or not 3CX will register to different SBCs or keep sticking to the same one. Seems like the latter. Just tried to find "something" for 3CX that could cause it to move onto another SBC when it's time to re-register.

Well, seems like no luck (one of my hopes was that when only a few records returned - it may behave itself) until 3CX will actually fix their SRV related behavior.