No announcement yet.
  • Filter
  • Time
  • Show
Clear All
new posts

  • Extension to Extension problem

    I have two remote users. They each have a 530 phone. Both are connected
    to the main office and the shoretel server via SonicWall hardware
    vpn's. When the person is dialed direct via their assigned phone number
    from one remote to another the call is crystal clear. However, when
    dialing the extension, the phone rings, but neither party can hear the
    other. Calls made and received to outside numbers work fine. It is just
    extension to extension. We are using the 6.1 release and I have
    teleworker checked.

    Thanks, Charles

  • #2
    I think I understand what you are saying.

    REM 1..REM2
    ...\ ....../
    ....\... ./
    .....\ ../
    ......\ /

    Rem 1 can not dial Rem 2 directly.
    Rem 1 Can dial the outside number (813)555-1212 of the Rem 2 and can connect.

    Does this sound correct? If so, your problem is routing.
    Think about this:
    Rem 1 can not see Rem 2. You can't even ping it. The VPN tunnel is between Rem 1 and HQ. HQ is not routing the packets. On an extension to extension call, the call is from the IP of Rem 1 to the IP of Rem 2.

    When you call them on the outside number, Rem 1 is talking to the HQ switch, and dials an outside line. The Switch then picks up the conversation on an incoming line, and the Switch talks to Rem 2. The switch, in essence is a proxy in this situation. Rem1 IS NOT communicating directly to Rem 2.

    There are 2 solutions.
    #1: Make the network 'Routable', whether with static routes or a router (adds latency)
    #2: Create a VPN tunnel between Rem 1 and Rem 2

    Hope this helps
    Last edited by Forum; 03-15-2007, 06:01 PM.


    • #3
      Thanks Charles,

      Your configuration is correct. The part I now need to figure out is how to connect the two remotes as they are both dynamic ip's. I know I can set up a hub and spoke with SonicWall (need to figure that out) but I am pretty certain that I cannot go direct (mesh) because of the dynamic ip's.

      The good news is that extension calls from the headquarters to the remote will work since that networking is mapped via the vpn.

      Thanks, Charles


      • #4
        Even though your external IP's are dynamic, your internal IP range at each remote site is static and unique, correct? Therefore, you should just have to add a static route at remote site 1 that says any traffic destined for the internal address range of remote site 2 should go through the VPN tunnel to headquarters. Add a second static route at remote site 2 that says any traffic destined for remote site 1's internal address range should go through the VPN tunnel to headquarters.

        This should create the hub and spoke config that you need. However, it may add enough latency to cause voice quality issues.