07-04-2025 01:55 AM - edited 07-04-2025 02:00 AM
if a call received to pilot number it will play prompt at unity connection . if the caller accept option to ring at reception it ring there and if no answer it should forward to mobile number. what happens is that it get forwarded and call get received at mobile but immediately get disconnected before answering. no ringing only shows miss call
Gateway is H323 gateway.
if im calling extension to extension that is extension to reception it is working fine. if the call is coming from pstn external this issue happening.
What could be the reason.
i have set calling party selection as "External first Number" for gateway in cucm but result is the same as originator.
if i selected check box for Redirect number IE delivery - outbound no redirect call getting received at h323 gateway itself
Call flow:
caller from PSTN calling pilot number ---> PRI line -- > H323 Gateway --> Cucm --> unity connection --> Reception phone--> 10 sec no answer --> forward to mobile --> H323 Gateway
Jul 3 14:12:26.458: ISDN Se0/1/0:15 Q931: RX <- SETUP pd = 8 callref = 0x6CEF
Bearer Capability i = 0x8090A3
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA9838C
Exclusive, Channel 12
Progress Ind i = 0x8281 - Call not end-to-end ISDN, may have in-band info
Calling Party Number i = 0x2183, '24786786'
Plan:ISDN, Type:National
Called Party Number i = 0xC1, '4369494'
Plan:ISDN, Type:Subscriber(local)
Sending Complete
Jul 3 14:12:26.458: ISDN Se0/1/0:15 Q931: Received SETUP callref = 0xECEF callID = 0x0AE3 switch = primary-net5 interface = User
Jul 3 14:12:26.470: ISDN Se0/1/0:15 Q931: TX -> CALL_PROC pd = 8 callref = 0xECEF
Channel ID i = 0xA9838C
Exclusive, Channel 12
Jul 3 14:12:26.482: ISDN Se0/1/0:15 Q931: TX -> CONNECT pd = 8 callref = 0xECEF
Jul 3 14:12:26.594: ISDN Se0/1/0:15 Q931: RX <- CONNECT_ACK pd = 8 callref = 0x6CEF
Jul 3 14:12:53.830: ISDN Se0/1/0:15 Q931: Applying typeplan for sw-type 0x12 is 0x0 0x0, Calling num 4269393
Jul 3 14:12:53.830: ISDN Se0/1/0:15 Q931: Sending SETUP callref = 0x2D01 callID = 0xAA0C switch = primary-net5 interface = User
Jul 3 14:12:53.834: ISDN Se0/1/0:15 Q931: TX -> SETUP pd = 8 callref = 0x2D01
Bearer Capability i = 0x8090A3
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98381
Exclusive, Channel 1
Display i = '24786786'
Calling Party Number i = 0x0081, '4369494'
Plan:Unknown, Type:Unknown
Called Party Number i = 0x80, '0603285444'
Plan:Unknown, Type:Unknown
Jul 3 14:12:53.866: ISDN Se0/1/0:15 Q931: RX <- STATUS pd = 8 callref = 0xAD01
Cause i = 0x82E328 - Information element not implemented
Call State i = 0x01
Jul 3 14:12:53.974: ISDN Se0/1/0:15 Q931: RX <- SETUP_ACK pd = 8 callref = 0xAD01
Channel ID i = 0xA98381
Exclusive, Channel 1
Jul 3 14:12:55.710: ISDN Se0/1/0:15 Q931: RX <- CALL_PROC pd = 8 callref = 0xAD01
Progress Ind i = 0x8288 - In-band info or appropriate now available
Jul 3 14:12:55.750: ISDN Se0/1/0:15 Q931: TX -> DISCONNECT pd = 8 callref = 0x2D01
Cause i = 0x80AF - Resource unavailable, unspecified
Jul 3 14:12:55.770: ISDN Se0/1/0:15 Q931: RX <- ALERTING pd = 8 callref = 0xAD01
Progress Ind i = 0x8288 - In-band info or appropriate now available
Jul 3 14:12:55.770: ISDN Se0/1/0:15 **ERROR**: Ux_BadMsg: Invalid Message for call state 11, call id 0xAA0C, call ref 0x2D01, event 0x1
Jul 3 14:12:55.770: ISDN Se0/1/0:15 Q931: TX -> STATUS pd = 8 callref = 0x2D01
Cause i = 0x80E201 - Message not compatible with call state or not implemented
Call State i = 0x0B
Jul 3 14:12:55.794: ISDN Se0/1/0:15 Q931: RX <- RELEASE pd = 8 callref = 0xAD01
Cause i = 0x0080AF - Resource unavailable, unspecified
Jul 3 14:12:55.798: ISDN Se0/1/0:15 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x2D01
Jul 3 14:13:02.810: ISDN Se0/1/0:15 Q931: RX <- DISCONNECT pd = 8 callref = 0x6CEF
Cause i = 0x028090 - Normal call clearing
Jul 3 14:13:02.810: ISDN Se0/1/0:15 Q931: TX -> RELEASE pd = 8 callref = 0xECEF
Jul 3 14:13:02.890: ISDN Se0/1/0:15 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x6CEF
07-04-2025 02:00 AM - edited 07-06-2025 03:44 AM
any help will be much appreciated,
what could be the reson
07-08-2025 03:40 AM
Hello,
The snippet that you shared shows the following messages:
Jul 3 14:12:55.750: ISDN Se0/1/0:15 Q931: TX -> DISCONNECT pd = 8 callref = 0x2D01
Cause i = 0x80AF - Resource unavailable, unspecified
Jul 3 14:12:55.770: ISDN Se0/1/0:15 Q931: RX <- ALERTING pd = 8 callref = 0xAD01
Progress Ind i = 0x8288 - In-band info or appropriate now available
Jul 3 14:12:55.770: ISDN Se0/1/0:15 **ERROR**: Ux_BadMsg: Invalid Message for call state 11, call id 0xAA0C, call ref 0x2D01, event 0x1
Jul 3 14:12:55.770: ISDN Se0/1/0:15 Q931: TX -> STATUS pd = 8 callref = 0x2D01
Cause i = 0x80E201 - Message not compatible with call state or not implemented
Call State i = 0x0B
Jul 3 14:12:55.794: ISDN Se0/1/0:15 Q931: RX <- RELEASE pd = 8 callref = 0xAD01
Cause i = 0x0080AF - Resource unavailable, unspecified
Jul 3 14:12:55.798: ISDN Se0/1/0:15 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x2D01
Jul 3 14:13:02.810: ISDN Se0/1/0:15 Q931: RX <- DISCONNECT pd = 8 callref = 0x6CEF
Cause i = 0x028090 - Normal call clearing
It seems that the call was disconnected because the codec negotiation failed; therefore, the "Resource unavailable". Can you check if the calls affected by this issue have "disconnect cause 47" when you run "show call history voice brief"?
07-22-2025 11:54 AM
there is not such command like show call history voice brief? can you please tell what is the exact command? what you mentioned is wrong.
07-22-2025 12:21 PM
What version of IOS are you using? That command does exist, see this link. https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/voice/vcr4/vcr4-cr-book/vcr-s4.html#wp1325748940
07-22-2025 12:25 PM
yes. sorry person didnt entered the command properly. i cannot see the "disconnect cause" but there is 47
07-08-2025 06:48 AM
Hi @jaheshkhan ,
The issue where calls forwarded to mobile disconnect immediately from external PSTN calls via the H323 gateway usually points to the gateway mishandling forwarded call signaling or lacking resources.
Check the following:
Ensure the H323 gateway supports Redirect/Forward Number info correctly.
Verify calling party and redirect number settings in CUCM and Unity.
Confirm the gateway has enough voice channels available.
Review dial plan and number transformations for the mobile number.
The Resource unavailable error suggests the gateway may reject forwarded calls due to missing info or insufficient resources.
Updating gateway firmware and enabling detailed call traces can help identify the root cause.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide