Microsoft Lync 2010 + VOIP

Forums › VoIP › Microsoft Lync 2010 + VOIP - SIP

tknz

182 posts

Master Geek

#84127 25-May-2011 09:31

Hi Guys,

Anyone ever connected a SIP Trunk to Lync 2010, company of around 300 staff, across NZ and AUS and we're looking at deploying unified COMS, OCS is the most used medium, just chat and voice, but ideally we would like to convert our ISDN lines to SIP for backup, but carry most voice over carrier grade SIP Trunks.

1 | 2

30853 posts

Uber Geek

Retired Mod

Trusted

Biddle Corp

Lifetime subscriber

#473899 25-May-2011 13:29

Talk to WorldxChange.

tknz

182 posts

Master Geek

#473981 25-May-2011 15:34

sbiddle: Talk to WorldxChange.

Thanks, however the question was wider than one VOIP provider, it was more directed towards whether anyone has "implemented" this before.

maverick

3594 posts

Uber Geek

Trusted

WorldxChange

#473995 25-May-2011 15:52

Yes we have , the previous version known as OCS is fully deployed on our network now, OCS has some unique requirements in that some call examples actually break normal SIP RFC so the providers SBC , SIP proxies must be capable of terminating OCS calls as well as TCP SIP, so when talking to a provider you may want to make sure they can.

Yes I am a employee of WxC (My Profile) ... but I do have my own opinions as well

https://www.facebook.com/wxccommunications

tknz

182 posts

Master Geek

#473997 25-May-2011 15:54

Oh excellent! so you guys currently are using OCS? we use OCS at present, moving to Lync 2010 shortly. Do you support SIP trunking into OCS/Lync? I'd be very interested in having a preliminary discussion with you guys.

maverick

3594 posts

Uber Geek

Trusted

WorldxChange

#474028 25-May-2011 16:28

No we have a customer using OCS with TCP SIP trunking across our network, we don't use it ourselves , are you deploying this yourselves or via a integrator ?

Yes I am a employee of WxC (My Profile) ... but I do have my own opinions as well

https://www.facebook.com/wxccommunications

tknz

182 posts

Master Geek

#474031 25-May-2011 16:32

Ourselves. I'm just interested in whether many people in this community have deployed the solution.

sbiddle

30853 posts

Uber Geek

Retired Mod

Trusted

Biddle Corp

Lifetime subscriber

#474050 25-May-2011 16:59

I know of a couple of people who have trialled Lync and use Asterisk as a proxy for the TCP<->UDP conversion since most VoIP providers don't support TCP for SIP.

Sharesies

Trade NZ and US shares and funds with Sharesies (affiliate link).

maverick

3594 posts

Uber Geek

Trusted

WorldxChange

#474054 25-May-2011 17:06

Not many as it can be pretty intensive so requires a bit of expertise it seems, Steve the biggest issue with this will be 183 without SDP you can proxy UDP - TCP but the SDP info was the biggest issue as it breaks normal RFC for session progress, MS decided they would go with it because they are MS

Yes I am a employee of WxC (My Profile) ... but I do have my own opinions as well

https://www.facebook.com/wxccommunications

tknz

182 posts

Master Geek

#474058 25-May-2011 17:16

All right well does Wxc do TCP SIP? If so I'd be interested in hearing from your staff.

Regs

4066 posts

Uber Geek

Trusted

Snowflake

#474060 25-May-2011 17:20

i have lync and callplus sip trunks working together (either over public internet or private vlan). MHA hosting use Orcon SIP trunks for their hosted Lync solution. WXC as above. Few options to consider.

Sales Engineer
Snowflake
www.snowflake.com

about.me/nzregs
Twitter: @nzregs

Regs

4066 posts

Uber Geek

Trusted

Snowflake

#474061 25-May-2011 17:24

unsure about WXC but Orcon and CallPlus both support TCP SIP trunks.

Also note that the RFC says you can use either TCP or UDP for SIP trunks. It doesnt mandate either UDP or TCP. TCP gives you a bit more control over bandwidth and delivery and I believe that is one of the reasons for choosing it.

Sales Engineer
Snowflake
www.snowflake.com

about.me/nzregs
Twitter: @nzregs

maverick

3594 posts

Uber Geek

Trusted

WorldxChange

#474072 25-May-2011 17:38

The RFC I'm referring to is nothing to with "SIP" itself it's to to do with the treatment of the session progress 183 message with no SDP info contained in it, this causes a no ring back issue for inbound calls if the proxy is not capable of dealing with it, what we have seen is people put in a proxy "siperator" box with various degress of sucess in between to handle this as apposed to working directly.

If you wish PM me your details and I can get one of my sales team to give you a call

Yes as I said in my earlier post, we have a customer already running this directly over a TCP trunk

Yes I am a employee of WxC (My Profile) ... but I do have my own opinions as well

https://www.facebook.com/wxccommunications

Regs

4066 posts

Uber Geek

Trusted

Snowflake

#474203 25-May-2011 23:37

i was intending my reply towards the 'most providers dont support tcp for sip' than the SDP proxy issues... there was always an argument that UDP is the 'right' way to do VoIP and that TCP was the 'wrong' way. Ideally, an SBC should support UDP, TCP and TLS, and not just 1/3.

wrt/ SDP issues - is this something you have encountered with OCS, OCS R2 and/or Lync? Out of interest, what are WXC using for SBC?

Sales Engineer
Snowflake
www.snowflake.com

about.me/nzregs
Twitter: @nzregs

maverick

3594 posts

Uber Geek

Trusted

WorldxChange

#474224 26-May-2011 07:14

The issue has been around since day one almost 3 or 4 years now, it's a non issue as far as MS are concerned they just didn't agree with the RFC as it didn't suit their deployment for OCS so they did it there own way, so now it requires a SP SBC or Proxy that can handle it natively or customers will have use an expensive "siperator" box in front of OCS to do the conversion for them.... You should be able to do it without the need for an expensive proxy in front, we support it natively.

Here lies the problem, an actual 183 session progress from a deployed OCS platform

SIP/2.0 183 Session Progress
FROM: ;tag=3515339458-607385
TO: ;tag=87e39abcbd;epid=A4D0D7DA50
CSEQ: 1 INVITE
CALL-ID: 22858659-3515339458-607377@
VIA: SIP/2.0/TCP xxx.xxx.xxx.xxx:5060;branch=z9hG4bKe81a6070c8ac88dd251d33f8cb2a08d1
CONTACT:
CONTENT-LENGTH: 0
ALLOW: CANCEL
ALLOW: BYE
ALLOW: UPDATE
ALLOW: PRACK
SERVER: RTCC/4.0.0.0 MediationServer

As for what we use here ... trade secret :)

Yes I am a employee of WxC (My Profile) ... but I do have my own opinions as well

https://www.facebook.com/wxccommunications

Regs

4066 posts

Uber Geek

Trusted

Snowflake

#474271 26-May-2011 10:08

maverick:
As for what we use here ... trade secret :)

the 'internet' would have me believe you're using Acme Packet products :-) I know they have done a lot of work with OCS/Lync compatibility..

Sales Engineer
Snowflake
www.snowflake.com

about.me/nzregs
Twitter: @nzregs

1 | 2