Dismiss Notice
We would like to remind you that we’re updating our login process for all 3CX forums whereby you will be able to login with the same credentials you use for the Partner or Customer Portal. Click here to read more.

error: 3cx v5 status problem after call transfer

Discussion in '3CX Phone System - General' started by carmico, Dec 14, 2007.

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

    Joined:
    Oct 11, 2007
    Messages:
    23
    Likes Received:
    0
    Hi.

    3cx v5 with thomson st2030 (supervised line - blf activated)

    when i receive a call from outside to a ringing group (all extensions rings) and then make a call transfer to another extension in the 3cx admin interface line status the extension that make the call transfer remains in Status: Ringing (orange color).

    logs from 3cx server status:

    16:16:08.406 Call::Terminate [CM503008]: Call(1): Call is terminated
    16:16:08.390 LineCfg::getInboundTarget [CM503010]: Inbound office hours' rule for LN:10000 forwards to DN:800
    16:16:00.500 CallLeg::eek:nFailure [CM503003]: Call(1): Call to sip:130@192.168.0.100:5060 has failed; Cause: 302 Moved Temporarily; from IP:192.168.0.130
    16:16:00.500 CallLeg::addRedirection [CM503004]: Call(1): Calling: Ext:Ext.120
    16:16:00.500 CallLeg::addRedirection [CM503006]: Call(1): Diverted to: [sip:120@192.168.0.100:5060;user=phone]
    16:15:54.015 CallCtrl::eek:nAnsweredCall [CM503002]: Call(1): Alerting sip:120@192.168.0.120:5060;user=phone
    16:15:54.000 CallCtrl::eek:nAnsweredCall [CM503002]: Call(1): Alerting sip:130@192.168.0.130:5060;user=phone
    16:15:53.921 MediaServerReporting::SetRemoteParty [MS210002] C:1.3:Offer provided. Connection(transcoding mode): 192.168.0.100:7434(7435)
    16:15:53.906 MediaServerReporting::SetRemoteParty [MS210002] C:1.2:Offer provided. Connection(transcoding mode): 192.168.0.100:7432(7433)
    16:15:53.890 CallCtrl::eek:nSelectRouteReq [CM503004]: Call(1): Calling: RingAll:800@[Dev:sip:120@192.168.0.120:5060;user=phone, Dev:sip:130@192.168.0.130:5060;user=phone]
    16:15:53.875 MediaServerReporting::SetRemoteParty [MS210000] C:1.1:Offer received. RTP connection: 212.97.59.91:44736(44737)
    16:15:53.875 Line::printEndpointInfo [CM505003]: Provider:[MessageNet SmartNumber VoIP IN] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [alpha] Transport: [sip:192.168.0.100:5060]
    16:15:53.875 LineCfg::getInboundTarget [CM503010]: Inbound office hours' rule for LN:10000 forwards to DN:800
    16:15:53.828 CallCtrl::eek:nIncomingCall [CM503001]: Call(1): Incoming call from 347xxxxx@(Ln.10000@SmartNumber VoIP IN) to [sip:800@192.168.0.100:5060]
    16:15:53.609 LineCfg::getInboundTarget [CM503010]: Inbound office hours' rule for LN:10000 forwards to DN:800


    regards,
    Carlo
    ps. if i verify others errors i will post it in the forum. 3cx is a really nice solution. I like it. So we have to participate to make it more powerful & stable.
     
  2. carmico

    Joined:
    Oct 11, 2007
    Messages:
    23
    Likes Received:
    0
    the problem verifies only if i make the call transfer to extension without answer the call.

    if i answer the call first, and then make the call transfer to another extension there's no problem.
     
  3. carmico

    Joined:
    Oct 11, 2007
    Messages:
    23
    Likes Received:
    0
    no one with an idea ?
     
  4. archie

    archie Well-Known Member
    3CX Support

    Joined:
    Aug 18, 2006
    Messages:
    1,299
    Likes Received:
    0
    We're still working on BLF, so bugs are expected :)
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Thread Status:
Not open for further replies.