Search results for query: *

I got it figured out and calls are passing between systems flawlessly.

Thanks @omonat. That is what I was missing. With this setup ALL calls from NEC are made from the internal prospective with PSTN routing handled on Asterisk. Perfect. Thank you!

@CoralTech, Do you troll every post in this forum? It's odd how often I see you post, but never seem to provide useful feedback. There is no confusion here between outbound route and CID. The question was if it were possible to route the call to an internal extension block, retaining the...

@CortalTech, of course you can. I asked how to add a specific route and more specifically alter the outbound CID to the calling part extension. Very easily done on other systems. If you don't know, why comment?

@CoralTech I don't believe so. Did I not ask a pretty straight forward question? If it is not possible to specify the route as I have requested (and you actually know this as fact), just say so. It is easily done on other systems. We cannot add an additional PRI or SIP trunk to our NEC server...

Is it possible to route outbound internal calls via our existing PRI which is currently used for external calling? I am trying to temporarily interconnect our NEC SV9100 server with a new asterisk system. We would like to slowly transition one block of extensions at a time to the new system...

@omonat Thank you for getting me pointed in the right direction here. What you have described will work perfect. Thank you!

@omonat Yes, even better. The one thing I will need to address is the SV9100 PRI is configured for 7 digits for PSTN. This was extended from 4 digits because of some public number overlap between prefixes. Our internal extensions are 4 digit. How is this handled on the NEC side coming in on the...

@omonat Thank you for that recommendation! The dual PRI gateway setup that you described will work perfect. We already have the PRI interface and resource license on the SV9100 which currently connects to PSTN. With this setup I can easily interconnect all systems. I may use a separate FreePBX...

@omonat Thank your for that advice. I had considered the PRI interconnect previously and think it would be a more familiar connection method on the NEC side and still just as easy as SIP on the PBXact/FreePBX side. However, we are currently using the only PRI interface on the 9100 currently for...

@OzzieGeorge Thank you for that insight. I knew the NEC side might be a challenge to setup, but did not imagine we would need to make changes via CLI. Fortunately, I have provisioned the cost to add the IP trunk licenses to facilitate a smooth transition. I also wondered if we might be able to...

I have considered cutting everything over at once. However, the phones are located across multiple geographic locations and have varying configurations (call routing, 9 for outside line, etc) which will need standardized along with overhead paging. I decided that we will need to be able to...

The system has around 300 phones.

We are needing to create a SIP trunk to link our existing SV9100 with our new PBXact (FreePBX/Asterisk based) server. This SIP trunk will need to facilitate 2-way extension to extension dialing between the systems while we migrate all extensions from NEC to PBXact. I am familiar with creating...