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.

failed bridge call

Discussion in '3CX Phone System - General' started by craigreilly, Aug 13, 2012.

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

    craigreilly Well-Known Member

    Joined:
    Feb 1, 2012
    Messages:
    3,569
    Likes Received:
    302
    Can anyone make sense of this? It is a call from Main Office to Remote Office via Bridge. The link is up. I see on the remote end the call coming in briefly on the Trunk Status page. My call gets a busy signal. The log shows Terminated. The Bridge is SLAVE-Direct-UDP to our Corporate Office (Master).
    Call is made from me 4954 to 15512. 155 signifies the bridge to use. It is stripped and 12 is the extension I called. In the log, 480-596-xxxx is my outbound caller id (I think for the extension makiing the call).
    10.0.1.100 is the remote pbx running the 8 call version.
    10.0.1.248 is Extension 11 on Remote PBX.

    Code:
    13-08-2012 09:20:10.678	Leg L:13.3[Extn] is terminated: Cause: 487 Request Terminated/INVITE from 10.0.1.248:5060
    13-08-2012 09:20:10.677	[CM503003]: Call(C:13): Call to <sip:12@10.0.1.100:5060> has failed; Cause: 487 Request Terminated/INVITE from 10.0.1.248:5060
    13-08-2012 09:20:10.488	Leg L:13.1[Line:10155<<480596xxxx] is terminated: Cause: 200 BYE from PBX
    13-08-2012 09:20:10.437	[CM503020]: Call(C:13): Normal call termination. Call originator: Line:10155<<480596xxxx. Reason: [color=#FF0000]Forbidden[/color]
    13-08-2012 09:20:10.437	[CM503016]: Call(C:13): Attempt to reach <sip:12@10.0.1.100:5060> from Line:10155<<480596xxxx has failed. Reason: [color=#FF0000]Forbidden[/color]
    13-08-2012 09:20:10.437	Leg L:13.2[Extn] is terminated: Cause: 603 Decline/INVITE from 10.0.1.249:5060
    13-08-2012 09:20:10.436	[CM503003]: Call(C:13): Call to <sip:12@10.0.1.100:5060> has failed; Cause: 603 Decline/INVITE from 10.0.1.249:5060
    13-08-2012 09:20:10.255	[CM503025]: Call(C:13): Calling T:Extn:12@[Dev:sip:12@10.0.1.249:5060;transport=udp,Dev:sip:12@10.0.1.248:5060;transport=udp]
    13-08-2012 09:20:10.248	[CM503025]: Call(C:13): Calling T:Extn:12@[Dev:sip:12@10.0.1.249:5060;transport=udp,Dev:sip:12@10.0.1.248:5060;transport=udp]
    13-08-2012 09:20:10.225	[CM503027]: Call(C:13): From: Line:10155<<480596xxxx ("Craig Reilly" <sip:480596xxxx@10.0.1.100:5060>)  to  T:Extn:12@[Dev:sip:12@10.0.1.249:5060;transport=udp,Dev:sip:12@10.0.1.248:5060;transport=udp]
    13-08-2012 09:20:10.225	[CM503004]: Call(C:13): Route 1: T:Extn:12@[Dev:sip:12@10.0.1.249:5060;transport=udp,Dev:sip:12@10.0.1.248:5060;transport=udp]
    13-08-2012 09:20:10.223	[CM503001]: Call(C:13): Incoming call from Line:10155<<480596xxxx to <sip:12@10.0.1.100:5060>
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  2. lneblett

    lneblett Well-Known Member

    Joined:
    Sep 7, 2010
    Messages:
    2,086
    Likes Received:
    65
    How are the 2 office physically connected?

    I am a little confused with "Decline/INVITE from 10.0.1.249:5060"

    You appear to be running the same LAN nets on both sites.
     
  3. craigreilly

    craigreilly Well-Known Member

    Joined:
    Feb 1, 2012
    Messages:
    3,569
    Likes Received:
    302
    Both are physically separate networks. No VPN or anything.
    Site 1: Main Office: 10.0.0.1-10.0.3.254
    Site 2: Remote Office: 10.0.1.1-10.0.1.254

    10.0.1.249 is the phone I was calling to.

    Would that cause an issue? Should I change their network scheme?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. craigreilly

    craigreilly Well-Known Member

    Joined:
    Feb 1, 2012
    Messages:
    3,569
    Likes Received:
    302
    Well I changed the scope of the rmeote site. changed out the router that had issues.
    Still 1 way audio.
    Then they told me when it started happening.

    I was here on Friday and the phones weren't getting an IP Address. So, I stuck a 169 address into the server (in addition to the 10.x) to program the phones and that seemed to be the culprit.

    Doh!
    :eek:
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. lneblett

    lneblett Well-Known Member

    Joined:
    Sep 7, 2010
    Messages:
    2,086
    Likes Received:
    65
    Knew you would figure it out.
     
Thread Status:
Not open for further replies.