Disable Proxy mode.

User to User - Answers are provided by the community. 3CX does NOT provide technical support via this forum. Commercial grade support should NOT be expected

Moderators: kevin, 3CX staff

Disable Proxy mode.

Postby wzaatar » Tue Sep 23, 2008 10:16 pm

Hello, everyone...

I've got a tough question here: :shock:

Scenario:

I have two LANs (192.168.1.0/24 and 192.168.2.0/24), each with one SIP ATA (192.168.x.5), in addition I have installed a 3CX server on 192.168.1.1

Configured everything without STUN, extensions (101 for 192.168.1.5 and 201 for 192.168.2.5) call each other without any problem.

Now... My issue:
I have recently acquired a DID number and set it to ring on ext. 101, everything works fine, audio is still crystal clear... However, when I set it to ring on ext. 201, audio is garbled: the reason, as I discovered it when logging verbose: the 3CX server sits as a 'proxy' and forwards RTP packets from 201 to the external DID and vice-versa...

So RTP packets going to 201 are going through the SIP server and are being relayed to the extension despite the fact that I disabled PBX audio relay in 3CX.

The link between the two subnets cannot handle extra bandwidth need.

Does anyone have any solution for this?

And thanks!

w.
Wadih Zaatar
email: wzaatar at gmail dot com
wzaatar
Expert
Expert
 
Posts: 106
Joined: Wed Aug 01, 2007 5:13 am
Location: Montreal

Re: Disable Proxy mode.

Postby alexmallia » Wed Sep 24, 2008 10:21 am

Even if you have disabled PBX delivers audio for both devices, you must have Supports Re-Invite enabled for both of them.

If this is disabled, the PBX will still deliver audio.

regards
Alex Mallia
Technical Support Engineer
3CX - Developers of IP PBX software
http://www.3cx.com
alexmallia
Site Admin
Site Admin
 
Posts: 126
Joined: Mon Aug 04, 2008 8:59 am

Re: Disable Proxy mode.

Postby wzaatar » Wed Sep 24, 2008 6:51 pm

Hi Alex,

Thanks for the reply!

Both the DID/DO and the extension are configured to support re-invite and 'replaces'... Yet it doesn't fix it! :cry:

3cxMedia snapshot:
20:50:03.854|.\MSEndPoint.cpp(1457)|Log2||??:[MS210000] C:12.1:Offer received. RTP connection: 192.16.2.5:5004(5005)
20:50:03.864|.\MSEndPoint.cpp(1215)|Log2||??:[MS210006] C:12.2:Offer provided. Connection(by pass mode): 192.16.2.5:5004(5005)
20:50:12.266|.\MSEndPoint.cpp(1462)|Log2||??:[MS210001] C:12.2:Answer received. RTP connection: 192.16.1.5:5004(5005)
20:50:12.266|.\MSEndPoint.cpp(1220)|Log2||??:[MS210007] C:12.1:Answer provided. Connection(by pass mode): 192.16.1.5:5004(5005)
21:08:35.052|.\MSEndPoint.cpp(1457)|Log2||??:[MS210000] C:13.1:Offer received. RTP connection: xxx.xxx.xxx.xxx:43614(43615)
21:08:35.072|.\MSEndPoint.cpp(1180)|Log2||??:[MS210004] C:13.2:Offer provided. Connection(proxy mode): 172.16.1.2:7322(7323)
21:08:40.239|.\MSEndPoint.cpp(1462)|Log2||??:[MS210001] C:13.2:Answer received. RTP connection: 192.16.1.5:5004(5005)
21:08:40.249|.\MSEndPoint.cpp(1185)|Log2||??:[MS210005] C:13.1:Answer provided. Connection(proxy mode):xxx.xxx.xxx.xxx:5004(5005)
21:19:46.577|.\MSEndPoint.cpp(1457)|Log2||??:[MS210000] C:14.1:Offer received. RTP connection: xxx.xxx.xxx.xxx:43628(43629)
21:19:46.597|.\MSEndPoint.cpp(1180)|Log2||??:[MS210004] C:14.2:Offer provided. Connection(proxy mode): 172.16.1.2:7324(7325)
21:19:52.786|.\MSEndPoint.cpp(1462)|Log2||??:[MS210001] C:14.2:Answer received. RTP connection: 192.16.1.5:5004(5005)
21:19:52.786|.\MSEndPoint.cpp(1185)|Log2||??:[MS210005] C:14.1:Answer provided. Connection(proxy mode):xxx.xxx.xxx.xxx:5006(5007)


You can see from the above that internal calls are in "by pass" mode whereas DID calls are "proxy mode"

Thanks!

W.
Wadih Zaatar
email: wzaatar at gmail dot com
wzaatar
Expert
Expert
 
Posts: 106
Joined: Wed Aug 01, 2007 5:13 am
Location: Montreal


Return to 3CX Phone System - General (Community-led, no tech support)


Who is online

Users browsing this forum: No registered users and 2 guests

Announcements: