When we try to put two Route Groups into the Route List, one with a PRI interface the other with a QSIG interface, it is not allowed. I get the following (which is actually the complete reverse of whats happening):
Note: This route list contains QSIG route groups. The above route group list does not include non-QSIG route groups because you cannot add QSIG and non-QSIG route groups to the same route list.
This is a requirement, because for least cost routing we go via QSIG to the corporate network, then via PSTN for overflow/failure.
Are there any alternatives or a better way of doing this?
Similar to your case, I tried to implement automated rerouting from a QSIG trunk (PBX) to a EURO ISDN trunk (PSTN) on a 6608. My workaround was to configure the PSTN trunk as QSIG; Inbound and outbound calls worked on this trunk, and also did rerouting.
Of course this setup won't be supported by TAC - I'll need to raise with our Cisco SE as well
Hmm - yes you can consider QSIG to be a superset of ISDN PRI. Good thinking. Some IEs may just be discarded by the other end running ISDN PRI and be aware of the D-channel usage (contiguous or not) in QSIG.
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.