Quick Sipxbridge Question

32 views
Skip to first unread message

Peter Krautle

unread,
Feb 16, 2022, 4:18:37 PMFeb 16
to sipxcom-users
We have a client running 20.08 with Sipxbridge connectivity to the ITSP - no changes to the configuration or ITSP for several months. All of a sudden incoming and outgoing calls stopped working. My partner restarted Sipxcom but it did not resolve the issue. I restarted Sipxbridge and service returned without issue.

In looking at the Sipxbridge log file last evening, one sees Sipxbridge exception could not do dns lookup for sip.aaa.com. The PCAP shows 500 internal server error, with a similar DNS error message.


Does anybody have any quick thoughts on what went on here?

Many thanks in advance.


Gerald Drouillard

unread,
Feb 16, 2022, 5:15:22 PMFeb 16
to Peter Krautle, sipxcom-users
is sip.aaa.com the localhost?
If so maybe add that into the /etc/hosts file 
I have seen issues if the dns does not come up right away.

--
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/f4dccf18-8016-46c2-8474-6b14f0dbb541n%40googlegroups.com.

Todd Hodgen

unread,
Feb 17, 2022, 3:22:25 AMFeb 17
to Peter Krautle, sipxcom-users

I think I recall an old issue where if the system was restarted, there was some type of race condition with sipXbridge that caused the SIP trunks not to re-establish due to some other service not being restarted yet.  I know I used to experience that in the past.  I thought I also recall a bug fix being implemented several years ago to fix it as well.  Maybe a new issue has been introduced, or the old issue re-introduced.   You might want to look back on old JIRA notes.

--

Matt Keys

unread,
Feb 18, 2022, 10:33:18 AMFeb 18
to sipxcom-users
Both screenshots indicate a DNS lookup failure for the domain. If you're specifying the ITSP by fqdn rather than IP in the trunk configuration, the server would need to resolve SRV records for that domain via DNS lookups. 

Peter Krautle

unread,
Feb 20, 2022, 5:31:35 PMFeb 20
to sipxcom-users
Thanks everyone for your responses. I looked back at the trace and expected DNS lookups after the incoming invite arrived - there were none. https://www.dropbox.com/s/cticvlqxvzqx9x8/sipxbridgesipdns.jpg?dl=0. The trunk currently uses an FQDN to point to the ITSP SIP trunk - will change to an IP address and see if the issue reappears.
Reply all
Reply to author
Forward
0 new messages