Steve -
I just recently had the same issue. It started popping up out of
nowhere. I opened a support requested with Proctor Labs and got it
figure out. This worked like a charm for me. The following is a quote
from support:
/Matthew,
I had some time to do some testing on Volume 1 Lab 11a and I found
that the initial and final config did not configure an IP address
between HQ-RTR and BR2-RTR. Drew and myself worked for a couple days
on the issue and could not resolve it, banging our heads against the
wall, as imagine you were too, 3 hours I think you said. In the end
the issue was above our pay grade :-) We had to pull Amy and Vik
into the mix to help us out. I apologize that I did not know this
Sunday night.
The issue is a known IOS bug. Once the configs load and if you run
into the issue again here are the configs to resolve the issue on
those two devices:
HQ-RTR(config)#interface Serial0/0/1:0
HQ-RTR(config-if)#no frame-relay traffic-shaping
HQ-RTR(config)#interface Serial0/0/1:0.2 point-to-point
HQ-RTR(config-subif)#no frame-relay interface-dlci 202
HQ-RTR(config-subif)#frame-relay interface-dlci 202
HQ-RTR(config-fr-dlci)# ip address 10.10.112.1 255.255.255.0
Matthew,
I had some time to do some testing on Volume 1 Lab 11a and I found
that the initial and final config did not configure an IP address
between HQ-RTR and BR2-RTR. Drew and myself worked for a couple days
on the issue and could not resolve it, banging our heads against the
wall, as imagine you were too, 3 hours I think you said. In the end
the issue was above our pay grade :-) We had to pull Amy and Vik
into the mix to help us out. I apologize that I did not know this
Sunday night.
The issue is a known IOS bug. Once the configs load and if you run
into the issue again here are the configs to resolve the issue on
those two devices:
HQ-RTR(config)#interface Serial0/0/1:0
HQ-RTR(config-if)#no frame-relay traffic-shaping
HQ-RTR(config)#interface Serial0/0/1:0.2 point-to-point
HQ-RTR(config-subif)#no frame-relay interface-dlci 202
HQ-RTR(config-subif)#frame-relay interface-dlci 202
HQ-RTR(config-fr-dlci)# ip address 10.10.112.1 255.255.255.0
/
*Matthew Berry*
/A+, CCENT, CCNA, CCNA Voice, CCVP, CCIE Voice Written/
*_Vitals:_*
*GVoice: *+1.612.424.5044
*Gmail*: ciscovoiceg...@gmail.com
*Skype*: ciscovoiceguru
*Twitter*: ciscovoiceguru
*_Cert Stats:_*
Cisco Cert Journey Began: Jan 1, 2009
1st Lab Attempt: Aug 16, 2010
On 4/23/2010 11:06 AM, Steve Denney (stdenney) wrote:
Been racking my brains and burning up lots of rack time (and support's
time as well) over this one. Would greatly appreciate any insights.
Suddenly, I am having major issues getting my softphones registered to
the BR2 CME router. This started last week on Voice Pod 14. Since it
was the first time I'd used that particular pod, I chalked it up to a
possible flaky pod. But this week, the same thing is happening on Pod
13 -- which I've used before several times. It's as if something has
changed, but I have no idea what. I've triple checked all of the soft
client settings and MAC addresses and router configs. Like I said,
this has always worked in the past -- it's not as if I have changed
any of my lab procedures which have worked up to now. I am using
Software VPN. Everything about HQ and BR1 seems fine -- the only
issues are with BR2.
Specific symptoms are:
My IPblue client, which should register as ephone 2, is not
registering to BR2, but to SRST somewhere (!!). The client is pointing
to 10.10.110.3, as it should, with the SRST box unchecked -- no changes.
My X-Lite client, which should register as voice register pool 2, is
getting "Registration error 408 - Request Timeout".
Finally, a third issue, not related to softphones: the BR2 Ph2 (7960
at Proctor Labs) will not convert from SCCP to SIP. I've hit this many
times in the past and was always able to use the time-tested procedure
of pointing the DHCP option 150 to the CUCM Sub, and letting it get
its SIP files from there. But since last week, that procedure no
longer works either.
I have purposely left out a lot of the troubleshooting details because
I did not want to overburden the list :) Has anyone else experienced
anything like this recently?
Any tips appreciated...essentially dead in the water in regards to BR2
/ CME / CUE until I can get this figured out. **sigh**
cheers, sd
_______________________________________________
For more information regarding industry leading CCIE Lab training, please visit
www.ipexpert.com
_______________________________________________
For more information regarding industry leading CCIE Lab training, please visit
www.ipexpert.com
