- 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)
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 |