Navigation

    Netgate Discussion Forum
    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    1. Home
    2. Tags
    3. voip
    Log in to post
    • All categories
    • T

      Current pfSense (through to at least 21.05.2), SIP phone behind firewall, incoming call audio cuts out after 25-30 minutes, how to fix?
      Firewalling • voip • • tea

      6
      0
      Votes
      6
      Posts
      961
      Views

      T

      @danievr said in Current pfSense (through to at least 21.05.2), SIP phone behind firewall, incoming call audio cuts out after 25-30 minutes, how to fix?:

      @tea Have you fixed it? Things you could try: NAT keepalive of 15 seconds; Register Expires 30 secs; If supported, use TCP instead of UDP; If your calls are proxied through your provider's servers, they might terminate the call based on policy. dslreports.com has a lot of info on VOIP.

      It turns out that this most likely was something in the interaction between the particular VoIP phone and the particular IP telephony provider through which I received most of my incoming calls.

      For reasons unrelated to this issue, I ended up needing to switch VoIP providers. Having made the minimum changes necessary to connect to the new provider (essentially server and authentication details), the problem seems to have disappeared.

      I wish I knew what the actual problem was, but at least it's working for me now.

    • D

      IPsec tunnel from remote site, need to pass VLAN traffic for phones?
      IPsec • l2tp vlan ipsec voip vpn • • djohnson

      2
      0
      Votes
      2
      Posts
      355
      Views

      R

      @djohnson
      This is a late reply but it may assist someone else in future.
      The VOIP audio traffic (RTP) require separate UDP ports to be open. The exact range will vary depending on your VoIP system.

      Hence, if the RTP ports are not open, you can experience a "working" system, but with a complete lack of audio.

    • W

      VOIP calls don't end
      NAT • voip • • WillemC

      13
      0
      Votes
      13
      Posts
      864
      Views

      Y

      For nearly a year now, we have multichannel numbers and 800 numbers from Hottelecom. When it was connected, it was a problem, but not significant, so the support service instantly decided everything. Have you contacted the support team?

    • J

      Problema con voz
      Español • voip • • jorge_torres_c

      2
      0
      Votes
      2
      Posts
      89
      Views

      ptt

      https://forum.netgate.com/topic/21817/recomendaciones-al-postear

      https://docs.netgate.com/pfsense/en/latest/search.html?q=voip&check_keywords=yes&area=default

      https://docs.netgate.com/pfsense/en/latest/search.html?q=sip&check_keywords=yes&area=default#

    • S

      Fritzbox als VOIP Telefonanlage vor pfSense
      Deutsch • fritzbox voip sip nat • • stvmyr

      16
      0
      Votes
      16
      Posts
      4987
      Views

      S

      Bei mir funktioniert es inzwischen auch wie beschreiben. Leitung bleibt auch beim telefonieren stabil. Ich kann von meinem VOIP Telefon hinter pfSense nach aussen Telefonieren, und theoretisch auch "rein". Allerdings ist das nur für ca. 5 Minuten möglich (nach dem letzten Telefonat nach aussen). Das gleiche passiert, wenn ich mit meinem DECT Telefon (das direkt an der FB angemeldet ist) das VOIP Telefon Intern anrufe.

      Ich vermute das es irgend ein NAT Timeout ist?

    • MMapplebeck

      VoIP quality issues switching from SG-8860 to XG-7100
      Official Netgate® Hardware • voip xg-7100 stutter priq codel • • MMapplebeck

      3
      0
      Votes
      3
      Posts
      382
      Views

      MMapplebeck

      Hey @Derelict Thanks for the ideas. I've managed to find the issue, and it was an equipment problem on our ISP side.

      I ran some packet captures on both the internal VoIP VLAN, and the external SBC interface(our phone comes in over the same fiber asour IP, but on a separate interface on the demarcation unit(T-340)), found a lot of dropped packets, moved onto our WAN switch, and saw that there was an EXCESSIVE amount of Tx/Rx errors and collisions on the demarcation interface. When I dug into the interface itself, found that it was only negotiating at half-duplex, which would explain the issues. When I went back through my old config files for the SG-8860, I found that I had to force it into full-duplex mode as the T-340 for some reason will not auto-negotiate to full-duplex, but if I force my side to full, it works just fine, and not a single error since.

      Thanks again for chiming in.

      Marc
    • A

      VOIP O2 ankommende Anrufe (inbound) nicht möglich
      Deutsch • voip inbound sip • • alexander90

      37
      0
      Votes
      37
      Posts
      1612
      Views

      mike69

      @pet_nie

      Na, das freut doch. :)

    • G

      One way VoIP behind pfSense
      NAT • voip speedport telekom • • Gubbl

      1
      0
      Votes
      1
      Posts
      278
      Views

      No one has replied

    • K

      Hangout priority
      Traffic Shaping • voip traffic shaping multi-wan multiple-lan • • kcallis

      1
      0
      Votes
      1
      Posts
      308
      Views

      No one has replied

    • H

      Telekom VoIP kann mit manchen Telekom VoIP Anschlüssen nicht telefonieren
      Deutsch • pfsense telekom voip sip nat • • highc

      36
      0
      Votes
      36
      Posts
      3639
      Views

      P

      Die Anzeige der Rufnummer ist von Anbieter zu Anbieter unterschiedlich und wird in der Fritzbox korrigiert, wenn du dort auch Telekom hinterlegst. Bei "anderm Anbieter" passiert das nicht bzw. du mußt das manuell machen. im ip-phone-forum ist da einiges zu finden.

      Gruß
      pfadmin

    • F

      [HowTo] Telekom Voip Einstellungen
      Deutsch • howto voip • • flix87

      35
      1
      Votes
      35
      Posts
      32934
      Views

      W

      Ich habe nun meine Konfiguration auf folgende Einstellung geändert:

      bb37f9fa-dbac-41ca-b16a-aac46085cae5-grafik.png

      Das scheint notwendig zu sein, da die Telekom für die IP-Telefonie in Zukunft nur noch DNS-SRV/NAPTR zulässt und nicht mehr die Registrierung über den Port 5060/5061 direkt per UDP oder TLS.