5291 unable to hear 5230 is there anything in this log?

Discussion in '3CX Phone System - General' started by rslattery, Mar 22, 2018.

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

    Joined:
    Dec 20, 2016
    Messages:
    12
    Likes Received:
    2
    03/22/2018 10:27:02 AM - L:12460.2[Extn:5230] has joined to L:12460.1[Extn:5291]
    03/22/2018 10:26:56 AM - [CM503025]: Call(C:12460): Calling T:Extn:5230@[Dev:sip:5230@192.168.21.200:64630;rinstance=0-0cb319c00e3f42d0bc94ab2f44f4a7bf;ob] for L:12460.1[Extn:5291]
    03/22/2018 10:26:56 AM - [CM503027]: Call(C:12460): From: Extn:5291 ("Sean Robillard" <sip:5291@10.2.100.250:5060>) to T:Extn:5230@[Dev:sip:5230@192.168.21.200:64630;rinstance=0-0cb319c00e3f42d0bc94ab2f44f4a7bf;ob]
    03/22/2018 10:26:56 AM - [CM503004]: Call(C:12460): Route 1: from L:12460.1[Extn:5291] to T:Extn:5230@[Dev:sip:5230@192.168.21.200:64630;rinstance=0-0cb319c00e3f42d0bc94ab2f44f4a7bf;ob]
    03/22/2018 10:26:56 AM - [Flow] Call(C:12460): has built target endpoint: Extn:5230 for call from L:12460.1[Extn:5291]
    03/22/2018 10:23:35 AM - L:12454.2[Extn:5230] has joined to L:12454.1[Extn:5291]
    03/22/2018 10:23:21 AM - [CM503025]: Call(C:12454): Calling T:Extn:5230@[Dev:sip:5230@192.168.21.200:64630;rinstance=0-0cb319c00e3f42d0bc94ab2f44f4a7bf;ob] for L:12454.1[Extn:5291]
    03/22/2018 10:23:21 AM - [CM503027]: Call(C:12454): From: Extn:5291 ("Sean Robillard" <sip:5291@10.2.100.250:5060>) to T:Extn:5230@[Dev:sip:5230@192.168.21.200:64630;rinstance=0-0cb319c00e3f42d0bc94ab2f44f4a7bf;ob]
    03/22/2018 10:23:21 AM - [CM503004]: Call(C:12454): Route 1: from L:12454.1[Extn:5291] to T:Extn:5230@[Dev:sip:5230@192.168.21.200:64630;rinstance=0-0cb319c00e3f42d0bc94ab2f44f4a7bf;ob]
    03/22/2018 10:23:21 AM - [Flow] Call(C:12454): has built target endpoint: Extn:5230 for call from L:12454.1[Extn:5291]
    03/22/2018 10:21:02 AM - L:12449.1[Extn:5291] forwards call from Extn:5230 to VMail:9999 based on rule Fwd[Available/NoAnsw]
    03/22/2018 10:21:02 AM - L:12449.1[Extn:5291] failed to reach Extn:5230, reason No Answer
    03/22/2018 10:20:42 AM - [CM503025]: Call(C:12449): Calling T:Extn:5230@[Dev:sip:5230@192.168.21.200:64630;rinstance=0-0cb319c00e3f42d0bc94ab2f44f4a7bf;ob] for L:12449.1[Extn:5291]
    03/22/2018 10:20:42 AM - [CM503027]: Call(C:12449): From: Extn:5291 ("Sean Robillard" <sip:5291@10.2.100.250:5060>) to T:Extn:5230@[Dev:sip:5230@192.168.21.200:64630;rinstance=0-0cb319c00e3f42d0bc94ab2f44f4a7bf;ob]
    03/22/2018 10:20:42 AM - [CM503004]: Call(C:12449): Route 1: from L:12449.1[Extn:5291] to T:Extn:5230@[Dev:sip:5230@192.168.21.200:64630;rinstance=0-0cb319c00e3f42d0bc94ab2f44f4a7bf;ob]
    03/22/2018 10:20:42 AM - [Flow] Call(C:12449): has built target endpoint: Extn:5230 for call from L:12449.1[Extn:5291]
    03/21/2018 12:34:13 PM - L:11961.1[Extn:5291] failed to reach Extn:5230, reason Not Found
    03/21/2018 12:34:13 PM - Call to T:Extn:5230@[Dev:sip:5230@192.168.21.200:50195;transport=TCP;rinstance=1-f0275b3a1fc34b6dab0a6af0a94db911;ob] from L:11961.1[Extn:5291] failed, cause: Cause: 404 Not Found/INVITE from 127.0.0.1:5080
    03/21/2018 12:34:13 PM - [CM503025]: Call(C:11961): Calling T:Extn:5230@[Dev:sip:5230@192.168.21.200:50195;transport=TCP;rinstance=1-f0275b3a1fc34b6dab0a6af0a94db911;ob] for L:11961.1[Extn:5291]
    03/21/2018 12:34:13 PM - [CM503027]: Call(C:11961): From: Extn:5291 ("Sean Robillard" <sip:5291@10.2.100.250:5060>) to T:Extn:5230@[Dev:sip:5230@192.168.21.200:50195;transport=TCP;rinstance=1-f0275b3a1fc34b6dab0a6af0a94db911;ob]
    03/21/2018 12:34:13 PM - [CM503004]: Call(C:11961): Route 1: from L:11961.1[Extn:5291] to T:Extn:5230@[Dev:sip:5230@192.168.21.200:50195;transport=TCP;rinstance=1-f0275b3a1fc34b6dab0a6af0a94db911;ob]
    03/21/2018 12:34:13 PM - [Flow] Call(C:11961): has built target endpoint: Extn:5230 for call from L:11961.1[Extn:5291]
    03/21/2018 12:31:08 PM - L:11954.1[Extn:5291] failed to reach Extn:5230, reason Not Found
     
  2. craigreilly

    craigreilly Well-Known Member

    Joined:
    Feb 1, 2012
    Messages:
    2,800
    Likes Received:
    133
    This log shows that 5291 couldn't even reach 5230 - never mind not hear them.
    IP Phoines? Softphones? Same Lan?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. rslattery

    Joined:
    Dec 20, 2016
    Messages:
    12
    Likes Received:
    2
    Hi

    The caller 5291 cannot hear the receiver but the receiver can hear him.

    Both handset/soft phone to receiver using a soft phone. I gave 5230 the receiver a new extension and it worked fine. When I switched back to 5230 it was not working gain.

    Same network different subnets and different locations/sites connected with an mpls.

    I was going to do a uninstall of the client with a third party tool and reinstall. It's just odd that it is with that extension and other users seem to be able to call the receiver extension fine.
     
Thread Status:
Not open for further replies.