cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
904
Views
0
Helpful
4
Replies

Intercluster SIP trunk

nguzman
Level 1
Level 1

Hello All,

 

We have two CUCM version 12.0.1.22017-1. We configured a SIP trunk between these 2 CUCM. We are having issues when we tried to connect a call but the issue isjust in one path, the another path is working properly. 

 

Call flow working

CUCM01 -- SIP -- CUCM02

Call flow not working

CUCM02 -- SIP -- CUCM01

 

In the call that is not working we are seeing that the Digit Analysis didn't show any partitionSearchSpace() parameter.

 

82776913.001 |12:38:12.634 |AppInfo  |Digit Analysis: star_DaReq: daReq.partitionSearchSpace(), filteredPartitionSearchSpaceString(), partitionSearchSpaceString()

 

On the other hand, the flow that it's working is showing correctly the Digit Analysis

05965192.001 |12:25:41.956 |AppInfo  |Digit Analysis: star_DaReq: daReq.partitionSearchSpace(9b79e488-9708-cf8b-8076-b2c1039774a7), filteredPartitionSearchSpaceString(PT_MIAMI:PT_Toronto_Internal), partitionSearchSpaceString(PT_MIAMI:PT_Toronto_Internal)

 

On both sides the SIP Security Profile, SIP profiles and SIP trunk configuration is exactly the same. We validated the Partition and CSS and everything seems to be ok. 

 

When we moved the internal ext in the destination cluster to the default partition the call is connecting without any issue. Does anyone have any idea why this is happening? 

 

Cisco TAC was working on this and they recommended to restart the Call Manager service and if that doesn't work perform a full restart of all the cluster but I have some doubts about this fix.

 

 

 

4 Replies 4

Jonathan Schulenberg
Hall of Fame
Hall of Fame

Just to ask some of the basics:

- Have you reset the trunk on CUCMN01 where DA is failing?

- Does everything checkout at the platform level? Examples “utils dbreplication runtimestate” and “utils diagnose test”?

All looks good at platform level and yes we are reseting the SIP trunk everytime we try a new parameter on it.

Cluster Detailed View from BKMIACUCM01 (3 Servers):

PING DB/RPC/ REPL. Replication REPLICATION SETUP
SERVER-NAME IP ADDRESS (msec) DbMon? QUEUE Group ID (RTMT) & Details
----------- ---------- ------ ------- ----- ----------- ------------------
CUCM01 X.X.X.30 0.022 Y/Y/Y 0 (g_2) (2) Setup Completed
CUCM03 X.X.X.31 0.837 Y/Y/Y 0 (g_10) (2) Setup Completed
CUCM02 X.X.X.32 0.139 Y/Y/Y 0 (g_3) (2) Setup Completed

 


admin:utils diag
admin:utils diagnose test
admin:utils diagnose test

Log file: platform/log/diag2.log

Starting diagnostic test(s)
===========================
test - disk_space : Passed (available: 958 MB, used: 12723 MB)
skip - disk_files : This module must be run directly and off hours
test - service_manager : Passed
test - tomcat : Passed
test - tomcat_deadlocks : Passed
test - tomcat_keystore : Passed
test - tomcat_connectors : Passed
test - tomcat_threads : Passed
test - tomcat_memory : Passed
test - tomcat_sessions : Passed
skip - tomcat_heapdump : This module must be run directly and off hours
test - validate_network : Passed
test - raid : Passed
test - system_info : Passed (Collected system information in diagnostic log)
test - ntp_reachability : Warning
The host 0.us.pool.ntp.org is not reachable, or it's NTP service is down.

Some of the configured external NTP servers are not reachable.
It is recommended that for better time synchronization all of
the NTP servers be reachable.

Please use the OS Admin GUI to add/remove NTP servers.

test - ntp_clock_drift : Passed
test - ntp_stratum : Passed
skip - sdl_fragmentation : This module must be run directly and off hours
skip - sdi_fragmentation : This module must be run directly and off hours

Diagnostics Completed

Hi,

Can you please activate "option ping" on both sides and see if the result in Full Service state?

Can you also tell us if you are using Media Termination Point on those ICT?

 

Please let me know

 

 

Regards

 

Carlo

Please rate all helpful posts "The more you help the more you learn"

Ping option is active on both sides of the SIP trunk:

Full Service Time In Full Service: 1 day 10 hours 5 minutes

 

We are not using MTP.