[OSL | CCIE_Voice] Proctor Labs issue?

2012-06-08 Thread Dan Quinlan (daquinla)
All, The past two times I've used ProctorLabs for rack time, I've seen my local (local to me) IP Phones deregister / reregister every few minutes and they usually don't come all the way back (DN's missing, etc). I haven't changed my hardware VPN connectivity at all. Has anyone else seen

Re: [OSL | CCIE_Voice] Proctor Labs issue?

2012-06-08 Thread Dan Quinlan
As a follow-up: this is an ongoing issue based on a ProctorLabs reconfiguration from the network issue they experienced earlier. For users on software VPN, setting your MTU to 1300 seems to fix the issue. For hardware VPN users, setting the MTU to 1300 doesn't seem to have fixed anything. I'm

Re: [OSL | CCIE_Voice] Proctor Labs issue?

2012-06-08 Thread William Affeldt
I had the same issue yesterday. It only happened on the CCM though not CME. Sent from my iPhone On Jun 8, 2012, at 10:51 AM, Dan Quinlan (daquinla) daqui...@cisco.com wrote: All, The past two times I've used ProctorLabs for rack time, I've seen my local (local to me) IP Phones

Re: [OSL | CCIE_Voice] Proctor Labs issue?

2012-06-08 Thread Dan Quinlan
Final follow-up: Proctor Labs made a change and now everything seems fine again. On 6/8/12 3:21 PM, Dan Quinlan daqui...@cisco.com wrote: As a follow-up: this is an ongoing issue based on a ProctorLabs reconfiguration from the network issue they experienced earlier. For users on software

Re: [OSL | CCIE_Voice] Proctor Labs issue?

2012-06-08 Thread Krishna
To: ccie_voice@onlinestudylist.com Sent: Friday, June 8, 2012 12:51 PM Subject: [OSL | CCIE_Voice] Proctor Labs issue? All, The past two times I've used ProctorLabs for rack time, I've seen my local (local to me) IP Phones deregister / reregister every few minutes and they usually don't come all

Re: [OSL | CCIE_Voice] Proctor Labs issue?

2012-06-08 Thread Marko Milivojevic
This issue should have been resolved now. On one of the Virtual-Template interfaces we needed to change the adjustment of the TCP MSS to reflect the VPN overhead. For some reason it was overlooked and caused issues that you are all describing. It was fixed some 3-4 hours ago. Those of you who