<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"> 
  <channel>
  <title>CME Hot Issues from Cisco TAC</title>
  <link>http://www.cisco.com/en/US/customer/products/sw/voicesw/ps556/products_tech_note09186a0080937324.shtml</link>
  <description>Hot Issues from Cisco TAC.  Please click the link for complete details.</description>
  <language>en-us</language>

  <managingEditor>wsisk@cisco.com (Wes Sisk)</managingEditor>
  <webMaster>news-at-cisco-rss@cisco.com (Cisco Newsroom)</webMaster>
  <pubDate>Mon, 13 May 2013 09:37:29 EDT</pubDate>
  <lastBuildDate>Mon, 13 May 2013 09:37:29 EDT</lastBuildDate>
  <generator>PERL</generator>

  <docs>http://www.cisco.com/en/US/customer/products/sw/voicesw/ps556/products_tech_note09186a0080937324.shtml</docs>
  <ttl>10080</ttl>

<item>
<title>UC560 crashes after IOS upgrade to 15.1(4)M5, Open CSCug37304</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCug37304</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
UC560 crashes after IOS upgrade to 15.1(4)M5
&lt;br&gt;&lt;B&gt;Conditions:&lt;/B&gt;
UC560 crashes after IOS upgrade to 15.1(4)M5
&lt;br&gt;&lt;B&gt;Workaround:&lt;/B&gt;
None

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCug37304</guid>
</item>
<item>
<title>Echo on call through FXO when Video enabled, Open CSCug74536</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCug74536</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Echo on call through FXO when Video enabled
&lt;br&gt;&lt;B&gt;Conditions:&lt;/B&gt;
Call flow is as follow:
1. PSTN user calls in through FXO to CME 9.1
2. Call is answered by 9951 SIP phone using sip9951.9-3-2-10
3. 9951 hits the transfer button and dials to an 8945 SIP phone using SIP894x.9-2-2-0 to make a consultative transfer
4. 9951 and 8945 are on call and video is showing fine between the two phones.
5. 9951 hits the transfer button again and call is connected between PSTN user and 8945.
6. At this point the Video screen shows in black instead of disappearing since there is no more video (CSCue93022), however echo is heard on 8945 IP Phone. Echo is not heard on the PSTN user.

If video is disabled no echo is heard
&lt;br&gt;&lt;B&gt;Workaround:&lt;/B&gt;
Disable video on CME

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCug74536</guid>
</item>
<item>
<title>memory leak due to asnl_get_new_evInfo, Open CSCug55996</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCug55996</link>
<description>&lt;B&gt;Symptom:

memory leak and crash preceded with error messages like Apr 24 15:52:40.776: %DIALPEER_DB-3-ADDPEER_MEM_THRESHOLD: Addition of dial-peers limited by available memory

memory leak due to skinny msg server and alloc_pc = asnl_get_new_evInfo
 &lt;/B&gt;
&lt;br&gt;
&lt;B&gt;Conditions:

2951 router running 15.3(2)T &lt;/B&gt;
&lt;br&gt;
&lt;B&gt;Workaround:
none

&lt;/B&gt;

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCug55996</guid>
</item>
<item>
<title>Configure &quot;Speeddial&quot; feature as a Softkey in SIP CME, Open CSCug54233</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCug54233</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

Enhancement request to be able to configure &quot;Speed dial&quot; feature as a softkey in 8961 phone registered with SIP CME.
This feature is currently not available in any of the CME versions.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

None
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

None

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCug54233</guid>
</item>
<item>
<title>9951 callback softkey on CME 9.X not working, Open CSCug75216</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCug75216</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
9951 callback softkey will not work on CME 9.X. When pressing the softkey it will have no effect at all.
&lt;br&gt;&lt;B&gt;Conditions:&lt;/B&gt;
Using 9951 with firmware sip9951.9-3-2-10, CME 9.X and enabling callback by editing featurepolicy.xml file:
&lt;featureDef name=&quot;Call Back&quot;&gt;
&lt;id&gt;6&lt;/id&gt;
&lt;enable&gt;true&lt;/enable&gt;
&lt;br&gt;&lt;B&gt;Workaround:&lt;/B&gt;
NA

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCug75216</guid>
</item>
<item>
<title>Crash at kadis_timer_ISR, Terminated CSCtt19540</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtt19540</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
router crash
&lt;br&gt;&lt;B&gt;Conditions:&lt;/B&gt;
no specific conditions when crashes
&lt;br&gt;&lt;B&gt;Workaround:&lt;/B&gt;
unknown yet



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtt19540</guid>
</item>
<item>
<title>3900 series router crashes due to speed dial function., Fixed CSCuf93606</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCuf93606</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

