Once again RTP packets problem

Discussion in '3CX Phone System - General' started by pcastro, Sep 19, 2007.

  1. pcastro

    Joined:
    Sep 19, 2007
    Messages:
    4
    Likes Received:
    0
    Hi there,

    here is my setup:

    Router ASUS WL500GP: 192.168.2.1 forwarding all packets on ports 5060, 5061, 9000-9500 to the 3CX server

    3CX server: 192.168.2.50

    Softphone: 192.168.2.22 (no firewall).

    When i try to make a call through a SIP provider, i can do the call... i can ear the remote user... but no audio OUT. This is the message on logs:


    [MS105000] Call(15) Ext.100: No RTP packets were received on 00000039@:remoteAddr=192.168.2.22:49160,extAddr=85.240.120.XX:9112,localAddr=0.0.0.0:9112


    Can someone please help me out?
     
  2. Mirzab

    Mirzab Member

    Joined:
    Jul 22, 2007
    Messages:
    400
    Likes Received:
    0
    Remote Address good, external address good, internal address seems to have gone south for a vacation :eek: 0.0.0.0 no good :evil:. I am not very sure why it is occurring, port or NAT issue? Softphone IP is right but why saying remote? Not on same LAN? Will need more info on setup for testing plus longer log maybe.
     
  3. pcastro

    Joined:
    Sep 19, 2007
    Messages:
    4
    Likes Received:
    0
    remoteAddr=192.168.2.22:49160 <-- this is my ip address using a softphone

    extAddr=85.240.120.XX:9112 <-- this is the ADSL External IP address

    The 3CX server is installed on 192.168.2.50, at the same lan.

    This is just a router on the, and 2 computers on the lan, the 2.22 (my ip) and the 2.50 (3CX)

    Any clue?

    Thanks for your reply
     
  4. Mirzab

    Mirzab Member

    Joined:
    Jul 22, 2007
    Messages:
    400
    Likes Received:
    0
    I would like to see a longer section of log around the error, just guessing right now. I don't understand why extension is designated as a remote address with the external address used. Calls from extensions on LAN, at least on my system, shows none of this. I strongly suspect a configuration error. An example from my log for an outbound call:
    As you can see no 0.0.0.0 , external addresses, remote addresses or such. Until you post more I would suggest reading manual and rechecking configuration.
     
  5. pcastro

    Joined:
    Sep 19, 2007
    Messages:
    4
    Likes Received:
    0
    Here are the logs.

    If i try a call to external number

    14:46:12.611 MediaServerReporting::RTPReceiver [MS105000] Call(18) Ext.100: No RTP packets were received on 00000011@:remoteAddr=192.168.2.22:49166,extAddr=85.240.120.xx:9032,localAddr=0.0.0.0:9032
    14:46:12.564 StratLink::eek:nHangUp [CM104001] Call(18): Ln:10000@Netcall hung up call; cause: BYE; from IP:82.94.244.100
    14:45:03.252 CallLegImpl::eek:nConnected [CM103001] Call(18): Created audio channel for Ln:10000@Netcall (195.22.26.84:16086) with Media Server (85.240.120.xx:9034)
    14:45:03.220 StratInOut::eek:nConnected [CM104005] Call(18): Setup completed for call from Ext.100 to Ln:10000@Netcall
    14:45:03.220 CallLegImpl::eek:nConnected [CM103001] Call(18): Created audio channel for Ext.100 (192.168.2.22:49166) with Media Server (85.240.120.xx:9032)
    14:44:58.564 CallConf::eek:nProvisional [CM103003] Call(18): Ln:10000@Netcall is ringing
    14:44:56.470 CallConf::eek:nIncoming [CM103002] Call(18): Incoming call from 100 (Ext.100) to sip:229384xxx@192.168.2.50


    To a internal extension (from 100 to 102)

    14:48:27.564 CallLegImpl::eek:nConnected [CM103001] Call(22): Created audio channel for Ext.100 (192.168.2.22:49172) with Media Server (85.240.120.xx:9048)
    14:48:26.173 CallConf::eek:nProvisional [CM103003] Call(22): Ext.102 is ringing
    14:48:25.673 CallConf::eek:nIncoming [CM103002] Call(22): Incoming call from 100 (Ext.100) to sip:102@192.168.2.50

    ...

    14:48:27.564 CallLegImpl::eek:nConnected [CM103001] Call(22): Created audio channel for Ext.100 (192.168.2.22:49172) with Media Server (85.240.120.xx:9048)
    14:48:26.173 CallConf::eek:nProvisional [CM103003] Call(22): Ext.102 is ringing
    14:48:25.673 CallConf::eek:nIncoming [CM103002] Call(22): Incoming call from 100 (Ext.100) to sip:102@192.168.2.50
     
  6. Mirzab

    Mirzab Member

    Joined:
    Jul 22, 2007
    Messages:
    400
    Likes Received:
    0
  7. pcastro

    Joined:
    Sep 19, 2007
    Messages:
    4
    Likes Received:
    0
    I believe that everything is ok like that post says.

    And yes, 3478 is forwarding to 3CX IP address on both protocols UDP and TCP.

    The weird thing on this, is that, now, sometimes i can't ear on the internal calls too.
     
  8. SY

    SY Well-Known Member
    3CX Support

    Joined:
    Jan 26, 2007
    Messages:
    1,821
    Likes Received:
    1
    Fortunately, I have a time to comment it :) . Version 4 takes to much time :)

    Again:
    remoteAddr=192.168.2.22:49160,extAddr=85.240.120.XX:9112,localAddr=0.0.0.0:9112

    remoteAddr - address specified by remote party. IT IS A DESTINATION FOR OUTGOING STREAM FOR PBX.
    extAddr/localAddr- one of these values is always 0.0.0.0:.... if both is not 0.0.0.0 it is a BUG, but you have no chance to find such situation. :)
    extAddr - STUN resolved address (used for external connections), localAddr - local destination (used for communications with local parties)

    address that is not equal to "0.0.0.0" is the address specified by PBX as destination for remote party (PBX will waiting for audio data there).

    from log:
    remoteAddr=192.168.2.22:49160 - it is local address and remote entity specified it as destination for stream sent by PBX to this entity.
    extAddr=85.240.120.XX:9112,localAddr=0.0.0.0:9112
    remote entity is marked as external in PBX configuration.

    So...
    PBX sends outgoing stream from 85.240.120.XX:9112 to 192.168.2.22:49160

    Do you think that it will arrive on 192.168.2.22:49160?

    remote entiry send stream to 85.240.120.XX:9112
    Are you sure that stream sent to 85.240.120.XX:9112 can be delivered by gateway of remote entity?

    Regards

    P.S. It is better to try to find on the forum. Here are a lot of threads and comments/solutions/workarounds... ;)
     

Share This Page