As I understand, if router is equipped with DID card, the router can receive digits from Telco, and transfer the call to specific extension. This's how DID works? in this case, is the analog line a trunk? I'm a bit confused in here. Thanks.
All FXO ports terminate standard analog lines, which are often referred to as "1FB"s The analog line does NOT pass ANI or DNIS because it is a simple signaling wire pair and does not have a mechanism for "reading / storing / forwarding" so to speak the Caller ID messages produced by the CO switch. This is often why you need a Caller ID enabled handset or a smartbox to interpret the data passed. A digital circuit, such as a PRI, are able to track caller ID by use of what are called progress messages, which allows the ANI to be embedded and passed to the CPE and used for queueing to a sig digit extension or "main number line" if you will. Typically, the best workaround for an FXO is to just use a plar mechanism or a null voice translation rule such as:
rule 1 ^$ 1000
voice translation-profile AA
translate called 1
dial-peer voice 1 voip
destination-profile incoming AA
** this takes any inbound calls on the FXO and converts the null digit string to 1000 and allows you to PLAR the call off to an FXS or a hunt group.
I know some of my telco jargon is probably not EXACT, but this is the general idea...
what you said is correct, only I'm not sure why you suggest the complication of translation rules etc for a thing that as you mention, is doen with a single 'connection plar' command.
Also, the exaple you have give, does not work in practice. First, the trnalation rule must be applied to a either a voice-port or pots incoming dial-peer. But in the example you made, threre is a voip dial-peer, and a 'destination-profile' command that doesn't exist.
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.