SL2100 behind FreePBX

[wirerun]

Hi NEC gurus, has anyone configured NEC system to work with on premises FreePBX server?
I’ve been looking for call recording solution for awhile now and freepbx seems like a good fit. Plan is to use freepbx as “sip proxy”, it will have 4 sip trunks and 4 extensions set as trunks for NEC to connect to. Calls will be answered by freepbx, greeting will be played and then routed to first available extension which nec will see as a trunk.
Question is how to configure sip trunks on NEC side? Sip subscriber with username and password or IP registration or some other way?

 

[OzzieGeorge]

Call Recording NEC VoIP signaling (SIP based) - Versadial Call Recording Software

Call Recording NEC VoIP (SIP based) NEC VoIP Compatible Versadial’s call recorder is capable of capturing proprietary NEC VoIP call details without SMDR

www.versadial.com

Features like????

 

[Shaun E]

I've had my SV9100 SIP trunked to Asterisk for years with two-way calling between extensions on a common dialplan (eg: NEC extensions 2xx, Asterisk extensions 3xx). IVRs and auto-attendants run on Asterisk and happily transfer calls to NEC extensions. Call recording works fine.

Before the SV9100 it was an SL1100. The SL2100 should be similar in config. I do IP authenticated trunks - not SIP registrations.

If on the FreePBX side you land incoming calls from the NEC in the from-internal context FreePBX will effectively treat them as internal calls and they'll follow the standard FreePBX call routes.

 

[OzzieGeorge]

But how does this add features to the NEC system?

Edited to ask, If you use the Asterisk system for VM, how do you light the message waiting light on the NEC? and that is just one example!

 

[wirerun]

But how does this add features to the NEC system?

Edited to ask, If you use the Asterisk system for VM, how do you light the message waiting light on the NEC? and that is just one example!

NEC AA and voicemail will be disabled.
Voice mail will be received by freepbx and sent by email to their corporate office, they will follow up on that voice mail not local branch.

 

[wirerun]

I've had my SV9100 SIP trunked to Asterisk for years with two-way calling between extensions on a common dialplan (eg: NEC extensions 2xx, Asterisk extensions 3xx). IVRs and auto-attendants run on Asterisk and happily transfer calls to NEC extensions. Call recording works fine.

Before the SV9100 it was an SL1100. The SL2100 should be similar in config. I do IP authenticated trunks - not SIP registrations.

If on the FreePBX side you land incoming calls from the NEC in the from-internal context FreePBX will effectively treat them as internal calls and they'll follow the standard FreePBX call routes.

Thank you Shaun for confirming it’s doable.
I’ve seen similar requests on freepbx forums but no solutions ever posted.
Do you mind sharing SIP profile settings from NEC
Do you recall what was set for SIP Carrier Choice

 

[OzzieGeorge]

Voice mail will be received by freepbx and sent by email to their corporate office, they will follow up on that voice mail not local branch.

The NEC can do that so no feature added there!

 

[wirerun]

The NEC can do that so no feature added there!

And I that’s what I would do few month ago, didn’t you get the memo?
Nec is dead end, I’m not investing a penny into licenses on something that will be obsolete in few month. What if cpu goes bad and you need to transfer licenses, who are you going to call? Resellers claim to stick around and provide support for much longer, but it all depends how much NEC hardware they still have in stock, before you know it they’ll start pushing new product maybe on premises or hosted and drop all support for NEC. They have no obligations to continue supporting it.

On another note, I can buy 6 sip phones for the cost of one voice mail to email license, switch client to hosted with all the features you can think of and collect my commission every month.

 

[Shaun E]

Do you mind sharing SIP profile settings from NEC
Do you recall what was set for SIP Carrier Choice

Carrier B.

Here's my profile. The internal IP address of the Asterisk machine goes into 03 and 13.

 

[wirerun]

Thank you Shaun! I’ll try these settings as well.

I’ve hired a guy on Upwork and he got asterisk up and running fairly quickly.
The only difference is NEC using registration.
We tried different settings and it worked with
02 was not checked
03, 06, 11, 12 local sip server
14 default

Another difference I noticed is we didnt have to open any ports in router firewall for asterisk to work. I was told to always forward 5060,10020-10300 to NEC

Thank you all for all tek-tips, every single comment matters, it’s nice to know someone out there cares!

 

[OzzieGeorge]

And I that’s what I would do few month ago, didn’t you get the memo?
Nec is dead end, I’m not investing a penny into licenses on something that will be obsolete in few month. What if cpu goes bad and you need to transfer licenses, who are you going to call? Resellers claim to stick around and provide support for much longer, but it all depends how much NEC hardware they still have in stock, before you know it they’ll start pushing new product maybe on premises or hosted and drop all support for NEC. They have no obligations to continue supporting it.

On another note, I can buy 6 sip phones for the cost of one voice mail to email license, switch client to hosted with all the features you can think of and collect my commission every month.

So NEC are continuing support just ceasing the supply of new product, didn't you get the memo? and you need hardware for voicemail to email since when?

It seems it's different for us in OZ as VM to email is a free inclusion, are you sure it isn't for you? With respect, I think you are overreacting and need to check the real facts before committing your company to a cobbled together solution that introduces additional potential points of failure for no real benefit.

 

[wirerun]

