Author Topic: 400 bad request from  (Read 2413 times)

Offline sunspark

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 986
  • Country: mx
  • Karma: +16/-1
    • View Profile
400 bad request from
« on: August 07, 2020, 02:59:56 PM »
i have two system in cluster with Mbg for sip trunk

When i shutdown the first system , i'm able to make internal call , but for outgoing calls i doesnt works.

Tcpdump :

From MBG to system 2 :

400 Bad request
reason : via header is unresolvable.

any idea ?



Offline sunspark

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 986
  • Country: mx
  • Karma: +16/-1
    • View Profile
Re: 400 bad request from
« Reply #1 on: August 07, 2020, 08:28:29 PM »
i found my error,

 in the sip peer profile of my second system, the address type was the FQDN and not the ip.

Offline markaldo

  • New Member
  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
Re: 400 bad request from
« Reply #2 on: March 01, 2022, 01:13:58 AM »
The 400 (Bad Request) status code indicates that the server cannot or will not process the request because the received syntax is invalid, nonsensical, or exceeds some limitation on what the server is willing to process. It means that the request itself has somehow incorrect or corrupted and the server couldn't understand it. The server is refusing to service the request because the entity of the request is in a format not supported by the requested resource for the requested method . Therefore, it prevents the website from being properly displayed. The main thing to understand is that the 400 Bad Request error is a client-side error.

The cause of a 400 error can be a wrongly written URL or a URL that contains unrecognizable characters. Another cause of the error might be an invalid or expired cookie. Also, if you try to upload a file that's too large. If the server is programmed with a file size limit, then you might encounter a 400 error.



 

Sitemap 1 2 3 4 5 6 7 8 9 10