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?

 

[CoralTech]

Look into USB call record.

 

[wirerun]

Look into USB call record.

USB recorders I looked into will not capture remote extensions, forwarded calls and require windows OS to run their management software.

Call recording is just one of the features. Voice mail to email and appointment reminders are the next 2 features to implement. I don’t feel like investing into NEC licenses anymore.
I do like NEC hardware and plan on keeping existing on premises setups, but need new solution in the future.
If nec sip trunk to freepbx is not an option I’ll use CO trunk cards and fxs adapters known to work with Freepbx.
Is it even possible to configure SL2100 sip trunks to a sip server on local network?

 

[jsaad]

Is your NEC licensed for SIP trunks? If not you are going to need that. NEC can do almost anything, there is an NTAC guide on SIP trunk connectivity.

 

[DoubleDriveLine]

There are a number of different ways you can connect the Asterisk to the SL2100. The first way would be SIP Trunks. If the SL2100 is not setup for that licensing then you could do a PRI in the SL2100 to a PRI Gateway going SIP to the Asterisk.

I had at one time a NEC 3C, SV8300, and SV9500 all running behind an Asterisk PBX. The 3C and 9500 were SIP trunks. The SV8300 was PRI. I used an Adtran Netvanta PRI gateway for the PRI connection.

 

[wirerun]

Yes, it has 4 sip trunk licenses and SLnet license. Currently with Clearfly.
NEC SL2100 cannot do Call recording

 

[wirerun]

There are a number of different ways you can connect the Asterisk to the SL2100. The first way would be SIP Trunks. If the SL2100 is not setup for that licensing then you could do a PRI in the SL2100 to a PRI Gateway going SIP to the Asterisk.

I had at one time a NEC 3C, SV8300, and SV9500 all running behind an Asterisk PBX. The 3C and 9500 were SIP trunks. The SV8300 was PRI. I used an Adtran Netvanta PRI gateway for the PRI connection.

Any chance you saved configuration of sip trunks to Asterisk?

 

[CoralTech]

USB recorders I looked into will not capture remote extensions, forwarded calls and require windows OS to run their management software.

Call recording is just one of the features. Voice mail to email and appointment reminders are the next 2 features to implement. I don’t feel like investing into NEC licenses anymore.
I do like NEC hardware and plan on keeping existing on premises setups, but need new solution in the future.
If nec sip trunk to freepbx is not an option I’ll use CO trunk cards and fxs adapters known to work with Freepbx.
Is it even possible to configure SL2100 sip trunks to a sip server on local network?

Um,

They have nothing to do with NEC. They also have trunk side options.

 

[quazimotto]

Wirerun,

I have an Asterisk ( Issabel ) connected to an NEC SV8100.
1. 10-03 set to sip
2. 10-23 check box; set ip address
3. 11-01 digit length F-Route
4. 14-09 Trunk Group Setup
5. 26-03 Dial Treatment set one to RE
6. 44-02 F-Route Analysis Set digits to dial to reach Asterisk Set to F-route Additional Data set to 1
7. 44-05 F-Route Table Set Trunk Group Dial Treatment Max Digits

That should do it.

Good Luck,
Quaz

 

[quazimotto]

Forgot 10-28 0-29 and 10-30 need to be set, too.

 

[wirerun]

There are a number of different ways you can connect the Asterisk to the SL2100. The first way would be SIP Trunks. If the SL2100 is not setup for that licensing then you could do a PRI in the SL2100 to a PRI Gateway going SIP to the Asterisk.

I had at one time a NEC 3C, SV8300, and SV9500 all running behind an Asterisk PBX. The 3C and 9500 were SIP trunks. The SV8300 was PRI. I used an Adtran Netvanta PRI gateway for the PRI connection.

Any chance you saved configuration of sip trunks to Asterisk?

Wirerun,

I have an Asterisk ( Issabel ) connected to an NEC SV8100.
1. 10-03 set to sip
2. 10-23 check box; set ip address
3. 11-01 digit length F-Route
4. 14-09 Trunk Group Setup
5. 26-03 Dial Treatment set one to RE
6. 44-02 F-Route Analysis Set digits to dial to reach Asterisk Set to F-route Additional Data set to 1
7. 44-05 F-Route Table Set Trunk Group Dial Treatment Max Digits

That should do it.

Good Luck,
Quaz

Wirerun,

