Vista SOUND-Problem only at incoming calls

[Tugi2o]

Hi,
now i've installed the latest software (Client 5.1.4492.0 & Server 4510) and i have still only one problem, described here:

We have a lot of computers, all connected to the 3cx server. OS on these computers: WinXP or Vista.
This problem appears only at those computers, whos OS is Vista.

When i (Ext 50, winXP) call my friend (Ext60, Vista), i can't hear him, but he can hear me.
When i check the system settings for sound (Micro) at Vista pc (EXT60), it is activated and the volume is 100%.
I can also see on EXT60 sound settings (during the call) the signal, when i talk to the micro. So the micro is activated and works.
Also my Sound-Settings are OK.

Then i call him again (50 calls 60) and i can hear him, everything works fine.
Then i call him again, and i can't hear him.
Then i call him again 10 minutes later and i can hear him.
:
:

so i can hear him only at every 2nd call. i think that there is something wrong?!? it cannot be by coincidence, or?
This problem appears only at incoming calls @ all of our computers with OS Vista.

...call terminated
11:28:19.250 CallCtrl:nLegConnected [CM503007]: Call(47): Device joined: sip:[email protected]:5070;rinstance=fc3b352aa473d744
11:28:19.234 CallCtrl:nLegConnected [CM503007]: Call(47): Device joined: sip:[email protected]:5070;rinstance=bd252b13785b2741
11:28:16.031 CallCtrl:nSelectRouteReq [CM503004]: Call(47): Calling: Ext:60@[Dev:sip:[email protected]:5070;rinstance=fc3b352aa473d744]
11:28:16.000 CallCtrl:nIncomingCall [CM503001]: Call(47): Incoming call from Ext.50 to [sip:[email protected]:5060]

We all use the same hardware = Logitech USB Headset

perhaps u can help me?

 

[nb]

Same here, ahd a lengthy session with the local 3cx guy, but could not resolve the problem, it is a real shame as otherwise all our hard phones are working perfectly, except for me and I am who pays..... so I am not upgrading to the paid system until this is fixed ......

Again what a shame.... this has been hanging around for a long time and when Windows 7 arrives , what happens then../quote]

I just posted a post -

I will repost it here (not exactly because not all is relevant)

Re: Is problem with no sound on incoming calls solved?
by nickybrg on Wed Nov 05, 2008 7:43 am

This is a common symptom in VOIP showing one or a combination of all the below:

1) Incorrect router configuration
2) Incorrect port mapping
3) Incorrect gateway config of gateway (analogue/Isdn etc)
4) Incorrect voip Provider config (in PBX) if tweaks were done manually or if using an unsupported voip Provider. Because the templates we ship are fully tested for those we support.
5) Incorrect eyebeam configuration.
6) Also machine device driver can be the source of this too.

As you can see the list can be endless especially where routing and networking is concerned.

I can assure you that if all the above are met, this will work in 6 too not to mention in 7.

What is the nature of the incoming call? is it coming from a voip Provider or from a gateway? Because like this we can start the process of elimination easier.

Another thing you can try to quickly rule out 3 quarters of the above list. Make the same call using another phone - not eyebeam. What is the result? If you dont get 1 way audio, then most probably a change is needed Eyebeam config.

 

[nb]

Send us logs or a capture taken from the PBX machine of a call with 1 way audio.

What phones are being used?

 

[beppler]

Hi, I´m using Windows Server 2008 and have the same problem.

When I receive a call, I can hear the other side, but the other side can not hear me.

 

[nb]

We need to see logs to help you out and too see whats happening.

Can you reproduce this? from this comment

We have this problem on local LAN with no tricks happening

it should not be too difficult to send us logs and reproduce correct ?

You can send them in private message.

You can also send me the Voip client ini file.

C:\Documents and Settings\nicky\Local Settings\Application Data 3cx voip client

There is a file here with all the connections you have set up in the voip client. Send it to me and I will check it.

Please remember to specify which of these connections produces 1 way audio if you have multiple connections. If you specify the profile name it would be enough.

 

[jkimbro]

We have been having the same problem and working with DeerField for 3 months now. We have tested and we can reproduce the problem on all versions of Vista. We have tried Windows 2003 server and Windows 2008 Server to Host. We have even tried the new Version 7 client and server and we still have the problem. Deerfield has had us take packet captures of the problem and sent it to devolpers. At this point we have started the process of looking at other solutions. I am dragging my feet because I do like the 3CX best, but if we can not get it to work on Vista than we have to look elsewhere.

 

[Alejandro Esteve]

Hello,

i have two files. Under Vista Ultimate inbound calls works one time and the secod time doesn´t works, and occurs everytimes. Intern calls works right. Outbound calls right too.

One file "funciona.txt" is when the audio works in both ways.

The file"NoFunciona.txt" is the second call, and in this case i listen but the other person can´t listen to me.

The problem is Vista because i probe in the same connection with an Xp computer and works perfectly with 3CX softphone.

Alejandro Esteve

 

[jkimbro]

I do not have them anymore, but Kevin at Deerfield should have them.

 

[nb]

Alejandro :
There is a voip provider in the mix. And to make matters even worse it is unsupported. The guys here are complaining that they cannot get audio from a simple internal call. Unfortunately these logs and your scenario are not enough to troubleshoot this case.

