How to Check if CCD/SAF is Working?

Step1 Verify that SAF neighborship is established between SAF forwarders.

R1#sh eigrp service-family ipv4 vrf MPLS neighbors

EIGRP-SFv4 VR(saf) Service-Family Neighbors for AS(5)

           VRF(MPLS)

H   Address                 Interface              Hold Uptime   SRTT   RTO  Q  Seq

                                                   (sec)         (ms)       Cnt Num

0   10.37.221.19            Gi0/1.204                12 1d00h       1   100  0  14

R2#sh eigrp service-family ipv4 vrf MPLS neighbors

EIGRP-SFv4 VR(saf) Service-Family Neighbors for AS(5)

           VRF(MPLS)

H   Address                 Interface              Hold Uptime   SRTT   RTO  Q  Seq

                                                   (sec)         (ms)       Cnt Num

0   10.37.221.21            Gi0/1.204                14 1d00h       1   100  0  14

Step2 Verify the at SAF Client registered with SAF Forwarder

R1#show service-routing xmcp clients

Service-Routing XMCP Clients

Codes: A - Authenticated, T - TCP

    Handle     Address                                    Port  Keepalive

AT  4          10.170.10.200                             52244    24/30 

    Client name: UCM/10.170.10.200/NodeId=1/9.1.1.20000-5

AT  6          10.170.10.201                             57333    17/30 

    Client name: UCM/10.170.10.201/NodeId=2/9.1.1.20000-5

R2#sh service-routing xmcp clients

Service-Routing XMCP Clients

Codes: A - Authenticated, T - TCP

    Handle     Address                                    Port  Keepalive

AT  16         10.45.230.10                              53076    28/30 

    Client name: UCM/10.45.230.10/NodeId=1/9.1.2.13900-10

Step3 Verify SAF routing table. You can see below the SAF Services learned from SAF forwarders and SAF Clients. Service ID 101:2:* refers to CCD Service.

On R1 SAF forwarder, you can see two CCD Services directly connected (learned from SAF Clients 10.170.10.200 and 10.170.10.201) and one CCD service learned from R2 SAF forwarder (SAF Client is 10.45.230.10).

R1#sh service-routing database

Service-Routing Database

Service ID (Service:Subservice:Instance)         Trust     Domain Owner Size

------------------------------------------------ --------- ------ ----- -----

      100:1:46545831-3634-3441-4853-430000000000 Connected *      1       333

      100:1:46545831-3634-3441-4853-4D0000000000 Learned   5      3       333

      100:2:46545831-3634-3441-4853-430000000000 Connected *      1      1426

      100:2:46545831-3634-3441-4853-4D0000000000 Learned   5      3      1426

      101:2:8976FD5D-F82E-62BC-AB80-DF860001B241 Connected 5      4       669

      101:2:8976FD5D-F82E-62BC-AB80-DF860002ED97 Connected 5      6       669

      101:2:AD8BC93D-A526-375D-6EFE-1BB700014E93 Learned   5      3       680

Step4 You can see the contents of the CCD Service learned from SAF Clients/Forwarders.

R1#show service-routing database 101:2:AD8BC93D-A526-375D-6EFE-1BB700014E93 text

Service-Routing Database

Service ID (Service:Subservice:Instance)         Trust     Domain Owner Size

------------------------------------------------ --------- ------ ----- -----

      101:2:AD8BC93D-A526-375D-6EFE-1BB700014E93 Learned   5      3       680

          Owner: SAF Forwarder AS(5) SFv4 VRF(MPLS)

          Sequence: 4       

          AFI: IPv4

          VRF: MPLS, Tableid: 3

          Subscription Handles:  5, 6

          Reachability:

            IPv4: 10.45.230.10:5060, protocol 6 (TCP)

          Service Data:

UCM9.1.2.13900-10sb-cluster10.45.230.10

sip:0a2d209c-6015-65c7-1071-bdaf032de992@CCMPub-SB

4XXX
3XXX

          Service Metadata:

You can see that the CCD Service was originated from sb-cluster with IP address of 10.45.230.10 and learned through SAF Forwarder. Also, the service contains two CCD patterns (hosted DNs) which are 4XXX and 3XXX.

Step5 You can verify the learned CCD Patterns on CCD Requesting clients using RTMT. Go to Call Manager > Report > Learned Patterns.