Dial Out from Voicemail Error

Discussion in '3CX Phone System - General' started by mevrick, Oct 8, 2012.

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

    Joined:
    Dec 2, 2011
    Messages:
    4
    Likes Received:
    0
    We have problem when try to make an external call from voicemail menu, but we have no problem when directy make a external call from the phone. Please check the log below. We have no problem when using 3CX 10.

    08-10-2012 08:23:36.019 Leg L:2.2[Line:10002>>7364378] is terminated: Cause: 487 Request Terminated/INVITE from 212.102.90.23:5060
    08-10-2012 08:23:35.929 [CM503008]: Call(C:2): Call is terminated
    08-10-2012 08:23:35.928 Leg L:2.1[Extn] is terminated: Cause: CANCEL from 24.119.46.12:5060
    08-10-2012 08:23:32.468 [CM505003]: Provider:[VOIP1] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] PBX contact: [sip: 111.212.88.99:5060]
    08-10-2012 08:23:29.726 [CM503025]: Call(C:2): Calling T:Line:10002>>7364378@[Dev:sip:212.102.190.23:5060] for L:2.1[Extn]
    08-10-2012 08:23:29.676 [CM503001]: Call(C:2): Incoming call from Extn:819 to "97364378" <sip:97364378@ 111.212.88.99:5060>



    08-10-2012 08:23:04.495 Leg L:1.2[VMail] is terminated: Cause: BYE from PBX
    08-10-2012 08:23:04.495 [CM503008]: Call(C:1): Call is terminated
    08-10-2012 08:23:04.493 Leg L:1.1[Extn] is terminated: Cause: BYE from 24.119.46.12:5060
    08-10-2012 08:22:58.975 L:1.1[Extn] failed to reach Line:10002>> 92601818, reason Server Failure
    08-10-2012 08:22:58.975 Leg L:1.4[Line:10002>> 92601818] is terminated: Cause: 500 Server Internal Error/INVITE from 212.102.90.23:5060
    08-10-2012 08:22:58.975 Call to T:Line:10002>> 92601818@[Dev:sip:212.102.190.23:5060] from L:1.1[Extn] failed, cause: Cause: 500 Server Internal Error/INVITE from 212.102.90.23:5060
    08-10-2012 08:22:58.974 [CM503003]: Call(C:1): Call to <sip: 92601818@212.102.190.23:5060> has failed; Cause: 500 Server Internal Error/INVITE from 212.102.90.23:5060

    08-10-2012 08:22:58.904 [CM503025]: Call(C:1): Calling T:Line:10002>> 92601818@[Dev:sip:212.102.190.23:5060] for L:1.1[Extn]
    08-10-2012 08:22:58.846 [CM503027]: Call(C:1): From: Extn:819 ("819" <sip:819@ 111.212.88.99:5060>) to T:Line:10002>> 92601818@[Dev:sip:212.102.190.23:5060]
    08-10-2012 08:22:58.846 [CM503004]: Call(C:1): Route 1: from L:1.1[Extn] to T:Line:10002>> 92601818@[Dev:sip:212.102.190.23:5060]
    08-10-2012 08:22:58.846 Line limit check: Current # of calls for line Lc:10002(@VOIP1[<sip:mad:212.102.190.23:5060>]) is 0; limit is 20
    08-10-2012 08:22:58.846 Call(C:1): Call from Extn:819 to 9 92601818 matches outbound rule 'VOIP1 - 9'
    08-10-2012 08:22:39.599 [CM504004]: Registration succeeded for: Lc:10000(@CallCentric[<sip:18652969232@callcentric.com:5060>])
    08-10-2012 08:22:38.607 Currently active calls - 1: [1]
    08-10-2012 08:22:35.735 L:1.1[Extn] failed to reach Line:10002>>7364378, reason Server Failure
    08-10-2012 08:22:35.734 Leg L:1.3[Line:10002>>7364378] is terminated: Cause: 500 Server Internal Error/INVITE from 212.102.90.23:5060
    08-10-2012 08:22:35.734 Call to T:Line:10002>>7364378@[Dev:sip:212.102.190.23:5060] from L:1.1[Extn] failed, cause: Cause: 500 Server Internal Error/INVITE from 212.102.90.23:5060
    08-10-2012 08:22:35.734 [CM503003]: Call(C:1): Call to <sip:7364378@212.102.190.23:5060> has failed; Cause: 500 Server Internal Error/INVITE from 212.102.90.23:5060


    08-10-2012 08:22:35.662 [CM503025]: Call(C:1): Calling T:Line:10002>>7364378@[Dev:sip:212.102.190.23:5060] for L:1.1[Extn]
    08-10-2012 08:22:35.608 [CM503027]: Call(C:1): From: Extn:819 ("819" <sip:819@ 111.212.88.99:5060>) to T:Line:10002>>7364378@[Dev:sip:212.102.190.23:5060]
    08-10-2012 08:22:35.608 [CM503004]: Call(C:1): Route 1: from L:1.1[Extn] to T:Line:10002>>7364378@[Dev:sip:212.102.190.23:5060]
    08-10-2012 08:22:35.608 Line limit check: Current # of calls for line Lc:10002(@VOIP1[<sip:mad:212.102.190.23:5060>]) is 0; limit is 20
    08-10-2012 08:22:35.608 Call(C:1): Call from Extn:819 to 97364378 matches outbound rule 'VOIP1 - 9'
    08-10-2012 08:22:17.826 Registration attempt for Lc:10000(@CallCentric[<sip:18652969232@callcentric.com:5060>]) is scheduled in 20 sec.
    08-10-2012 08:22:14.539 [CM503007]: Call(C:1): VMail:999 has joined, contact <sip:999@127.0.0.1:40600>
    08-10-2012 08:22:14.536 [CM503007]: Call(C:1): Extn:819 has joined, contact <sip:819@24.119.46.12:5060>
    08-10-2012 08:22:14.534 L:1.2[VMail] has joined to L:1.1[Extn]
    08-10-2012 08:22:14.382 [CM503025]: Call(C:1): Calling T:VMail:999@[Dev:sip:999@127.0.0.1:40600;rinstance=e1f08a9bb0c2af11] for L:1.1[Extn]
    08-10-2012 08:22:14.344 [CM503027]: Call(C:1): From: Extn:819 ("819" <sip:819@ 111.212.88.99:5060>) to T:VMail:999@[Dev:sip:999@127.0.0.1:40600;rinstance=e1f08a9bb0c2af11]
    08-10-2012 08:22:14.344 [CM503004]: Call(C:1): Route 1: from L:1.1[Extn] to T:VMail:999@[Dev:sip:999@127.0.0.1:40600;rinstance=e1f08a9bb0c2af11]
    08-10-2012 08:22:14.341 [CM503001]: Call(C:1): Incoming call from Extn:819 to "999" <sip:999@ 111.212.88.99:5060>
     
  2. craigreilly

    craigreilly Well-Known Member

    Joined:
    Feb 1, 2012
    Messages:
    2,977
    Likes Received:
    183
    Do I see 3 different subnets
    212.x.x.x
    24.x.x.x
    111.x.x.x

    I think I see the extensions on 111 and 24 and 212 on Callcentric.
    Pleas explain which network is which and layout the network a bit for us?
    Quick glance looks like a 9 is being sent to Callcentric - are you using a dial 9 rule for external calls?

    You do have this enabled in the settings to make external calls from vm system?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,368
    Likes Received:
    229
    Could there be a datafill error somewhere? I see IP 212.102.90.23:5060 and 212.102.190.23:5060.

    Note the 90 and 190.
     
Thread Status:
Not open for further replies.