Cannot make outgoing calls via DIDLogic

Discussion in '3CX Phone System - General' started by psings, May 6, 2014.

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

    Joined:
    May 6, 2014
    Messages:
    2
    Likes Received:
    0
    Hi,

    I've been having issues and racking my brains trying to resolve this.

    I use DIDLogic.com as a landline telephone number provider. I can log into their website and get all calls to the number forwarded to my 3CX installation successfully but I am having many issues trying to get outgoing calls to work.

    I've played around with all kinds of settings in 3CX and the DIDLogic control panel. The last configuration I set, loops outgoing calls back to me!

    I have the landline number set up to forward to a 3CX Generic VOIP Provider (as there are no DIDLogic templates available), so it's set to forward to "4401202xxxxxx@93.104.xxx.xxx" which works fine for incoming calls.

    Does anyone have previous experience with this provider on 3CX, or does anyone have any hints as to what's required?

    Below is my log...

    Many thanks,
    Paul



    ------
    06-May-2014 14:33:19.359 Leg L:59.3[VMail] is terminated: Cause: BYE from PBX
    06-May-2014 14:33:19.358 [CM503008]: Call(C:59): Call is terminated
    06-May-2014 14:33:19.354 Leg L:59.1[Line:10000<<441202xxxxxx] is terminated: Cause: BYE from 176.74.184.153:5060
    06-May-2014 14:33:19.061 Leg L:58.2[Line:10000>>447937xxxxxx] is terminated: Cause: 487 Request Terminated/INVITE from 176.74.184.153:5060
    06-May-2014 14:33:18.928 [CM503008]: Call(C:58): Call is terminated
    06-May-2014 14:33:18.924 Leg L:58.1[Extn] is terminated: Cause: CANCEL from 195.137.xxx.xxx:49523
    06-May-2014 14:33:18.654 [CM503007]: Call(C:59): VMail:200 has joined, contact <sip:200@127.0.0.1:40600>
    06-May-2014 14:33:18.652 [CM503007]: Call(C:59): Line:10000<<441202xxxxxx has joined, contact <sip:00000@sip.uk.didlogic.net:5060>
    06-May-2014 14:33:18.646 L:59.3[VMail] has joined to L:59.1[Line:10000<<441202xxxxxx]
    06-May-2014 14:33:18.453 [CM503025]: Call(C:59): Calling T:VMail:200@[Dev:sip:200@127.0.0.1:40600;rinstance=db7e437fa2f9696d] for L:59.1[Line:10000<<441202xxxxxx]
    06-May-2014 14:33:18.442 Leg L:59.2[Extn] is terminated: Cause: 486 Busy Here/INVITE from 195.137.xxx.xxx:49523
    06-May-2014 14:33:18.439 [CM503005]: Call(C:59): Forwarding: T:VMail:200@[Dev:sip:200@127.0.0.1:40600;rinstance=db7e437fa2f9696d]
    06-May-2014 14:33:18.439 L:59.1[Line:10000<<441202xxxxxx] forwards call from Extn:101 to VMail:200 based on rule Fwd[Available/Busy]
    06-May-2014 14:33:18.438 L:59.1[Line:10000<<441202xxxxxx] failed to reach Extn:101, reason Busy
    06-May-2014 14:33:18.438 Call to T:Extn:101@[Dev:sip:101@195.137.xxx.xxx:49523;ob] from L:59.1[Line:10000<<441202xxxxxx] failed, cause: Cause: 486 Busy Here/INVITE from 195.137.xxx.xxx:49523
    06-May-2014 14:33:18.438 [CM503003]: Call(C:59): Call to <sip:101@93.104.xxx.xxx:5060> has failed; Cause: 486 Busy Here/INVITE from 195.137.xxx.xxx:49523
    06-May-2014 14:33:16.010 [CM505003]: Provider:[DIDLogic] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [DIDLogic SBC] PBX contact: [sip:99206@93.104.xxx.xxx:5060]
    06-May-2014 14:33:15.442 [CM503025]: Call(C:59): Calling T:Extn:101@[Dev:sip:101@195.137.xxx.xxx:49523;ob] for L:59.1[Line:10000<<441202xxxxxx]
    06-May-2014 14:33:15.401 [CM503005]: Call(C:59): Forwarding: T:Extn:101@[Dev:sip:101@195.137.xxx.xxx:49523;ob]
    06-May-2014 14:33:15.401 L:59.1[Line:10000<<441202xxxxxx] forwards call from Extn:100 to Extn:101 based on rule Fwd[Available/NotReg]
    06-May-2014 14:33:15.401 L:59.1[Line:10000<<441202xxxxxx] failed to reach Extn:100, reason Not Registered
    06-May-2014 14:33:15.398 [CM503017]: Call(C:59): Target is not registered: Extn:100
    06-May-2014 14:33:15.397 [CM505003]: Provider:[DIDLogic] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [DIDLogic SBC] PBX contact: [sip:00000@93.104.xxx.xxx:5060]
    06-May-2014 14:33:15.394 [CM503001]: Call(C:59): Incoming call from Line:10000<<441202xxxxxx to <sip:100@93.104.xxx.xxx:5060>
    06-May-2014 14:33:15.393 Line limit check: Current # of calls for line Lc:10000(@DIDLogic[<sip:00000@sip.uk.didlogic.net:5060>]) is 2; limit is 2
    06-May-2014 14:33:15.384 [CM503012]: Inbound any hours rule (Huckleberry) for 10000 forwards to DN:100
    06-May-2014 14:33:13.617 [CM503025]: Call(C:58): Calling T:Line:10000>>447937xxxxxx@[Dev:sip:00000@sip.uk.didlogic.net:5060] for L:58.1[Extn]
    06-May-2014 14:33:13.580 [CM503027]: Call(C:58): From: Extn:101 ("Paul" <sip:101@93.104.xxx.xxx:5060>) to T:Line:10000>>447937xxxxxx@[Dev:sip:00000@sip.uk.didlogic.net:5060]
    06-May-2014 14:33:13.580 [CM503004]: Call(C:58): Route 1: from L:58.1[Extn] to T:Line:10000>>447937xxxxxx@[Dev:sip:00000@sip.uk.didlogic.net:5060]
    06-May-2014 14:33:13.580 Line limit check: Current # of calls for line Lc:10000(@DIDLogic[<sip:00000@sip.uk.didlogic.net:5060>]) is 0; limit is 2
    06-May-2014 14:33:13.580 Call(C:58): Call from Extn:101 to 07937xxxxxx matches outbound rule 'Rule for Out'
    06-May-2014 14:33:13.576 [CM503001]: Call(C:58): Incoming call from Extn:101 to <sip:07937xxxxxx@93.104.xxx.xxx:5060>
     
  2. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,586
    Likes Received:
    252
    I'm a bit confused about the problem, and your set-up. You mention a DID number provider, yet are having a problem with outgoing calls.

    Can you provide some scenarios in which calls are failing, and what routes they are supposed to take. I see extension not registered, and call forwarding involved.
     
  3. psings

    Joined:
    May 6, 2014
    Messages:
    2
    Likes Received:
    0
    Hi, thanks for your reply.

    After some much needed sleep, I've come back and changed the settings at my SIP provider and changed everything around.

    I can now call external lines successfully!
     
Thread Status:
Not open for further replies.