SV9100 SIP trunk to 3CX

[SchlAdmin]

Good Day,
I am trying to assist our Work From Home situation by linking a 3CX system to our SV9100 system.
I have created a SIP Trunk in 3CX and a SIP Profile on the SV9100.

I can call the NEC system from the 3CX system but I am unable to call from NEC to 3CX. I have F-Routes configured and it shows on NEC system that it is using the correct trunk but a packet trace shows no traffic from SV9100 to the 3CX system.

A previous thread ( thread937-1804105) suggested this could be caused by needing registration for outbound calls. I have tried adjusting 84-39-12 to 1 for Register, but still unable to make outgoing calls.

A further thread (thread937-1803360) mentioned a write up on integrating the two systems, was this published?
Alternatively, could anyone please share a SIP Setup script (PCS file) with the 84-39 options to get the SV9100 talking to the 3CX server?

 

[OzzieGeorge]

Ok so I think it is me you are talking about and yes I did get it working but due to other developments, the project was abandoned (actually the NEC was abandoned) I can see if I have some backups still but IIRC the key was the name of the trunk in the 3CX had to be used in the NEC as the trunk ID (eg 11000). As a company we were totally devastated by the assitance provided by NEC on trying to work from home! we tried to get a demo licence set up to initially use ST500s (we were a major dealer with high sales figures 3-4 systems a week) but recieved no help and then got sold a "Teams" integration package that even their experts never managed to get working. We went totally 3CX in the interim and then switched to a Telstra (OZ main carrier) product called TIPT (Telstra IP Telephony) and ditched the NEC completely! This of course was devastating to me but a real positive for the company as TIPT is also able to be Webex based so offers all the benefits of 3CX but as it is an original Broadworks product, it is really customer friendly. Sorry if you don't have that alternative!

 

[SchlAdmin]

Thanks OzzieGeorge, we found NEC WfH the same, we tried the NEC UC solution and found it didn't really work and was severely lacking in features and usability.
To get things working during lockdown we did a dodgy workaround by having NEC register a SIP trunk with a virtual FreePBX which then routed calls to 3CX, but would prefer to eliminate that as part of a more permanent solution.

In 3CX were you using a Bridge or a SIP Trunk to connect to the NEC? We tried a bridge and the NEC was able to register with 3CX but as it uses different SIP header options we were only able to call from 3CX to NEC and not the other way. We are now trying to configure using a 3CX SIP Trunk rather than a bridge as it gives more SIP header configuration options, but does not let the NEC register to it.
We are using the 3CX Trunk ID as the User ID in NEC but it doesn't seem to connect.

We are also using Telstra as our SIP provider, but as we are a public high school we are limited in what products we can access, so I don't believe we can access TIPT.

If you have any other notes on configuring 3CX and NEC to talk that would be great.
I think ultimately we would like to go full 3CX as well, but only purchased the NEC system 2 years ago so hard to justify writing off that much expenditure.

Thanks

 

[Daniel_RO]

Have you investigated remote handsets on the NEC as an option. Port forwarding of 5080 to VOIP IP, 10020-10531 to DSP IP (Ports can be changed for further security in 10-46-06 for Reg port, and 84-26 for DSP Port, If you change these, more programming is required in handsets), and in your remote handset:

SIP Settings > NAT Traversal > WAN Settings - register WAN Mate IP (School Static IP), WAN SIP Mate Port (5080)

Alternately you can register a VPN from school to teacher premise, and keep all other settings, but change SIP Settings > Access Mode to 'Remote'

Does away with having to register 3CX and NEC together, and ensures remote users don't have to learn new things. This is one of the ways I have incorporated remote users with the lockdowns etc.

The other method is Mobile Extensions:

13-04 - Register Mobile No. in Speed Dial
15-22 - Register Mobile Extension using Speed Dial, change to no confirmation
22-11 - Register DID to Mobile Extension Number

with this, staff call DID, get internal tone from system, and can then call out of the system using the system trunks, or call internally within the system also.

 

[SchlAdmin]

Thanks for the ideas Daniel, unfortunately we have very little control of our firewall for port forwarding due to being centrally managed.

I was able to get the SV9100 to call the 3CX system. I needed to add a 10-23 IP System Interconnection to get it to work without registering.

I kept reviewing other threads and read the NTAC Basic SIP Trunk Tie Line to 3rd Party PBX article to check my settings.

Thanks to OzzieGeorge for several other threads that helped me find the solution and assisted with the configuration.

 

[OzzieGeorge]

Ok so we didn't register the sip trunks, they were programmed as ad hock trunks so they never actually registered so in 10-36 we just had an ID with no registration details with it. You have to have an ID in there to allow it to build the SIP header correctly.

 

[OzzieGeorge]

Well done!, My last answer I typed yesterday and forgot to submit it, I just did only to find you had sorted it!