QSIG link between IP500V2 and an NEC SV8100 2

[wjtcol]

Hi,

My client has a third party looking to link their NEC SV8100 PBX to their IP500V2; the NEC is going to be sending calls to extensions on the IP500 and also using the IP500s SIP line for external calls.

We're getting them a PRI card for the IP500, and we already have the Voice networking license.

I've no idea what sort of cable to use to link them together though.

I also have no idea how it's going to handle routing the calls into the system; when the NEC sends a call to the Avaya, does it get handled by ICR like a "normal" PRI line?

Thanks,

Will

 

[hairlessupportmonkey]

why not use SIP to the NEC as well?

ACSS - SME
General Geek

 

[amriddle01]

Qsig links use shortcodes, Line shortcodes first and in their absence/no match system shortcodes. I would be tempted to use SIP to link these systems, does the NEC do SIP?


Avaya Implementation Qualified Professional Specialist Technical Engineer (AIQPSTE)

 

[madwok]

The NEC SV8100 do support SIP trunks and SIP endpoints. Like other had said, do the SIP instead .

 

[eddiebullman]

Hi

I have tried to link SV8100 to Avaya with a direct sip link and had problems on the SV side of things

If you have a PRI card in both systems i would use QSIG as for the cable you need a crossover cable pin 1 to 4 and pin 2 to 5 then 4 to 1 and 5 to 2

on the SV8100 you need to use F-route to send calls across the link and incoming call tables to route incoming calls

on the Avaya use shortcodes to route call across the link and then incoming call routes to route incoming calls


P.S if sone one has this working with SIP let me know as i had a lot of fun with the NEC.

 

[amriddle01]

QSIG does not use Incoming Call Route, it uses shortcodes (when not an extn)

The line Short Code tab is shown for internal trunk types: QSIG (T1, E1, H323), BRI S0, H323, SCN. Incoming calls are routed by looking for a match to the incoming digits in the following order:

· Extension number (including remote numbers in a Small Community Network).

· Line short codes (excluding ? short code).

· System short codes (excluding ? short code).

· Line ? short code.

· System ? short code.

Avaya Implementation Qualified Professional Specialist Technical Engineer (AIQPSTE)

 

[wjtcol]

Thanks all, very useful information.

Cheers,

Will

 

[wjtcol]

OK, resurrecting this one... We are able to call the NEC, but nothing happens when they call in. Can anyone give me an example of how the line shortcode should be set?

 

[wjtcol]

Ah hang on, I've re-read that excerpt from the help files -

Incoming calls are routed by looking for a match to the incoming digits in the following order:

· Extension number (including remote numbers in a Small Community Network).

Am I right then to interpret that as meaning if the NEC sends "801" and there is an extension numbered 801, it will just ring 801?

 

[wjtcol]

And yes, it does mean that, the NEC guys have been able to call the Avaya. Looks like they were just having trouble sending their traffic down their PRI instead of down their BRIs.

Next question: sending their traffic out over a SIP trunk on the Avaya - we have a system shortcode that Avaya users use to call externally via SIP, ie 9N; , if the NEC system sends a call with a 9 prefix, will that match to the system shortcode and send the call out over the SIP trunk?

 

[amriddle01]

Yes it will, but it's quicker and easier to just try this stuff first then ask here, you will also learn more that way


Avaya Implementation Qualified Professional Specialist Technical Engineer (AIQPSTE)