Buy or Renew
Buy or Renew
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
635
Views
2
Helpful
8
Replies

Cisco voice failure

Go to solution
haininghuang3185
Level 1
Level 1

‎07-31-2023 08:37 PM

The customer has two sites A and B. The current problem is that when site A calls site B, the phone rings, but the phone at site B will automatically hang up after being answered. It is normal for site B to call site A.

haininghuang3185_0-1690860881588.png

The customer has two sites A and B. The current problem is that when site A calls site B, the phone rings, but the phone at site B will automatically hang up after being answered. It is normal for site B to call site A.
The topology diagram is as follows: the H323 protocol configured by the CUCM at site B points to 10.10.210.1 (a voice router) at site A, the voice router at site A is also configured with the H323 protocol, and the session target ip is CUCM at site B (172.25.150.58)

What is the cause of this failure?

1 Accepted Solution

Accepted Solutions

Go to solution
b.winter
VIP
VIP
In response to haininghuang3185

‎08-01-2023 02:30 AM

With RTMT?! That's the most essential tool here.

Sorry to say that, but if you don't even know how to do basic troubleshooting in CUCM, it will be very hard to help you here, because you are probably missing basic skills and knowledge.

View solution in original post

0 Helpful
8 Replies 8

Go to solution
M02@rt37
VIP
VIP

‎07-31-2023 09:42 PM

Hello @haininghuang3185

Since phones ring then NO h323 issue.

Codec issue? Do Phone A and B have the same set of Codec ?

 

Best regards
.ı|ı.ı|ı. If This Helps, Please Rate .ı|ı.ı|ı.
0 Helpful

Go to solution
haininghuang3185
Level 1
Level 1
In response to M02@rt37

‎07-31-2023 09:56 PM

Phone A and B have the same set of Codec.

The failure occurred after the B Site SDWAN router was replaced. The customer replaced the B Site SDWAN router. The B Site SDWAN router only serves as the bearer of IP routing and has no related voice configuration. After the replacement, the voice registration device 10.10.210.1 at site A and the CUCM 172.25.150.58 at site B communicate normally on the network. However, when site A calls site B, the phone rings but cannot be answered and will automatically hang up.

0 Helpful

Go to solution
M02@rt37
VIP
VIP
In response to haininghuang3185

‎07-31-2023 10:10 PM

Thanks for that clarification.

Best regards
.ı|ı.ı|ı. If This Helps, Please Rate .ı|ı.ı|ı.
0 Helpful

Go to solution
b.winter
VIP
VIP
In response to M02@rt37

‎08-01-2023 12:58 AM

Typical symptom of a codec issue.
@haininghuang3185 Have you checked the call logs for such a call?

If you would have routing issues because of the network change, the call wouldn't work at all.

Go to solution
haininghuang3185
Level 1
Level 1
In response to b.winter

‎08-01-2023 01:26 AM

May I ask how to check the corresponding call logs on CUCM?

0 Helpful

Go to solution
Roger Kallberg
VIP
VIP
In response to haininghuang3185

‎08-01-2023 02:30 AM

Get the CallManager (SDL) logs with RTMT.



Response Signature


0 Helpful

Go to solution
b.winter
VIP
VIP
In response to haininghuang3185

‎08-01-2023 02:30 AM

With RTMT?! That's the most essential tool here.

Sorry to say that, but if you don't even know how to do basic troubleshooting in CUCM, it will be very hard to help you here, because you are probably missing basic skills and knowledge.

0 Helpful

Go to solution
haininghuang3185
Level 1
Level 1
In response to b.winter

‎08-01-2023 07:33 PM

The phone number of site A is 8141053, and the phone number of site B is 8149411
The following is the log of the call from site A to site B:

