Solved Cannot make Outbound Calls

Status
Not open for further replies.

DCB

Bronze Partner
Basic Certified
Joined
Oct 5, 2021
Messages
42
Reaction score
2
Hello All,
Bandwidth.com recently retired one of their old servers. On our office network we could not make outbound calls until we switched IPs to the new Bandwidth.com server, under SIP trunks. I have a customer that is having the same issue, cannot dial out. I updated their trunks as well, but no change.
They are getting a 500 internal server error.
Here's the logs (IPs and phone #s replaced with Xs)

07/07/2022 11:36:06 AM - Exception: ParseException ../../rutil/ParseBuffer.hxx:230, Parse failed unexpected eof in context: 402xxxxxxx ^ @ ../../rutil/ParseBuffer.hxx:230
07/07/2022 11:36:06 AM - Call to T:Line:10001>>402xxxxxxx@[Dev:sip:[email protected]] from L:6421.1[Extn:210] failed, cause: Cause: 500 Internal Server Error/INVITE from 67.231xxxx:5060
07/07/2022 11:36:06 AM - [CM503003]: Call(C:6421): Call to <sip:[email protected]:0> has failed; Cause: 500 Internal Server Error/INVITE from 67.231xxxx:5060
 
Looks like bandwidth is rejecting your calls

500 Internal Server Error/INVITE from 67.231xxxx:5060

The 67.231.x.x the address is bandwidth Ip address correct? Suggest contacting bandwidth and asking them why this is.
 
  • Like
Reactions: Charles_3CX
That's what I thought, and I do have an open ticket with them. Just wanted to get a 2nd pair of eyes on the issue, in case there was something I forgot to check. Thanks CIsVIP
 
Just to update this thread, bandwidth.com had to make a change to their ACL list, allowing the 3CX IP. Outbound calls are working.
 
  • Like
Reactions: YiannisH_3CX
That's good news. Thanks for the update. Glad to hear your issue was resolved.
 
Status
Not open for further replies.

Latest Posts

Members Online Now

Forum statistics

Threads
111,831
Messages
589,276
Members
164,660
Latest member
RJenkinsROCK