Toshba CIX40 Network eManager VPN

Hello all,

So just a disclaimer, I am not a phone system savvy individual but I will do my best. We have several locations that have a Toshiba STRATA box at their office and we have a Toshiba IP Edge at our corporate office. All of our offices are linked via VPN (Cisco ASA 5505). We have the STRATAs at our branch stores connected to their ASAs and we can ping the unit. However, when firing up Strata Network eManager we are unable to connect to any of the locations. The company that provided the systems tell me it has to be a port issue, but in our VPN settings we have NAT exemptions for all traffic from branch to corporate, so all traffic should be allowed. It should not be a port issue because all traffic is allowed via the NAT exemption.

My question is how can I get eManager to connect? As i said, the IP address from out corp office to the strata is pingable both directions via the VPN. As far as I know the communityName is still default. When we attempt to connect I get:

Connection failed! CIX40XXXXXXX:ERROR_COULD_NOT_CONNECT_TO_CALL_AGENT

Any help would be appreciated.
slipy120Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Dirk MareSystems Engineer (Acting IT Manager)Commented:
We had a similar issue and it was related to natting on a router in my MPLS network.

Example of my network..
HQ
192.168.1.0/24
Pbx 192.168.1.246
Local network connected to Router interface eth3 with Ip 192.168.1.10. MPLS connected to eth1 with ip 172.16.0.4

Branch office..
192.168.3.0/24
Pbx 192.168.3.246
Local network connected to Router interface eth3 with Ip 192.168.3.10. MPLS connected to eth1 with ip 172.16.0.8

Running traceroutes between sites worked great and completed every time with results similar to below..

Hq to branch
Hop 1 192.168.1.10
Hop 2 172.16.0.8
Hop 3 192.168.3.246

Branch to hq
Hop 1 192.168.3.10
Hop 2 172.16.0.4
Hop 3 192.168.1.246

Seems to be working.. But deeper packect inspection I found the when you look at traffic to and from both pbx it was receiving data from a mpls router..

172.16.0.1 would communicate directly with 192.168.3.246 and when the ..3.246 pbx replied the data went directly to 172.16.0.1 and not to hq router 172.16.0.4 all data was dropped because the mpls router 172.16.0.1 did not know what to do with this data or mpls provider resolved this by disabling the Nat on the mpls router..

Disclaimer,
We aren't using strata or cisco just very similar issue with a suggestion to capture data to and from your network..

DirkMare

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
VPN

From novice to tech pro — start learning today.