Buy or Renew
Buy or Renew
Cisco + Splunk: It’s a new day for your data. Learn more.
 
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
3434
Views
4
Helpful
16
Replies

Phones registered to different subscriber cannot communicate

Go to solution
iftikharsyed_2
Level 1
Level 1

‎12-10-2009 05:08 AM - edited ‎03-15-2019 08:45 PM

We have 4 CUCM in PUB-SUB scenario

1 -PUB and 3 SUBs with cucm 6.0

everything was working fine but from last few days we are facing an issue,

Phones registered with Subscriber A can communiate with phones on Subscriber B and C both

Phones registered to Subscriber B can commnicate with subscriber A but not Subscriber C

Phones registered to sub Subscriber C cannot communicate with subscriber B but they can communicate with subscriber A

There are times when subscriber C phones can communicate with Subscriber B phones but its very rare.

I have verified DB replication status and its 2

I have tried to insert phones from subscriber C Admin page and it works.

There no latency or packet drops issues between Subscriber to Subscriber and Publisher to subscriber.

Any suggestion to solve the issue.

Labels:
0 Helpful
16 Replies 16

Go to solution
iftikharsyed_2
Level 1
Level 1
In response to vivkalra

‎12-11-2009 10:44 PM

Hi,

Thanks to all of you for replying,

As i posted earlier, there are no issues with WAN link, link between these two sites is STM1 link with no packet loss and latency around 12ms.

MTU for the network path is 1500.

If it is a Bad NIC issue then problem should occur between all three sites.

Vivek,

Utils diagnose test is not a valid command in CUCM 6.

Unfortunately we don't have essential software support at this moment to open TAC case.

Kindly let me know which DSL trace can be used to check issue with SDL linkOSS. as this is the only error displayed on RTMT application Log

Regards,

Iftikhar Ahmed

0 Helpful

Go to solution
iftikharsyed_2
Level 1
Level 1
In response to iftikharsyed_2

‎12-12-2009 03:00 AM

Hi,

I have checked realtime SDL traces and i see following

