No outgoing audio except onhold music

[luisdin]

Hello,
we have a 3CX installation on a Windows 10 machine sitting behind a FritzBox. The Fritzbox is configured to let the right ports through but I could not get ports 9000 - 10000 through, only 9000 to 9256. Please tell me if this could solve the problem. On our desks we use 3 x Grandstream Gxp1610 ip telephones.
After hours of configuring, everything works how it should, except audio doesn´t go out of the network. This is not including the onhold music when pausing a call. I find that a little bit confusing and I can´t find the reason why this is. It would be great If you could take a look at the support files.

Thanks and best wishes.
Luis Dinnebier

[Edited by Administrator]

 

[AWS2P]

Hi,
Have you done FW checker from dashboard ? is it Green or RED?
do you have audio on internal calls?
For RTP range you need to open 9000 to 10999 UDP ports for audio
Put the logs on verbose and see messages

you Should remove the attachment file , it may have sensitive informations on your 3CX, this is a public forum, this kind of file is generally for 3CX support team use

 

[luisdin]

Hi,
I changed the port forwarding settings in the FritzBox to let 9000 to 10999 through. Now the FW checker is green but audio doesn´t go through nevertheless.

Best wishes

 

[luisdin]

Hello,
here is a log from a call from inside to a phone outside:

04/09/2019 4:14:29 PM - Leg L:14.2[Line:10002>>01717265021] is terminated: Cause: BYE from local

04/09/2019 4:14:29 PM - [CM503008]: Call(C:14): Call is terminated

04/09/2019 4:14:29 PM - Leg L:14.1[Extn:02] is terminated: Cause: BYE from 10.11.12.6:5060

04/09/2019 4:14:20 PM - [CM503007]: Call(C:14): Line:10002>>01717265021 has joined, contact <sip:[email protected]-online.de:5060>

04/09/2019 4:14:20 PM - [CM503007]: Call(C:14): Extn:02 has joined, contact <sip:[email protected]:5060>

04/09/2019 4:14:20 PM - L:14.2[Line:10002>>01717265021] has joined to L:14.1[Extn:02]

04/09/2019 4:14:14 PM - [CM505003]: Provider:[03040042332] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] PBX contact: [sip:[email protected]:5060;transport=TCP]

04/09/2019 4:14:14 PM - [CM503002]: Call(C:14): Alerting Line:10002>>01717265021 by contact <sip:[email protected]-online.de:5060>

04/09/2019 4:14:13 PM - [CM503025]: Call(C:14): Calling T:Line:10002>>01717265021@[Dev:sip:[email protected]-online.de:5060;transport=TCP] for L:14.1[Extn:02]

04/09/2019 4:14:13 PM - [CM503027]: Call(C:14): From: Extn:02 (<sip:[email protected]:5060>) to T:Line:10000>>01717265021@[Dev:sip:[email protected]-online.de:5060;transport=TCP]

04/09/2019 4:14:13 PM - [CM503004]: Call(C:14): Route 2: from L:14.1[Extn:02] to T:Line:10000>>01717265021@[Dev:sip:[email protected]-online.de:5060;transport=TCP]

04/09/2019 4:14:13 PM - Line limit check: Current # of calls for line Lc:10000(@03040042330[<sip:[email protected]-online.de:5060>]) is 0; limit is 1

04/09/2019 4:14:13 PM - [CM503027]: Call(C:14): From: Extn:02 (<sip:[email protected]:5060>) to T:Line:10002>>01717265021@[Dev:sip:[email protected]-online.de:5060;transport=TCP]

04/09/2019 4:14:13 PM - [CM503004]: Call(C:14): Route 1: from L:14.1[Extn:02] to T:Line:10002>>01717265021@[Dev:sip:[email protected]-online.de:5060;transport=TCP]

04/09/2019 4:14:13 PM - Line limit check: Current # of calls for line Lc:10002(@03040042332[<sip:[email protected]-online.de:5060>]) is 0; limit is 1

04/09/2019 4:14:13 PM - Call(C:14): Call from Extn:02 to 01717265021 matches outbound rule '2'

04/09/2019 4:14:13 PM - [Flow] Call(C:14): has built target endpoint: Out#:>>Rule{2}>>01717265021 for call from L:14.1[Extn:02]

04/09/2019 4:14:13 PM - [Flow] Target endpoint for 01717265021 is Out#:>>Rule{2}>>01717265021

04/09/2019 4:14:13 PM - [CM503010]: Call(C:14): Making route(s) from Extn:02 to <sip:[email protected]:5060>

04/09/2019 4:14:13 PM - [CM505001]: Endpoint Extn:02: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Grandstream GXP1610 1.0.4.125 000b827e1479] PBX contact: [sip:[email protected]:5060]

04/09/2019 4:14:13 PM - [CM500002]: Call(C:14): Info on incoming INVITE from Extn:02: Invite-IN Recv Req INVITE from 10.11.12.6:5060 tid=6520926 Call-ID=[email protected]: INVITE sip:[email protected] SIP/2.0 Via: SIP/2.0/UDP 10.11.12.6:5060;branch=z9hG4bK6520926;rport=5060 Max-Forwards: 70 Contact: <sip:[email protected]:5060> To: <sip:[email protected]> From: <sip:[email protected]>;tag=1517252950 Call-ID: [email protected] CSeq: 81 INVITE Accept: application/sdp, application/dtmf-relay Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, INFO, REFER, UPDATE, MESSAGE Content-Type: application/sdp Proxy-Authorization: Digest username="YG1ywWxGOn",realm="3CXPhoneSystem",nonce="414d535c12bd39b472:3956c3015c2c31080a8d7536a11b757f",uri="sip:[email protected]",response="4bfbe63acc1e086585add578cee617a2",algorithm=MD5 Supported: replaces, path, timer User-Agent: Grandstream GXP1610 1.0.4.125 000b827e1479 Privacy: none P-Preferred-Identity: <sip:[email protected]> P-Access-Network-Info: IEEE-EUI-48;eui-48-addr=E0-28-6D-EB-85-28 P-Emergency-Info: IEEE-EUI-48;eui-48-addr=00-0B-82-7E-14-79 Content-Length: 372 v=0 o=02 8000 8000 IN IP4 10.11.12.6 s=SIP Call c=IN IP4 10.11.12.6 t=0 0 m=audio 5026 RTP/AVP 9 0 8 18 97 2 101 a=sendrecv a=rtpmap:9 G722/8000 a=ptime:20 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:97 iLBC/8000 a=fmtp:97 mode=30 a=rtpmap:2 G726-32/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15

