SBC and Remote Phones

63 views
Skip to first unread message

Brant Kenny

unread,
Jun 14, 2021, 4:47:36 PMJun 14
to sipxcom-users
All,
Good afternoon.  Banging my. head against a wall here.  Remote phones are using port 25983 to connect to the SBC.  The SBC, in turn, is forwarding the request to SipX on port 5060.  The SBC receives a 408 from SipX and the connection fails.  I've added the SBC in Internet Calling with 25983 and 5060 (just for testing) with no change.  

I'm feeling like I'm missing something simple.  Any help is appreciated. 

Peter Krautle

unread,
Jun 16, 2021, 5:01:21 PMJun 16
to sipxcom-users
What kind of SBC are you using?

Peter

Brant Kenny

unread,
Jun 16, 2021, 6:04:12 PMJun 16
to sipxcom-users
We're using an Audiocodes M1k SBC.  I'm working with Audiocodes implementation support for that half.  We're seeing the register being sent to SipX with SipX returning a 408.

Brant Kenny

unread,
Jun 17, 2021, 3:53:34 PMJun 17
to sipxcom-users
Kept rolling on this - SipX is sending a DNS_LOOKUP_FAILED error when trying to contact the SBC.  The SBC has valid _sip._tcp, _sip._udp, and _sip._tls.  records in our dns.  nslookup shows the correct weights, priorities, and hostnames in the file (including the . at the end of the hostname).  

Doesn't surprise me that it's DNS. 

Peter Krautle

unread,
Jun 17, 2021, 5:30:16 PMJun 17
to Brant Kenny, sipxcom-users

Hi Brent,

 

Have you gone through this wiki page http://wiki.sipxcom.org/display/sipXcom/Bria+Solo+with+Sipxcom . I suspect the domain name on the phone or Bria client from the SBC to Sipxcom cannot be found. If your SIP domain for your server is pbx.test.com, then the phone or Bria client should be using the domain name of lvtest.com. In the domain field, you can also define alternate aliases. Ascertain you push the server profiles in order for the alias to take.

 

Hope this helps.

 

Peter

--
You received this message because you are subscribed to the Google Groups "sipxcom-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sipxcom-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/f460b25b-1b25-4eff-91a8-4d9f133125c4n%40googlegroups.com.

Brant Kenny

unread,
Jun 21, 2021, 1:02:22 PMJun 21
to sipxcom-users
Peter - thanks for your message.  I was able to add the alias for the SBC to SipX. Getting 401 and 406 errors now.  At least it's progress.  Reviewing my Bria account to see if there's an issue there. 

Brant Kenny

unread,
Jun 21, 2021, 1:29:29 PMJun 21
to sipxcom-users
Looks like the Mediant isn't passing auth info to sipx.  Fun times.

12:26:02.000 AcTransactionUser::DecideAboutAuthenticationHandling - No user name was found (for authorization purpose) 



Matt Keys

unread,
Jul 9, 2021, 7:52:39 PMJul 9
to sipxcom-users
"We're seeing the register being sent to SipX with SipX returning a 408" -- A 408 Request Timeout usually means side A couldn't get a response from side B in the expected time. Typically it's network related, for example one side can't talk to the other or vice versa. Pay attention to the transport specification, if any, and use tools like nmap from side A and B to verify paths of what was requested. Typically the Contact: header of the INVITE (or whatever the request was) just prior to the 408 will give you the clue as to what and where a response was expected.

I agree when dealing with registrations the DNS response is important -- the query, where the client is looking for an answer, and the response. 

Regards,
Matt

Matt Keys

unread,
Jul 9, 2021, 8:25:43 PMJul 9
to sipxcom-users
Sorry one more thing to add regarding 408s -- if there's an expected level of latency between those the two sites you may get some improved performance by tweaking the T1 timer beneath system - services - sip proxy (show advanced) - " SIP Round Trip Time (T1 Timer)". The default is 100ms but most UAs (and the RFC spec if I'm not mistaken) specify T1 at 500ms. This will make the proxy wait longer before responding 408, but if you're running multiple proxies it may slow down client selection of a secondary (waits longer before looking for a secondary). 

Regards,
Matt

Brant Kenny

unread,
Jul 20, 2021, 9:30:11 PMJul 20
to sipxcom-users
Thanks for the info.  We made it past the 408 errors.  Now, we're getting 401s.  The same configuration works perfectly when we're registering directly to SipX.  It'll be fun to determine what the M1k is doing...again.
Reply all
Reply to author
Forward
0 new messages