CME Fails on cfwd noan to CUE with Disconnect Cause 41

[r.stockton]

I have a multi-site, multi-cme deployment.

CME versions 7.x

Site A: CME/CUE

Site B: CME/CUE

Site C: CME - uses Site B CUE

Among other things :), intermittently, calls are failing to VM on calls directed to Site C: but fwd to Site B:

Calling Number = 313 (Site B:)

Called Number = 777

call-forward noan *400 timeout 3 (3 for testing, 14 live)

Ext. 400 resides on Site B:

Ext direct-to-VM number is *400

When setting call-fwd all *400 I am unable to repeat the issue

When setting cfwd-noan *400 I will hear ring busy sometimes.

voice service voip

allow-connections h323 to h323

allow-connections h323 to sip

allow-connections sip to h323

no supplementary-service h450.3

supplementary-service h450.12

!

ephone-dn 55 dual-line

number 777

label Loans

description Loans

name Loans

preference 1

call-forward noan *400 timeout 3

huntstop channel

no huntstop

!

I have attached output showing the output of deb ccsip messages. Note the disconnect cause code on the bad call. The good call was placed one minute later.

So, I guess the best question is...how to troubleshoot disconnect cause 41?

Thanks!

[Nicholas Matthews]

The debugs is actually just the CDR output, so it doesn't help much.

I'm guessing you're running CME between the routers?

Have you tried adding this to both:

voice service voip

no supp sip refer

no supp sip moved

allow-connections sip-to-sip

-nick

[paolo bevilacqua]

There is no debug ccsip message in the attachment.

[r.stockton]

oops, debugs included this time.

Can you describe the logic of the following:

no supp sip refer

no supp sip moved

Also, should SIP to SIP be on both CMEs?

[paolo bevilacqua]

Before I read further, for voicemail CME C uses IP address of CUE B, not CME B, correct ?

[r.stockton]

Correct. Site C used CUE IP address.

[r.stockton]

This may be dsp related since g.729 is being transcoded for VM. Trying to figure out how to prove this, though....