Audio and connectivity Problems

[Jonnaz]

I have V 8.0.10116.583 of 3cx installed on a Windows 2008 server in a Public data centre.

In my office I have my PC with the 3CX VoIP phone and a Linksys ATA.

I have 1 main extension and 1 test extension set up on the server as 100 (main) and 101 (test) I also have a DID which is setup with the main extension.

At the moment if I call from the ATA (ext 100) to the soft phone (ext 101) the call connects as it should, but there is no audio between the PC and the phone.

If I call from the soft phone to the ATA the soft phone and 3cx look to connect but the phone on the ATA doesn't ring or seem to register the call.

if I use the DID to call the ATA (using my mobile phone) it's the same, but if I set the soft phone to ext 100 it rings no problem although there is audio from the soft phone to the mobile there is no audio from the mobile to the soft phone.
This is the same for connecting to the VM, it looks to connect but there is no audio, although when connected via the DID the option to leave a message is perfectly clear, but I don't know if any of the test messages I have left were successful.

 

[leejor]

"No audio" problems are most often a result of Ports being blocked at some point. When using this Public Data Centre, are you allowed to choose which ports are forwarded to 3CX? Is everything set to use STUN? Since any devices you use will be outside the 3CX LAN you have to make sure that if they are operating on the same "outside" LAN that they each have a different port number. A few things to start with...

 

[Jonnaz]

"No audio" problems are most often a result of Ports being blocked at some point. When using this Public Data Centre, are you allowed to choose which ports are forwarded to 3CX? Is everything set to use STUN? Since any devices you use will be outside the 3CX LAN you have to make sure that if they are operating on the same "outside" LAN that they each have a different port number. A few things to start with...

As far as I know the server is DMZ no forwards or blocks.

By different ports I'm not sure I understand what you mean, I am very new to all this and all the stuff I have done before has been on LAN not WAN.

Thanks

 

[leejor]

By different ports I'm not sure I understand what you mean, I am very new to all this and all the stuff I have done before has been on LAN not WAN.