So NEC are continuing support just ceasing the supply of new product, didn't you get the memo? and you need hardware for voicemail to email since when?

It seems it's different for us in OZ as VM to email is a free inclusion, are you sure it isn't for you? With respect, I think you are overreacting and need to check the real facts before committing your company to a cobbled together solution that introduces additional potential points of failure for no real benefit.

US version is different, no free voice mail to email, no sip trunk licenses come with a system.
I had a call from a client ones asking for call accounting software because they’ve seen it on the web, turned out it was only for OZ market.

I don’t think asterisk proxy solution will be bad. I have a feeling asterisk is backbone at most hosted VoIP providers.
It also seems to be easier finding tech support for freepbx than for NEC. Couldn’t find anyone on Upwork with NEC skills and hundreds of freelancers and companies offering freepbx turnkey solutions and customization.
Purchasing commercial licenses (if needed) for freepbx is a matter of couple clicks and it’s delivered instantly, not 3-5days later like NEC.

I’m not trying to say that NEC is bad.
It was great while it lasted and it’s time to learn new tricks

 

[CoralTech]

Wait, you are talking about an SL2100 right? Fairly certain 8 SIP/VOIP ports out of the box and VM to email was standard. Ya, been dealing with Asterisk for over a decade. Good luck.

 

[OzzieGeorge]

Wow, you guys got shafted! we get VM to Email and 4 Sip trunk licenses as standard on SL2100! At the end of the day, the Asterisk solution introduces additional potential points of failure that I couldn't justify to a customer. That being said, I used to work for NEC when Asterisk first came out and I flagged it as a future threat!

All that said, ask the question here.....

NEC PABX Forum - Australian Communications Forum

and you may get an additional resource to help work out how to set up your SIP trunks.

Oh and I don't need to learn new tricks as NEC systems will be around for at least 20 years (although I am technically at retirement age already). I always point to the system at Royal Perth Hospital who replaced their NEC system a few years ago with another NEC. It was a 2400 MMG and was 30 years old and about 10 - 15 years out of support so I don't think the current systems will fall off the perch in the next 10 years or so! Although last month I was called out to an NEC SDS which is 40 years old and still in service (pictures available on the link posted)!

 

[wirerun]

It looks like outbound trunk on freepbx to SV9500, to route calls to NEC. What about the other way around? Do you mind sharing settings from sv9500 for a sip trunk to freepbx.
I’m having trouble finding sip trunk setting for NEC system to connect to inbound trunk of freepbx.

Wait, you are talking about an SL2100 right? Fairly certain 8 SIP/VOIP ports out of the box and VM to email was standard. Ya, been dealing with Asterisk for over a decade. Good luck.

Thanks CoralTech, sl2100 cpu has 8 built in IP resources and zero IP trunks, unlike sl1100 that came with 4 trunks. None of SL series come with voicemail to email license.
Isn’t it the same licensing scheme with SV series? I thought these come completely unusable and need licenses for everything including extensions?

 

[wirerun]

Wow, you guys got shafted! we get VM to Email and 4 Sip trunk licenses as standard on SL2100! At the end of the day, the Asterisk solution introduces additional potential points of failure that I couldn't justify to a customer. That being said, I used to work for NEC when Asterisk first came out and I flagged it as a future threat!

All that said, ask the question here.....

NEC PABX Forum - Australian Communications Forum

and you may get an additional resource to help work out how to set up your SIP trunks.

Oh and I don't need to learn new tricks as NEC systems will be around for at least 20 years (although I am technically at retirement age already). I always point to the system at Royal Perth Hospital who replaced their NEC system a few years ago with another NEC. It was a 2400 MMG and was 30 years old and about 10 - 15 years out of support so I don't think the current systems will fall off the perch in the next 10 years or so! Although last month I was called out to an NEC SDS which is 40 years old and still in service (pictures available on the link posted)!

You know what else we don’t have here in US? The Metric system I’ve been here for 25 years and still can’t wrap my head around Imperial nonsense

I believe you, NEC is a solid system, I also have some DSXs 80,40 running in closets for over a decade with zero issues.

 

[DoubleDriveLine]

You know what else we don’t have here in US? The Metric system I’ve been here for 25 years and still can’t wrap my head around Imperial nonsense

We do and some of us do both rather easily. You just had to be raised in that era where Metric was getting more ground in the US but standard was still the standard. If you came from just the one it makes the other harder. Thankfully we are not engineers who might need to convert from one to the other to land a rover on Mars.

 

[DoubleDriveLine]

My 9500 notes will not help you much. It uses an external device MG-SIP as a gateway between the 9500 and the SIP provider. It is just a matter of pointing the MG-SIP to the SIP Provider IP.

 

[wirerun]

My 9500 notes will not help you much. It uses an external device MG-SIP as a gateway between the 9500 and the SIP provider. It is just a matter of pointing the MG-SIP to the SIP Provider IP.

Thanks for your help. You and other guys confirmed it can be done and that gave me confidence.
When I was searching the web for solutions I wasn’t using proper asterisk terminology. In Asterisk outbound routes are not necessarily for outbound routes only. Extensions in asterisk are not exactly user extensions… When someone told me that all I need to solve my task is to create dialplan in asterisk I would’ve never guessed it’s a scripting language.
Learning basics of Asterisk is not as hard as I thought it would be, most used modules are well documented and there are a lot of examples built right into it.