Sound problem / one way audio

Status
Not open for further replies.

iossi01

Joined
May 2, 2011
Messages
6
Reaction score
0
Hello

I'm a newbie in 3CX.
I've installed yesterday the free version (V.10) intending to learn it.
The installation works fine on a WIN-XP machine.
I've build 2 extensions (100,101) and added a VOIP provider.
One extension was connected by BRIA as explained. The Bria connects fine to the 3cx.
At 3CX I've defined "outgoing rule". Till here everything is fine.
Upon connecting a call I am unable to hear the party on the other end.
It seems there is a mute option enabled or a span security option enabled. See attached desc.!
Please help and advice.

I've tried to perform Echo test (*777) and everything is fine there !
Iossi

13:54:40.781 [MS105000] C:4.2: No RTP packets were received:remoteAddr=192.168.10.14:8314,extAddr=0.0.0.0:0,localAddr=127.0.0.1:7006
13:54:40.250 [MS105000] C:4.1: No RTP packets were received:remoteAddr=10.228.66.117:10838,extAddr=62.219.135.26:9006,localAddr=62.219.135.26:9006
13:54:39.437 [CM503008]: Call(4): Call is terminated
13:54:39.265 C:4.2(LOCAL):Incorrect source of RTCP. expected:192.168.10.14:8315 but received from 127.0.0.1:8315
13:54:39.250 C:4.2(LOCAL):Incorrect source of RTP stream. expected:192.168.10.14:8314 but received from 127.0.0.1:8314
13:54:39.234 C:4.2(LOCAL):Incorrect source of RTP stream. expected:192.168.10.14:8314 but received from 127.0.0.1:8314
13:54:39.218 C:4.2(LOCAL):Incorrect source of RTP stream. expected:192.168.10.14:8314 but received from 127.0.0.1:8314
13:54:39.203 C:4.2(LOCAL):Incorrect source of RTP stream. expected:192.168.10.14:8314 but received from 127.0.0.1:8314
13:54:39.171 C:4.2(LOCAL):Incorrect source of RTP stream. expected:192.168.10.14:8314 but received from 127.0.0.1:8314
13:54:39.156 C:4.2(LOCAL):Incorrect source of RTP stream. expected:192.168.10.14:8314 but received from 127.0.0.1:8314
13:54:39.140 C:4.2(LOCAL):Incorrect source of RTP stream. expected:192.168.10.14:8314 but received from 127.0.0.1:8314
13:54:39.125 C:4.2(LOCAL):Incorrect source of RTP stream. expected:192.168.10.14:8314 but received from 127.0.0.1:8314
 
Are both extensions on the same LAN as 3CX? No audio between what? Extension to extensions? One/both extensions outbound ? Audio one way, or just none at all? Did you open (forward) all necessary ports in the router that 3Cx is behind? Did you run the firewall check within 3CX?
 
leejor said:
Are both extensions on the same LAN as 3CX? No audio between what? Extension to extensions? One/both extensions outbound ? Audio one way, or just none at all? Did you open (forward) all necessary ports in the router that 3Cx is behind? Did you run the firewall check within 3CX?


Hi leejor,

On the same LAN everything works fine.
I've checked the firewall within 3CX and everything works fine.
The problem is that the Bria extension calls the party is unable to hear. I hear the other party ok.
Even Echo test is not working regardless what I said previously.

Thank you.
 
Bria is...a SIP application? I'm not familiar with it. You're using it from outside your LAN? That is the only SIP device that has problems? Do you have it set to make use of STUN.
 
If Bria and PBX are running on the same computer, then (in Bria configuration) you need to specify server location as 127.0.0.1 (not 192.168.10.14)
 
Thank you for the tip. I'll try it tomorrow at my office and I'll tell you if it was a success.

Iossi ;)
 
Hi Stepan,

Your advice was real good. Now the situation is much better.
I have one small little problem remaining.
I have 2 extensions (100,101). Extension 100 is connected to Bria inside the LAN and your advice solved the one way audio problem.
The second extension (101) is connected to a SIP device outside the LAN. I've added there stun as requested.
From ext. 101 I can call everywhere and it's OK. (this includes ext 100)
The problem is that I cannot call 101 from 100. The call waits for a while and than the voice recorder starts... (Cause: 408 Request Timeout; internal)

Have you any idea about that ?

Thanks a lot,
Iossi

10:04:32.187 [CM503008]: Call(5): Call is terminated
10:04:24.921 [CM503007]: Call(5): Device joined: sip:[email protected]:40600;rinstance=cac4ebb454021303
10:04:24.906 [CM503007]: Call(5): Device joined: sip:[email protected]:13648
10:04:24.906 [CM505001]: Ext.99: Device info: Device Identified: [Man: 3CX Ltd.;Mod: Voice Mail Menu;Rev: General] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CX Voice Mail Menu] PBX contact: [sip:[email protected]:5060]
10:04:24.906 [CM503002]: Call(5): Alerting sip:[email protected]:40600;rinstance=cac4ebb454021303
10:04:24.734 [CM503025]: Call(5): Calling Ext:Ext.999@[Dev:sip:[email protected]:40600;rinstance=cac4ebb454021303]
10:04:24.718 [CM503005]: Call(5): Forwarding: Ext:Ext.999@[Dev:sip:[email protected]:40600;rinstance=cac4ebb454021303]
10:04:24.718 [CM503003]: Call(5): Call to sip:[email protected] has failed; Cause: 408 Request Timeout; internal
10:04:24.406 Currently active calls - 1: [5]
10:03:52.656 [CM503025]: Call(5): Calling Ext:Ext.101@[Dev:sip:[email protected]:14715;rinstance=FB0FD07B]
10:03:52.406 Currently active calls - 1: [5]
10:03:52.390 [CM503004]: Call(5): Route 1: Ext:Ext.101@[Dev:sip:[email protected]:14715;rinstance=FB0FD07B]
10:03:52.390 [CM503010]: Making route(s) to <sip:[email protected]>
 
Status
Not open for further replies.

Members Online Now

No members online now.

Forum statistics

Threads
111,835
Messages
589,291
Members
164,668
Latest member
Infinity Network