Can't forward calls from any phone

Discussion in '3CX Phone System - General' started by MarkS, Mar 24, 2015.

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

    Joined:
    Feb 11, 2015
    Messages:
    14
    Likes Received:
    0
    I'm in the process of testing 3CX with a 3CX instance in our datacenter and a handful of test phones SNOM, Aastra, 3CX softphone at office running through the 3CX Session border controller. I can make internal calls between phones OK, but I cannot get any of the phones to automatically forward to another extension, they just come back with failed or media negotiation failed. Looking in the server logs it seems to report a "no route" error (see logs below). Calling from extension 102 to 104 which has a call forward to 105, doesn't matter which phones you try to set the call forward on. Network config is 192.168.36.10 is 3CX server at datacenter, 172.20.140.11 is a Windows SBC @ office, phones are also reside of 172.20.140.x subnet. Surely you can forward a phone when running behind an SBC, would appreciate any ideas, Thanks.

    24-Mar-2015 11:48:28.548 Leg L:135.1[Extn] is terminated: Cause: BYE from PBX
    24-Mar-2015 11:48:28.497 Leg L:135.2[Extn] is terminated: Cause: 302 Moved Temporarily/INVITE from 192.168.36.10:5080
    24-Mar-2015 11:48:28.496 [CM503003]: Call(C:135): Call to "Tony" <sip:104@192.168.36.10:5060> has failed; Cause: 302 Moved Temporarily/INVITE from 192.168.36.10:5080
    24-Mar-2015 11:48:28.496 [CM503020]: Call(C:135): Normal call termination. Call originator: Extn:102. Reason: Terminated
    24-Mar-2015 11:48:28.496 L:135.1[Extn] failed to reach Extn:104, reason Redirected
    24-Mar-2015 11:48:28.496 [CM503014]: Call(C:135): No known route from Extn:102 to target: <sip:105@172.20.140.11:5060>
    24-Mar-2015 11:48:28.496 [CM503006]: Call(C:135): Diverted to: <sip:105@172.20.140.11:5060>
    24-Mar-2015 11:48:28.496 Call to T:Extn:104@[Dev:sip:104@172.20.140.76:39710;line=bd59091e] from L:135.1[Extn] failed, cause: Cause: 302 Moved Temporarily/INVITE from 192.168.36.10:5080
    24-Mar-2015 11:48:26.867 [CM503025]: Call(C:135): Calling T:Extn:104@[Dev:sip:104@172.20.140.76:39710;line=bd59091e] for L:135.1[Extn]
    24-Mar-2015 11:48:26.819 [CM503027]: Call(C:135): From: Extn:102 ("Paull" <sip:102@192.168.36.10:5060>) to T:Extn:104@[Dev:sip:104@172.20.140.76:39710;line=bd59091e]
    24-Mar-2015 11:48:26.819 [CM503004]: Call(C:135): Route 1: from L:135.1[Extn] to T:Extn:104@[Dev:sip:104@172.20.140.76:39710;line=bd59091e]
    24-Mar-2015 11:48:26.818 [CM503001]: Call(C:135): Incoming call from Extn:102 to <sip:104@192.168.36.10:5060>
     
  2. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,369
    Likes Received:
    229
    Does Ext 105, show, in the logs, as being registered at 172.20.140.11:5060 ?

    Not having made use of the SBC just yet, I'm wondering if, because this would appear to be a direct SIP call, you require having that option enabled (it isn't) , in 3CX?
     
  3. MarkS

    Joined:
    Feb 11, 2015
    Messages:
    14
    Likes Received:
    0
    All the extensions show in the logs as being registered on their internal LAN address (see example below)

    24-Mar-2015 12:30:39.062 [CM504001]: Endpoint Extn:105: new contact is registered. Contact(s): [sip:105@172.20.140.97:5060 / 105]

    Just tried enabling the direct sip option but still not working. Almost looks like the 3CX doesn't know to route the call back to the SBC on <sip:105@172.20.140.11:5060>, the SBC just connects on a single port (5090) back to the 3CX in the datacenter, no VPN in place.
     
  4. MarkS

    Joined:
    Feb 11, 2015
    Messages:
    14
    Likes Received:
    0
    Just setup a softphone at another site connected to the same 3CX server and that can call extensions back at the office connected to the SBC OK. Just having the issue if call forward to another extension is set on the phone.
     
  5. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,369
    Likes Received:
    229
    The log error you get, is what i would expect to see if the forwarded number were forwarded to an outside phone using outbound rules. I'm not sure why it would even say "no route" when it is to an extension. I should make no difference if the extension is at a remote location, behind an SBC, or a single set behind a router.
     
  6. MarkS

    Joined:
    Feb 11, 2015
    Messages:
    14
    Likes Received:
    0
    I'm running v12 of the Cloud Server product at moment, might install a standalone version of 12.5 to see if that exhibits the same symptons.
     
  7. MarkS

    Joined:
    Feb 11, 2015
    Messages:
    14
    Likes Received:
    0
    Have done a fresh install of 12.5 and still the same problem, can't set a phone to forward all calls to another extension just get errors in the server log such as No known route from Extn:101 to target: <sip:103@172.20.140.11:5060>

    All the extensions can call each other OK and can transfer a call to another extension.

    Has anyone else got this working using phones behind a SBC.
     
  8. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,369
    Likes Received:
    229
    Just to confirm...you are using the forward to Extension (drop down extension number menu) option, rather than forward to External Number or Skype ID, correct?
     
  9. MarkS

    Joined:
    Feb 11, 2015
    Messages:
    14
    Likes Received:
    0
    I'm setting the forward on the phone (snom 715) by pressing the Cfwd button and entering the extension number, tried the same from an old Astra phone as well.
     
  10. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,369
    Likes Received:
    229
    In your initial post, you said "automatically forward", so I assumed you meant using the forwarding rules within the 3CX extension settings. In your case, there may be an issue with how the set (key) is implementing the forwarding.

    Does call forwarding work correctly if the extension call forward setting are in place (in the 3CX extension settings) and a call goes unanswered?
     
  11. MarkS

    Joined:
    Feb 11, 2015
    Messages:
    14
    Likes Received:
    0
    appologies for delay in replying leejor.

    If I set the forward by using the 3cx console it works. Using the call forward button on the phone and setting the extension to forward to on the phone does not. Setting the forward on the phone uses the "302 Moved Temporarily" sip header which contains the sip address to redirect to which then fails with a no route to.

    In the server log the phones show as being registered as SIP:extension@lan-ip-address whereas the sip address in the redirect message is SIP:extension@SBC-ip-address this is true if I also set the forward number on the phone to be the voicemail number for the 3CX.

    Could the fact the phones are sitting behind the SBC be the issue ?
     
  12. MarkS

    Joined:
    Feb 11, 2015
    Messages:
    14
    Likes Received:
    0
    Just taken a look at the Snom web console. There are 2 settings in the sip profile, the 1st is "Registrar" and the 2nd "Outbound Proxy". Both of these were set to the SBC-Lan-IP-Address:5060, I've changed the registrar to IP-Address-of-the-3cx:5060 and with that the call forward button on the phone works and the "302 Temporarily Moves" SIP header now contains the redirect SIP address as SIP:extension@IP-Address-of-the-3cx:5060

    Not sure if this is a bug or whether I need to modify the provisioning template
     
  13. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,369
    Likes Received:
    229
    Someone much more familiar with the use of the Snom sets behind an SBC, would have to answer that, but both may be true.
     
Thread Status:
Not open for further replies.