04/09/2019 4:14:13 PM - [CM503001]: Call(C:14): Incoming call from Extn:02 to <sip:[email protected]:5060>

 

[AWS2P]

Can't see something related to audio in that log, is the log in verbose mode ?

No sip ALG on fritzbox?
IP 10.11.12.3 is your 3CX ?
did you check windows FW rules , sometimes they are not well done during install
No antivirus running on part of 3CX needing to be excluded from scan?

Is your trunk provider 3cx supported?

 

[luisdin]

No its medium, here is verbose

 

[luisdin]

I deactivated all numbers in the fritzbox then the FW test runs fine. Therefore I think alg is disabled.
10.11.12.3 is the 3cx and 10.11.12.1 the router.
The windows firewall seems to be fine. 3CX ports are let in from the outside. Everything is let out. I don´t have an antivirus.

We are using Deutsche Telekom call and srf which is supported but in the dashboard it says that it´s not.

Internal calls work fine.

 

[AWS2P]

is it DT or SRF trunk provider or both?
Which one is not seen as supported trunk ?
If it's really not supported do you have another trunk to test with ?
your 3CX is always running V15.5 ?

 

[AWS2P]

I deactivated all numbers in the fritzbox

What do you mean ? don't understand .
Do you have several LAN some IP adress in log are with 192.168.11.xxx format.

Hope you don't have double nated network

Ports for 3cx are not just open on FW they are forwarded to 3CX IP 10.11.12.3 ?

 

[luisdin]

Sorry I tried to write call and Surf thats our telekom plan : https://www.3cx.de/docs/deutsche-telekom-call-und-surf/

I did not update yet to v16 so yes it runs 15.5.

With the disabled numbers I mean that I´ve put all numbers offline in the fritzbox. This seems to deactivate the internal telephone system completly, so that it doesn´t block the needed ports for the 3cx.

The 192. ip adresses are really weird and I don´t know where they are coming from. We don´t double nat but maybe it could be the wifi card in the computer although this is disabled.

I will check tomorrow if the ports are actually forwarded inside windows (in the router they are for sure).

 

[AWS2P]

So DT trunk is not seen as a supported one?
Have you tried to delete the trunk and re done it from scratch?

To find where and who is using IP adress you can use very good free software here:
https://www.advanced-ip-scanner.com/de/

 

[JohnS_3CX]

Hi @luisdin

Please try (as a test) to put your 3CX machine in "Exposed Host" mode. This is how Fritz!Box does does DMZ functionality and will expose the PBX to the internet.



If this works for you it means that the problem was indeed the Fritz!Box firewall. If not, then there is also a way to capture packets from the Fritz!Box for analysis (http://fritz.box/html/capture.html) so you can compare your PBX capture VS the modem capture and see if the traffic is being blocked.

 

[luisdin]

Thank you very much!
Did I maybe forgot to forward a Port?
I forwarded these ones:

5001 tcp
5060 udp & tcp
5061 tcp
5090 udp & tcp
9000 - 10999 udp

Is it unsecure to expose the machine in the long term?

 

[JohnS_3CX]

Your ports can all be found here https://www.3cx.com/docs/ports/

Yes it is insecure because all ports reach this machine, you would not want that necessarily especially if other things need other ports.

The Fritz!Box will not allow you to share 2000 ports in one go, you have to add them in separate batches of 255, so:

• 9000-9255
• 9255-9500
• etc
• etc
• etc
• etc
• etc
• etc

 

[luisdin]

I know, already did that.

Now only the 3cx softphone has audio in both directions. The problems remains on the phones.

Edit: now the softphone doesn´t work also

 

[AWS2P]

Is the Box removable almost for testing time and replaced by a modem/router ?
is it DSL fiber line?

did you DL the software to scan Ip adress on lan ?

 

[luisdin]

The box is router/modem its more for consumers but the software is pretty good and flexible too -> https://en.wikipedia.org/wiki/Fritz!Box Our internet is a normal DSL.

The software gives no result meaning the ip is non existent as I expected.

 

[AWS2P]

Did you search on 10.11.12.xxx Lan range or 192.168.11.xxx range?

 

[JohnS_3CX]

If you opened the correct ports, please run the firewall checker first before troubleshooting the no audio. There's no point looking for other issues in case we cannot verify the router indeed opened the ports.

If that passes, then we can check verbose logs, and if needed then move on to captures until we can find the reason the audio is blocked

 

[luisdin]

Hello,

with the additional help of the 3CX team I could now solve the problem.
Indeed it was the 192.168.11.100 ip address that confused the 3cx
The ip came from the 3cx windows machine itself because the ip was manually assigned to it in the windows settings a long time ago. Because of some windows failover it got a normal ip via dhcp at the same time. So most of the time it used the working ip and sometimes the faulty one. I corrected this and now it runs perfectly!

Thanks at everyone that tried to help me!

Best wishes.

@JohnS_3CX if would you would have read my opening post you would have seen that the test passed fine.