Kitz ADSL Broadband Information
adsl spacer  
Support this site
Home Broadband ISPs Tech Routers Wiki Forum
 
     
   Compare ISP   Rate your ISP
   Glossary   Glossary
 
Please login or register.

Login with username, password and session length
Advanced search  

News:

Pages: 1 [2]

Author Topic: VoIP Hardware  (Read 2036 times)

EC300

  • Just arrived
  • *
  • Posts: 10
Re: VoIP Hardware
« Reply #15 on: May 05, 2022, 04:59:04 PM »

Yealink W60P with a total of 3 handsets.  Don't get very many calls but the handsets are good to use as intercoms in the house.

Connected to Sipgate with two numbers over IPv6 (no NAT keepalives or STUN servers required anymore).
Logged

Alex Atkin UK

  • Kitizen
  • ****
  • Posts: 3788
    • Thinkbroadband Quality Monitors
Re: VoIP Hardware
« Reply #16 on: May 05, 2022, 10:01:10 PM »

Frustrating Gigaset haven't added IPv6 to the N300.
Logged
INTAKE (ECI) Home Hub 5A (OpenWRT) on Zen, 2xHauwei CPE Pro 2 H122-373 (VOXI 4G,Three 5G) Router: pfSense (i5-7200U) WiFi: Zyxel NWA210AX + Ubiquiti nanoHD (OpenWRT)
My Broadband History & Ping Quality Monitors

aesmith

  • Kitizen
  • ****
  • Posts: 1137
Re: VoIP Hardware
« Reply #17 on: May 06, 2022, 04:00:08 PM »

Connected to Sipgate with two numbers over IPv6 (no NAT keepalives or STUN servers required anymore).
Can you clarify on the keepalives?  Normally these are needed not just for NAT but to keep alive the permissions in the firewall.  Of course it depends on your firewall, however in most installations the action of a host inside your network sending data out to the Internet, causes the firewall to permit inbound packets representing replies.  In the case of UDP these rules normally timeout fairly quickly, hence the need to the SIP endpoint to keep them alive with Options ping or similar. Do you have a static inbound permission on your firewall?
Logged

EC300

  • Just arrived
  • *
  • Posts: 10
Re: VoIP Hardware
« Reply #18 on: May 07, 2022, 11:28:49 AM »

Indeed they would also keep a firewall state open, however with Sipgate on IPv6, incoming signalling for calls on port 5060 can arrive from several different IPv6 servers with different addresses, so keepalives anyway are not reliable on IPv6 with Sipgate, as the firewall will only allow in packets from the original IPv6 address that is 'keeping alive' the firewall state.  To make it all work, I simply have a firewall rule that allows all traffic in from Sipgate's IPv6 range (2001:ab7::/32), therefore no keepalives. 
Logged
Pages: 1 [2]