This would only apply if you were trying to use two or more different devices on a single remote LAN behind a router. Each device should be set to use a different port. If , say, the public IP of the remote LAN were 123.456.789.110 then the address of one device would be the public IP + port 5060 (if that is the one you've chosen to use), the second device would have to have 5061 (as long as it is a different port) so that the router at the remote end knew where to send the info, this may require port forwarding at the remote end as well. Think of the public IP as the country/city/street and address of an apartment building and the port numbers as apartment numbers.

 

[Jonnaz]

By different ports I'm not sure I understand what you mean, I am very new to all this and all the stuff I have done before has been on LAN not WAN.

This would only apply if you were trying to use two or more different devices on a single remote LAN behind a router. Each device should be set to use a different port. If , say, the public IP of the remote LAN were 123.456.789.110 then the address of one device would be the public IP + port 5060 (if that is the one you've chosen to use), the second device would have to have 5061 (as long as it is a different port) so that the router at the remote end knew where to send the info, this may require port forwarding at the remote end as well. Think of the public IP as the country/city/street and address of an apartment building and the port numbers as apartment numbers.

Yeah I thought that was the case, I have the soft phone forwarded on port 5060 and the ATA forwarded on port 5061 in the office, but still no audio

I also still have the problem that the ATA doesn't look to be accepting inbound calls altho outbound works

 

[leejor]

Try to capture the 3CX logs showing the registration of each of the devices. Of course this requires someone at each end, one to capture the logs and one to restart the phones at the far end. The logs should show how 3Cx sees the devices. What sort of router/firewall is at the remote end, some don't "play" well with VoIP. If you can, you could try running the ATA with a public IP, connected directly to the internet, no router. If you get audio with no problem then you'll know that your problems have something to do with the router at that end. If the issues persist then you may have to start looking at the settings at the other end.

 

[Jonnaz]

Try to capture the 3CX logs showing the registration of each of the devices. Of course this requires someone at each end, one to capture the logs and one to restart the phones at the far end. The logs should show how 3Cx sees the devices. What sort of router/firewall is at the remote end, some don't "play" well with VoIP. If you can, you could try running the ATA with a public IP, connected directly to the internet, no router. If you get audio with no problem then you'll know that your problems have something to do with the router at that end. If the issues persist then you may have to start looking at the settings at the other end.

In the office we have a linksys WAG54GS ADSL Router, with a Dynamic Public IP

This log is:

Phones connecting to 3CX, call from ext 101 to ext 100 (with no connection as it doesn't...), call from ext 100 to ext 101 connected and terminated.

12:06:58.357 [CM503008]: Call(11): Call is terminated
12:06:56.279 Session 88186 of leg C:11.1 is confirmed
12:06:56.107 [CM503007]: Call(11): Device joined: sip:[email protected]:59703;rinstance=21b655d6f1847863
12:06:56.107 [CM503007]: Call(11): Device joined: sip:[email protected]:5061
12:06:56.107 [MS210003] C:11.1:Answer provided. Connection(transcoding mode[unsecure]):77.95.32.34:9038(9039)
12:06:56.107 [MS210001] C:11.2:Answer received. RTP connection[unsecure]: 86.171.113.187:40006(40007)
12:06:56.107 Remote SDP is set for legC:11.2
12:06:46.982 [CM505001]: Ext.101: Device info: Device Identified: [Man: 3CX Ltd.;Mod: 3CXVoipPhone;Rev: General] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CXVoipPhone 3.1.8571.0] PBX contact: [sip:[email protected]:5060]
12:06:46.982 [CM503002]: Call(11): Alerting sip:[email protected]:59703;rinstance=21b655d6f1847863
12:06:46.763 [CM503025]: Call(11): Calling Ext:Ext.101@[Dev:sip:[email protected]:59703;rinstance=21b655d6f1847863]
12:06:46.763 [MS210002] C:11.2:Offer provided. Connection(transcoding mode): 77.95.32.34:9040(9041)
12:06:46.560 [CM503004]: Call(11): Route 1: Ext:Ext.101@[Dev:sip:[email protected]:59703;rinstance=21b655d6f1847863]
12:06:46.560 [CM503010]: Making route(s) to <sip:[email protected]>
12:06:46.560 [MS210000] C:11.1:Offer received. RTP connection: 192.168.1.5:16464(16465)
12:06:46.560 Remote SDP is set for legC:11.1
12:06:46.560 [CM505001]: Ext.100: Device info: Device Identified: [Man: Linksys;Mod: SPA Series;Rev: General] Capabilities:[reinvite, no-replaces, able-no-sdp, recvonly] UserAgent: [Linksys/PAP2T-5.1.6(LS)] PBX contact: [sip:[email protected]:5060]
12:06:46.560 [CM503001]: Call(11): Incoming call from Ext.100 to <sip:[email protected]>
12:06:46.373 [CM500002]: Info on incoming INVITE:
INVITE sip:[email protected] SIP/2.0
Via: SIP/2.0/UDP 192.168.1.5:5061;branch=z9hG4bK-fe24d23c;received=86.171.113.187
Max-Forwards: 70
Contact: "CSI:NE"<sip:[email protected]:5061>
To: <sip:[email protected]>
From: "CSI:NE"<sip:[email protected]>;tag=19e94a6014f59a77o1
Call-ID: [email protected]
CSeq: 102 INVITE
Expires: 240
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER
Proxy-Authorization: Digest username="Jonnaz",realm="3CXPhoneSystem",nonce="414d535c01380cd681:d92cfd1e33b371690e98c8bc0d5ba8df",uri="sip:[email protected]",algorithm=MD5,response="9b5444a84ad191d8562dbd425f52e1df"
Supported: x-sipura, replaces
User-Agent: Linksys/PAP2T-5.1.6(LS)
Content-Length: 0

12:06:28.576 [CM503008]: Call(10): Call is terminated
12:06:17.826 [CM503025]: Call(10): Calling Ext:Ext.100@[Dev:sip:[email protected]:5061]
12:06:17.826 [MS210002] C:10.2:Offer provided. Connection(transcoding mode): 77.95.32.34:9036(9037)
12:06:17.591 [CM503004]: Call(10): Route 1: Ext:Ext.100@[Dev:sip:[email protected]:5061]
12:06:17.591 [CM503010]: Making route(s) to <sip:[email protected]:5060>
12:06:17.591 [MS210000] C:10.1:Offer received. RTP connection: 86.171.113.187:40004(40005)
12:06:17.591 Remote SDP is set for legC:10.1
12:06:17.591 [CM505001]: Ext.101: Device info: Device Identified: [Man: 3CX Ltd.;Mod: 3CXVoipPhone;Rev: General] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CXVoipPhone 3.1.8571.0] PBX contact: [sip:[email protected]:5060]
12:06:17.591 [CM503001]: Call(10): Incoming call from Ext.101 to <sip:[email protected]:5060>
12:06:17.388 [CM500002]: Info on incoming INVITE:
INVITE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.4:59703;branch=z9hG4bK-d8754z-e417d92ea032c17f-1---d8754z-;rport=59703;received=86.171.113.187
Max-Forwards: 70
Contact: <sip:[email protected]:59703>
To: <sip:[email protected]:5060>
From: "3CXPhone"<sip:[email protected]:5060>;tag=2f7a120c
Call-ID: ZjJkMTVkNjU4Y2EwMDE3ZGRjMjQ5Y2ExZjdmZTFjMDQ.
CSeq: 2 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO
Proxy-Authorization: Digest username="101",realm="3CXPhoneSystem",nonce="414d535c01380cb911:5a8bd48be699b52d60d656ab933c2744",uri="sip:[email protected]:5060",response="f11d6ece10640d11b2bfc813dd91d119",algorithm=MD5
Supported: replaces
User-Agent: 3CXVoipPhone 3.1.8571.0
Content-Length: 0

12:04:56.310 [CM504001]: Ext.101: new contact is registered. Contact(s): [sip:[email protected]:59703;rinstance=21b655d6f1847863/101]
12:04:52.685 [CM504002]: Ext.100: a contact is unregistered. Contact(s): [sip:[email protected]:5061/100]