2023/08/02 09:38:06.915|CC|RELEASE|23748263|0|1
2023/08/02 09:38:07.779|CC|SETUP|23748257|23748258|8149411|18141053#|18141053#
2023/08/02 09:38:07.847|CC|OFFERED|23748257|23748258|8149411|18141053#|18141053#|SEP2C01B5E462FC|10.10.210.1
2023/08/02 09:38:12.416|SIPL|23748257|TCP|OUT|192.168.0.28|5060|SEP2C01B5E462FC|192.168.40.68|4841|1,100,14,317.3^10.10.210.1^*|3599310|be30aa00-06a6-4014-8872-dd55a32d0942|183 Session Progress
2023/08/02 09:38:14.161|SIPT|23748256|TCP|IN|192.168.0.28|5060|China_voice_gateway|192.168.0.68|5060|1,100,14,2.63579^192.168.0.68^*|3599314|302e0700-4c91b36f-fa65-1c00a8c0@192.168.0.28|200 OK
2023/08/02 09:38:14.169|SIPT|23748256|TCP|OUT|192.168.0.28|5060|China_voice_gateway|192.168.0.68|5060|1,100,14,2.63579^192.168.0.68^*|3599315|302e0700-4c91b36f-fa65-1c00a8c0@192.168.0.28|ACK
2023/08/02 09:38:14.171|SIPL|23748255|TCP|OUT|192.168.0.28|5060|SEP34F8E77BED68|192.168.40.51|4954|1,100,14,2.63579^192.168.0.68^*|3599316|4b511b3b-e205-471c-945a-6108aae2269f|200 OK
2023/08/02 09:38:14.171|SIPL|23748255|TCP|OUT|192.168.0.28|5060|SEP34F8E77BED68|192.168.40.51|4954|1,100,14,2.63579^192.168.0.68^*|3599317|4b511b3b-e205-471c-945a-6108aae2269f|SUBSCRIBE
2023/08/02 09:38:14.260|SIPL|23748255|TCP|IN|192.168.0.28|5060|SEP34F8E77BED68|192.168.40.51|4954|1,100,14,57.27066^192.168.40.51^*|3599318|4b511b3b-e205-471c-945a-6108aae2269f|ACK
2023/08/02 09:38:14.561|SIPL|23748255|TCP|IN|192.168.0.28|5060|SEP34F8E77BED68|192.168.40.51|4954|1,100,14,57.27067^192.168.40.51^*|3599319|4b511b3b-e205-471c-945a-6108aae2269f|200 OK
2023/08/02 09:38:14.571|SIPL|23748255|TCP|IN|192.168.0.28|5060|SEP34F8E77BED68|192.168.40.51|4954|1,100,14,57.27068^192.168.40.51^*|3599320|4b511b3b-e205-471c-945a-6108aae2269f|NOTIFY
2023/08/02 09:38:14.572|SIPL|23748255|TCP|OUT|192.168.0.28|5060|SEP34F8E77BED68|192.168.40.51|4954|1,100,14,57.27068^192.168.40.51^*|3599321|4b511b3b-e205-471c-945a-6108aae2269f|200 OK

The following is the log of the phone at site B calling the phone at site A:

2023/08/02 09:38:45.880|CC|SETUP|23748265|23748266|8149411|18141053#|18141053#
2023/08/02 09:38:45.970|CC|OFFERED|23748265|23748266|8149411|18141053#|18141053#|SEP2C01B5E462FC|10.10.210.1
2023/08/02 09:38:50.356|SIPL|23748265|TCP|OUT|192.168.0.28|5060|SEP2C01B5E462FC|192.168.40.68|4841|1,100,14,318.4^10.10.210.1^*|3599401|b8c50066-62e9-41ef-8e74-e3e7631041e6|180 Ringing
2023/08/02 09:38:50.783|SIPL|23748265|TCP|OUT|192.168.0.28|5060|SEP2C01B5E462FC|192.168.40.68|4841|1,100,14,319.7^10.10.210.1^Port 19760|3599402|b8c50066-62e9-41ef-8e74-e3e7631041e6|180 Ringing
2023/08/02 09:38:50.783|SIPL|23748265|TCP|OUT|192.168.0.28|5060|SEP2C01B5E462FC|192.168.40.68|4841|1,100,14,319.7^10.10.210.1^Port 19760|3599403|b8c50066-62e9-41ef-8e74-e3e7631041e6|SUBSCRIBE
2023/08/02 09:38:51.091|SIPL|23748265|TCP|IN|192.168.0.28|5060|SEP2C01B5E462FC|192.168.40.68|4841|1,100,14,71.28308^192.168.40.68^*|3599404|b8c50066-62e9-41ef-8e74-e3e7631041e6|200 OK
2023/08/02 09:38:51.131|SIPL|23748265|TCP|IN|192.168.0.28|5060|SEP2C01B5E462FC|192.168.40.68|4841|1,100,14,71.28309^192.168.40.68^*|3599405|b8c50066-62e9-41ef-8e74-e3e7631041e6|NOTIFY
2023/08/02 09:38:51.131|SIPL|23748265|TCP|OUT|192.168.0.28|5060|SEP2C01B5E462FC|192.168.40.68|4841|1,100,14,71.28309^192.168.40.68^*|3599406|b8c50066-62e9-41ef-8e74-e3e7631041e6|200 OK
2023/08/02 09:38:53.138|SIPL|23748265|TCP|OUT|192.168.0.28|5060|SEP2C01B5E462FC|192.168.40.68|4841|1,100,14,318.6^10.10.210.1^*|3599407|b8c50066-62e9-41ef-8e74-e3e7631041e6|200 OK
2023/08/02 09:38:53.226|SIPL|23748265|TCP|IN|192.168.0.28|5060|SEP2C01B5E462FC|192.168.40.68|4841|1,100,14,71.28310^192.168.40.68^*|3599408|b8c50066-62e9-41ef-8e74-e3e7631041e6|ACK
2023/08/02 09:39:00.971|SIPL|23748265|TCP|OUT|192.168.0.28|5060|SEP2C01B5E462FC|192.168.40.68|4841|1,100,14,318.8^10.10.210.1^*|3599421|b8c50066-62e9-41ef-8e74-e3e7631041e6|BYE
2023/08/02 09:39:00.987|SIPL|23748265|TCP|IN|192.168.0.28|5060|SEP2C01B5E462FC|192.168.40.68|4841|1,100,14,71.28311^192.168.40.68^*|3599422|b8c50066-62e9-41ef-8e74-e3e7631041e6|200 OK

0 Helpful
Customers Also Viewed These Support Documents