SV9100 Internal Call Routing via PRI

[JacobiC]

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. We would like to utilize the existing PRI which is currently used for PSTN calling. How would the outbound routes be configured on the NEC side with an internal context? ie. the outbound caller-id would be the extension number rather than the configured outbound CPN. Struggling to figure out how this outbound route is specified on the NEC side.

Diagram:

 

[CoralTech]

Who is doing this install? You seem to be WAY over your head. Why not just tie line the systems together with some tie/pri/sip?

 

[JacobiC]

@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. This is why I am asking if it is possible to specify an outbound route to use the existing PRI. No need to comment if you don't know yourself.

 

[CoralTech]

@JacobiC, you can add a lot of routes on an SV9100. It's easy if the logic is sound.

 

[JacobiC]

@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]

21-13
20-08-13 and possibly 14.
14-01-36

There is a difference between route and CID. Because these forums are for techs is why I commented. Pretenders and all.

 

[JacobiC]

@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 internal extension as the sending number rather than that specified in the CPN table for external calls. If it's not possible (and you actually know that to be true), just say so. Otherwise, there is no need to comment on the post.

 

[omonat]

Very possible.
If i have implemented several that way.
I my setups, the Line from the Telco goes into Port 1 of the PRI VoIP Gateway and the your NEC SV9100 would plug into port-2 of the PRI VoIP Gateway. Now the gateway convert both lines from the Telco & from SV9100 into SIP trunks for connections to Asterisk - Asterisk sees both as SIP Trunks. NOTE: Let Asterisk handle the routing to and from PSTN.

wanetelecoms@gmail.com

 

[JacobiC]

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!

 

[OzzieGeorge]

Unfortunately this won't solve the issue for a staged cutover as no one has told you how to make what was an extension to extension call on the NEC change for moved extensions so that they then go out to the VoIP gateway to be routed to the Asterisk. In View of your response to CoralTech who is nothing more than helpful to any and all, I for one won't be offering to help with that. Your terminology is, I believe, what made CoralTech query your ability to do this as there is no such thing as an outbound internal call, it is internal or outbound not both. I suggest you get an NEC qualified tech in to deal with this.

 

[eddiebullman]

it can be done but very complex to do

one thing though your extensions on the asterisk server will need to be on a different number range from that used by the NEC.

you will need to setup LCR on the NEC to route extension numbers on the new PBX via the PIR trunk which then needs to intercepted by the VoIP gateway to then route them to the PBX and do the same on the new PBX. this would need to be done on digits dialed by each PBX not on CLI

also all call will be treated as external calls

 

[omonat]

@ Ozzie & Eddie, those are obvious things to have been noted.
I have implemented the same except that it was with a Panasonic &ricsson system.
Therouting is easier when handled by asterisk.
Ozzie's note on Terminology is very correct!
And Eddie's note on number range.
Any issues will be happy to guide.

wanetelecoms@gmail.com

 

[OzzieGeorge]

Actually the extensions on the Asterisk can be the same range as the NEC. for example say you have extensions 3xx, there is a way in the NEC to individually redirect each extension out to the Asterisk (Eg 311 goes out to the asterisk because it is being moved to the new platform but all others stay internal). I have done this myself with a 3CX.

 

[JacobiC]

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