• V20: 3CX Re-engineered. Get V20 for increased security, better call management, a new admin console and Windows softphone. Learn More.

Voice call only on way

Status
Not open for further replies.

merc01

Joined
Sep 14, 2007
Messages
2
Reaction score
0
I have installed 3CX ver 3.1.2434.0 behind a router. Ext 100 is setup using a ATA in the same network as the IPPBX. I have another ATA setup in a remote site.

Both devices are able to register. Ext 102 has the Extension is External and Bind Media server enabled.

If I use ext 102 to call to 100, the call is able to get thru.

However if the reverse is done, from 100 to 102 it rings but no audio when the call is picked up.

The remote ATA has its STUN enabled.

IPPBX is behind a full cone router.

Please see log file

58.595 StratLink::eek:nHangUp [CM104001] Call(14): Ext.100 hung up call; cause: BYE; from IP:192.168.0.103
16:06:39.367 CallLegImpl::eek:nConnected [CM103001] Call(14): Created audio channel for Ext.102 (202.156.160.141:51004) with Media Server (58.185.20.135:9026)
16:06:39.307 StratInOut::eek:nConnected [CM104005] Call(14): Setup completed for call from Ext.100 to Ext.102
16:06:39.307 CallLegImpl::eek:nConnected [CM103001] Call(14): Created audio channel for Ext.100 (192.168.0.103:40000) with Media Server (192.168.0.101:7026)
16:06:34.790 CallConf::eek:nProvisional [CM103003] Call(14): Ext.102 is ringing
16:06:32.076 CallConf::eek:nIncoming [CM103002] Call(14): Incoming call from 100 (Ext.100) to sip:[email protected]
16:06:16.935 StratLink::eek:nHangUp [CM104001] Call(13): Ext.102 hung up call; cause: BYE; from IP:202.156.160.141
16:05:30.738 CallLegImpl::eek:nConnected [CM103001] Call(13): Created audio channel for Ext.100 (192.168.0.103:40000) with Media Server (192.168.0.101:7024)
16:05:30.728 StratInOut::eek:nConnected [CM104005] Call(13): Setup completed for call from Ext.102 to Ext.100
16:05:30.728 CallLegImpl::eek:nConnected [CM103001] Call(13): Created audio channel for Ext.102 (202.156.160.141:51004) with Media Server (58.185.20.135:9024)
16:05:29.877 CallConf::eek:nProvisional [CM103003] Call(13): Ext.100 is ringing
16:05:29.757 CallConf::eek:nIncoming [CM103002] Call(13): Incoming call from 102 (Ext.102) to sip:[email protected]

As can be seen, when 100 is dialled to 102, its dialling to a private IP. Could this be a problem?

Can anyone help?
 
Could you please check if established call will not be unexpectedly dropped after ~30-40 sec? (I mean call from 102 to 100)

And please check call that was unestablished (call from 100 to 102), as well (just wait for about 30-40 sec).

Thanks a lot for information
 
Yes the successful call can last for more than 40 secs, infact I could use it for over 1min.

As for the unestablished call, the setup will be teared down after awhile when the audio does not get thru.

Will there be a problem if the remote router is a Port restricted router?

Thank you.
 
Status
Not open for further replies.
Get 3CX - Absolutely Free!

Link up your team and customers Phone System Live Chat Video Conferencing

Hosted or Self-managed. Up to 10 users free forever. No credit card. Try risk free.

3CX
A 3CX Account with that email already exists. You will be redirected to the Customer Portal to sign in or reset your password if you've forgotten it.