no ringing time out V5

Discussion in '3CX Phone System - General' started by andy, Dec 15, 2007.

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

    Oct 22, 2007
    Likes Received:
    I newly installed V5 and created 2 extension.
    100 (Siemens S450IP) and 200 (x-lite SW client)
    SIP server is in the internet and the 2 extension behind an NAT device.
    When I try to call from 200 to 100 it fails. see log.
    It works fine in V3.

    08:06:32.520 Call::Terminate [CM503008]: Call(2): Call is terminated
    08:06:32.500 Call::RouteFailed [CM503013]: Call(2): Attempt to reach "100"[] failed. Reason: No Answer
    08:06:32.450 CallLeg::eek:nFailure [CM503003]: Call(2): Call to has failed; Cause: 408 Request Timeout; internal
    08:06:00.294 MediaServerReporting::SetRemoteParty [MS210002] C:2.2:Offer provided. Connection(transcoding mode):
    08:06:00.054 CallCtrl::eek:nSelectRouteReq [CM503004]: Call(2): Calling: Ext:100@[Dev:sip:100@]
    08:06:00.054 CallCtrl::eek:nSelectRouteReq Making route(s) to "100"[]
    08:06:00.054 MediaServerReporting::SetRemoteParty [MS210000] C:2.1:Offer received. RTP connection:
    08:06:00.054 CallLeg::setRemoteSdp Remote SDP is set for legC:2.1
    08:06:00.054 Extension::printEndpointInfo [CM505001]: Ext.200: Device info: Device Identified: [Man: Counterpath;Mod: X-Lite;Rev: General] Capabilities:[reinvite, no-replaces, unable-no-sdp, recvonly] UserAgent: [X-Lite release 1011s stamp 41150] Transport: [sip:]
    08:06:00.014 CallCtrl::eek:nIncomingCall [CM503001]: Call(2): Incoming call from Ext.200 to "100"[]
    08:05:44.842 ExtnCfg::updateContact [CM504001]: Ext.100: new contact is registered. Contact(s): [sip:100@]
Thread Status:
Not open for further replies.