I have an Asterisk ( Issabel ) connected to an NEC SV8100.
1. 10-03 set to sip
2. 10-23 check box; set ip address
3. 11-01 digit length F-Route
4. 14-09 Trunk Group Setup
5. 26-03 Dial Treatment set one to RE
6. 44-02 F-Route Analysis Set digits to dial to reach Asterisk Set to F-route Additional Data set to 1
7. 44-05 F-Route Table Set Trunk Group Dial Treatment Max Digits

That should do it.

Good Luck,
Quaz

I’ll certainly try mysterious F-route again. Couldn’t get it to work last time.

 

[OzzieGeorge]

Seems like a heck of a lot of trouble and the introduction of more potential points of failure just to save a small license fee. Add to that the fact that the call detail recording, if done on the asterisk, won't have extension details from the 2100, it seems to be a half baked solution. Also the NEC will have to do the voicemail to email anyway in order for it to work for the 2100 extensions so a really messy solution as against a simple and more comprehensive solution by doing it all in the NEC.

 

[DoubleDriveLine]

@OzzieGeorge he isn't looking for call accounting. He is looking to do trunk side audio recording. This solution for recording is kind of foggy but the better solution would be to switch to the Asterisk and forget the NEC. That said, that switch comes with its own set of problems. It might mean this method is a good short term option.

@wirerun I can't get you that setup until tomorrow. I am positive I still have it.

 

[wirerun]

Seems like a heck of a lot of trouble and the introduction of more potential points of failure just to save a small license fee. Add to that the fact that the call detail recording, if done on the asterisk, won't have extension details from the 2100, it seems to be a half baked solution. Also the NEC will have to do the voicemail to email anyway in order for it to work for the 2100 extensions so a really messy solution as against a simple and more comprehensive solution by doing it all in the NEC.

It’s not about saving a fee, nec is officially leaving our market, why spend a dime on quitters.
Also I’m not talking about recording call details but actual voice call recordings, it was never an option NEC offered, not in US market at least.
Voice mail to email is standard feature of freepbx and it will not be Dee and

@OzzieGeorge he isn't looking for call accounting. He is looking to do trunk side audio recording. This solution for recording is kind of foggy but the better solution would be to switch to the Asterisk and forget the NEC. That said, that switch comes with its own set of problems. It might mean this method is a good short term option.

@wirerun I can't get you that setup until tomorrow. I am positive I still have it.

I would appreciate that. switching from NEC is no brainer, but I sold this client 5 systems within last year, need to get few more years out of it, who knew nec would flop like that.
I’m sure Asterisk has issues, but they certainly not going away as long as people still use handsets for communication.

 

[DoubleDriveLine]

@wirerun
For the SV9500 connection the Asterisk IPBX side was

Chan_sip trunks
Note there is no registration for the SV9500 trunks. Yes this trunk is disabled because it is no longer in use. I just did not want to delete the code.



SIP Settings

There is data in the Outgoing tab and no data in the incoming tab



The Adtran Netvanta used a registration. The general tab was the same basically as the SV9500. The only difference is the Trunk Name has to be unique. The trunk is disabled like the 9500

If you are going the Adtran Netvanta SIP to PRI you will need to find a tutorial online to setup the adtran. I found one rather quickly a few years ago.

If you have SIP licensing in the 2100 then I would think this is the one you use.

 

[wirerun]

@wirerun
For the SV9500 connection the Asterisk IPBX side was

Chan_sip trunks
Note there is no registration for the SV9500 trunks. Yes this trunk is disabled because it is no longer in use. I just did not want to delete the code.

View attachment 808

SIP Settings

There is data in the Outgoing tab and no data in the incoming tab

View attachment 809

The Adtran Netvanta used a registration. The general tab was the same basically as the SV9500. The only difference is the Trunk Name has to be unique. The trunk is disabled like the 9500

If you are going the Adtran Netvanta SIP to PRI you will need to find a tutorial online to setup the adtran. I found one rather quickly a few years ago.

If you have SIP licensing in the 2100 then I would think this is the one you use.

View attachment 810

 

[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.

 

[wirerun]

Instead of Investing into adtran and pri card might as well get Sangoma or Yealink phones and forget NEC.

 

[jsaad]

usbcallrecord.com has a call recording system via SIP and was the call recording partner for NEC.

 

[wirerun]

usbcallrecord.com has a call recording system via SIP and was the call recording partner for NEC.

Implementation of freepbx solves call recording and a dozen of other features NEC will never have