3945E router is crashing.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

Extension mobility is to be configured for the phone. The logout profile should NOT be configured with any number.
In the logged out state, user has to press the &quot;NewCall&quot; softkey followed by dialing any digit between 1 - 9 (excluding 0). 
And instead of pressing &quot;Dial&quot; softkey, press &quot;AbbrDial&quot; softkey.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Have a proper number configured under the logout profile.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCuf93606</guid>
</item>
<item>
<title>SYS-3-INVMEMINT and SYS-2-MALLOCFAIL for -Process= &quot;&lt;interrupt level&gt;&quot;, Open CSCug57177</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCug57177</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Logs show messages like these occasionally:

 %SYS-3-INVMEMINT: Invalid memory action (malloc) at interrupt level 

%SYS-2-MALLOCFAIL: Memory allocation of 14 bytes failed from 0x22CB46A8, alignment 0
Pool: Processor  Free: 238660812  Cause: Interrupt level allocation 
Alternate Pool: None  Free: 0  Cause: Interrupt level allocation 
 -Process= &quot;&lt;interrupt level&gt;&quot;, ipl= 1, pid= 370
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Unknown at this time.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Unknown.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCug57177</guid>
</item>
<item>
<title>CME RFC2833 SIP DTMF Relay via NTE pkts should use valid RTP timestamps, Fixed CSCsa88753</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsa88753</link>
<description>Symptoms:
=========
RFC2833 DTMF relay via the SIP NTE method may be unsuccessful when digits are
entered from an IP Phone registered to a Cisco Call Manager Express (CME) or a
Cisco Survivable Remote Site Telephony (SRST) voice router.  The receiving party
on the voice call will not hear the DTMF digits correctly.
&lt;br&gt; 

Conditions:
===========
RFC2833 DTMF relay via the SIP NTE method was introduced in IOS 12.3(11)T for 
both CME 3.2 and SRST 3.2.  These symptoms may be observed when the Cisco CME
or SRST voice gateway interoperates with a non-Cisco peer SIP voice gateway.
This problem will not be observed when the two SIP voice gateways are both 
Cisco voice routers.
&lt;br&gt;

Workaround:
===========
Workarounds, if available at all, will depend on how the non-Cisco voice router
implements RFC2833 DTMF relay via the SIP NTE method.  Please contact the Cisco
Technical Assistance Center (TAC) for further analysis and direction if the use
of an IOS listed in the &quot;First Fixed-in Version&quot; field has already been 
evaluated and found to fail.



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsa88753</guid>
</item>
<item>
<title>sip phones not registering with SRST with &#39;number&#39; cli, Fixed CSCud33882</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCud33882</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
SIP phones not registering to SRST when number cli with wild card configured under voice register pool.
&lt;br&gt;&lt;B&gt;Conditions:&lt;/B&gt;
Configure number cli with wild card configuration under voice register pool.
number 1 900....
&lt;br&gt;&lt;B&gt;Workaround:&lt;/B&gt;
Create separate pools for all the phones without wild cards.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCud33882</guid>
</item>
<item>
<title>Memory leak in dialog_set_entity, Fixed CSCug37242</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCug37242</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

Router crash due to memory leak.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

Voip related configuration - not narrowed down yet. 
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Not found yet.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCug37242</guid>
</item>
<item>
<title>crash due to %ALIGN-1-FATAL: Illegal accesswhile processing h323 traffic, Fixed CSCtf67170</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtf67170</link>
<description>Symptoms: There is a crash due to the following error:
  
  %ALIGN-1-FATAL: Illegal access
&lt;br&gt;  
  Conditions: The symptom is observed when &quot;call monitor&quot; is configured.
&lt;br&gt; 
  Workaround: Remove call monitor, if interfacing with UCCX is not needed. 
 
 



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtf67170</guid>
</item>
<item>
<title>%SYS-3-INVMEMINT: Invalid memory action error message, Fixed CSCtx99353</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx99353</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

Error message on router

%SYS-3-INVMEMINT: Invalid memory action (malloc) at interrupt level

The error message can lead the device to crash
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

Moh is enabled
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Disabling the music on hold stopped the issue.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx99353</guid>
</item>
<item>
<title>[ENH] CME: should support skinny version 21 and higher, Open CSCug73803</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCug73803</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

On a 6945 SCCP phone that is currently on a call, when &#39;Hold&#39; button is pressed and then &#39;NewCall&#39;, you&#39;ll receive this error message regardless of the number of max calls configured under the ephone - 

&quot;Unable to create a call; the maximum number of calls for this line has been reached&quot;
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

