<font size="2"><font face="verdana,sans-serif">Hi All,</font></font><div><font size="2"><font face="verdana,sans-serif"><br></font></font></div><div><font size="2"><font face="verdana,sans-serif">Experienced some strange gatekeeper issue today after applying config on a "Common Phone Profile". This is reproducible every time. I want to see what people's thoughts are on this.</font></font></div>
<div><font size="2"><font face="verdana,sans-serif"><br></font></font></div><div><font size="2"><font face="verdana,sans-serif">The scenario is that we have CUCM 8.5 > H225 Trunk (Gatekeeper Controlled) > Gatekeeper (2821 IOS 12.4(25b)) > H225 Trunk (Gatekeeper Controlled) > CUCM 5.1.3. Both phone systems have a catch all route pattern that route calls to the gatekeeper, but don't worry the trunks do not have access to route calls to the gatekeeper, no loops.</font></font></div>
<div><font class="Apple-style-span" face="verdana, sans-serif"><br></font></div><div><font class="Apple-style-span" face="verdana, sans-serif">On CUCM 8.5.1.11900-21</font></div><div><font class="Apple-style-span" face="verdana, sans-serif"><br>
</font></div><div><font class="Apple-style-span" face="verdana, sans-serif"><div>I click "Apply Config" on a common phone profile, the phones reset I then can not call across the gatekeeper, I get the following reject reason.</div>
<div><br></div><div><br></div><div>Mar 9 07:38:55.967: RAS OUTGOING PDU ::=</div><div><br></div><div>value RasMessage ::= admissionReject : </div><div> {</div><div> requestSeqNum 26123</div><div> rejectReason calledPartyNotRegistered : NULL</div>
<div> nonStandardData </div><div> {</div><div> nonStandardIdentifier h221NonStandard : </div><div> {</div><div> t35CountryCode 181</div><div> t35Extension 0</div><div> manufacturerCode 18</div>
<div> }</div><div> data '80400160'H</div><div> }</div><div> }</div><div><span class="Apple-tab-span" style="white-space:pre"> </span></div><div>If I then just reset the gatekeeper or the trunk from CUCM 8.5 I get the following registration reject</div>
<div><br></div><div>value RasMessage ::= registrationReject : </div><div> {</div><div> requestSeqNum 31</div><div> protocolIdentifier { 0 0 8 2250 0 4 }</div><div> rejectReason duplicateAlias : </div><div>
{</div><div> }</div><div> gatekeeperIdentifier {"CM8LAB"}</div><div> }</div><div><br></div><div>I have to then restart the call manager service then reset the gatekeeper or trunk from CUCM 8.5 to get calls working again.</div>
<div><br></div><div>value RasMessage ::= registrationConfirm : </div><div> {</div><div> requestSeqNum 4</div><div> protocolIdentifier { 0 0 8 2250 0 4 }</div><div> callSignalAddress </div><div> {</div>
<div> }</div><div> terminalAlias </div><div> {</div><div> h323-ID : {"GK-Trunk_1"}</div><div> }</div><div> gatekeeperIdentifier {"CM8LAB"}</div><div> endpointIdentifier {"44CD0D6800000007"}</div>
<div> alternateGatekeeper </div><div> {</div><div> }</div><div> timeToLive 60</div><div> willRespondToIRR FALSE</div><div> maintainConnection FALSE</div><div> }</div><div><br></div><div><br>
</div><div>Does this sound like a bug to anyone? Why would applying a common phone profile interfere with gatekeeper registration.</div><div><br></div><div>Does anyone have a similar setup they could test?</div><div><br></div>
<div>I can reproduce on demand so its not a once off glitch.</div><div><br></div><div>cheers,</div><div><br></div><div>Dan </div><div><br></div></font></div>