Remote NodeId: 1, AppId: 300, Address: [10.100.200.12:8004]
000549312| 2009/12/12 15:51:05.838| 012| SdlError  |                                       |                               |                                 |                                 |                                         | - Unable to connect to remote node.> Remote NodeId: 1, Remote AppId: 300, Address: [10.100.200.12:8004]
000549313| 2009/12/12 15:51:08.567| 012| LnkState  |                                       |                               |                                 |                                 |                                         | Remote NodeId: 3, AppId: 300, Address: [10.100.200.11:8004]
000549314| 2009/12/12 15:51:08.577| 012| SdlError  |                                       |                               |                                 |                                 |                                         | - Unable to connect to remote node.> Remote NodeId: 3, Remote AppId: 300, Address: [10.100.200.11:8004]
000549315| 2009/12/12 15:51:08.677| 012| LnkState  |                                       |                               |                                 |                                 |                                         | Remote NodeId: 2, AppId: 300, Address: [10.120.200.11:8004]
000549316| 2009/12/12 15:51:08.704| 012| SdlError  |                                       |                               |                                 |                                 |                                         | - Unable to connect to remote node.> Remote NodeId: 2, Remote AppId: 300, Address: [10.120.200.11:8004]
000549317| 2009/12/12 15:51:10.477| 012| LnkState  |                                       |                               |                                 |                                 |                                         | Reason: Send Error, NodeId: 3, AppId: 100, TCPAddr: 10.100.200.11:8002
000549318| 2009/12/12 15:51:10.477| 012| LnkState  |                                       |                               |                                 |                                 |                                         | NodeId: 3 AppId: 100 [10.100.200.11:8002]
000549319| 2009/12/12 15:51:10.477| 012| LnkState  |                                       |                               |                                 |                                 |                                         | NodeId: 3, AppId: 100, TCPAddr: 10.100.200.11:8002
000549320| 2009/12/12 15:51:10.478| 012| LnkState  |                                       |                               |                                 |                                 |                                         | <:SENDTHREAD -="" waiting="" for="" closecomplete=""> NodeId: 3, AppId: 100, TCPAddr: 10.100.200.11:8002
000549321| 2009/12/12 15:51:10.478| 012| LnkState  |                                       |                               |                                 |                                 |                                         | <:RECEIVETHREAD -="" going="" to="" closecomplete=""> NodeId: 3, AppId: 100, TCPAddr: 10.100.200.11:8002
000549322| 2009/12/12 15:51:10.478| 012| LnkState  |                                       |                               |                                 |                                 |                                         | <:SENDTHREAD -="" going="" to="" connecting=""> NodeId: 3, AppId: 100, TCPAddr: 10.100.200.11:8002
000549323| 2009/12/12 15:51:10.490| 012| AlarmErr  |                                       |                               |                                 |                                 |                                         | AlarmClass: CallManager, AlarmName: SDLLinkOOS, AlarmSeverity: Error AlarmMessage: , AlarmDescription: SDL link to remote application out of service., AlarmParameters:  LocalNodeId:12, LocalApplicationID:100, RemoteIPAddress:10.100.200.11, RemoteNodeID:3, RemoteApplicationID:100, LinkID:12:100:3:100, AppID:Cisco CallManager, ClusterID:StandAloneCluster, NodeID:CMSUB-ISL-IPT,
000549324| 2009/12/12 15:51:15.287| 012| LnkState  |                                       |                               |                                 |                                 |                                         | Remote NodeId: 1, AppId: 100, Address: [10.100.200.12:8002]
000549325| 2009/12/12 15:51:15.298| 012| LnkState  |                                       |                               |                                 |                                 |                                         | - Connection Accepted Waiting to go InService - Remote NodeId: 1, Remote AppId: 100 Hostname: [10.100.200.12]
000549326| 2009/12/12 15:51:15.568| 012| SdlSig    | ReapOldTokenRegistrationsTimer        | wait                          | SIPStationInit(12,100,77,1)     | SdlTimerService(12,100,3,1)     | (12,100,89,2).1-(*:*)                   | [R:HP - HP: 0, NP: 0, LP: 0, VLP: 0, LZP: 0 DBP: 0]
000549327| 2009/12/12 15:51:15.837| 012| LnkState  |                                       |                               |                                 |                                 |                                         | Remote NodeId: 1, AppId: 300, Address: [10.100.200.12:8004]
000549328| 2009/12/12 15:51:15.847| 012| SdlError  |                                       |                               |                                 |                                 |                                         | - Unable to connect to remote node.> Remote NodeId: 1, Remote AppId: 300, Address: [10.100.200.12:8004]
000549329| 2009/12/12 15:51:16.307| 012| LnkState  |                                       |                               |                                 |                                 |                                         | <:RECEIVEDTHREAD -="" sending="" linkconnectionattempt="" message=""> NodeId: 1, AppId 100, TCPAddr: 10.100.200.12:8002
000549330| 2009/12/12 15:51:18.568| 012| LnkState  |                                       |                               |                                 |                                 |                                         | Remote NodeId: 3, AppId: 300, Address: [10.100.200.11:8004]
000549331| 2009/12/12 15:51:18.580| 012| SdlError  |                                       |                               |                                 |                                 |                                         | - Unable to connect to remote node.> Remote NodeId: 3, Remote AppId: 300, Address: [10.100.200.11:8004]
000549332| 2009/12/12 15:51:18.698| 012| LnkState  |                                       |                               |                                 |                                 |                                         | Remote NodeId: 2, AppId: 300, Address: [10.120.200.11:8004]
000549333| 2009/12/12 15:51:18.723| 012| SdlError  |                                       |                               |                                 |                                 |                                         | - Unable to connect to remote node.> Remote NodeId: 2, Remote AppId: 300, Address: [10.120.200.11:8004]
000549334| 2009/12/12 15:51:20.488| 012| LnkState  |                                       |                               |                                 |                                 |                                         | Remote NodeId: 3, AppId: 100, Address: [10.100.200.11:8002]
000549335| 2009/12/12 15:51:20.497| 012| LnkState  |                                       |                               |                                 |                                 |                                         | - Connection Accepted Waiting to go InService - Remote NodeId: 3, Remote AppId: 100 Hostname: [10.100.200.11]
000549336| 2009/12/12 15:51:21.498| 012| LnkState  |                                       |                               |                                 |                                 |                                         | <:RECEIVEDTHREAD -="" sending="" linkconnectionattempt="" message=""> NodeId: 3, AppId 100, TCPAddr: 10.100.200.11:8002

connections is established on port 8002 and 8003 but on port 8004 servers are unable to communucate. There is no port blockage at network level over the WAN.

Any suggestions now?

Regards,

Iftikhar

0 Helpful
Customers Also Viewed These Support Documents