Inbound calls to internal ext. not forwarding to voicemail

[James Boothe]

My current setup

Sip provider --------------- h323 gateway---------------CUCM 8 --- Unity connection 8

My sip trunk is registered with provider on the gateway and h323 communication is working to CUCM.

Inbound sip calls works correctly dialing a internal extension however it will not forward to the users voicemail. The call just continues to ring.

Internal calls to another extension will correclty forward to the users voicemail after the expected no answer timer expires.

Any ideas where to start searching. When i get to a different workstation i will provide debugs if nessacary.

[Jaime Valencia]

Do you have the CFNA and CFB external configured for the phones?

HTH

java

If this helps, please rate

www.cisco.com/go/pdihelpdesk

[James Boothe]

Yes i do have those fields correctly set for voicemail

[Brandon Buffin]

Try this command on the gateway terminating the SIP trunk.

voice service voip

no supplementary-service sip moved-temporarily

Hope this helps.

Brandon

[dksingh]

I doubt if that command on CUBE will help as CCM

does not support H.450. And moreover the

forwarded call from CUCM should not be hitting the

CUBE anyway so I don't see how/where CUBE is

going to get a SIP 3XX msg. I'd think that

CFB/CFNA shd be handled internally on CUCM and

the h323 and SIP leg should not be disturbed.

Is MTP in use on the h323 GW/trunk ?

I think the fact that external call keeps ringing, indicates

that the CFB/CFNA is not kicking in.

Perhaps a review of CCM trace will point us in the right

direction.

[Jaime Valencia]

Have you tried CFA just for testing?

HTH

java

If this helps, please rate

www.cisco.com/go/pdihelpdesk

[James Boothe]

No MTP is not in use. I will work on getting the CCM trace.

I also tried routing the calls from gateway to a CTI route point that has CFA sent straight to voicemail and get the same result from the external call will just continue to hear ringing.

[akinsconsult]

Did you resolve this? We have the same issue.

[Marwan ALshawi]

if you have same issue

can you try adding the Gateway as SIP gateway not H323 to make the CM as th eprotocol trnslator

SIP ----SIP/CUBE----SIP--CM---VM

and see if it dose work or not

[jboothe]

I did resolve this...i clicked the media termination point required check box on the gateway configuration page.

Hope this helps

Jim Boothe, CCNA