Operator EXT 1000 returns Busy status

Discussion in '3CX Phone System - General' started by swim, Jul 12, 2011.

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

    Joined:
    Sep 23, 2008
    Messages:
    26
    Likes Received:
    0
    Any help on this would be much apreciated as I can not work this out :S

    3CX V 10 sp 1.1
    server 2008
    Hyper V install

    3 Snom 820 ip phones

    All extensions work correctly internally and externally except extension 1000

    test call from extension 1001 to 1000

    19:01:29.267 Currently active calls [none]
    19:01:21.940 [CM503008]: Call(1): Call is terminated
    19:01:19.009 Session 350 of leg C:1.1 is confirmed
    19:01:18.368 [CM503007]: Call(1): Device joined: sip:5555@127.0.0.1:40600;rinstance=ab31c3ef1274c968
    19:01:18.364 [CM503007]: Call(1): Device joined: sip:1001@192.168.1.38:1024;line=cduli2sd
    19:01:18.361 [MS210005] C:1.1:Answer provided. Connection(proxy mode):192.168.1.4:7000(7001)
    19:01:18.355 [MS210001] C:1.2:Answer received. RTP connection[unsecure]: 127.0.0.1:40610(40611)
    19:01:18.353 Remote SDP is set for legC:1.2
    19:01:18.346 [CM505001]: Ext.5555: Device info: Device Identified: [Man: 3CX Ltd.;Mod: Voice Mail Menu;Rev: General] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CX Voice Mail Menu] PBX contact: [sip:5555@127.0.0.1:5060]
    19:01:18.346 [CM503002]: Call(1): Alerting sip:5555@127.0.0.1:40600;rinstance=ab31c3ef1274c968
    19:01:18.203 [CM503025]: Call(1): Calling Ext:Ext.5555@[Dev:sip:5555@127.0.0.1:40600;rinstance=ab31c3ef1274c968]
    19:01:18.200 [MS210004] C:1.2:Offer provided. Connection(proxy mode): 127.0.0.1:7002(7003)
    19:01:18.144 [CM503005]: Call(1): Forwarding: Ext:Ext.5555@[Dev:sip:5555@127.0.0.1:40600;rinstance=ab31c3ef1274c968]
    19:01:18.138 [CM503016]: Call(1): Attempt to reach <sip:1000@192.168.1.4:5060;user=phone> failed. Reason: Busy
    19:01:18.138 [CM503014]: Call(1): No known route to target: <sip:1000@192.168.1.4:5060;user=phone>
    19:01:18.115 [CM503010]: Making route(s) to <sip:1000@192.168.1.4:5060;user=phone>
    19:01:18.113 [MS210000] C:1.1:Offer received. RTP connection: 192.168.1.38:50656(50657)
    19:01:18.110 Remote SDP is set for legC:1.1
    19:01:18.110 [CM505001]: Ext.1001: Device info: Device Identified: [Man: Snom;Mod: 8xx series;Rev: General] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [snom820/8.4.31] PBX contact: [sip:1001@192.168.1.4:5060]
    19:01:18.106 [CM503001]: Call(1): Incoming call from Ext.1001 to <sip:1000@192.168.1.4:5060;user=phone>
    19:01:17.024 [CM500002]: Info on incoming INVITE:
    INVITE sip:1000@192.168.1.4:5060;user=phone SIP/2.0
    Via: SIP/2.0/UDP 192.168.1.38:1024;branch=z9hG4bK-p4iml6nnioys;rport=1024
    Max-Forwards: 70
    Contact: <sip:1001@192.168.1.38:1024;line=cduli2sd>;reg-id=1
    To: <sip:1000@192.168.1.4:5060;user=phone>
    From: "Tracie "<sip:1001@192.168.1.4:5060>;tag=0smw8pe42f
    Call-ID: 3c2ea10f6b60-9g8nv46dx312
    CSeq: 2 INVITE
    Session-Expires: 3600;refresher=uas
    Min-SE: 90
    Accept: application/sdp
    Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO, UPDATE
    Proxy-Authorization: Digest username="1001",realm="3CXPhoneSystem",nonce="414d535c042d1cec22:52256b4c1b70cb8220a26aef7ceed2d4",uri="sip:1000@192.168.1.4:5060;user=phone",response="8a9bb4124d28e113808b8af21253c994",algorithm=MD5
    Supported: timer, 100rel, replaces, from-change
    User-Agent: snom820/8.4.31
    Allow-Events: talk, hold, refer, call-info
    Content-Length: 0
    X-Serialnumber:removed
    P-Key-Flags: resolution="31x13", keys="4"

    19:00:57.267 Currently active calls [none]
    19:00:51.329 [CM504001]: Ext.1000: new contact is registered. Contact(s): [sip:1000@192.168.1.37:1024;line=e7w8wg8t/1000]

    many thanks :)
     
  2. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,847
    Likes Received:
    299
    It looks like 3CX can't find Ext 1000 (not registered?), but 1000 is forwarded to Ext 5555, and that is where the call is going.
     
  3. swim

    Joined:
    Sep 23, 2008
    Messages:
    26
    Likes Received:
    0
    thanks for the reply leejor, its really bizzare as 3cx management console shows extension 1000 as registered, the snom phone shows extension 1000 as registered and the 3CX logs show extension 1000 as registered.

    19:00:57.267 Currently active calls [none]
    19:00:51.329 [CM504001]: Ext.1000: new contact is registered. Contact(s): [sip:1000@192.168.1.37:1024;line=e7w8wg8t/1000]

    I have tested extension 1000 by moving it to different phones and every time I get failed. Reason: Busy from the logs and you are correct the call goes to voicemail 5555
    therefore I can rule out the hard phones, and point the issue to the extension itself ( which shows as available and logged in )

    just cant get my head round this one :S
     
  4. nbailey

    nbailey Member

    Joined:
    Jan 31, 2011
    Messages:
    359
    Likes Received:
    0
    sounds like DND is set possibly and the extension is set to forward to ext 5555, as it doesn't show DND status in the phone system trying giving that a glance, I don't work with snom phones so I can't help you with the settings.

    Thanks,
    Nate
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. swim

    Joined:
    Sep 23, 2008
    Messages:
    26
    Likes Received:
    0
    thanks Nate, it does sound like DND is "stuck" on, I can toggle DND on/off with the snom phone with no effect, also to confirm that I have put this extension on 3 different Snom phones which replicates the same problem. I can also replicate the same issue with a 3cx softphone.
     
  6. StefanW

    StefanW Head of Customer Support and Training
    Staff Member 3CX Support

    Joined:
    Jun 2, 2009
    Messages:
    1,217
    Likes Received:
    89
    go to the phone and dial once *60, does this solve the issue?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Thread Status:
Not open for further replies.