NEC SV9100 PRI to SIP Trunk for TEAMS integration

[alex_de]

Hello,

We have a case with a NEC SV9100 Main Software 10.00.50 and our target is to make integration with Microsoft Teams. Currently we have 3 PRI connected to the NEC SV9100 with a wide spectrum of 100 numbers (spectrum) per PRI. One approach is to implement the integration with an offsite SBC of a SIP provider. From the feature activation of NEC SV9100 we have (among others)

5001 System Port License IP Trunk 10
5103 System feature License VoIP Channel 177
5201 System feature License Mobile extension 30

The requirement is to receive incoming calls via the PRI in the provided spectrum and "forward" the calls to the SIP trunk with SBC showing as a caller id the number of the extension from the provided spectrum. Then, the SBC will interconnect with Microsoft TEAMS. In the field of integration of SBC with Microsoft TEAMS we have confirmed that the domain is declared and healthy and provided via powershell the details of pilot domain user accounts (user account, 10 digit telephone number and 4 digit extension).

We have establsihed the SIP trunk and confirmed that there is an active SIP trunk port 5060 (profile 1).

So far we can make a phone call from Microsoft Teams to our extension numbers and the internal phone devices are ringing and communicating. However, we cannot "forward" the incoming call from PRI to SIP Trunk with SBC. We have verifed with packet capture from NEC SV9100 and the firewall that there are no invite sip messages from NEC towards the SBC when we test for a call dierectly through the phone devices (805, the number of the SIP trunk and a formated number, for example 111111-number of the extension (10digit)).

The first question is:

1. Is there a guide for "forwarding" incoming calls from PRI to SIP trunk and simultaneously to ring the internal phone device (both ring)?
2. Could you provide a guidance in order to implement the aforementioned task, for example would you suggest forward an incoming call to a mobile extension or virtual extension and then forward to the SIP trunk maintaining the info for the extension number?
3. Is there a guide for the integration of NEC SV9100 with SBC and integration with Microsoft TEAMS?

Thank you in advance

Alex

 

[CoralTech]

First question, are you are certified NEC tech on the SV9100?

 

[alex_de]

No, I am not certified NEC technician. Actually, I this is my first time working with NEC SV9100. So please forgive my ignorance on these issues. I am trying to coordinate a team of experienced technicians with nec sv8100, sv9100 with external consultants.

 

[CoralTech]

Ok, first if you cannot forward ANY calls through the NEC SV9100 hire or get another vendor to help you. You should be able AT A MINIMUM do trunk to trunk calls. Of course the devil is in the details on what the sip carrier/TEAMS is looking for to work properly. There are literally hundreds of settings for this. Integrations are hard and really should be setup in a lab before deployment. I am assuming you can make/receive calls on the SIP lines correct?

 

[OzzieGeorge]

Has any F route programming been done on the SV9100 as you have to create an access code for the sip trunks and then forward trunk to trunk using that access code and the Teams number (you can use short codes and translate them in the SBC to the full Teams number if you prefer).

 

[alex_de]

Thank you for your replies and guidance

I am assuming you can make/receive calls on the SIP lines correct?

The specific NEC SC9100 is in production and there are 3 PRI with a wide sprctrum working currently. Incoming and outgoing calls are working smmothly through the PRIs. The problem is the forwarding of calls from the PRI to the SIP Trunk and vice versa

The addition to the configuration of the specific NEC is the SIP trunk with the external SBC that handles the integration with Microsoft TEAMS. We have confirmed that the incoming calls to the NEC from the SBC originating from Microsoft Teams are working. However, the problem remains with the outgoing calls from the NEC (extensions and PRI forwarding) towards the SIP Trunk.

I will give your advices to the technicians for the F-route

 

[OzzieGeorge]

Alex

In my set up (not yet working due to licensing) I have extension numbers 3xxx so I created an access code of 4 as trunk access and then used F route programming to get to the trunk group I have the sip trunks that go to the SBC in. I will make the xxx of the 3xxx match the 4xxx number (I do not strip the 4 off when sending the call to the sip trunk) This way if you want the desk phone say 3123 that is what you dial but if you want the Teams link only you dial 4123. You then, if required, set call forward ring both if the user wants it to ring both. The SBC should be able to receive the 4xxx number and translate it to the full teams number.

Once set up, you should be able to wireshark the sip trunks and see the 4xxx calls being sent to the SBC to confirm that the PBX is sending the call.

 

[CoralTech]

A couple of suggestions. You might want to try using VE forwarded to that number. Assign that VE to the trunk group you want it to dial out on. Another option is to make the SIP lines into TIE instead of DID lines. I don't know if this would work but it does on PRI. One you have TIE lines it becomes WAY easier to handle calls between systems. Then assign your leading digits in your numbering plan and F-route tables and you are good to go. Make sure to use Caller-ID cut through on the trunks and allow trunk to trunk.