Hi team,

There is a scenario where the organization is using an Avaya PBX solution which connects to  an SBC that does the SIP routing. Lync Enterprise Voice is to be introduced and I'm thinking of whats the best approach to a scenario like this.

(C)->>>--SIP ROUTE-----| SBC |---| Lync GW |----| Lync Server |-----(Lync with ext 2xx) (B)
                                          |
                                          |
                                   |Avaya PBX|----(Endpoints with ext 1xx) (lets Call A)

In this scenario, 

1) Is this a possible scenario?
2) Can I have routing configured on the Gateway that will Route A->A, A->B, A-C and vise-versa with the different extensions 1xx and 2xx ?
3) In this case, can I have a user on the B side calling a user having a AVAYA extension(A) with Lync enabled ? In this case how can i get the option to dial both the traditional phone and the lync client together of User in Side A ? In what way can I achieve this ?

Thank You.
Cheers.

Hi, See the answers below: 1. Yes this is a possible scenario if you create the correct routes on the Avaya, gateway and in Lync. Although this would cause all calls from external to internal being handeled by the Avaya. Why not placing the gateway in front of the Avaya. In that case calls can be directly routed to either the Avaya or Lync 2. As already mentioned I recommend to place the gateway in front of the Avaya. 3. This is not possible in this scenarios although though you might trick it with simultanious call but this would require to unique extensions per user. If you want to perform RCC for example you will need an additinal aplpliance or 3rd party software Johan

Hi Johan,

Thank you for the explanations,

1) Could you please explain me "this would cause all calls from external to internal being handeled by the Avaya"? I was having the thought that if i make the below routes from the gateway, the External calls will go to the appropriate destination depending on the extension and the routes. (I'm not 100% sure about the below but is just an assumption)

• Call from External, If dest ext 1xx detected, route to Avaya
• Call from External, if dest ext 2xx detected, route to Lync (GW)
• Call from Internal (Avaya), if dest ext 2xx detected, route to Lync (GW)
• Call from Internal (Lync), if dest ext 1xx detected, route to Avaya

2)so as per the my understanding, your suggested topology will look like this with the below routes?

(C)->>>--SIP ROUTE-----| SBC |
                                        |
                                  | Lync GW |----| Lync Server |-----(Lync with ext 2xx) (B)
                                        |
                                  |Avaya PBX|----(Endpoints with ext 1xx) (lets Call A)

If I go ahead with this, can you please give me some insights as what should the following be enabled in terms of routing and number assigning?

1) SBC (The SBC already uses SIP to connect to the current Avaya, hence when in the new topology, all incoming calls from the External (C) are to be routed to the GW?)

2) Then in the Gateway, we need to have two routes configured 

• We need to have two routes configured to the following;
• ****The incoming from the SBC with the destination ext with 1xx is to be routed to the Avaya
• ****The incoming from the SBC with the destination ext with 2xx is to be routed to the Mediation Server

• Have another route configured to handle;
• ****The incoming calls from the Avaya with the dest. ext with 2xx to be routed to Mediation Server

• Have another route configured to handle;
• ****The incoming calls from the Lync with the dest. ext with 1xx to be routed to Mediation Server

Thank You.
Cheers.

Hi,

Your correct if the gateway is placed in front of the Avaya then you can do routing on the gateway to either Lync or Avaya.

1. Is the SBC located at your end or with the SIP provider? Normally the SIP trunk is terminated on the gateway. Keep in mind that sometimes requires a specific license on a gateway
2. Yes your correct. What numbers will you assign to the users full E.164 or only the extension?

Regards,

Johan