Problems with Outbound Calls with AudioCodes MP-114

Discussion in '3CX Phone System - General' started by LLangston, Oct 4, 2007.

  1. LLangston

    Joined:
    Aug 27, 2007
    Messages:
    57
    Likes Received:
    0
    Ok, We have changed our equipment from Grandstream because of poor audio quality. We are now using the AudioCodes MP-114 FXO gateway and the Polycom Soundpoint 501 phones. Straight out of the box using the 3CX configuration incoming calls are great, beautiful audio quality; however, I can't get the outbound calls to work. We have two pstn lines both of which have been setup and we will have a total of 4 extensions (I have only set up one so far). I am enclosing a copy of the server status logs. I would greatly appreciate any help in figuring out what I have not configured correctly.

    Message
    13:32:38.308 CallConf::Rejected [CM103005] Call(32) is rejected: Not Found
    13:32:38.308 StratInOut::eek:nCancel [CM104008] Call(32): Call from Ext.201 to 4644446 terminated; cause: 404 Not Found; from IP:10.10.10.25
    13:32:37.847 CallConf::eek:nIncoming [CM103002] Call(32): Incoming call from 201 (Ext.201) to sip:94644446@10.10.10.17
    13:03:07.988 StratInOut::eek:nHangUp [CM104007] Call(31): Call from Ln:10001@Connection Technologies to 801 has been terminated by Ln:10001@Connection Technologies; cause: BYE; reason: Q.850 ;cause=3
    13:02:37.099 CallLegImpl::eek:nConnected [CM103001] Call(31): Created audio channel for Ln:10001@Connection Technologies (10.10.10.25:6010) with Media Server (10.10.10.17:7142)
    13:02:22.806 CallConf::eek:nProvisional [CM103003] Call(31): Ext.201 is ringing
    13:02:22.486 CallConf::eek:nIncoming [CM103002] Call(31): Incoming call from 10001 (Ln:10001@Connection Technologies) to sip:10001@10.10.10.17
    13:02:01.973 CallConf::Rejected [CM103005] Call(30) is rejected: Not Found
    13:02:01.973 StratInOut::eek:nCancel [CM104008] Call(30): Call from Ext.201 to 2138765 terminated; cause: 404 Not Found; from IP:10.10.10.25
    13:02:01.642 CallConf::eek:nIncoming [CM103002] Call(30): Incoming call from 201 (Ext.201) to sip:92138765@10.10.10.17
    13:01:49.824 CallConf::Rejected [CM103005] Call(29) is rejected: Not Found
    13:01:49.824 StratInOut::eek:nCancel [CM104008] Call(29): Call from Ext.201 to 4644446 terminated; cause: 404 Not Found; from IP:10.10.10.25
    13:01:49.463 CallConf::eek:nIncoming [CM103002] Call(29): Incoming call from 201 (Ext.201) to sip:94644446@10.10.10.17
    13:01:16.871 CallConf::Rejected [CM103005] Call(28) is rejected: Not Found
    13:01:16.871 StratInOut::eek:nCancel [CM104008] Call(28): Call from Ext.201 to 4644446 terminated; cause: 404 Not Found; from IP:10.10.10.25
    13:01:16.260 CallConf::eek:nIncoming [CM103002] Call(28): Incoming call from 201 (Ext.201) to sip:94644446@10.10.10.17
    12:53:58.936 CallConf::Rejected [CM103005] Call(27) is rejected: Not Found
    12:53:58.936 StratInOut::eek:nCancel [CM104008] Call(27): Call from Ext.201 to 4644446 terminated; cause: 404 Not Found; from IP:10.10.10.25
    12:53:58.606 CallConf::eek:nIncoming [CM103002] Call(27): Incoming call from 201 (Ext.201) to sip:94644446@10.10.10.17
    12:52:32.519 CallConf::Rejected [CM103005] Call(26) is rejected: Not Found
    12:52:32.519 StratInOut::eek:nCancel [CM104008] Call(26): Call from Ext.201 to 4644446 terminated; cause: 404 Not Found; from IP:10.10.10.25
    12:52:32.178 CallConf::eek:nIncoming [CM103002] Call(26): Incoming call from 201 (Ext.201) to sip:94644446@10.10.10.17
    10:39:25.019 CallConf::Rejected [CM103005] Call(25) is rejected: Not Found
    10:39:25.019 StratInOut::eek:nCancel [CM104008] Call(25): Call from Ext.201 to 4705824 terminated; cause: 404 Not Found; from IP:10.10.10.25
    10:39:24.628 CallConf::eek:nIncoming [CM103002] Call(25): Incoming call from 201 (Ext.201) to sip:94705824@10.10.10.17
    10:22:34.164 CallConf::Rejected [CM103005] Call(24) is rejected: Not Found
    10:22:34.164 StratInOut::eek:nCancel [CM104008] Call(24): Call from Ext.201 to 4705824 terminated; cause: 404 Not Found; from IP:10.10.10.25
    10:22:33.824 CallConf::eek:nIncoming [CM103002] Call(24): Incoming call from 201 (Ext.201) to sip:94705824@10.10.10.17
    10:21:56.394 StratLink::eek:nHangUp [CM104001] Call(23): Ext.201 hung up call; cause: BYE; from IP:10.10.10.18
    10:21:09.870 CallLegImpl::eek:nConnected [CM103001] Call(23): Created audio channel for Ext.201 (10.10.10.18:2236) with third party (10.10.10.25:6010)
    10:21:09.860 StratInOut::eek:nConnected [CM104005] Call(23): Setup completed for call from Ln:10001@Connection Technologies to Ext.201
    10:21:09.860 CallLegImpl::eek:nConnected [CM103001] Call(23): Created audio channel for Ln:10001@Connection Technologies (10.10.10.25:6010) with third party (10.10.10.18:2236)
    10:21:06.936 CallConf::eek:nProvisional [CM103003] Call(23): Ext.201 is ringing
    10:21:06.585 CallConf::eek:nIncoming [CM103002] Call(23): Incoming call from 10001 (Ln:10001@Connection Technologies) to sip:10001@10.10.10.17
    10:19:19.075 ServRegs::eek:nAdd [CM113002] Registered: Ln:10000@Connection Technologies
    10:19:18.954 ServRegs::eek:nAdd [CM113002] Registered: Ln:10001@Connection Technologies

    Please help, I am starting to go bald :(
     
  2. Nick Galea

    Nick Galea Site Admin

    Joined:
    Jun 6, 2006
    Messages:
    1,718
    Likes Received:
    39
    Just to be sure:

    1.Do you have a 4 port FXO gateway (not a 2 port FXO & 2 port FXS)
    2.Have you assigned an abound rule and are people dialing the prefix?

    We are updating the configuration guide next week, since it seems that it needs to be updated for the latest MP 114 versions....
     
  3. LLangston

    Joined:
    Aug 27, 2007
    Messages:
    57
    Likes Received:
    0
    I am sorry that I have not replied back before now, but have been out of the office. I reset the AudioCodes back to factory defaults and went back through the set-up configuration from 3CX again and it is working great now except for we can not make long distance calls. I am sure that that is something I need to configure either in the phone or in the gateway and not a problem with 3CX. I have just gotten back into the office and have not as yet had a chance to explore what that issue is. Thank you for your reply though.
     

Share This Page