dial-peer matching not working as expected (but functioning nonetheless)
I've always had a suspicion that my dial-peers are not functioning like I think they should, but haven't ever been able to prove it. Obviously this is somewhat of a minor issue since we're able to place/take calls without any serious problems, but when I look at the log it seems as though there is a lot of unnecessary "matching" going on. Another issue is that I cannot block certain incoming numbers as I'd like. I created the rules below:
voice translation-rule 6
rule 1 reject /^1234567890/
voice translation-profile BLOCK
translate calling 6
dial-peer voice 1011 voip
translation-profile incoming BLOCK
translation-profile outgoing OUT
voice-class codec 1
session protocol sipv2
session target dns:chcg.global.voip.mcleodusa.net
incoming called-number .
but the incoming translation profile is ignored completely. The call gets through without a hitch. I will attach a copy of my debug log and see if that makes sense to anyone. It does seem to be picking the correct dial-peer (probably based on the "incoming called-number ." line), but it doesn't reject the number. Strangely, if I change the rule to rewrite the incoming number to a blank string, this works. It blanks the caller ID on my end. So I know that the translation-profile is working to some degree.
Let me know what you're thinking. I can provide any extra logs necessary.
Re: dial-peer matching not working as expected (but functioning
It is indeed a SIP circuit. I never thought about that being the problem. Perhaps I'll have to open up a TAC case and see I can verify that. If that's the case, it saves me lots of troubleshooting time :).
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.