 ceverett
Member
Team Member
Joined: Apr 2008  ID, USA
 Posts: 10395 Feedback: 0% (0) |
Posted: 7/27/2012 5:02:49 PM
THE IMAGE ABOVE IS A PAID ADVERTISEMENT |
|
|
|
com-guy
Communicaitons Guy
Team Member
Joined: Feb 2003 MO, USA
Posts: 619 Feedback: 100% (1) Link To This Post |
Posted: 7/28/2012 8:53:38 AM
What issues are you having? I've not played with the 250's, but have a customer with several locations using the 350's with S8300 servers.
|
|
|
ceverett
Member
Team Member
Joined: Apr 2008 ID, USA
Posts: 10414 Feedback: 0% (0) Link To This Post |
Posted: 7/28/2012 5:20:38 PM
Originally Posted By com-guy: What issues are you having? I've not played with the 250's, but have a customer with several locations using the 350's with S8300 servers. I'm having issues with the ETHE WAN port (10/2 on these) Everything seems to work, but I can't get the phones that are on the G250 to connect to call server (an S8300 in a remote G450) The G250 will register to the S8300, and I can ping the phone from the S8300, but the phone just sits there and says "Discovering X.X.X.X" If I create an additional VLAN and use an ETHE WAN port, it works. Just not on the WAN port. And I have a couple of locations where I really need all 8 of the local LAN ports. |
|
|
|
com-guy
Communicaitons Guy
Team Member
Joined: Feb 2003 MO, USA
Posts: 622 Feedback: 100% (1) Link To This Post |
Posted: 7/31/2012 7:43:17 PM
I had a similar problem between two IP Office systems over a VPN. It ended up being a issue with the Cisco routers/firewalls that were used to create the VPN. I think it was a packet size issue, but not sure.
As to this problem with the system you're working with; I have never worked with that equipment in that configuration. My sites all have an 8300 at all offices as stand alone systems. |
|
|
ceverett
Member
Team Member
Joined: Apr 2008 ID, USA
Posts: 10444 Feedback: 0% (0) Link To This Post |
Posted: 7/31/2012 11:44:09 PM
Originally Posted By com-guy: I had a similar problem between two IP Office systems over a VPN. It ended up being a issue with the Cisco routers/firewalls that were used to create the VPN. I think it was a packet size issue, but not sure. As to this problem with the system you're working with; I have never worked with that equipment in that configuration. My sites all have an 8300 at all offices as stand alone systems. Well, to make things more confusing, now I have another location where I can't connect when I am connected via a ETHE LAN port.  Yet I can still register the gateway itself.
FML. |
|
|
|
ceverett
Member
Team Member
Joined: Apr 2008 ID, USA
Posts: 10697 Feedback: 0% (0) Link To This Post |
Posted: 8/15/2012 11:21:27 AM
In case anybody reads this at some point, I figured it out. Needed to update the ip-network-regions on the 8300.
My vendor left out that step in the procedure for setting up a new gateway. |
|
|
ARCHIVED
