Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

Cisco Employee

Problems on vg200 with q931 Debuging on

I'm getting this error since we just changed carriers on our PRI this morning.

Can't seem to figure out what is causing it. We didn't have this error before.

*May 19 05:48:32 arizona: ISDN Se1/0:23: RX <- RELEASE pd = 8 callref = 0xD23C

*May 19 05:48:32 arizona: %ISDN-6-CALL_COLLISION: Interface Se1/0:23 Call Cid 0x

385E Cref 0x8126 collision on Channel 1 in_use_cid 0x385D cref 0x8126, Channel

awarded to the received call

3 REPLIES
Cisco Employee

Re: Problems on vg200 with q931 Debuging on

Also getting this message now...

*May 19 08:35:51 arizona: Redirecting Number i = 0x00008F, '8050'

*May 19 08:35:51 arizona: ISDN Se1/0:23: RX <- FACILITY pd = 8 callref = 0x0195

*May 19 08:35:51 arizona: Facility i = 0x9F8B0100A1080201010201008400

*May 19 08:35:51 arizona: ISDN Se1/0:23: Ux_BadMsg(): Invalid Message for call s

tate 9, call id 0x38DA, call ref 0x8195, event 0x62

*May 19 08:35:51 arizona: ISDN Se1/0:23: TX -> STATUS pd = 8 callref = 0x8195

*May 19 08:35:51 arizona: Cause i = 0x80E262 - Message not compatible wi

th call state or not implemented

*May 19 08:35:51 arizona: Call State i = 0x09

Cisco Employee

Re: Problems on vg200 with q931 Debuging on

Is your new service provider's ISDN switch type the same as the old one?

Cisco Employee

Re: Problems on vg200 with q931 Debuging on

Yes, we switched from dms100 to 5ess. I changed that on the vg200 (we are running h323.) and calls work in and out except for those errors.

129
Views
0
Helpful
3
Replies
CreatePlease login to create content