Point-To-Point Question

[Shawn Crow]

Hi Experts
We have a new remote site with the following in place:

Blended T1's from site to site with Adtran Routers between.

Site #1 (Home Office):
Cisco ASA 5510
Cisco Catalyst 4507R with two POE Switches
ShoreGear T1
ShoreGear 120/24 (2 each)

Site #2 (New Office):
Adtran 24 Port POE Switch

I'm looking for some advice on how to configure the ShoreWare Director to allow VoIP traffic between the two sites. So far we have added a new IP Phone Address Map List for the new site. The Adtrans can see each other without issues. The Adtran VoIP connection in the main office coming from the new site is connected to our Catalyst 4507R VoIP Switch and configured for pass through.

We desire to use the same numbers we currently have and run everything via the home office.

Thanks for your help.
Shawn

[southeasternMI]

What are your phones doing? Are you applying all your phone settings via DHCP or statically configuring the phone? Can you ping the ST server from the remote site? You double check GW, you running V-LANs?

[Shawn Crow]

Just getting back after the new year. We are running phones with DHCP. The phones seem to get the correct address when booting up in the new office. However, they don't have enough information to start successfully. I'll comment back with the exact details. Thanks for the reply.

[Shawn Crow]

My new error is "No MGC IP Configured".

[Jason Learmouth]

My new error is "No MGC IP Configured".

It sounds like the DHCP server that this phone is getting its IP address from isn't giving out option 156, or the info in 156 is wrong. Does the phone contact the FTP server successfully during boot up?

Also, when you say you have added an IP address map for the new site, have you actually created a new site in ShoreWare Director? If so you will need to have a ShoreGear switch in the home office - that is the MGC IP phones will look for. If you aren't planning to have a ShoreGear switch at the home office then it shouldn't be a site in ShoreWare Director. Just set the IP address map to the HQ site (for example) and tick "teleworkers". That will let the phones talk to a ShoreGear Switch at the main office.

[Shawn Crow]

I set the IP Address Map to point to Headquarters and checked the Teleworkers box. This did not work. I did not create a new site in ShoreWare Director. It leads to licensing issues. Thanks for the comments. Much appreciated. I will have to personally test the phone at the remote site tomorrow to see if it see the ftp server on boot.

[Jason Learmouth]

I set the IP Address Map to point to Headquarters and checked the Teleworkers box. This did not work. I did not create a new site in ShoreWare Director. It leads to licensing issues. Thanks for the comments. Much appreciated. I will have to personally test the phone at the remote site tomorrow to see if it see the ftp server on boot.

If the DHCP server at the remote site can't do boot options then you can enter in the FTP server IP address on the phone manually and still let it get its IP from DHCP. You may want to put in a time server as well. MGCP IP should be pulled from the FTP when it connects.

[Shawn Crow]

I have removed DHCP and entered static information on the phone at the remote site. The server at headquarters can now see the phone, as well as Shoreware Director. However, the phone boots and ends on "requesting service". The event log viewer displays an ID 1341 = "insufficient bandwidth at headquarters". I made a change to allow for 768kbps in the "Admission Control Bandwidth" location in Shoreware Director. With or without the MGCP IP entered...the results are the same. Anything else I can try?

[Shawn Crow]

I would like to thank everyone for their input. We had to get ShoreTel on the phone a couple of times to resolve this issue. The problem was isolated to our Shoregear T-1 Switch and one of our ShoreGear 120/24 Switches. The correct gateway routes were required to pass traffic. They used Telnet to gain access to the hardware and fix the problem. The total phone time was 3 hours tops between the two sessions.

[davidbec]

I have a related question.

A new client of our wants to be able to dial by extension from one building to another about half a mile away. They cannot connect through wireless or fibre. They are using analog trunks for the PSTN connection at both buildings, but there is an ADSL 768K/2M data link between the buildings.

Do they have to install VPN's on the ADSL?
If they did how many phone calls would that allow?
Can they use the analog trucks to transfer calls if is setup as 2 separate sites under one HQ?

I've log a case with TAC, but they have not responded yet.

[knabs]

This sort answer is yes.

You would really need to nail down QOS for the upstream DSL, or segment your voip traffic onto a secondary DSL connection only used for VOIP back to HQ...

I would say around 16 would be the upper limit if you dedicated a DSL connection for VPN VOICE.

Yes, if you place a shoretel switch at that branch..

[eazeaz]

Adsl

Are they using this DSL for internet access currently? They have one internet DSL connection at both locations?

If its being used for internet traffic, you are going to have to really nail the QOS..... for how cheap DSL lines are, I would get one just for voice... or better yet, ditch the DSL and get a T1 between the buildings.

if both DSL lines are with the same provider, it would be possible to get decent quality (the packets would never really hit the internet anyway, they would stay on the providers network only). Latency is usually pretty good inside a CO network until you leave their routers.

[davidbec]

Thanks all.

Yes they are using the same provider whose office and telecoms equipement is on the same island.
The ADSL would be used for company data as well.
The company is small so there are probably only going to be about 4-6 calls max across the link and they are geting cisco routers. So I could probably separate the data and voice, with 320K for voice and the remainder for data.

Correct?

Thanks again.

[eazeaz]

Dsl

You can control what goes OUT using QOS. You can't control what comes IN.

if they are sharing the line with internet traffic, you may have to just try it and see if it is ok for you.

VPN's over DSL that are shared with internet traffic are not ideal for voice.