Your mcast group IP@ in below debug is 239.1.1.3
The same group IP@ should be configured on SiteB router.
No need to enable G.729 for MoH - if you ticked "increment on IP address" 
that's probably why the group IP@ got changed.
Rgds
Alex 


  From: Kumar, Narinder 
  To: ccie_voice@onlinestudylist.com 
  Sent: Tuesday, January 13, 2009 12:36 PM
  Subject: [OSL | CCIE_Voice] MOH Issue


  Quick Que  on MOH   

   

  CCM running multicast MOH.

   

  Between Site A and Site B only g729 allowed

   

  SiteA will receive multicast MOH .

  Site B will receive multicast MOH from router flash, no multicast traffic 
allowed between Ste A and SiteB.

   

  The way I do this question is

   

  Configure the MOH source file and tick multicast and play continuously

  Enable multicast on the MRG and MOH server

  Change the ip voice media service parameter to allow both g711 and g729

   

  Site A works without any issue

   

  Site B Configuration:

   

  Call-manager-fallback

  Moh filename ( Moh file in flash)

  multicast moh 239.1.1.1 port 16384 route x.x.x.x

   

  MOH from site B doesn't work , what am I missing here ?

   

  ***************************************

  debug ccm-manager music-on-hold all

  **************************************

  an 13 13:13:30.023: moh_update_rtp: callID 17 dstCallID 18

  *Jan 13 13:13:30.023: moh_process_ccb: dstadr 0.0.0.0, callid 18, port 0, 

                  codec 65535, moh_en 0, moh_addr 0.0.0.0

  *Jan 13 13:13:30.023: moh_update_rtp: callID 17 dstCallID 18

  *Jan 13 13:13:30.079: moh_process_ccb: dstadr 142.102.65.6, callid 18, port 
23552, 

                  codec 5, moh_en 0, moh_addr 0.0.0.0

  *Jan 13 13:13:30.079: moh_update_rtp: callID 17 dstCallID 18

  *Jan 13 13:13:31.391: %ISDN-6-CONNECT: Interface Serial0/1/0:2 is now 
connected to 911 N/A

  *Jan 13 13:13:31.395: moh_update_rtp: callID 17 dstCallID 18

  *Jan 13 13:13:31.395: moh_process_ccb: dstadr 142.102.65.6, callid 18, port 
23552, 

                  codec 5, moh_en 0, moh_addr 0.0.0.0

  *Jan 13 13:13:31.399: moh_update_rtp: callID 17 dstCallID 18

  *Jan 13 13:13:33.103: moh_update_rtp: callID 17 dstCallID 18

  *Jan 13 13:13:33.103: moh_update_rtp: callID 17 dstCallID 18

  *Jan 13 13:13:33.103: moh_update_rtp: callID 17 dstCallID 18

  *Jan 13 13:13:33.119: moh_update_rtp: callID 17 dstCallID 18

  *Jan 13 13:13:33.139: moh_process_ccb: dstadr 239.1.1.3, callid 18, port 
16384, 

                  codec 16, moh_en 0, moh_addr 0.0.0.0

  *Jan 13 13:13:33.139: moh_process_ccb:multicast addr add_ccb

  *Jan 13 13:13:33.139: moh_add_ccb: ip addr 239.1.1.3 port 16384 callid 18

  *Jan 13 13:13:33.139: moh_add_ccb: vmccb does not exists - creating a 

                          new one for 239.1.1.3 through IGMP

  *Jan 13 13:13:33.139:  moh_join_group_command called for 239.1.1.3

  *Jan 13 13:13:33.139: moh_join_group_command: Looking at valid idb's to 
configure 239.1.1.3

  *Jan 13 13:13:33.139: moh_join_group_command: IGMP API on group 239.1.1.3 idb 
Se0/0/0.201

  *Jan 13 13:13:33.139: moh_join_group_command: IGMP API on group 239.1.1.3 idb 
Vl102

  *Jan 13 13:13:33.139: moh_create_session: called

  *Jan 13 13:13:33.139:  moh_create_session : dstadr 239.1.1.3 does not exist - 
creating a                        control block

  *Jan 13 13:13:33.139: 
moh_insert_multicast_hashtable:moh_insert_multicast_hashtable buc 2

  *Jan 13 13:13:33.139: moh_create_session : Created a new vmccb for 239.1.1.3

  *Jan 13 13:13:33.139: moh_send_join: Looking at valid idb's to configure 
239.1.1.3

  *Jan 13 13:13:33.139: moh_add_ccb: Done inserting CCB for 239.1.1.3

  *Jan 13 13:13:33.139: moh_update_rtp: callID 17 dstCallID 18

  *Jan 13 13:13:36.091: moh_update_rtp: callID 17 dstCallID 18

  *Jan 13 13:13:36.091: moh_update_rtp: callID 17 dstCallID 18

  *Jan 13 13:13:36.091: update_stream_info: stream_flag Reset

  *Jan 13 13:13:36.091: moh_update_rtp: callID 17 dstCallID 18

  *Jan 13 13:13:36.091: update_stream_info: stream_flag Reset

  *Jan 13 13:13:36.115: moh_update_rtp: callID 17 dstCallID 18

  *Jan 13 13:13:36.115: update_stream_info: stream_flag Reset

  *Jan 13 13:13:36.183: moh_process_ccb: dstadr 142.102.65.6, callid 18, port 
24164, 

                  codec 5, moh_en 1, moh_addr 239.1.1.3

  *Jan 13 13:13:36.183: moh_process_ccb:multicast addr delete_ccb call id 18

                                    moh_call_id 18

  *Jan 13 13:13:36.183: moh_delete_ccb: called dstadr 239.1.1.3, callid 18

  *Jan 13 13:13:36.183: moh_delete_ccb_ext:called dstadr 239.1.1.3, callid 18

  *Jan 13 13:13:36.183: moh_delete_ccb_ext:ipaddr 239.1.1.3 callid 18

  *Jan 13 13:13:36.183: moh_delete_ccb_ext : Deleted the ccb entry

  *Jan 13 13:13:36.183: moh_leave_group_command called for 239.1.1.3

  *Jan 13 13:13:36.183: moh_remove_group: called for 239.1.1.3

  *Jan 13 13:13:36.183: moh_remove_group Leaving 239.1.1.3

  *Jan 13 13:13:36.187: moh_remove_group Leaving 239.1.1.3

  *Jan 13 13:13:36.195: moh_delete_session : Freed up vmccb for 239.1.1.3

  *Jan 13 13:13:36.195: moh_update_rtp: callID 17 dstCallID 18

  *Jan 13 13:13:37.427: moh_update_rtp: callID 17 dstCallID 18

  *Jan 13 13:13:37.439: moh_update_rtp: callID 17 dstCallID 18

   

  Thanks

  Narinder

   

   

   

   



------------------------------------------------------------------------------
  CONFIDENTIALITY - The information contained in this electronic mail message 
is confidential and is intended solely for the addressee(s). If you are not an 
authorised recipient of this message please contact Getronics Australia 
immediately by reply email and destroy/delete this message from your computer. 
Any unauthorised form of reproduction of this message, or part thereof, is 
strictly prohibited.
  DISCLAIMER - Unless specifically indicated otherwise, the views and opinions 
expressed in this email are those of the sender and not Getronics Australia. 
While we endeavour to protect our network from computer viruses, Getronics 
Australia does not warrant that this email or any attachments are free of 
viruses or any other defects or errors. It is the duty of the recipient to 
virus scan and otherwise test any information contained in this email before 
loading onto any computer system.

Reply via email to