cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
8517
Views
5
Helpful
4
Replies

Log on Voice Gateway %SIP-3-BADPAIR: Unexpected event 38 (SIPSPI_EV_CC_OPTIONS_RESP) in state 9 (STATE_DISCONNECTING) substate 0 (SUBSTATE_NONE)

johntim20
Level 1
Level 1

Hi All

I have been receiving this logs on my H.323 Voice Gateway 3945 IOS Version 15.0(1)M1, RELEASE SOFTWARE (fc1), having SIP Trunk from Service Provider and CUCM 7.1.5 Pub and Sub.At the moment i dont face any calling issues and Please let me know the required action for this logs.Thanks in advance.

*Mar 28 06:05:04.014: %SIP-3-BADPAIR: Unexpected event 38 (SIPSPI_EV_CC_OPTIONS_RESP) in state 9 (STATE_DISCONNECTING) substate 0 (SUBSTATE_NONE)

*Mar 31 06:04:11.284: %SIP-3-BADPAIR: Unexpected event 31 (SIPSPI_EV_CC_MEDIA_XCODE) in state 9 (STATE_DISCONNECTING) substate 0 (SUBSTATE_NONE)

*Mar 31 10:41:53.555: %SIP-3-BADPAIR: Unexpected event 38 (SIPSPI_EV_CC_OPTIONS_RESP) in state 9 (STATE_DISCONNECTING) substate 0 (SUBSTATE_NONE)

*Apr  1 06:51:16.182: %SIP-3-BADPAIR: Unexpected event 31 (SIPSPI_EV_CC_MEDIA_XCODE) in state 9 (STATE_DISCONNECTING) substate 0 (SUBSTATE_NONE)

*Apr  1 06:51:21.298: %SIP-3-BADPAIR: Unexpected event 31 (SIPSPI_EV_CC_MEDIA_XCODE) in state 9 (STATE_DISCONNECTING) substate 0 (SUBSTATE_NONE)

*Apr  1 06:59:33.602: %SIP-3-BADPAIR: Unexpected event 31 (SIPSPI_EV_CC_MEDIA_XCODE) in state 9 (STATE_DISCONNECTING) substate 0 (SUBSTATE_NONE)

*Apr  1 11:41:21.621: %SIP-3-BADPAIR: Unexpected event 38 (SIPSPI_EV_CC_OPTIONS_RESP) in state 9 (STATE_DISCONNECTING) substate 0 (SUBSTATE_NONE)

*Apr  2 06:33:58.120: %SIP-3-BADPAIR: Unexpected event 31 (SIPSPI_EV_CC_MEDIA_XCODE) in state 9 (STATE_DISCONNECTING) substate 0 (SUBSTATE_NONE)

*Apr  2 08:12:40.160: %SIP-3-BADPAIR: Unexpected event 38 (SIPSPI_EV_CC_OPTIONS_RESP) in state 9 (STATE_DISCONNECTING) substate 0 (SUBSTATE_NONE)

*Apr  2 11:45:17.703: %SIP-3-BADPAIR: Unexpected event 38 (SIPSPI_EV_CC_OPTIONS_RESP) in state 9 (STATE_DISCONNECTING) substate 0 (SUBSTATE_NONE)

*Apr  3 08:26:12.206: %SIP-3-BADPAIR: Unexpected event 38 (SIPSPI_EV_CC_OPTIONS_RESP) in state 9 (STATE_DISCONNECTING) substate 0 (SUBSTATE_NONE)

*Apr  3 08:42:08.621: %SIP-3-BADPAIR: Unexpected event 38 (SIPSPI_EV_CC_OPTIONS_RESP) in state 9 (STATE_DISCONNECTING) substate 0 (SUBSTATE_NONE)

*Apr  4 12:03:32.667: %SIP-3-BADPAIR: Unexpected event 38 (SIPSPI_EV_CC_OPTIONS_RESP) in state 9 (STATE_DISCONNECTING) substate 0 (SUBSTATE_NONE)

*Apr  8 07:47:39.524: %SIP-3-BADPAIR: Unexpected event 38 (SIPSPI_EV_CC_OPTIONS_RESP) in state 9 (STATE_DISCONNECTING) substate 0 (SUBSTATE_NONE)

*Apr  8 08:26:40.692: %SIP-3-BADPAIR: Unexpected event 31 (SIPSPI_EV_CC_MEDIA_XCODE) in state 9 (STATE_DISCONNECTING) substate 0 (SUBSTATE_NONE)

*Apr  8 09:41:02.079: %SIP-3-BADPAIR: Unexpected event 38 (SIPSPI_EV_CC_OPTIONS_RESP) in state 9 (STATE_DISCONNECTING) substate 0 (SUBSTATE_NONE)

*Apr  8 09:43:18.279: %SIP-3-BADPAIR: Unexpected event 38 (SIPSPI_EV_CC_OPTIONS_RESP) in state 9 (STATE_DISCONNECTING) substate 0 (SUBSTATE_NONE)

1 Accepted Solution

Accepted Solutions

HI

It is "harmless" as in it does not effect the Gateway. However for the call in question, that EVENT will be "dropped".

The BADPAIR message is benign.  It just let's us know we received an event we cannot

process at that time.

To see the actual cause of the BADPAIR message we would need the entire debugs

(ccsip all) of the session in question when there is an error with  %SIP-3-BADPAIR.

Unless you are currently experiencing voice issues, these messages can be safely ignored.

My be this can be un resoveld bug

http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCsg56740

Regards

Ronak patel

Please rate helpful posts by clicking stars below the answer.

Regards Ronak Patel Rate all helpful post by clicking stars below the answer.

View solution in original post

4 Replies 4

johntim20
Level 1
Level 1

Dear All could any one knows about this logs is it a bug or transcoder issues please provide me some solution to tackle this log.

HI

It is "harmless" as in it does not effect the Gateway. However for the call in question, that EVENT will be "dropped".

The BADPAIR message is benign.  It just let's us know we received an event we cannot

process at that time.

To see the actual cause of the BADPAIR message we would need the entire debugs

(ccsip all) of the session in question when there is an error with  %SIP-3-BADPAIR.

Unless you are currently experiencing voice issues, these messages can be safely ignored.

My be this can be un resoveld bug

http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCsg56740

Regards

Ronak patel

Please rate helpful posts by clicking stars below the answer.

Regards Ronak Patel Rate all helpful post by clicking stars below the answer.

Thanks for your support i really appreciate it i would like to know how to find out this "BugID"

Hi John,

You can use Cisco bug tool

http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs

Regards

Ronak patel

Plese rate helpful posts.

Regards Ronak Patel Rate all helpful post by clicking stars below the answer.