Problems with Nikotel

Discussion in '3CX Phone System - General' started by michael.tanner, Feb 14, 2007.

  1. michael.tanner

    Joined:
    Feb 14, 2007
    Messages:
    1
    Likes Received:
    0
    Hi,

    I try to get my Nikotel line running, I have checked FAQ and Manual but still have a "Target is not resolved" problem. (phone 120 not registered, VM enabled and configured as destination when not registered)
    I have set the "External Number" field to 16193300999, is this wrong for Nikotel?

    Public IP during test was 81.62.240.191 (strange addresses in trace...)

    21:22:12.784 ExtLine::Register: Send registration for "16193300999"<sip:xy@calamar0.nikotel.com:5060>
    21:21:59.206 CallConf::eek:nIncoming: Can not resolve target for call from <sip:66.52.2.22>;tag=2E07C8E4-2434 to <sip:16193300999@63.214.186.6>
    21:21:59.206 CallConf::Rejected: Call (C:3) is rejected: Target is not resolved
    21:21:59.190 CallConf::eek:nIncoming: Incoming call from Ln:10000@Nikotel to sip:16193300999@63.214.186.6
    21:21:43.815 ClientRegs::eek:nSuccess: Registration of sip:xy@calamar0.nikotel.com:5060 is successful
    21:21:42.815 ExtLine::Register: Send registration for "16193300999"<sip:xy@calamar0.nikotel.com:5060>

    --------------------------------------------------
    SIP/2.0 100 Trying
    Via: SIP/2.0/UDP 63.214.186.6;branch=z9hG4bK5f6ac9dedd5c410aa6cd42ab390c040c
    Via: SIP/2.0/UDP 66.52.2.22
    To: <sip:16193300999@63.214.186.6>;tag=002d7456
    From: <sip:66.52.2.22>;tag=2E07C8E4-2434
    Call-ID: DAEBF253-BB9F11DB-A876AA54-A00904BE@66.52.2.22
    CSeq: 102 INVITE
    Content-Length: 0


    21:21:59.190|.\CallConf.cpp(71)|Log2|CallControl|CallConf::eek:nIncoming: Incoming call from Ln:10000@Nikotel to sip:16193300999@63.214.186.6
    21:21:59.190|.\CallStrategies.cpp(363)|Trace5|CallManager|StratInOut::initialize: Initialize InOut call strategy
    21:21:59.206|.\Registrar.cpp(132)|Debug2|Registrar|Registrar::getDNsContact: No AOR for DN=120 is registered!
    21:21:59.206|.\Extension.cpp(63)|Trace5|Endpoints|Extension::Extension: Extension Ext.120 is not registered!
    21:21:59.206|.\CallStrategies.cpp(369)|Trace5|CallManager|StratInOut::initialize: Caller overrides call target to be: []
    21:21:59.206|.\CallConf.cpp(277)|Log2|CallControl|CallConf::Rejected: Call (C:3) is rejected: Target is not resolved
    21:21:59.206|ServerInviteSession.cxx(384)|Trace5|Resip|>>: UAS_EarlyOffer: reject(404)
    21:21:59.206|.\ISHandler.cpp(139)|Trace5|CallControl|ISHandler::eek:nReadyToSend: InviteSession(13) sends SIP/2.0 404 Not Found
    21:21:59.206|.\ISHandler.cpp(140)|Message5|CallControl|ISHandler::eek:nReadyToSend: IS(13) sends:

    SIP/2.0 404 Not Found
    Via: SIP/2.0/UDP 63.214.186.6;branch=z9hG4bK5f6ac9dedd5c410aa6cd42ab390c040c
    Via: SIP/2.0/UDP 66.52.2.22
    To: <sip:16193300999@63.214.186.6>;tag=002d7456
    From: <sip:66.52.2.22>;tag=2E07C8E4-2434
    Call-ID: DAEBF253-BB9F11DB-A876AA54-A00904BE@66.52.2.22
    CSeq: 102 INVITE
    Warning: 404 "Target is not resolved"
    Content-Length: 0


    21:21:59.206|InviteSession.cxx(2046)|Trace5|Resip|>>: Transition UAS_EarlyOffer -> InviteSession::Terminated
    21:21:59.206|.\ISHandler.cpp(100)|Trace5|CallControl|ISHandler::eek:nTerminated: Terminated: is=13;reason=Ended
    21:21:59.206|.\Call.cpp(144)|Trace5|CallControl|CallLeg::eek:nEnded: Leg.onEnded 10000@L:1@C:3 got zero msg
    21:21:59.206|.\CallStrategies.cpp(577)|Trace5|CallManager|StratInOut::eek:nHangUp: InOut: got Hang-Up from 10000@L:1@C:3
    21:21:59.206|.\CallStrategies.cpp(698)|Trace5|CallManager|StratInOut::~StratInOut: InOut: strategy is terminated
    21:21:59.206|.\CallConf.cpp(77)|Critical0|CallControl|CallConf::eek:nIncoming: Can not resolve target for call from <sip:66.52.2.22>;tag=2E07C8E4-2434 to <sip:16193300999@63.214.186.6>
    21:21:59.206|.\CallConf.cpp(364)|Trace5|CallControl|CallConf::~CallConf: Destroying call C:3
    21:21:59.221|.\CallEvents.cpp(78)|Trace5||FireStatusEvent: Fire event: OnHook; DN 10000
    21:21:59.221|.\Call.cpp(748)|Trace5|CallControl|CallLeg::~CallLeg: Leg 10000@L:1@C:3 is destroyed
    21:22:12.752|.\CallEvents.cpp(166)|Trace5||DBUpdateListener: Got DB update event
    21:22:12.752|.\CallMgr.cpp(261)|Trace5||DBUpdateListener: Got DB update event: p1=0;p2=0; p3="10000"



    Thanks for any advice.

    Mike
     
  2. 3CXsupport

    3CXsupport New Member
    3CX Staff

    Joined:
    Aug 21, 2006
    Messages:
    193
    Likes Received:
    0
    Hi Mike.

    All seems to be fine from the external line's side. It looks like the call is failing when the PBX sees that the extention is not registered. Either the forward to VM on unregistered is not correctly set or somehow it is not correctly entered into the database.

    Can you try to set it up once again ? i.e. disable the forwarding to VM for the extension in question, and set it up again. If it still doesn't work please do a quick test on a newly created extension. Hope this solves the issue.
     
  3. cs

    cs

    Joined:
    Sep 18, 2008
    Messages:
    27
    Likes Received:
    0
    hello

    what do I have to choose to connect nikotel on 7.1?

    1. generic SIP Proviver
    2. SIP Server: calamar0.nikotel.com:5060, outbound proxy: same
    3. external: accountname, auth Id: same, auth pass: password, max sim call: 1 (?)
    4. conntect to ... (phonenummer internal)
    5. rule ... (phonenumber internal)

    logfile says reg succeeded, but the calls are not working.

    does nikotel use are specal codec?

    Marc
     
  4. Nick Galea

    Nick Galea Site Admin

    Joined:
    Jun 6, 2006
    Messages:
    1,677
    Likes Received:
    18
    I suggest you switch to SIPgate...
     
  5. cs

    cs

    Joined:
    Sep 18, 2008
    Messages:
    27
    Likes Received:
    0
    :)

    i already did - sipgate ist working perfectly ... but i still have arround 350 euros on my nikotel acccout :-(
     
  6. cs

    cs

    Joined:
    Sep 18, 2008
    Messages:
    27
    Likes Received:
    0
    after a long nikotel hotline phone call:

    Nikotel works !

    but really I didn't change anything ...
     

Share This Page