6945 SCCP phone registered to CME.
It should have a line that is currently on call.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Convert to SIP.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCug73803</guid>
</item>
<item>
<title>UC560 Not able to enable Presence for Internal Lines, Open CSCug51393</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCug51393</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
UC560 Not able to enable Presence for Internal Lines
&lt;br&gt;&lt;B&gt;Conditions:&lt;/B&gt;
UC560 Not able to enable Presence for Internal Lines
&lt;br&gt;&lt;B&gt;Workaround:&lt;/B&gt;
None

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCug51393</guid>
</item>
<item>
<title>MWI unsolicited mode fails with line key monitoring a floating extension, Fixed CSCtx59445</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx59445</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
When MWI is in unsolicited mode, and a message is left for a floating extension&#39;s mailbox, a line key monitoring that extension does not get an envelope icon. When using regular MWI DNs, it does change the envelope icon for floating extensions.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

MWI unsolicited
IOS: 15.1(2)T4
CME 8.1
CUE 8.0.6
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

None



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtx59445</guid>
</item>
<item>
<title>Ephone disconnecting call after FXO detected fxols_rvs_battery, Open CSCug25559</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCug25559</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt; Intermittently, ephone disconnects an inbound call (changes to efxs_offhook_onhook) after FXO detected battery reversal. Problem clears by itself (hard reboot doesn&#39;t help). Disabling battery-reversal also did not help. 
&lt;br&gt;

&lt;B&gt;Conditions:&lt;/B&gt;
CME - 8.6
IOS - 15.1(4)M5
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt; None

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCug25559</guid>
</item>
<item>
<title>Support for H323 trunking in SIP CME and SIP SRST, Open CSCub00715</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCub00715</link>
<description>This is to track the feature enhancement for the SIP Phones registered with CME to be able to call over H323 trunk.
NOTE: Even if the call works in these scenarios, we could encounter several issues with supplementary services. The normal call might fail as well with different problems in H245 signalling.

Currently we do not support SIP Phones registered with CME/SRST calling over H323 trunks.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
Ideally Network re-design required. As SCCP Phones work, a workaround like following can be put in place:
For example, using SIP Phone you need to call 671XX over H323 trunk. Configure:
--------------------
ephone-dn  9
number 671..
loopback-dn 10 forward 5
caller-id local
no huntstop

ephone-dn  10
number 71..
loopback-dn 9 forward 4 prefix 6
caller-id local
no huntstop
--------------------
Dial 71XX instead, to reach 671XX. This &#39;simulates&#39; a SCCP endpoint calling over H323 trunk and solves the purpose. It actually splits up the call into call-legs:
SIP Phone (inbound :VOIP DP) ------ ephone-dn (outbound: POTS DP)
ephone-dn (inbound : POTS DP) ------ H323 trunk (outbound: VOIP DP)
and hence, loops the call within CME before sending it out.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCub00715</guid>
</item>
<item>
<title>CME sends SetLampMessage even those lines not bound to extn in question, Open CSCug79260</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCug79260</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;

It takes a long time (5 seconds) to disconnect the call after the user pressing Endcall soft key
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

- A new voicemail is read/deleted.
- Every phone has two sidecars (7914s)  attached to it. Thus, 20 additional lines per phone.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

Use MWI outcall method instead of SIP NOTIFY method.

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCug79260</guid>
</item>
<item>
<title>DTMF duration is fixed for calls from CME / UC500 to PSTN, Open CSCsm63154</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsm63154</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
DTMF to certain IVRs fail
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Only occurs when using SCCP phones on CME going to PSTN
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;
none

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCsm63154</guid>
</item>
<item>
<title>Improper memory allocation by CTI process crashing CME, Fixed CSCty64721</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCty64721</link>
<description>Symptoms: Improper memory allocation by CTI process crashes the CME.
&lt;br&gt;
Conditions: The CTI front end process is using up huge memory causing the CME
to crash eventually. When the crash occurs:

Processor Pool Total:  140331892 Used:  140150164 Free:     181728
      I/O Pool Total:   27262976 Used:    5508816 Free:   21754160
&lt;br&gt;
Workaround: There is no workaround. 



</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCty64721</guid>
</item>
<item>
<title>CME/SRST does not down the virtual pots when translation is involved,   CSCug55833</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCug55833</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
CME 8.5 using SRST . When the call manager fails and the CM phone use the CME router as SRST everything works fine. The issue is that when the phone revert back to CM the virtual POTS dial-peers stay up and the call fails with user busy as the first choice dial-peer is the ephone dial-peer. 
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;

Call FLow: 
PSTN -&gt;E1 PRI -&gt;CME-SRST Gateway Router (H.323) -&gt; CUCM

IOS version : 15.1.3T3 

Incoming calls failing after translation as outgoing dial-peer as the system dial-peer created by ephone-dn was getting matched. The DN was provisioned during SRST Fallback.

Call is passed to CCAPI for dial-peer hunting
Mar 20 20:09:34.710: //-1/EB2387CA8007/CCAPI/cc_api_display_ie_subfields: 
cc_api_call_setup_ind_common: 
cisco-username= 
----- ccCallInfo IE subfields ----- 
cisco-ani=2089547848 
cisco-anitype=2 
cisco-aniplan=1 
cisco-anipi=0 
cisco-anisi=3 
dest=502 
cisco-desttype=0 
cisco-destplan=1 
cisco-rdie=FFFFFFFF 
cisco-rdn= 
cisco-rdntype=-1 
cisco-rdnplan=-1 
cisco-rdnpi=-1 
cisco-rdnsi=-1 
cisco-redirectreason=-1 fwd_final_type =0 
final_redirectNumber = 
hunt_group_timeout =0
Call fails with cause code 17 which means user busy
Mar 20 20:09:34.722: feature call basic 
Mar 20 20:09:34.722: //551/EB2387CA8007/CCAPI/ccCallDisconnect: 
Cause Value=17, Tag=0x0, Call Entry(Previous Disconnect Cause=0, Disconnect Cause=0) 
Mar 20 20:09:34.722: //551/EB2387CA8007/CCAPI/ccCallDisconnect: 
Cause Value=17, Call Entry(Responsed=TRUE, Cause Value=17)
Mar 20 20:09:34.726: ISDN Se0/0/0:15 Q931: TX -&gt; DISCONNECT pd = 8 callref = 0x8001 
Cause i = 0x8091 - User busy
The issue is caused because the SRST dial-peer outranks the ones going to call manager and so we get a busy tone. 
List of Matched Outgoing Dial-peer(s): 
1: Dial-peer Tag=20046 
2: Dial-peer Tag=200 
3: Dial-peer Tag=100

Mar 25 18:00:33.931: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore: 
Calling Number=, Called Number=502, Peer Info Type=DIALPEER_INFO_SPEECH 
Mar 25 18:00:33.931: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore: 
Match Rule=DP_MATCH_DEST; Called Number=502 
Mar 25 18:00:33.931: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore: 
No Outgoing Dial-peer Is Matched; Result=NO_MATCH(-1) 
Mar 25 18:00:33.931: //-1/xxxxxxxxxxxx/DPM/dpMatchSafModulePlugin: 
dialstring=502, saf_enabled=0, saf_dndb_lookup=1, dp_result=-1 
Mar 25 18:00:33.931: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersMoreArg: 
Result=NO_MATCH(-1) 
Mar 25 18:00:33.931: //-1/xxxxxxxxxxxx/CCAPI/cc_setupind_match_search: 
Try with the demoted called number 502
&lt;br&gt;

&lt;B&gt;Workaround:&lt;/B&gt;

The workaround is to manually configure the ephone-dn of the Call Manager ip phones and change the preference from 0 to 9 and then make sure the VOIP H.323 dial-peer is set to higher than 9 say leave it at 0. Then the config is the most important. Change the dial-peer hunt from default 0 to 2. This changes the dial-peer hunting from longest match in phone number to explicit preference.
0 - Longest match in phone number, explicit preference, random selection. 
1 - Longest match in phone number, explicit preference, least recent use. 
2 - Explicit preference, longest match in phone number, random selection. 
3 - Explicit preference, longest match in phone number, least recent use. 
4 - Least recent use, longest match in phone number, explicit preference. 
5 - Least recent use, explicit preference, longest match in phone number. 
6 - Random selection. 
7 - Least recent use.

&lt;snip&gt;
config t
dial-peer hunt 2
telephony-service
max-dn 400 preference 9
&lt;/snip&gt;

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCug55833</guid>
</item>
<item>
<title>Rotuer Crash at kadis_timer_ISR, Terminated CSCtq06557</title>
<link>http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtq06557</link>
<description>&lt;B&gt;Symptom:&lt;/B&gt;
Software Forced Crash (Signal 23) on a Cisco2801 running 15.1(3)T1.
&lt;br&gt;
&lt;B&gt;Conditions:&lt;/B&gt;
Similiar Crashes were also seen 15.1(2)T1 as well.
&lt;br&gt;
&lt;B&gt;Workaround:&lt;/B&gt;

None

</description>
<guid isPermaLink="true">http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;bugId=CSCtq06557</guid>
</item>
   
</channel>
</rss>
