inband call disconnect every 4.30min but outband calls good

Discussion in '3CX Phone System - General' started by todd, Jul 23, 2007.

  1. todd

    Joined:
    Jun 9, 2007
    Messages:
    35
    Likes Received:
    0
    3CX Phone System v3.0.2328.0
    all outband calls good. but inband call disconnect every 4-5 min.
    All of our internal external extensions, IP phone or soft phone are same.

    any help ?

    Thank you very much!
     
  2. 5qg4

    5qg4 Active Member

    Joined:
    Jan 31, 2007
    Messages:
    643
    Likes Received:
    0
    Please provide the system log.

    Connected to PSTN gateway or VoIP Provider?
     
  3. Anonymous

    Anonymous Guest

    Looks like it is sip registration issue.

    Does the same apply when you get a PSTN call comming in? or is it on sip calls only?
     
  4. todd

    Joined:
    Jun 9, 2007
    Messages:
    35
    Likes Received:
    0
    Connected to VoIP Provider engin (Austrlia Company)
    Same apply when I get a PSTN &sip call comming.

    Line(s) Configuration:
    Registrar/Proxy Hostname or IP 65306;syd.byo.engin.com.au
    Registrar/Proxy Port :5060
    Outbound Proxy Hostname or IP in.com.au :syd.byo.engin.com.au
    Outbound Proxy Port (default is 5060) :5060
    STUN server Hostname or IP
    STUN server Port (default is 3478) STUN server Port (default is 3478)
    Time between registration attempts (in seconds) :30
    Require (optionally: authorized) registration for: Both in-out calls
    Which IP to use in 'Contact' field for registration :Specified IP (My Ip)
    Specify how this voip provider handles transfers :Supports Re-Invite
    Specify in which SIP Header field the call destination will be included
    'To.user' field, 'Request-Line-URI' field

    PBX delivers audio

    Caller-ID is in 'user' part of (one of following) :'From' field
    Called-Number (for inbound calls) is in: 'To' field





    12:19:12.718 MediaServerReporting::RTPReceiver [MS005001] Call(174) Ln:10000@engin 9.95: payload #18 doesn't correspond initial SDP datalen=20
    12:19:12.703 MediaServerReporting::RTPReceiver [MS005001] Call(174) Ln:10000@engin 9.95: payload #18 doesn't correspond initial SDP datalen=20
    12:19:12.687 MediaServerReporting::RTPReceiver [MS005001] Call(174) Ln:10000@engin 9.95: payload #18 doesn't correspond initial SDP datalen=20
    12:19:12.656 MediaServerReporting::RTPReceiver [MS005001] Call(174) Ln:10000@engin 9.95: payload #18 doesn't correspond initial SDP datalen=20
    12:19:12.640 MediaServerReporting::RTPReceiver [MS005001] Call(174) Ln:10000@engin 9.95: payload #18 doesn't correspond initial SDP datalen=2
    12:

    11:44:25.656 StratLink::eek:nHangUp [CM104001] Call(181): Ln:10000@engin 9.95 hung up call; cause: BYE; from IP:203.161.160.69
    11:44:25.515 Endpoint::findSource [CM010001] Line configuration does not allow identification of the source of this call. Check Advanced Options for Gateways and Providers and match a field to a correct value from the following: Contact IP: '203.161.160.79'; From: '0292127806'; To: '0280040111'; Rline: '3cxPbx'; Contact: '0LWLy8HYWmuKrpiW1BbCcPXE1_mh9wxA6c.'
    11:44:21.734 ClientRegs::eek:nSuccess [CM113005] Registration of sip:0281972588@syd.byo.engin.com.au is successful
    11:44:21.531 ExtLine::Register [CM110004] Send registration for "Darren Tech"<sip:0281972588@syd.byo.engin.com.au>
    11:44:21.531 ExtLine::Register [CM110002] Use Specified IP for device line registration DN='10000' device='engin 9.95'
    11:44:21.218 StunClient::process [CM115002] STUN resolved external IP=60.241.248.251:5060 by server 194.221.62.209
    11:39:54.812 CallLegImpl::eek:nConnected [CM103001] Call(181): Created audio channel for Ext.8001 (192.168.1.101:35854) with Media Server (192.168.1.2:7344)
    11:39:54.796 StratInOut::eek:nConnected [CM104005] Call(181): Setup completed for call from Ln:10000@engin 9.95 to Ext.8001
    11:39:41.203 CallConf::eek:nProvisional [CM103003] Call(181): Ext.8001 is ringing
    11:39:32.015 MediaServerReporting::DTMFhandler [MS211000] Call(181) Ln:10000@engin 9.95: DTMF (RTP) from 203.161.160.79:16826 arrived. in-band DTMF tone detection is turned off.
    11:39:25.359 CallLegImpl::eek:nConnected [CM103001] Call(181): Created audio channel for Ln:10000@engin 9.95 (203.161.160.79:16826) with Media Server (60.241.248.251:9374)
    11:39:25.343 CallConf::eek:nIncoming [CM103002] Call(181): Incoming call from 0292127806 (Ln:10000@engin 9.95) to sip:0280040111@voice.mibroadband.com.au
    11:39:20.578 StunClient::process [CM215001] STUN failed to resolve external IP using server 194.221.62.209
     
  5. Anonymous

    Anonymous Guest

    Get a local STUN server. Use that and let me know what happens, looks like the call is setup but is dropped due to registration.

    Not sure, but no harm in trying.
     
  6. todd

    Joined:
    Jun 9, 2007
    Messages:
    35
    Likes Received:
    0
    I use my IP for Registration, So I didnot put any thing to "STUN server Hostname or IP" field. but the General Settings, I put 2 of STUN server:

    stunserver.org
    stun.3cx.com
    in the most of time, they are not warking for Sydney.

    It's very hard to find a Sydney STUN server.
    I'll try to find one for me.

    BTW,if the caller use PSTN call me 4.30M disconnect and use Voip call me will 3.40M will disconnect.

    what's mean about :
    15:31:48.703 CallConf::eek:nIncoming [CM103002] Call(217): Incoming call from 8006 (Ext.8006) to sip:097925439@60.241.248.251:5060
    15:31:36.125 StratLink::eek:nHangUp [CM104001] Call(216): Ext.8001 hung up call; cause: BYE; reason: SIP;description="User Hung Up"
    15:31:33.593 MediaServerReporting::RTPSender [MS004000] Call(216) Ext.8001: (ACTIVE): Can't send RTP stream to 0.0.0.0:39780 destination unreachable
    15:30:22.468 MediaServerReporting::RTPReceiver [MS005001] Call(176) Ln:10000@engin 9.95: payload #18 doesn't correspond initial SDP datalen=2
    15:30:22.421 MediaServerReporting::RTPReceiver [MS005001] Call(176) Ln:10000@engin 9.95: payload #18 doesn't correspond initial SDP datalen=2
    15:30:22.390 MediaServerReporting::RTPReceiver [MS005001] Call(176) Ln:10000@engin 9.95: payload #18 doesn't correspond initial SDP datalen=2



    Thank you very much!
     
  7. todd

    Joined:
    Jun 9, 2007
    Messages:
    35
    Likes Received:
    0
    I test lsat night.

    when I put a incoming call on hold, will receice the message:

    15:30:22.468 MediaServerReporting::RTPReceiver [MS005001] Call(176) Ln:10000@engin 9.95: payload #18 doesn't correspond initial SDP datalen=2

    maybe help for understand the log.

    but I really need help to fix the incoming call problem.
     
  8. todd

    Joined:
    Jun 9, 2007
    Messages:
    35
    Likes Received:
    0
    the new lgo

    07:58:24.203 StratLink::eek:nHangUp [CM104001] Call(9): Ext.8001 hung up call; cause: unknown
    07:58:24.046 MediaServerReporting::RTPSender [MS104000] Call(9) Ext.8001: (ACTIVE) RTP stream to 192.168.1.101:11058 restored.
    07:58:15.890 MediaServerReporting::RTPReceiver [MS005001] Call(9) Ext.8001: payload #126 doesn't correspond initial SDP datalen=4
    07:58:05.656 MediaServerReporting::RTPReceiver [MS005001] Call(9) Ext.8001: payload #126 doesn't correspond initial SDP datalen=4
    07:57:55.421 MediaServerReporting::RTPReceiver [MS005001] Call(9) Ext.8001: payload #126 doesn't correspond initial SDP datalen=4
    07:57:45.078 MediaServerReporting::RTPSender [MS004000] Call(9) Ext.8001: (ACTIVE): Can't send RTP stream to 0.0.0.0:11058 destination unreachable
    07:55:06.234 MediaServerReporting::RTPSender [MS104000] Call(9) Ext.8001: (ACTIVE) RTP stream to 192.168.1.101:11058 restored.
    07:54:56.234 MediaServerReporting::RTPSender [MS004000] Call(9) Ext.8001: (ACTIVE): Can't send RTP stream to 0.0.0.0:11058 destination unreachable
    07:54:28.765 MediaServerReporting::RTPSender [MS104000] Call(9) Ext.8001: (ACTIVE) RTP stream to 192.168.1.101:11058 restored.
    07:54:27.843 MediaServerReporting::RTPSender [MS004000] Call(9) Ext.8001: (ACTIVE): Can't send RTP stream to 0.0.0.0:11058 destination unreachable
    07:54:20.984 MediaServerReporting::RTPSender [MS104000] Call(9) Ext.8001: (ACTIVE) RTP stream to 192.168.1.101:11058 restored.
    07:54:18.812 MediaServerReporting::RTPReceiver [MS005001] Call(9) Ext.8001: payload #126 doesn't correspond initial SDP datalen=4
    07:54:17.984 StunClient::process [CM215001] STUN failed to resolve external IP using server 80.239.235.209
    07:54:08.468 MediaServerReporting::RTPSender [MS004000] Call(9) Ext.8001: (ACTIVE): Can't send RTP stream to 0.0.0.0:11058 destination unreachable
    07:50:21.828 CallLegImpl::eek:nConnected [CM103001] Call(9): Created audio channel for Ext.8001 (192.168.1.101:11058) with Media Server (192.168.1.2:7006)
    07:50:21.828 StratInOut::eek:nConnected [CM104005] Call(9): Setup completed for call from Ln:10003@engin 19.95 to Ext.8001
    07:50:10.656 CallConf::eek:nProvisional [CM103003] Call(9): Ext.8001 is ringing
    07:49:59.390 MediaServerReporting::DTMFhandler [MS211000] Call(9) Ln:10003@engin 19.95: DTMF (RTP) from 203.161.160.84:16990 arrived. in-band DTMF tone detection is turned off.
    07:49:46.734 CallLegImpl::eek:nConnected [CM103001] Call(9): Created audio channel for Ln:10003@engin 19.95 (203.161.160.84:16990) with Media Server (60.241.248.251:9006)
    07:49:46.640 CallConf::eek:nIncoming [CM103002] Call(9): Incoming call from 0280040111 (Ln:10003@engin 19.95) to sip:0281972588@voice.mibroadband.com.au



    When I put incoming call on hold:

    07:54:56.234 MediaServerReporting::RTPSender [MS004000] Call(9) Ext.8001: (ACTIVE): Can't send RTP stream to 0.0.0.0:11058 destination unreachable

    After I remove the on hold:

    07:55:06.234 MediaServerReporting::RTPSender [MS104000] Call(9) Ext.8001: (ACTIVE) RTP stream to 192.168.1.101:11058 restored.
     
  9. todd

    Joined:
    Jun 9, 2007
    Messages:
    35
    Likes Received:
    0
    Today, I try use my PSTN gateway to receive the incoming calls. All good
    so, all problem should in the Voip line configeration.
    any help? I really need it's working.
     
  10. Anonymous

    Anonymous Guest

    I think we spoke about this briefly (me running between workshops and meetings).

    I believe you use the SPA3102, and this does not apply to your GSM Terminal. If so send me your config here is how:

    For the Router Tab:
    >
    > 1. Select Admin Login
    >
    > 2. Select Advanced
    >
    > 3. Save as router.HTML file
    >
    >
    >
    > for the Voice Tab:
    >
    > 1. Select Admin Login
    >
    > 2. Select Advanced
    >
    > 3. Save as voice.HTML file

    Send both files to me and Ill write your config and send it back so you can upload it direct into your SPA. :) got a nifty new trick for that as outlined in the SPA3201-3CX document.

    Also make sure you have a ADSL filter (if you are on ADSL) between your SPA and the phone port.
     
  11. SY

    SY Well-Known Member
    3CX Staff

    Joined:
    Jan 26, 2007
    Messages:
    1,821
    Likes Received:
    1
    Your phone setups 0.0.0.0 address in SDP to put call on hold. It is deprecated behavior. Just ignore these messages if they appear during hold/retrive operations.

    These messages signal that remote party doesn't follow to SDP negotiations. #18 payload should not be delivered to MediaServer in any case. Media server ignores packets with incorrect content but put information about this situation to log. If I remember it is G.729 and we don't support it.
     
  12. todd

    Joined:
    Jun 9, 2007
    Messages:
    35
    Likes Received:
    0
    Thank you !!!

    The inband call disconnect every 4-5 min. I got a Log here.

    [CM010001] Line configuration does not allow identification of the source of this call. Check Advanced Options for Gateways and Providers and match a field to a correct value from the following: Contact IP: '203.161.160.81'; From: '0731390275'; To: '0280040111'; Rline: '3cxPbx'; Contact: 'C7ip1sv-yy-gcAqoeEr5cQI_L2gpGfJyeQiYOYsWbqdeIMLqakNKrkvsOnlDS3FvLDb2OBQtFzKwfM.'

    this is the reason. But I can not understand how to fix up. Which field is "identification of the source "?
     
  13. todd

    Joined:
    Jun 9, 2007
    Messages:
    35
    Likes Received:
    0
    Endpoint::findSource [CM010001] Line configuration does not allow identification of the source of this call. Check Advanced Options for Gateways and Providers and match a field to a correct value from the following: Contact IP: '203.161.160.79'; From: '0731390275'; To: '0280040111'; Rline: '3cxPbx'; Contact: 'A7rYmJJJLCwiYR-2YT7-khZimkXv788jc5VRDsSHVwY1emzBrQZmL0Nb0cUSpQkPxqa24puCks7aA

    any tips let me know what happend?
    Thanks!
     

Share This Page