Lync integration HELP!

[ConfusedEngineer]

Hi Guys,

I have a client with IPO500 on r9.0, they have had an Audiocodes Gateway installed to connect Lync to the IPO using a PRI trunk between IPO and Lync Gateway. Site dials out over another PRI circuit OR a SIP trunk.

The easier part:
Using Twinning to existing users calls are working inbound and outbound, however...

I need to be able to split which users on the LYNC dial out over the SIP and which dial over the PRI (This should work using a dialling prefix shortcode but i'm trying to avoid prefixing if possible), at the moment all calls are dialling out over the PRI.

The HARD PART:

I need to present the users DDI over the SIP or PRI (depending on which trunk the user is dialling out over. The users will not change the trunk they use, if they have a DDI on the SIP they will dial out from the SIP, likewise on the PRI)
At present the Lync users present the Lync EXTN number internally but present the default PRI trunk number on external calls.



This has been giving me a headache for a couple of days now!!!
Any suggestions??????

AIPS/ACSS

 

[mkoker]

So they're using Lync and the IPO for Voice?

 

[ConfusedEngineer]

that's correct. Lync dials out via AudioCodes gateway PRI to PRI on the Avaya, then makes the call out from the Avaya by either another PRI or SIP depending on the Users DDI (some have DDI on PRI trunk some on SIP)

AIPS/ACSS

 

[amriddle01]

Why is the audiocodes in the mix? A direct SIP link would be better and easier to manage

 

[ConfusedEngineer]

We were told that is how they were doing it, no option was given, site simply asked us to provide a PRI trunk for them to connect to. I can see it being ripped out in the future!

AIPS/ACSS

 

[pkdev]

On the Lync side, you should split your users in 2 groups with 2 different dialplan. Each dialplan will had a prefix to external number. Lync users wont have to had the prefix, Lync server will to it.

On the IPO side, create 2 "Dial" shortcode with the 2 different prefix added by Lync. Each dialplan use a different ARS to go out on SIP or PRI.

Presenting the right DID is really the hard part of this I think.
Is there a logic between internal number and DID ? For example, user 200 as a DID +XXXXXX200 ?
If so it will be easy, just use .XXXXXE in your ARS.
If not it will be harder. Maybe you can use Lync URI if IPO or Audiocode gateway can interpret it (something like sip:+XXXXX200,tel:200).
Does someone knows if IPO will use the DID present in "Incoming call route" if the destination is not an IPO internal user ?

 

[ConfusedEngineer]

pkdev:
I was hoping to avaoid the prefix for outbound dialling, but I think it will be the only way!

The DDI presentation...
I have an incoming route from the audiocodes trunk of incomming number * with destination of . This appears to be working OK. Calls route to EXTN on the Avaya or externally over ISDN (with the default ISDN base number)
I am testing a shortcode on the ISDN outbound ? . sXXE
The extn numbers are the last 4 digits of the DDI, I have insisted this with site as the only way to make this work!

The SIP outgoing CLI is the hardest part, by default the system is going to be looking for the USER SIP tab for outgoing CLI number, obviously this won't exist on the extn coming from the gateway, so i'm not sure how/where to create a rule to present the number. I guess there will need to be a URI set in the SIP ARS?

AIPS/ACSS

 

[pkdev]

did you test the ?/.sXXXE on the SIP ARS ? I think it should work too

 

[ConfusedEngineer]

Thanks pkdev.
It's with site to test now!

AIPS/ACSS