at home I have a1&1 DSL connection with a VoIP-PBX (Auerswald COMpact 3000) behind a pfSense v2.4.3 firewall with the siproxd plugin. Outbound calls are working right now. Inbound calls sometimes work but most of the time I have no audio (both ways). In the captured packets I can see that the non-audio calls always have the internal IP address of the PBX in it: "Status: 200 OK" packet: "Connection information (c): IN IP4 192.168.100.100" in the message body or "Contact: sip:4912345654321@192.168.100.100:5060" in the message header. When I have a working inbound call with correct two-way-audio there is always my public IP address in the header/body.
Does someone has an explanation of that behaviour or an idea how I could fix it??
Best regards
Harl
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
at home I have a1&1 DSL connection with a VoIP-PBX (Auerswald COMpact 3000) behind a pfSense v2.4.3 firewall with the siproxd plugin. Outbound calls are working right now. Inbound calls sometimes work but most of the time I have no audio (both ways). In the captured packets I can see that the non-audio calls always have the internal IP address of the PBX in it: "Status: 200 OK" packet: "Connection information (c): IN IP4 192.168.100.100" in the message body or "Contact: sip:4912345654321@192.168.100.100:5060" in the message header. When I have a working inbound call with correct two-way-audio there is always my public IP address in the header/body.
Does someone has an explanation of that behaviour or an idea how I could fix it??
Best regards
Harl