I am trying to prevent a loop scenario. We have a SIP trunk to a Service provider and trying block the calls going out on SIP trunk if we received the call from that trunk. Some thing similar to CallManager config where CSS of trunk wouldn't have the partition of RP pointing to that trunk.
Second question can we block the calls if they do not have certain preceding digit.some thing like we only route the call if digits start with 408
What is it about your Dial Plan that is causing the loop? You might just be able to fix that.
As far as your question goes, you can either use COR by assigning inbound COR on the dial-peer matching LEC calls, as well as outbound COR on that dial-peer (inbound COR shouldn't contain items in the outbound COR). You could also just add a special prefix to calls coming in from the LEC, and force those not to go back to that dial-peer.
Yes, you can also block the calls based on ANI or DNIS.
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.