3cx VOIP Phone Call Transfer

Discussion in 'Windows' started by inibiru, Jul 20, 2012.

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

    Joined:
    May 10, 2012
    Messages:
    9
    Likes Received:
    0
    Hello, I have a user who's phone when calls are being transferred to her the call goes straight to voicemail even though she is all green lights. I was wondering about any trouble shooting steps I can do to fix this. I have tried reinstalling the phone I have checked all her settings serverside and everything seems fine.
     
  2. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,769
    Likes Received:
    286
    What does the 3CX log show, when a call is attempted to her extension? Does the same thing happen when you call the extension directly from another extension, or does the call behave differently than a transferred call?
     
  3. mixig

    mixig Active Member

    Joined:
    Dec 13, 2011
    Messages:
    523
    Likes Received:
    12
    you can configure in windows e.g. DSCP for some particular apps...

    http://forums.speedguide.net/showthread.php?274421-Windows-7-resets-DiffServ-%28DSCP%29-to-0x00
     
  4. mixig

    mixig Active Member

    Joined:
    Dec 13, 2011
    Messages:
    523
    Likes Received:
    12
    sorry, replay befrore was for some other topic..

    can you put some logs as leejor said, 3cx logs, wireshark, is that only with local calls or every call
     
  5. qiaok

    Joined:
    Jul 23, 2012
    Messages:
    2
    Likes Received:
    0
    What does the 3CX log show?

    Image no longer available
     
  6. inibiru

    Joined:
    May 10, 2012
    Messages:
    9
    Likes Received:
    0
    Sorry about not getting back to you guys soon enough I was on vacation here. When I go into the server and watch the log I can't seem to recreate the issue however when I was doing this I noticed that this Error kept popping up.


    13:34:10.084 [MS105000] C:8740.1: No RTP packets were received:remoteAddr=192.168.2.161:5008,extAddr=0.0.0.0:0,localAddr=192.168.2.140:7220


    Could this have anything to do with it?
     
  7. jpillow

    jpillow Well-Known Member

    Joined:
    Jun 20, 2011
    Messages:
    1,342
    Likes Received:
    0
    That could be the issue however it looks like that error is due to no voice/media packets being received by the softphone. Could you replicate and post more of the log?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  8. inibiru

    Joined:
    May 10, 2012
    Messages:
    9
    Likes Received:
    0
    Ya here is a Log of one that I caught:


    15:03:18.603 [CM503008]: Call(15132): Call is terminated
    14:58:38.811 [MS105000] C:15132.1: No RTP packets were received:remoteAddr=192.168.2.161:5008,extAddr=0.0.0.0:0,localAddr=192.168.2.140:7146
    14:58:38.093 [CM503007]: Call(15132): Device joined: sip:101@192.168.2.32:51488;rinstance=a61aef7841bd7467
    14:58:35.452 [CM503025]: Call(15132): Calling Ext:Ext.101@[Dev:sip:101@192.168.2.32:51488;rinstance=a61aef7841bd7467]
    14:58:35.405 [CM503004]: Call(15132): Route 1: Ext:Ext.101@[Dev:sip:101@192.168.2.32:51488;rinstance=a61aef7841bd7467]
    14:58:32.062 [MS105000] C:15132.1: No RTP packets were received:remoteAddr=192.168.2.161:5008,extAddr=0.0.0.0:0,localAddr=192.168.2.140:7140
    14:58:30.515 [CM503007]: Call(15132): Device joined: sip:*0@127.0.0.1:40000;rinstance=d7a0dcfb2dd3867b
    14:58:30.312 [CM503025]: Call(15132): Calling Ext:Ext.*0@[Dev:sip:*0@127.0.0.1:40000;rinstance=d7a0dcfb2dd3867b]
    14:58:30.296 [CM503004]: Call(15132): Route 1: Ext:Ext.*0@[Dev:sip:*0@127.0.0.1:40000;rinstance=d7a0dcfb2dd3867b]
    14:58:01.406 [CM503007]: Call(15132): Device joined: sip:999@127.0.0.1:40600;rinstance=eabd1c034ce5a486
    14:58:01.250 [CM503025]: Call(15132): Calling Ext:Ext.999@[Dev:sip:999@127.0.0.1:40600;rinstance=eabd1c034ce5a486]
    14:58:01.187 [CM503005]: Call(15132): Forwarding: Ext:Ext.999@[Dev:sip:999@127.0.0.1:40600;rinstance=eabd1c034ce5a486]
    14:58:01.187 [CM503016]: Call(15132): Attempt to reach <sip:170@127.0.0.1:5060> failed. Reason: Not Registered
    14:58:01.187 [CM503017]: Call(15132): Target is not registered: Ext.170
    14:57:35.172 [CM503007]: Call(15132): Device joined: sip:999@127.0.0.1:40600;rinstance=eabd1c034ce5a486
    14:57:35.016 [CM503025]: Call(15132): Calling Ext:Ext.999@[Dev:sip:999@127.0.0.1:40600;rinstance=eabd1c034ce5a486]
    14:57:34.969 [CM503005]: Call(15132): Forwarding: Ext:Ext.999@[Dev:sip:999@127.0.0.1:40600;rinstance=eabd1c034ce5a486]
    14:57:34.969 [CM503003]: Call(15132): Call to sip:101@192.168.2.140:5060 has failed; Cause: 486 Busy Here; from IP:192.168.2.32:51488
    14:57:34.797 [CM503025]: Call(15132): Calling Ext:Ext.101@[Dev:sip:101@192.168.2.32:51488;rinstance=a61aef7841bd7467]
    14:57:34.750 [CM503004]: Call(15132): Route 1: Ext:Ext.101@[Dev:sip:101@192.168.2.32:51488;rinstance=a61aef7841bd7467]
    14:51:18.726 [CM503007]: Call(15132): Device joined: sip:120@127.0.0.1:51901;rinstance=c67b9c580b8dad14
    14:51:12.367 [CM503025]: Call(15132): Calling Ext:Ext.120@[Dev:sip:120@127.0.0.1:51901;rinstance=c67b9c580b8dad14]
    14:51:12.320 [CM503004]: Call(15132): Route 1: Ext:Ext.120@[Dev:sip:120@127.0.0.1:51901;rinstance=c67b9c580b8dad14]
    14:51:02.867 [CM503007]: Call(15132): Device joined: sip:101@192.168.2.32:51488;rinstance=a61aef7841bd7467
    14:51:02.695 [CM503025]: Call(15132): Calling @[Dev:sip:101@192.168.2.32:51488;rinstance=a61aef7841bd7467]
    14:50:57.883 [CM503007]: Call(15132): Device joined: sip:807@127.0.0.1:5488
    14:50:57.727 [CM503025]: Call(15132): Calling Ext:Ext.807@[Dev:sip:807@127.0.0.1:5488]
    14:50:57.664 [CM503004]: Call(15132): Route 1: Ext:Ext.807@[Dev:sip:807@127.0.0.1:5488]
    14:50:28.477 [CM503007]: Call(15132): Device joined: sip:812@127.0.0.1:40600;rinstance=21080f7f6ea3ed4a
    14:50:28.477 [CM503007]: Call(15132): Device joined: sip:10014@192.168.2.161:5064;transport=udp
    14:50:28.321 [CM503025]: Call(15132): Calling Ext:Ext.812@[Dev:sip:812@127.0.0.1:40600;rinstance=21080f7f6ea3ed4a]
    14:50:28.274 [CM503004]: Call(15132): Route 1: Ext:Ext.812@[Dev:sip:812@127.0.0.1:40600;rinstance=21080f7f6ea3ed4a]
    14:50:28.274 [CM505002]: Gateway:[GXW4108 192.168.2.161] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Grandstream GXW4108 (HW 1.1, Ch:1) 1.3.4.10] PBX contact: [sip:10014@192.168.2.140:5060]
    14:50:28.258 [CM503001]: Call(15132): Incoming call from 5307106890@(Ln.10014@GXW4108 192.168.2.161) to <sip:812@192.168.2.140:5060>


    I grabbed everything that had to do with that specific call. There were a few calls being taken place during this call and I didn't grab that info. If you want I can grab the full log next time but I figured this would do.
     
  9. inibiru

    Joined:
    May 10, 2012
    Messages:
    9
    Likes Received:
    0
    Edit: It was during the call transfer between extension 120 and 110 that the caller was sent to the Voice mail system just to be clear
     
  10. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,769
    Likes Received:
    286
    Did you mean ext 101?

    Is this the log of the failed call ? If so then for some reason, 3CX sees the extension as being busy at the time of the call.
     
  11. inibiru

    Joined:
    May 10, 2012
    Messages:
    9
    Likes Received:
    0
    Do you have any idea how that could happen? Obviously the Extension isn't busy during that time frame.
     
  12. jpillow

    jpillow Well-Known Member

    Joined:
    Jun 20, 2011
    Messages:
    1,342
    Likes Received:
    0
    Have you also checked the web GUI to assure the phone isnt set to auto answer?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  13. jpillow

    jpillow Well-Known Member

    Joined:
    Jun 20, 2011
    Messages:
    1,342
    Likes Received:
    0
    set phone to fascatory default reboot the phone than reconfigure/provision.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Thread Status:
Not open for further replies.