Target is not registered: Ext:Ext.(NO : just 1 Ext !)

Discussion in '3CX Phone System - General' started by pcros1, Jun 24, 2008.

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

    Joined:
    Apr 28, 2008
    Messages:
    2
    Likes Received:
    0
    Hi folks,

    Got the following trace ("Target is not registered: Ext:Ext.201") when placing a call to extension 201 from a Grandstream GXP-2000 SIP phone (extension 101), even though the call to extension 201 connects allright when placed from a Grandstream BudgetTone-100 SIP phone (extension 100) (see further down), which should demonstrate that extension 201 is properly registered under 3CX :

    16:26:11.373 Call::Terminate [CM503008]: Call(1): Call is terminated
    16:26:11.264 Call::RouteFailed [CM503014]: Call(1): Attempt to reach [sip:201@192.168.0.10] failed. Reason: Not Registered
    16:26:10.889 Call::RouteFailed [CM503014]: Call(1under 3CX): Attempt to reach [sip:201@192.168.0.10] failed. Reason: Not Registered
    16:26:10.889 CallCtrl::eek:nSelectRouteReq [CM503015]: Call(1): Target is not registered: Ext:Ext.201
    16:26:09.514 CallCtrl::eek:nIncomingCall [CM503001]: Call(1): Incoming call from Ext.101 to [sip:201@192.168.0.10]


    18:59:10.417 Call::Terminate [CM503008]: Call(2): Call is terminated
    18:59:10.392 Call::Terminate [CM503008]: Call(2): Call is terminated
    18:55:34.863 CallCtrl::eek:nLegConnected [CM503007]: Call(2): Device joined: sip:201@192.168.0.14
    18:55:34.854 CallCtrl::eek:nLegConnected [CM503007]: Call(2): Device joined: sip:100@192.168.0.12
    18:55:00.413 CallCtrl::eek:nSelectRouteReq [CM503004]: Call(2): Calling: Ext:201@[Dev:sip:201@192.168.0.14]
    18:55:00.333 CallCtrl::eek:nIncomingCall [CM503001]: Call(2): Incoming call from Ext.100 to [sip:201@192.168.0.10]

    Can anybody help ?

    What does this "double Ext:" (Ext:Ext.201) SIP ID mean to you :shock: anyway ?

    Thank you for your most appreciated help.

    pcros
    :roll:
     
Thread Status:
Not open for further replies.