I have a 6608 in my 6509. I've heard two things about it, and would like to get a 2nd opinion:
1. You can not purchase a fractional PRI for the 6608. You must purchase all 23+1 DS0s on the PRI for it to work properly -- even if you only need two or three lines.
2. You can not assign one PRI to a partition. I'd like to have the ability to have different tenants use a PRI exclusively.
I want to provide VoIP in a multi-tenant building, but I don't have the ability to provide LD billing records and the management of that. I'd therefore like to have the tenant purchase the PRI, and I'll provide the technology on top of it (i.e. Call Manager, gateways, phones, etc.).
For the secon, any gateway device (except fxs mgcp) can not have a partition assigned to it. This is because a partition is only assigned to devices that have phone numbers assigned to them. In the case of a gateway, they do not have phone numbers directly assigned, instead a route pattern is created and points to the gateway.
You can do what you want to do, but you have to assign the partition at the route pattern and point it to the corresponding gateway.
1. True story, there is no mechanism in Call Manager to handle that. You could use CAS T1s, but that limits functionality.
2. You can set up partitions and calling search spaces for each tenant. Example; create a tenant1_LD partition and add a route pattern of 9.@ to that partition, and assign the tenant 1 PRI. You would then need a Calling Search Space like tenant1_LD that includes the tenant1_LD partitition, and assign that CSS to the phones for tenant 1. All calls from tenant 1 would only match route patterns that use their gateway.
You might also look at using calling number billing from your carrier, which would let multiple tenants share PRIs. You can pass all the DIDs through or manipulate the calling number so all calls form tenant 1 originate from a single number, and tenant 2 another number. Of course this would depend on the desires of your customer as well. The advantage of this approach would be better fault tolerance, or perhaps you could get by with a single PRI.
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.