Having problems trying to get the proper dial peer matching to work. I have a voip inbound call that I want to hairpin back out on the same dial peer using the session-target. The calls does match inbound on the peer based on the incoming called-number field, however, the outbound peer is being matched against only the pots ones I have and not voip.
Below are two three peer sections. If I have a called number 12345 it will match dialpeer outbound 4004 (or 4005 round robin) and not 4531006. However, if I change the destination pattern on 4005 to the same 'incoming called-number 12345' as the voip peer then it works to match specifically every time on that pots peer.
My question is why is the voip peer not being used during the match process?
Looks like the AS5400 might not support what I want to accomplish. I believe that the IP to IP is not supported on this platform. In looking at the IOS featuresets I think what I need is in the Voice IP to IP GW code which is not listed under the 5400. I do see it listed under the 37xx series:
I can't say if IPIP GW is a better fit for you. And I can confirm that IPIPGW definitely not supported in AS series equipment. And my Cisco contacts tell me it will not be supported there anytime soon. It is akin to, but more sophisticated than, the old h323 proxy function.
That said, in my 5400HPX, the basic option to passthrough IP to IP is available, at least in the CLI. However, I must admit I haven't implemented this function as it is not needed, and the risk of incorrect hairpinning is very real in my environment.
Here's some output:
Cisco IOS Software, 5400 Software (C5400-IS-M), Version 12.3(11)T7, RELEASE SOFT
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.