voip dial-peer got busied out without reason

indian567 · ‎04-21-2016

Hello,

voip dial-peer get busied out despite of that the sip option ping got responses from CUCM (v8.6) within 1 second. Is there any reason for that? Or mistake in configuration?

The second problem is that once the dial-peer 1250 got busied out, the second dial-peer 1255 is not selected and the call ends

c2900-universalk9-mz.SPA.152-4.M7

CISCO2921/K9

dial-peer configuration:

dial-peer voice 1250 voip
permission term
description SIP server
preference 4
destination-pattern [2-7].......$
monitor probe icmp-ping
session protocol sipv2
session target ipv4:X.X.X.200
voice-class codec 1
voice-class sip profiles 1000
voice-class sip options-keepalive
dtmf-relay rtp-nte

dial-peer voice 1255 voip
permission term
description SIP server
huntstop
preference 5
destination-pattern [2-7].......$
monitor probe icmp-ping
session protocol sipv2
session target ipv4:X.X.X.72
voice-class codec 1
voice-class sip profiles 1000
voice-class sip options-keepalive
dtmf-relay rtp-nte

SIP trace:

(several same sent/received messages are exchanged prior to this output, all responses are within 1 second)

Apr 21 09:46:47.243 UTC: //809744/000000000000/SIP/Msg/ccsipDisplayMsg:
Sent:
OPTIONS sip:X.X.X.200:5060 SIP/2.0
Via: SIP/2.0/UDP X.X.X.199:5060;branch=z9hG4bK982CF26EE
From: <sip:X.X.X.199>;tag=B03DDF74-A73
To: <sip:X.X.X.200>
Date: Thu, 21 Apr 2016 09:46:47 GMT
Call-ID: CC5A9731-6DC11E6-874FEC69-4594C0FA@X.X.X.199
User-Agent: Cisco/v14 r1/ptn02
Max-Forwards: 70
CSeq: 101 OPTIONS
Contact: <sip:X.X.X.199:5060>
Content-Length: 0

Apr 21 09:46:47.743 UTC: %SIP-5-DIALPEER_STATUS: VoIP dial-Peer <81> is Busied out

Apr 21 09:46:47.899 UTC: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP X.X.X.199:5060;branch=z9hG4bK982CF26EE
From: <sip:X.X.X.199>;tag=B03DDF74-A73
To: <sip:X.X.X.200>;tag=957248771
Date: Thu, 21 Apr 2016 09:46:47 GMT
Call-ID: CC5A9731-6DC11E6-874FEC69-4594C0FA@X.X.X.199
CSeq: 101 OPTIONS
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
Content-Length: 0

ptn02# sh dial- voic sum | i 125
1250 voip up up [2-7].......$ 4 syst ipv4:X.X.X.200 busyout
1255 voip up up [2-7].......$ 5 syst ipv4:X.X.X.72 active

Any idea is more than welcome

Thanks

MOHIT SINGH · ‎04-21-2016

Hi,

The operation status of dial peer is still "UP" so i don't think router will use another dial peer even though keep alive is "busyout". Apart from Options Ping if you want to use other dial peer for failover then you can change SIP to use TCP (session transport TCP) or/and configure "retry invite 3" under "sip-ua".

indian567 · ‎04-21-2016

Hi Mohit,

thanks for quick answer. As I know, the "sip options-keepalive" technique is mainly used for redundancy support, so once the dial peer is busied-out, the second dial-peer should be matched immediately to minimize the delay. So that's why the "busy-out" state was introduced - as described in e.g. https://supportforums.cisco.com/discussion/12514401/will-keepalive-option-be-available-voip-gateway-without-cube or https://supportforums.cisco.com/document/12538231/ios-sip-options-ping

I can remove the "sip options-keepalive" but then the dial-peer goes down only when the new call setup is requested - and it's too late and takes some time due to "retry invite" mechanism.

MOHIT SINGH · ‎04-21-2016

Hi,

I am not sure when Options Ping will mark Operation state as "Down". You can enable TCP for SIP if you don't want delay due to retry invite. If primary server is not available then TCP handshake will fail and calls will be routed using next dial peer.

indian567 · ‎04-21-2016

Hi,

as I understand, Option Ping just changes the keepalive to busyout but the Op state remains Up. But that busyout should cause that the dial-peer won't be selected.

Anyway, your suggestion would probably solve the issue ;)

But I still don't understand that behavior - why the dial-peer gets busyout if the sip option gets responses? Why the second dial-peer 1255 is not selected? May it be related to IOS (bug?) ?

Thanks for your time, really appreciate it.

MOHIT SINGH · ‎04-21-2016

Hello,

Can you share complete logs for dial peer busyout and call failure? For the calls not selecting 1255 i would need below debugs

debug ccsip message

debug ccsip error

debug voip ccapi inout

indian567 · ‎04-27-2016

Hello,

sorry for delay, the issue didn't happen until now.

Finally it happened yesterday so the trace is attached. Strange is that the issue happens any time.

Thanks for your time

MOHIT SINGH · ‎04-27-2016

Hello,

In the logs i can see dial peer was marked busy out due to max retries but the Options Ping was sent only once.

Apr 26 15:39:44.161 UTC: //831433/000000000000/SIP/Error/act_sent_OODoptions_wait_response:
Out of retries

+ Why have you configured "monitor probe icmp-ping" under same dial peer when you have SIP options enabled? I believe they both can mark dial peer down. If you are not using "monitor probe icmp-ping" then can you remove it and test.

http://www.cisco.com/c/en/us/td/docs/ios/voice/command/reference/vr_book/vr_c3.html

http://www.cisco.com/c/en/us/td/docs/ios/voice/cube/configuration/guide/vb_book/vb_book/vb_9321.html

indian567 · ‎05-05-2016

Hello,

finally got some new traces, see attachment. I removed the "monitor probe icmp-ping" command from dial-peer, but the dial peer still gets to busyout state, see attachment.

Thanks for your time.