Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

SAF Plug in Dial Peer not being matched

2 CUCM 9 clusters connected via 2951 routers and successfully using SAF/CCD between them.  One of the CUCMs also has a  second  2951 as a CME router also running SAF.

This particular client wants a "default / catch-all" dial peer that dumps calls to the CUCM (just assume that this is a non-negotiable point)

CUCM 2 is hosting DN pattern 16xx.  This pattern is visible to the CME router as evidenced by a show voice saf dndb all statement.

A call generated by an IP phone hanging off the CME to a 16XX number is matching to the catch-all dial peer and not to the SAF Plug-In dial peer, as evidenced by doing a  debug voice dialpeer and watching the outbound dial peer matches.

Partial configuration of the router is below:

dial-peer voice 3 voip

description Default Dial Peer for SAF

destination-pattern .T

session target saf

         

dial-peer voice 1028 voip

description Default Catch All Dial Peer to dump to Corps CUCM

translation-profile outgoing 10

destination-pattern ....

session target ipv4:172.16.57.60

dtmf-relay h245-alphanumeric

no vad

I ran a number of tests, altering the destination-pattern of the SAF dial peer and then watching the output of a debug voice dialpeer command.

Even if I changed the destination-pattern to a complete match, ie destination-patten 1600, dial-peer 3 does not match and the call matches to dial-peer 1028.

However, if I change the SAF plug in dial-peer to be a normal dial-peer, ie I replace the session target saf command with session target ipv4:1.1.1.1, and place the same call, dial-peer 3 then matches.

Below is the router's SAF configuration

router eigrp SAF_FORWARDER

!

service-family ipv4 autonomous-system 11

  !

  topology base

  exit-sf-topology

  neighbor 172.16.88.1 Loopback0 remote 10

  neighbor 172.16.88.2 Loopback0 remote 10

  neighbor 172.16.88.6 Loopback0 remote 10

  neighbor 172.16.88.16 Loopback0 remote 10

  neighbor 172.16.88.18 Loopback0 remote 10

  neighbor 172.16.88.20 Loopback0 remote 10

  neighbor 172.16.88.52 Loopback0 remote 10

  neighbor 172.16.88.54 Loopback0 remote 10

  neighbor 172.16.88.56 Loopback0 remote 10

  neighbor 172.16.88.86 Loopback0 remote 10

  neighbor 172.16.88.88 Loopback0 remote 10

  neighbor 172.16.88.90 Loopback0 remote 10

  neighbor 172.16.88.124 Loopback0 remote 10

  neighbor 172.16.88.125 Loopback0 remote 10

  neighbor 172.16.88.126 Loopback0 remote 10

  neighbor 172.16.88.127 Loopback0 remote 10

  neighbor 172.16.88.128 Loopback0 remote 10

  neighbor 172.16.88.51 Loopback0 remote 10

exit-service-family

voice service saf

profile trunk-route 11

  session protocol sip interface Loopback0 transport udp port 5060

         profile dn-block 11

  pattern 1 type extension 6[01]XX

  pattern 2 type extension 999X

profile callcontrol 11

  dn-service name CCD

   description CCD over SAF

   trunk-route 11

   dn-block 11

call

channel 11 vrouter SAF_FORWARDER asystem 11

  subscribe callcontrol wildcarded

  publish callcontrol 11

So, anyone with any thoughts on why Im not matching to the SAF Plug-in Dial Peer?

Jeff

349
Views
0
Helpful
0
Replies
CreatePlease login to create content