1

VoIP Register Trunk Registration Failed / Re-registered

Maciej Kwadrans

August 09, 2018 05:26

None

Follow

Good morning Yeastar Community.
Another problem.

S20
Firmware: 30.8.0.14

We are using Event Notifications and very often during the day we are getting lot's  of above two one so: VoIP Register Trunk Registration Failed / Re-registered
First is of course Registration Failed and couple second later we are getting Event about Re-Registered. It would not be surprising for us, but we get this from our all clients where we have S20. From common things, they have also same main router: UBNT Er-Lite 3. ISP's are random.
What is funny, we are getting alerts almost during same time from each locations.
And now main point: In the setting of the TRUNK we are using fqdn of the SIP Provider but if we will change it to IP - issue is addressed. We are not getting any on above alerts. First thought DNS. Ewerywhere we have same UBNT configuration but honestly everything else works like a charm.

Please advise.
Any suggestions ?

Waiting for your feedback.

Thank you in advance.

• Facebook
• Twitter
• LinkedIn

10 comments

• 1
  
  Maciej Kwadrans August 10, 2018 07:36

  Someone can help me ??

• 1
  
  Steven August 15, 2018 10:32

  Same problem here!
  S300 with firmware 30.8.0.14.

• 0
  
  Oscar Colka August 15, 2018 11:38

  This sounds like an issue related to DNS resolution. 

  Did this issue happen only after firmware upgrade?

• 0
  
  Maciej Kwadrans August 16, 2018 07:47

  Hi Oscar.
  I don't remember exactly but I think that this was starting happen more often after last ( or 2 firmwares before ) upgrade. Of course it sounds like a DNS issue but as I wrote before - everything elese which is using fqdn to resolve IP in my network work like a charm.

• 0
  
  Steven August 16, 2018 07:57

  Same here.  I don't remember exactly but I think the problem started about the beginning of July / end of June. 

• 0
  
  Oscar Colka August 20, 2018 11:29

  Maciej, Steven,

  How many SIP trunks do you have? Are they from the same SIP trunk provider? Did this issue happen on all the SIP trunks?

  Is it possible for you to capture the SIP logs for this issue and post the pcap logs(a download link of the pcap logs) here?

• 0
  
  Steven August 20, 2018 13:17

  We have three SIP trunks registered in the S300. But two of them are disabled.

  The issue happened on every SIP trunk as soon as they are enabled.

  
  
  I will try to capture a log as soon as it happens again.

• 0
  
  Maciej Kwadrans August 20, 2018 13:27

  Same here. Multiple Trunks, same issue.
  I will try to capture logs too.

   

   

   

• 0
  
  Jonathan November 16, 2018 23:04

  Do you have firewall rules and drop all enabled?

• 0
  
  Michael Rautenbach June 10, 2020 14:21

  What ever happened to this thread - how was the problem resolved?

  I have the same thing now in 2020

   

  Mike