Trouble with IP Phones and Cisco routers - For Info

[afrogley]

Just a FYI - update
Having finished pulling my hair out I'm talking to a chap who knows about these things (or at least seems to - talked about a lot of things that I just didn't understand!) - he's had a look at our routers and can see the traffic coming from the IPO into a router - from there it goes out but never reaches the other one ... he's at a loss to know why it disappears ... he's not seen this behaviour before and the config looks ok ... he's playing with some other settings now....

At least I don't feel so bad about not being able to get it to work ... it's just a little odd as it did before!

I know this isn't quite an Avaya IPO question ... but as I'd asked about it and got some very helpful replies I thought you'd like to know ....

 

[intrigrant]

from there it goes out but never reaches the other one ...

sounds odd indeed, there must be something in between dropping the data or the damn thing is just broken....
can you access the other end just to see if the packets are deliverd?

If it ain't dutch it ain't much

 

[hairlessupportmonkey]

cisco - it wont be broken, just not configured correctly - or the broadband is up the swanny

ACSS - SME

 

[Bas1234]

What type of router?
Did you try to reboot the router? (don't forget the wr mem)

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged (Avaya Search tool

http://tinyurl.com/bas1234

)
______________________________________

 

[afrogley]

Routers are 887s ...

The Cisco chappie syncronised the software last night and it's still not working ... and I get a strange result from tracert ..

50.254 is a remote router for Internet - PC's and servers use this as their default gateway.
50.252 is a remote router for Voice - Telephones use this as their default gateway.
255.1 is an IP address on the local router (best ask the Cisco guy about this ... !)

From the remote network ->
To the IPO:

Tracing route to 10.10.0.10 over a maximum of 30 hops
  1    <1 ms    <1 ms    <1 ms  192.168.50.254 
  2    <1 ms    <1 ms    <1 ms  192.168.50.252 
  3    39 ms    30 ms    40 ms  192.168.255.1 
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7    50 ms    32 ms    43 ms  10.10.0.10 
Trace complete.

To a unit that isn't the IPO

Tracing route to 10.10.0.3 over a maximum of 30 hops
  1    <1 ms    <1 ms    <1 ms  192.168.50.254 
  2    <1 ms    <1 ms    <1 ms  192.168.50.252 
  3    30 ms    30 ms    30 ms  192.168.255.1 
  4    38 ms    32 ms    31 ms  10.10.0.3 
Trace complete.

I've just changed the IPO (Lan2) to 10.10.0.2 - same results as on 10.10.0.10.

I've yet to do a hard reset on the phone system.....

 

[afrogley]

That was interesting - Did a hard reset and got a slightly different result ...

Tracing route to 10.10.0.2 over a maximum of 30 hops
  1    <1 ms    <1 ms    <1 ms  192.168.50.254
  2    <1 ms    <1 ms    <1 ms  192.168.50.252
  3    38 ms    30 ms    30 ms  192.168.255.1
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *       32 ms     *     10.10.0.2
  7    32 ms    32 ms    31 ms  10.10.0.2

Doing a continuous "Ping" gives about a 1% loss - over a few thousand pings ...

 

[hairlessupportmonkey]

simply sounds like the ciscos arent configured correctly

we use 800 series all the time and generally dont have a problem.

I suggest checking your NAT rules, or, reset them and start fresh.

sometimes when they have been frigged about with so much, their configs dont work.....

just use the start up wizards on each to configure them (Via

https://10.10.10.1

then use Configuration professional to create the VPN tunnels.

Job done.

Normally takes me less than an hour to get remote handsets configured via site to site vpn.

ACSS - SME
General Geek

 

[afrogley]

I think I'll go for the wipe and reload of the cisco routers ... although one of them is remote so I'll have to keep the VLAN1 config to be able to telnet to it.

 

[afrogley]

well - I tried to remote reconfigure them - whilst I could get the VPN up and working (for a short while) it still didn't resolve the routing issue..

So - out with the trusty DG834Gs - quick config and run the second one down to the remote site - phones back up in an instant (although same tracert pattern!) ..

Now I've got the Cisco routers out I'll do a reset and rebuild - I may try to substitute just one first (leaving the other DG834g in place)

Thanks for your (continued!) support

 

[hairlessupportmonkey]

try ensuring your have them on a late version of IOS

ACSS - SME
General Geek

 

[afrogley]

Well - it all went tits up again this morning - one way audio through the netgear routers - so it's not the routers!!

Finally got it working by going through a different VPN to the LAN1 connection on the IPO ... whether or not that stays up is a different matter...

I think I'm going to have to sit down and sort out my WAN ... design is obviously not working...

 

[hairlessupportmonkey]

ive seen this before where the ISP rebalances their connections across multiple pipes completely killing the RTP.

e.g

Pipe 1 gets busy, reloads traffic to Pipe 2 - tunnel re-establishes, but any current RTP sessions die.



ACSS - SME
General Geek

 

[afrogley]

Ah - so may not be anything to do with the routers, IPO or config anyway ... !!

I think we're going to put in a second IPO at the remote site now - we don't do much site2site calling anyway and it was an attempt to save the cash on buying a second IPO ...
Their traffic will be in and out via SIP channels direct to voip.co.uk then ..
We've not had problems with our SIP trunks - never had the facility to test the remote site direct to SIP ..