SIP TRUNK LICENSE VERSUS VOICE NETWORKING LICENSE

[smartedge1]

We have a customer having IP office server edition at the head office and IPOv2 at the branch office both on release 9.1. They want users at both sites to be able to call each other .I told them that they require voice networking license at both ends for the SCN but the IT manager said he wants to connect both offices via sip trunk since he already has some sip trunk channel licenses on the server edition . I would like to know what is the advantage or disadvantage of this methods . Thanks in advance .

 

[CarGoSki]

You can look up SCN features and eliminate them all.
Mostly SCN is used for centralized voicemail and you purchase the voice networking licenses for max simultaneous channels.
But there are many SCN features when the ip trunk is configured as SCN.
So your IT has a plan to configure SIP lines directly to each other?
I know you can with the PRI cards but I have not heard of that using SIP trunks.
For PRI one has to be set as the CO and the other set as CPE.

 

[janni78]

If they just wanna be able to call each other you can configure a SIP trunk between the systems.

"Trying is the first step to failure..." - Homer

 

[smartedge1]

Thanks for the hint . I have seen that there are more features using SCN license . Sip trunk will just be for extension to extension calling across the branches .

 

[amriddle01]

It works well for that, as long as you aren't using the users SIP tab for SIP trunks it will also pass name and number as though internal

 

[Albus2]

smartedge1,
As you have a server edition at the HQ, why not attach the two 500v2 as gateways?
If you want more independent systems, go for SIP trunks.

 

[IPGuru]

Advantages:
They wont need to buy any additional licences

Disadvantages:
operation will be poor & potentialy troublesome.

Probably the biggest potential problem is No ant-tromboning, so if a call gets repeatedly transferred you will use up all available trunks.




A Maintenance contract is essential, not a Luxury.
Do things on the cheap & it will cost you dear

 

[jhengel]

The most simple answer is that one gives you a headache and one gives proper results and adequate features.

The Server Edition and the IP500v2 expansion system each require an SE license, it is quite different from the old SCN license model (which I have not seen brought up here much yet). Having the IP500v2 as an expansion system will give a centrally managed, centrally licensed, system with fluid features and call functionality between the two. The SIP trunks between systems "works" for basic calling but when all systems are Avaya across the board we generally draw a pretty hard line for the customer to save them from themselves. This is generally where we go - "You can certainly go down that path but another business partner may be better serving you".

 

[janni78]

If someone wanna send their customers to other BPs cause the wanna interconnect using SIP please send them to me.

It's basic SIP trunking no different than connecting it to a 3rd party solution on which you can find a bunch of devconnect application notes.
If the customer is fine with just basic site to site calling why invest in a SE license to centralize the whole system.
Far more custom solutions are recommended here on a regular basis.

"Trying is the first step to failure..." - Homer

 

[smartedge1]

I think adding a IPOV2 system as an expansion on an SE will generate a virtual SE license on the IPOV2 . Please correct me if i am wrong .
@ Albus2 what do you mean by adding IPOV2 as gateway ? . Do you mean adding the V2 as secondary server ?.

 

[janni78]

You'll need an additional SE license for each gateway you add to the solution.

"Trying is the first step to failure..." - Homer

 

[tlpeter]

When you make it a gateway for the server edition than it is connected like it is local.
all users are configured on the server edition and you have unlimited SCN channels and 2 extra VMPro ports on the server edition.
It is an expensive license but do not forget no voice networking licenses needed and two VMPro channels with it (per IP500V2).



BAZINGA!

I'm not insane, my mother had me tested!