cannot dial out thro 3cx

Discussion in '3CX Phone System - General' started by hairymonster2000, Aug 12, 2008.

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

    Joined:
    Jul 14, 2008
    Messages:
    10
    Likes Received:
    0
    Hi

    I'm having problems making calls via InPhonex thro 3cx. Everything works OK using a Grandstream HT386 connected directly to InPhonex but not thro 3cx. I can't even get the softphone to work thro 3cx, again it works fine directly with InPhonex.

    3cx has been installed on two different computers at different locations in accordance with the 3cx configuration guide and both have the same problem. I've tried varying the configuration slightly to see if I can resolve it but without success.

    3cx version 6.0.806.0

    Just noticed a discrepancy and not sure if this will have any bearing on what's happening. The 3cx software says it's the version above, but InPhonex recognises it as version 6.0.805.0
     
  2. alexmallia

    alexmallia New Member
    3CX Support

    Joined:
    Aug 4, 2008
    Messages:
    130
    Likes Received:
    0
    Does the VOIP line show as registered in the 3CX config->Line Status?

    Do you get the problem on incoming and outgoing calls?

    When you try calling using the InPhonex, does the line in the 3CX config->Line Status show as being used?

    What does the 3CX config->Server Status show at this time when making/receiving a call?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. hairymonster2000

    Joined:
    Jul 14, 2008
    Messages:
    10
    Likes Received:
    0
    Hi alexmallia, in answer to your questions:

    Yes

    Outgoing only

    No

    18:05:44.015 Call::Terminate [CM503008]: Call(11): Call is terminated
    18:05:43.984 Call::RouteFailed [CM503015]: Call(11): Attempt to reach [sip:100@192.168.1.10;user=phone] failed. Reason: Not Found
    18:05:43.984 CallCtrl::eek:nSelectRouteReq [CM503014]: Call(11): No known route to target: [sip:100@192.168.1.10;user=phone]
    18:05:43.968 CallCtrl::eek:nSelectRouteReq [CM503010]: Making route(s) to [sip:100@192.168.1.10;user=phone]
    18:05:43.968 Extension::printEndpointInfo [CM505001]: Ext.1000: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Grandstream HT386 1.0.3.57 FXS1] Transport: [sip:192.168.1.10:5060]
    18:05:43.921 CallCtrl::eek:nIncomingCall [CM503001]: Call(11): Incoming call from Ext.1000 to [sip:100@192.168.1.10;user=phone]

    Many thanks
     
  4. SWB

    SWB New Member

    Joined:
    Mar 26, 2008
    Messages:
    136
    Likes Received:
    0
    Is the extension you are trying to reach, 100, created and registered?

    If you are attempting to reach a number rather than an extension make sure you have an outbound rule created with a route defined for that type of call.
     
  5. hairymonster2000

    Joined:
    Jul 14, 2008
    Messages:
    10
    Likes Received:
    0
    Hi SWB, sorry, posted wrong extract.

    18:05:36.640 Call::Terminate [CM503008]: Call(10): Call is terminated
    18:05:36.593 Call::RouteFailed [CM503015]: Call(10): Attempt to reach [sip:966731525@192.168.1.10;user=phone] failed. Reason: Not Found
    18:05:36.593 CallCtrl::eek:nSelectRouteReq [CM503014]: Call(10): No known route to target: [sip:966731525@192.168.1.10;user=phone]
    18:05:36.578 CallCtrl::eek:nSelectRouteReq [CM503010]: Making route(s) to [sip:966731525@192.168.1.10;user=phone]
    18:05:36.578 Extension::printEndpointInfo [CM505001]: Ext.1000: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Grandstream HT386 1.0.3.57 FXS1] Transport: [sip:192.168.1.10:5060]
    18:05:36.515 CallCtrl::eek:nIncomingCall [CM503001]: Call(10): Incoming call from Ext.1000 to [sip:966731525@192.168.1.10;user=phone]
     
  6. SWB

    SWB New Member

    Joined:
    Mar 26, 2008
    Messages:
    136
    Likes Received:
    0
    No problem. Have you created an outbound rule for outgoing calls? If not you'll need to create one. Below is an example rule we created for local calls, and how we configured it.

    1) Click Add to add a new rule.
    2) Gave the new rule a Rule Name under General.
    3) Under Apply this rule to these calls we have 9 in the Calls to Numbers starting with (Prefix) text box. Office personnel here have been use to dialing a 9 before the number to make an outgoing call.
    4) Finally under Make Outbound Calls on select your provider in the drop down menu for Route 1. We Strip Digits, 1, because we have to drop the 9 prefix. We then also Prepend 1+our local area code (Example: 1215).

    So the way our rule works is person dials 91112222. The rule is activated because the call begins with 9. Then the rule strips the 9 and prepends the number with 1215. So the outgoing number is 12151112222, and the rule also defines which service/provider (i.e. route) the outgoing call will go through.

    Hope that all makes sense.
     
  7. hairymonster2000

    Joined:
    Jul 14, 2008
    Messages:
    10
    Likes Received:
    0
    I have added an outbound rule that prepends the code to the dialed number and this is the result. I hadn't added the rule as I thought I'd read somewhere that you could simply dial the local number thro 3cx. Seems I was wrong there.

    22:12:34.468 Call::Terminate [CM503008]: Call(2): Call is terminated
    22:12:34.281 Call::RouteFailed [CM503015]: Call(2): Attempt to reach [sip:966746584@192.168.1.10;user=phone] failed. Reason: Server Failure
    22:12:34.281 CallLeg::eek:nFailure [CM503003]: Call(2): Call to sip:01134966746584@sip.inphonex.com:5060 has failed; Cause: 503 Service Unavailable; from IP:208.239.76.163:5060
    22:12:27.531 CallCtrl::eek:nSelectRouteReq [CM503004]: Call(2): Calling: VoIPline:01134966746584@(Ln.10000@its)@[Dev:sip:6501180@sip.inphonex.com:5060]
    22:12:27.515 CallCtrl::eek:nSelectRouteReq [CM503010]: Making route(s) to [sip:966746584@192.168.1.10;user=phone]
    22:12:27.500 Extension::printEndpointInfo [CM505001]: Ext.1000: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Grandstream HT386 1.0.3.57 FXS1] Transport: [sip:192.168.1.10:5060]
    22:12:27.437 CallCtrl::eek:nIncomingCall [CM503001]: Call(2): Incoming call from Ext.1000 to [sip:966746584@192.168.1.10;user=phone]
     
  8. alexmallia

    alexmallia New Member
    3CX Support

    Joined:
    Aug 4, 2008
    Messages:
    130
    Likes Received:
    0
    This issue needs further troubleshooting and you would need to open a support ticket for it. To get technical support on this one, you can contact our technical support (This requires commercial edition with support package). If you have a commercial edition, but no support package, you can purchase one here:

    https://erp.3cx.com/orderform/support.aspx

    regards
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Thread Status:
Not open for further replies.