Thanks a bunch to all, I found the error, I ran the sho sccp comamnd and found the problem:
BR2-RTR#sho sccp SCCP Admin State: UP Gateway IP Address: 10.1.202.1, Port Number: 2000 IP Precedence: 5 User Masked Codec list: None Call Manager: 10.1.202.1, Port Number: 2000 Priority: N/A, Version: 3.1, Identifier: 1 Transcoding Oper State: ACTIVE_IN_PROGRESS - Cause Code: CCM_REGISTER_FAILED Active Call Manager: 10.1.202.1, Port Number: 2000 TCP Link Status: NOT_CONNECTED, Profile Identifier: 1 BR2-RTR#sho dsp profile 1 Dspfarm Profile Configuration Profile ID = 1, Service = TRANSCODING, Resource ID = 1 Profile Description : Profile Admin State : UP Profile Operation State : ACTIVE IN PROGRESS Application : SCCP Status : ASSOCIATION IN PROGRESS Resource Provider : FLEX_DSPRM Status : UP I then changed the CCM address to the lopback0 address that i used for CCME and everthing worked R2-RTR#sho sccp SCCP Admin State: UP Gateway IP Address: 10.1.202.1, Port Number: 2000 IP Precedence: 5 User Masked Codec list: None Call Manager: 172.1.102.1, Port Number: 2000 Priority: N/A, Version: 3.1, Identifier: 1 Transcoding Oper State: ACTIVE - Cause Code: NONE Active Call Manager: 172.1.102.1, Port Number: 2000 TCP Link Status: CONNECTED, Profile Identifier: 1 ________________________________ From: Ryan Trauernicht <[email protected]> To: Chris Parker <[email protected]> Cc: Tony reyes <[email protected]>; James Key <[email protected]>; [email protected] Sent: Monday, December 22, 2008 9:00:43 PM Subject: Re: [OSL | CCIE_Voice] troubleshooting calls forwarded to CUE I dont see codec G729br8 in there. That is the codec Call Manager uses for G729. You did get the "call-forward pattern .T" which is good, but the codec is missing. Thanks, Ryan Trauernicht On Mon, Dec 22, 2008 at 6:33 PM, Chris Parker <[email protected]> wrote: What do you see when you type show sccp? Chris ________________________________ From: Tony reyes <[email protected]> Sent: Monday, December 22, 2008 5:28 PM To: James Key <[email protected]>; [email protected] Subject: Re: [OSL | CCIE_Voice] troubleshooting calls forwarded to CUE yep have both configured as shown below ...been looking at config fro a while and at ths point was looking for any troublshooitng steps i may be abe to use to find the issue here. sccp local FastEthernet0/0.210 sccp ccm 10.1.202.1 identifier 1 sccp ! sccp ccm group 1 associate ccm 1 priority 1 associate profile 1 register mtp0015f9de54a0 ! dspfarm profile 1 transcode codec g711ulaw codec g711alaw codec g729r8 maximum sessions 4 associate application SCCP Then under telephony-service Telephony-service sdspfarm units 1 sdspfarm transcode sessions 4 sdspfarm tag 1 mtp0015f9de54a0 voicemail 3600 call-forward pattern .T ephone-dn 1 dual-line number 3001 no-reg both description 3313213001 name BR2 Phone 1 call-forward busy 3600 call-forward noan 3600 timeout 10 Thanks in advance. Tony ________________________________ From: James Key <[email protected]> To: Tony reyes <[email protected]>; [email protected] Sent: Monday, December 22, 2008 4:10:29 PM Subject: RE: [OSL | CCIE_Voice] troubleshooting calls forwarded to CUE Tony, A couple of things. Make sure you have an xcoder defined on the CME router. Also make sure that you have call forward pattern and transfer pattern configured under Telephony service. James From:[email protected] [mailto:[email protected]] On Behalf Of Tony reyes Sent: Monday, December 22, 2008 4:03 PM To: [email protected] Subject: [OSL | CCIE_Voice] troubleshooting calls forwarded to CUE I'm trying to get the CS phones to leave a message at BR 2/CME CUE site and getting a fast busy when the call is forwarded at BR2 to CUE. BR 2 phones to BR2 phones messages work fine along with MWI, CM/CS calls to BR2/CME site calls work, but CS/CM phones get fast busy when going to CUE VM? Any useful commands that can help me troubleshoot where the issue lies here? Thanks in advance for the help. Tony NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies.
