No Answer timeout issue

[CSCO12111341]

Hello All,

I am facing with wierd issue with no answer timeout in CUCM 9.1.2. In service parameters is change default value to of this timer to 30 seconds. Same value I set up under DN configuration but for all phone which are under one specific Device Pool (Rotterdam) it ignore this value and incoming call is forwarded to VM or dropped after 12 seconds. Phones which are in different device pool (Bratislava) accept no answer timeout whcih I specified and phone is ringing after 12 second without any problem.

Have you ever met with this?

Thank you in advance.

[Chris Deren]

Are those phones registered to different CUCM sub?

Make sure your CUCM database replication is in healthy state.

Have you rebooted the phones to see if that resolves it?

[CSCO12111341]

Hello Chris,

phones are registered to same CUCM sub. CUCM database replication is good. I have reloaded phones several times but it didn't help.

Actulaly we moved this location from ISDN to new SIP trunk. Could it be related to thsi problem?

After 12 seconds I can hear: "Call cannot be complated at this time please call later"

[Chris Deren]

So, does the phone ring for 12 seconds and them you hear the message?

Or it never rings at all?

Can you provide "debug ccsip messages" from CUBE?

[CSCO12111341]

It is ringing and you can answer that call within 12 second without any problem but after that 12 second it is forwarded.

From debug you can see I am getting cancel message from CUCM to CUBE.

CANCEL sip:672@10.101.10.11 SIP/2.0
Via: SIP/2.0/UDP 10.101.33.242:5060;branch=z9hG4bK6B53A21B88
From: <sip:+XXXXXXXXXXXX@10.101.33.242>;tag=5876E74C-1212
To: <sip:672@10.101.10.11>
Date: Thu, 03 Dec 2015 14:14:06 GMT
Call-ID: F2CBC988-98FE11E5-8FA893C8-70F5B18A@10.101.33.242
CSeq: 101 CANCEL
Max-Forwards: 70
Timestamp: 1449152061
Reason: Q.850;cause=102
Content-Length: 0

[Carlo Poggiarelli]

Hi,

I would also check through routeplan report if there is another extension with the same number and check the value there.

Also check the T301 timer under service parameter if it has been modified.

T301 timer should be higher than RNA timeout.

Let us know

Regards

Carlo

[CSCO12111341]

Hello Carlo,

there is not other DN same to this one and T301 is set to 180000msec.

I would say that problem is with SIP provider from which we getting 408 Request Timeout. I will try to open trouble ticket with them.

[Carlo Poggiarelli]

Hi,

just to be sure... 

Can you please indicate the call flow?

You have the same issue if you call internally?

Are all IP phones on the same cluster?

Are IP phones having this issue, registered using sip or SCCP?

Thanks 

Regards

Carlo

[CSCO12111341]

Hello Chris,

problem was with ip rtcp report interval which was set up to 3000

Below is way how i fixed it.

https://supportforums.cisco.com/discussion/12564201/cancel-after-15-secounds-cube-if-call-itsp

[Carlo Poggiarelli]

Hi,

Under sevice parameter, did you check that the value of 30 seconds is configured on all servers?

Click on top right corner link "Parameters for all servers" to check.

Please let us know

HTH

Regards

Carlo

[CSCO12111341]

Yes it is configrued same way on both CUCMs