<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=utf-8">
<META content="MSHTML 6.00.2900.3492" name=GENERATOR></HEAD>
<BODY text=#000000 bgColor=#ffffff>
<DIV>interesting...learn something new every day! </DIV>
<DIV> </DIV>
<DIV>The outbound calls were working - is this because the outbound dial-peers use the local PRIs and do not get processed by the Call Manager? Only the inbound have Call Manager target.</DIV>
<DIV> </DIV>
<DIV>Steve</DIV>
<DIV> </DIV>
<DIV>
<DIV><FONT face=Arial color=#006600 size=2>Please consider the impact on our environment before printing this e-mail.</FONT> </DIV><BR><BR>>>> Wes Sisk <wsisk@cisco.com> 3/16/2009 4:39 PM >>><BR>working as designed.<BR><BR>in CM h323 gwA is configured to use device pool dpA<BR>dpA uses cmgroup gpA<BR>gpA contains cm3 and cm4<BR><BR>only nodes cm3 and cm4 will start the h323 daemon for gwA. Only cm3 and cm4 will accept calls from gwA.<BR><BR>However, a phone registered to any nodem cm1, cm2, cm3, or cm4 can initiate a call and the call will properly route out gwA. This happens because the h323 daemon for gwA is only active on cm3 and cm4. Only those nodes can process the H.323 messaging from that gateway. When phone registered to cm1 initiates call it routed by intracluster communication (SDL) from cm1 to cm2 where the routelist is registered. the routelist process selects gwA. call is extended from cm2 to cm3 where the daemon for gwA is active. cm3 initiates the h323 signaling over the network to gwA.<BR><BR>Covered in various details in the SRND. Specifically comes into play for CVP designs that allow agent to agent and agent to queue transfers.<BR><BR>/wes<BR><BR>On Monday, March 16, 2009 4:05:31 PM, STEVEN CASPER <A class=moz-txt-link-rfc2396E href="mailto:SCASPER@mtb.com"><SCASPER@mtb.com></A> wrote:<BR></DIV>
<BLOCKQUOTE cite=mid:49BE78C9.9874.0039.0@mtb.com type="cite">
<META content="MSHTML 6.00.2900.3492" name=GENERATOR>
<DIV>sorry if this duplicates... thought I sent it this morning but do not see it.......</DIV>
<DIV> </DIV>
<DIV>anyway, had a strange problem this morning....over the weekend we changed the Call Manager group for the device pool and route lists for one of our sites. So the phones and RLs are now using Subscriber C as the primary, they used to use Subscriber A. Got a call this morning that no inbound calls could be made to the site only outbound could be made. ISDN Debug indicated a network error. The primary voip dial-peer was pointed to the previous primary Call Manager A. Changed the session target to point to Call manager C and all was well. Call Manager A seems to be working fine.
<DIV> </DIV>
<DIV>This does not make sense to me. Regardless of the Call Manager that the phones and Route lists are registered to I would think it does not matter which Call Manager Subscriber the dial-peers on the H323 gateway are pointing to. Need to set up some more testing but wanted to see if anyone had any thoughts.</DIV>
<DIV> </DIV>
<DIV>Steve</DIV>
<DIV> </DIV>
<DIV>
<DIV><FONT face=Arial color=#006600 size=2>Please consider the impact on our environment before printing this e-mail.</FONT> </DIV></DIV></DIV><PRE>************************************
This email may contain privileged and/or confidential information that is intended solely for the use of the addressee. If you are not the intended recipient or entity, you are strictly prohibited from disclosing, copying, distributing or using any of the information contained in the transmission. If you received this communication in error, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. This communication may contain nonpublic personal information about consumers subject to the restrictions of the Gramm-Leach-Bliley Act and the Sarbanes-Oxley Act. You may not directly or indirectly reuse or disclose such information for any purpose other than to provide the services for which you are receiving the information.
There are risks associated with the use of electronic transmission. The sender of this information does not control the method of transmittal or service providers and assumes no duty or obligation for the security, receipt, or third party interception of this transmission.
************************************
</PRE><PRE wrap=""><HR width="90%" SIZE=4>
_______________________________________________
cisco-voip mailing list
<A class=moz-txt-link-abbreviated href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A>
<A class=moz-txt-link-freetext href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A>
</PRE></BLOCKQUOTE><BR><pre>************************************
This email may contain privileged and/or confidential information that is intended solely for the use of the addressee. If you are not the intended recipient or entity, you are strictly prohibited from disclosing, copying, distributing or using any of the information contained in the transmission. If you received this communication in error, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. This communication may contain nonpublic personal information about consumers subject to the restrictions of the Gramm-Leach-Bliley Act and the Sarbanes-Oxley Act. You may not directly or indirectly reuse or disclose such information for any purpose other than to provide the services for which you are receiving the information.
There are risks associated with the use of electronic transmission. The sender of this information does not control the method of transmittal or service providers and assumes no duty or obligation for the security, receipt, or third party interception of this transmission.
************************************
</pre></BODY></HTML>