Dismiss Notice
We would like to remind you that we’re updating our login process for all 3CX forums whereby you will be able to login with the same credentials you use for the Partner or Customer Portal. Click here to read more.

Static on phone calls

Discussion in '3CX Phone System - General' started by Ryguy, Jun 3, 2008.

Thread Status:
Not open for further replies.
  1. Ryguy

    Joined:
    Jun 3, 2008
    Messages:
    4
    Likes Received:
    0
    Hi,
    I've been playing around with the configuration of 3cx version 6 for the past week and just configured an AudioCodes MP-114 based on the directions found on the 3cx wiki. 3 of the lines are recognized in line status but the 4th says not registered, oh well, not important right now. I wanted to test the system by plugging a phone line into line one on the mp-114 which is seen by 3cx as line no 10800. I have 3cx configured to send any incoming calls on this line to extension 201. So, I tried calling the external phone number to see if it would work....well it kinda did. When I called from my cell phone I got a bunch of static, I hung up the call and about 5-10 seconds later extension 201 started ringing, on the screen it said call from 10800 (shouldn't it pass the phone number I called from, called id?) and I picked it up but I heard the same static I did when I was on my cell phone.

    I am using a Linksys 922 as extension 201 and the gateway is an AudioCodes MP-114, 3cx is running version 6.0.381.0.

    Here are the logs that appeared during that time:
    19:32:09.372 Call::Terminate [CM503008]: Call(75): Call is terminated
    19:32:09.357 LineCfg::getInboundTarget [CM503011]: Inbound out-of-office hours' rule for LN:10800 forwards to DN:201
    19:32:09.341 LineCfg::getInboundTarget [CM503011]: Inbound out-of-office hours' rule for LN:10800 forwards to DN:201
    19:32:09.341 Call::Terminate [CM503008]: Call(75): Call is terminated
    19:32:09.341 LineCfg::getInboundTarget [CM503011]: Inbound out-of-office hours' rule for LN:10800 forwards to DN:201
    19:32:06.435 CallCtrl::eek:nLegConnected [CM503007]: Call(75): Device joined: sip:201@192.168.1.216:5060
    19:32:06.435 LineCfg::getInboundTarget [CM503011]: Inbound out-of-office hours' rule for LN:10800 forwards to DN:201
    19:32:06.419 CallCtrl::eek:nLegConnected [CM503007]: Call(75): Device joined: sip:10800@192.168.1.2:5060
    19:31:51.435 CallCtrl::eek:nSelectRouteReq [CM503004]: Call(75): Calling: Ext:Ext.201@[Dev:sip:201@192.168.1.216:5060]
    19:31:51.435 Line::printEndpointInfo [CM505002]: Gateway:[Gateway1] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Audiocodes-Sip-Gateway-MP-114 FXO/v.5.00A.024] Transport: [sip:192.168.1.52:5060]
    19:31:51.435 LineCfg::getInboundTarget [CM503011]: Inbound out-of-office hours' rule for LN:10800 forwards to DN:201
    19:31:51.404 CallCtrl::eek:nIncomingCall [CM503001]: Call(75): Incoming call from 10800@(Ln.10800@Gateway1) to [sip:201@3cx.chiquesumc.org:5060]
    19:31:51.404 LineCfg::getInboundTarget [CM503011]: Inbound out-of-office hours' rule for LN:10800 forwards to DN:201

    If anyone could provide me with some help I would greatly appreciate it! Thanks Ryan
     
  2. Ryguy

    Joined:
    Jun 3, 2008
    Messages:
    4
    Likes Received:
    0
    OK, well I figured out the static issue, after I switched from hotline to enabled in the mp-114 settings as stated from another post, that fixed some problems I was having there. So now I can recieve incoming calls but the caller ID on the Linksys 922 still shows up as call from 10800 (which is line one on the mp-114). How can I fix this so the mp-114 is passing caller ID information to 3cx and then to the phone?

    Another problem, is I can't make outgoing calls. I have one simple outgoing rule set up that states if a string has a 9 in front to strip the 9 before passing it to the mp-114. But when I dial from the Linksys 922 it never makes it and I get a fast busy signal.

    Here's the log during the incoming call where I don't get caller ID info:
    18:54:26.826 Call::Terminate [CM503008]: Call(236): Call is terminated
    18:54:26.826 LineCfg::getInboundTarget [CM503011]: Inbound out-of-office hours' rule for LN:10800 forwards to DN:201
    18:54:26.810 LineCfg::getInboundTarget [CM503011]: Inbound out-of-office hours' rule for LN:10800 forwards to DN:201
    18:54:26.810 Call::Terminate [CM503008]: Call(236): Call is terminated
    18:54:26.810 LineCfg::getInboundTarget [CM503011]: Inbound out-of-office hours' rule for LN:10800 forwards to DN:201
    18:54:17.295 CallCtrl::eek:nLegConnected [CM503007]: Call(236): Device joined: sip:201@192.168.1.216:5060
    18:54:17.295 LineCfg::getInboundTarget [CM503011]: Inbound out-of-office hours' rule for LN:10800 forwards to DN:201
    18:54:17.279 CallCtrl::eek:nLegConnected [CM503007]: Call(236): Device joined: sip:10800@192.168.1.2:5060
    18:54:15.951 CallCtrl::eek:nSelectRouteReq [CM503004]: Call(236): Calling: Ext:Ext.201@[Dev:sip:201@192.168.1.216:5060]
    18:54:15.951 Line::printEndpointInfo [CM505002]: Gateway:[Gateway1] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Audiocodes-Sip-Gateway-MP-114 FXO/v.5.00A.024] Transport: [sip:192.168.1.52:5060]
    18:54:15.951 LineCfg::getInboundTarget [CM503011]: Inbound out-of-office hours' rule for LN:10800 forwards to DN:201
    18:54:15.920 CallCtrl::eek:nIncomingCall [CM503001]: Call(236): Incoming call from 10800@(Ln.10800@Gateway1) to [sip:201@3cx.chiquesumc.org:5060]
    18:54:15.920 LineCfg::getInboundTarget [CM503011]: Inbound out-of-office hours' rule for LN:10800 forwards to DN:201


    Here's the log during the attempted outgoing call:
    18:55:00.076 Call::Terminate [CM503008]: Call(240): Call is terminated
    18:55:00.045 Call::RouteFailed [CM503014]: Call(240): Attempt to reach [sip:93805058@192.168.1.52] failed. Reason: Not Found
    18:55:00.045 CallLeg::eek:nFailure [CM503003]: Call(240): Call to sip:3805058@192.168.1.2:5060 has failed; Cause: 404 Not Found; from IP:192.168.1.2:5060
    18:54:59.920 CallLeg::eek:nFailure [CM503003]: Call(240): Call to sip:3805058@192.168.1.2:5060 has failed; Cause: 404 Not Found; from IP:192.168.1.2:5060
    18:54:59.795 CallLeg::eek:nFailure [CM503003]: Call(240): Call to sip:3805058@192.168.1.2:5060 has failed; Cause: 404 Not Found; from IP:192.168.1.2:5060
    18:54:59.654 CallLeg::eek:nFailure [CM503003]: Call(240): Call to sip:3805058@192.168.1.2:5060 has failed; Cause: 404 Not Found; from IP:192.168.1.2:5060
    18:54:59.529 CallCtrl::eek:nSelectRouteReq [CM503004]: Call(240): Calling: PSTNline:3805058@(Ln.10800@Gateway1)@[Dev:sip:10800@192.168.1.2:5060, Dev:sip:10801@192.168.1.2:5060, Dev:sip:10802@192.168.1.2:5060, Dev:sip:10803@192.168.1.2:5060]
    18:54:59.498 CallCtrl::eek:nIncomingCall [CM503001]: Call(240): Incoming call from Ext.201 to [sip:93805058@192.168.1.52]

    Thanks for any help you're able to provide!
    Ryan
     
  3. Ryguy

    Joined:
    Jun 3, 2008
    Messages:
    4
    Likes Received:
    0
    Still having problems here, anyone know what I might be missing in order to make outgoing calls and get caller id?
     
  4. Andy Schmidt

    Andy Schmidt New Member

    Joined:
    Apr 3, 2008
    Messages:
    118
    Likes Received:
    0
    I had to set "RingsBeforeCallerID" to 2 to recognize the callerID from Cell Phones and certain other sources.

    Not a problem of the AudioCodes, it's a matter of how long it takes the providers to transmit CallerID info.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. nitup

    Joined:
    May 16, 2008
    Messages:
    16
    Likes Received:
    0
    For outgoing calls check dial plan of your gateway. It seems it thinks that 7 digits is not enough to be completed number.
     
  6. Ryguy

    Joined:
    Jun 3, 2008
    Messages:
    4
    Likes Received:
    0
    Thanks for your help, it turned out the caller ID issue was something on the phone company end, something they had missed, so thats working now. The outgoing calls had me stumpted for awhile and then I just started tweaking with things in the gateway (MP-114) and under one of the endpoint settings screens where it lists the 4 lines, the configuration page from 3cx said to leave the hunt group column blank and put a number 1 in the profile ID column which I did. Turns out that after I put a number 1 in the hunt group column also now all the sudden I could make outgoing calls. I figured this out after reading through pages and pages of log files from the mp-114 and found something about endpoint settings which lead me to this.

    Hopefully this will help someone else who might have the same problem.
    Ryan
     
Thread Status:
Not open for further replies.