Signaling Being Slow

[Mitelmatt]

Hi Guys

Wonder if someone can help me on this

3300 MXe 4.1

On a HP Procurve Network

Randomly, the when a user calls another phone, the voice isn;t heard for the first couple of seconds, then once the voice is established, the call is fine. If you make a second call straight after it works fine.

There is multiple switches in the network

It's almost like the signaling is going to sleep

We've had a look at the switches but can't see anything obvious, i'm sure it's a network thing but can't quite work it out

any ideas?

 

[nytalkin]

Look for an un-intended loop. I've seen this problem and it was as simple as someone connecting two L2 ports together.

NO GOOD DEED GOES UNPUNISHED!

 

[Mitelmatt]

hi nytalkin

Thanks, kinda reaffirmed what i was thinking really.

They have a meshed network of data swithes

Any idea of where to start looking or commands / tools we can use to assist?

 

[cknipe]

intresting you say this. today I installed my first newer model CX with 4.1. I put this in thier colo on its own vlan but I was noticing the 5320 having a hard time keeping up with me (on the display) as I was dialing some test numbers. I forgot what model cisco switches the customer was using but ill have a better look next time. Just found it odd as the phone was on the same LAN and same switch.

was your issue on a new cx or MXe mitelmatt?

 

[Mitelmatt]

was MXE, but still interesting

 

[nytalkin]

try Maint Logs first. You might find more than one device on the network with the same IP. A wireshark trace will kick out these errors as well.

NO GOOD DEED GOES UNPUNISHED!

 

[Mitelmatt]

Maint logs on the 3300 or HP?

Thanks, looked at the wireshark, threre some signaling that has the correct IP addresses in it but ports 've never seen before, 3999 (Norman distributes scanning service) and i tink it's 7666 off the top of my head. They come up highlighted in red in the trace. Not sure if tha has anything to do with it?