Some tips just the same:
Confirm that the Provider is connected to Media Server. It should be from the logs but double check.
I think it is a problem with the provider or incorrect configuration of 3CX, or Incorrect VC configuration. Especially if you are saying that the second call does not give you audio. It is not a VISTA problem for sure. Otherwise you will never have audio. So Vista is definately not the problem. If you made the same calls on XP, you were just lucky. Or you have better network mappings on XP.

What I can tell you is that there is a consistency between the two logs you sent. ports are correct. PBX is working as it is supposed too. Bind the Voip Client to media server (Note Im telling you this to compensate for any network issues / and to compensate for Telsome Provider.)

 

[aesteve]

Alejandro :
There is a voip provider in the mix. And to make matters even worse it is unsupported. The guys here are complaining that they cannot get audio from a simple internal call. Unfortunately these logs and your scenario are not enough to troubleshoot this case.

* My VoIp provider is Identix. The distributor of 3CX in Spain.

Some tips just the same:
Confirm that the Provider is connected to Media Server. It should be from the logs but double check.
I think it is a problem with the provider or incorrect configuration of 3CX, or Incorrect VC configuration. Especially if you are saying that the second call does not give you audio. It is not a VISTA problem for sure. Otherwise you will never have audio. So Vista is definately not the problem. If you made the same calls on XP, you were just lucky. Or you have better network mappings on XP.

* I think that the problem is vista for some reasons:
- With Windows Xp the client works. There are not soft firewalls in any scenario. With the same configuration and the same connection with XP works and with Vista is, one time work, the another one no work, the next work, the following no, and it´s repeates all times. One work the bext no work.
- With the x-lite softphone under windows Vista, the system work´s fine all the time.
- The unique problem i encountered in this escenario is Windwos Vista and the client of 3CX.

What I can tell you is that there is a consistency between the two logs you sent. ports are correct. PBX is working as it is supposed too. Bind the Voip Client to media server (Note Im telling you this to compensate for any network issues / and to compensate for Telsome Provider.)

 

[nb]

We can do the following:

make a capture with wireshark of a successful call.
Then another with an unsuccessful call.

We will check it no problem.

 

[aesteve]

hi,

thanks nickybrg for your interest.

In the attachments are the WireShark files.

Regards

 

[nb]

You have captured nothing here - there is no sip

You have tunnel data passing but no sip.

Start wireshark - make call. Finish call - stop wireshark. Make sure you are capturing on the correct interface.
Save capture and send.

 

[aesteve]

You have captured nothing here - there is no sip

You have tunnel data passing but no sip.

Start wireshark - make call. Finish call - stop wireshark. Make sure you are capturing on the correct interface.

* I make the process you say in your post in the same order. If i open "funciona" and apply de filter "sip" appears 3 lines

In the filter of "NoFunciona" with the "sip" filter only appears one line.

Save capture and send.

 

[aesteve]

Sorry,

i passed wireshark in the interface of the client.

It´s waht you want, no ? or do you want to capture on the PBX interface ?

regards.

 

[nb]

You are using the tunnel and through it a voip provider then?
I think your Voip client is not configured correctly.

Can you send me the Voip client ini file?

Documents and settings\User account\Local settings\application data\3cx voip client\phone.ini

Ideally better if the captures are made from the pbx machines.

In the meantime send me this file and tell me the name of the profile you are using.

 

[aesteve]

Hi,

this is the .ini file

Regards.

 

[aesteve]

Sorry,

here is the attachment

 

[nb]

What I can tell you is the following:

1) To configure voip client directly with voip provider you should do the following:
Profile 1 - unconfigured - no problem (in office)
Profile 2 - unconfigured - no problem (Out of office)
Profile 3 - configured Out of office tunnel - Problem Final Remoto del tunel - this is wrong. It is set to My domain.

I will concentrate on the VOIP PROVIDER section:

This is profile 4 named voip provider.
After entering the Auth ID, User and password (which I assume you removed intentionally) you have to start configuring the tabs.
a) SIP PORT (puerto sip) can be anything on your local machine - 5060, 5070 etc. Note that if you use voip client on the same machine of the PBX you will have problems using 5060. Leave rtp ports as they are.
b) STUN - Stun was unchecked. This is a major problem. A voip provider connection from phone to provider must always have stun enabled. No wonder you have problems.

Check stun and you will work.

Also this is why the captures before had tunnel data in them, and not sip. Because the tunnel profile was the default.

 

[aesteve]

Hi and thanks,

My profile is the 3 - tunnel. I write "MyDomain" for security but in the real .ini is the real domain.

The 4 profile works when i put de data. but i need the 3 profile because i´m out of the office.

Regards.

 

[nb]

Your profile 3 is a tunnel connection.

You cannot connect it to a voip provider

You have to connect it to a listening tunnel residing on a 3cx phonesystem

Follow these steps -
IP PQDN - local ip of 3cx phonesystem - port 5060
Authentication Normal
Ports tab leave everything defuault
General tab - make sure stun is unchecked.
Tunnel tab - check tunnel
Use tunnel of host - the ip address local of the machine where the voip client is installed port 5080
Remote end of tunnel - the public IP ADDRESS of the remote 3CX phonesystem on port 5090
Tunnel password- the password set in the PBX section under Settings\Network\3cxtunnel tab (in version 7)
The ID - this is the line number - example if the tunnel on 3cx is created with line number 10000, you have to put 10000 in the voip client ID box.
DTMF tab leave as is
Codec tab leave as is

press apply and ok.

Make sure that in the log in screen the actual tunnel connection is selected and press ok.
If you are prompted to restart restart the voip client.