Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SIP Trunk To Interface SBCE "408 Request Timeout"

Status
Not open for further replies.

Anymol2e

Systems Engineer
Jun 29, 2019
8
TH
I try to Test SIP trunk to SBCE.

SIPTrue IPv4 10.7.14.248 5060 TCP FALSE DOWN 408 Request Timeout DOWN

SM100 IP : 10.7.14.61
Interface A1 IP 10.7.14.248

but I can use SM 10.7.14.60 ping to 10.7.14.248 is normally and Interface A1 ping to SM or SM100 is normally too.

Please help and advise us.
Thank you very much.
 
 https://files.engineering.com/getfile.aspx?folder=6802c14a-8acc-40f2-997b-c1334e558b7c&file=1.PNG
entity link monitoring is the process of sending a SIP OPTIONS to the other side and looking for any response to see if it's up. 200OK, 404 not found, 503 server internal error, those are all valid answers that say "the other end of this entity link is there"

By getting a timeout and marking it out of service, SM will save 10ish seconds on a call that should try that link first and go right to the next choice.

But, your SBC needs to be configured to answer it - or at least pass it along to the carrier/B1/Other side for the carrier to provide a response.

In your domain policies, in signaling rules that apply to the SM link, there's a tab in there where you can add "OPTIONS that are out of dialog, block with 200OK" and the SBC will immediately send a 200OK back to SM for that

Or just turn off that entity link monitoring towards the SBC from SM if you're lazy.
 
Thx kyle555

Now I change protocol to udp it up but has reason code 604 Does Not Exist Anywhere.
 
that's fine. it's a response from the far end. If calls route out that way, you're fine
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top