Lync 2010 Server and 3CX IP-PBX?
-
Thursday, January 20, 2011 12:14 PM
How can we connect Lync 2010 Server to 3CX IP-PBX?
Now we have 3CX IP-PBX for all voice communication, but we are looking at Lync 2010 Server because of its features.
But Lync 2010 Server has limitations in ways to connect to VOIP SIP Providers, so we intend to use our 3CX IP-PBX as proxy to connect Lync 2010 Server to our VOIP providers. (Internal Lync Users (Phones and Clients) - Lync 2010 Server - 3CX IP-PBX - Our current VOIP SIP Providers)
Can anybody tell us how to implement this?
Big thanks in advance.
- Moved by Ben-Shun ZhuModerator Friday, January 21, 2011 10:11 AM incorrect queue (From:Planning and Deployment)
All Replies
-
Thursday, January 20, 2011 4:18 PM
I'd be interested in this kind of implementation as well.
I'm halfway through, I can get the calls to 3CX, but it refuses them when they come from lync since the extension is not registered... really frustrating. Anybody has got experiences with this?
This is what I get in the 3CX logs if I try to call a 3CX extension from Lync. Same issue if I try to do an external call...
15:50:58.904 [CM500002]: Unidentified incoming call. Review INVITE and adjust source identification:
INVITE sip:585@192.168.10.31;user=phone SIP/2.0
Via: SIP/2.0/TCP 10.10.3.33:60323;branch=z9hG4bK1b5b3caa
Max-Forwards: 70
Contact: <sip:SKHQ-LYNC.contoso.com:5068;transport=Tcp;maddr=10.10.3.33;ms-opaque=bf52fcd38d48c2ee>
To: <sip:585@192.168.10.31;user=phone>
From: "Lync User"<sip:+44207123456;ext=456@skhq-lync.contoso.com;user=phone>;tag=343d01ff8;epid=0E93FF0C5D
Call-ID: 50107655-ab5c-497e-b104-a65e1fb16533
CSeq: 1 INVITE
Allow: ACK, CANCEL, BYE, INVITE, PRACK, UPDATE
Supported: 100rel
User-Agent: RTCC/4.0.0.0 MediationServer
Content-Length: 0
15:50:58.904 [CM302001]: Authorization system can not identify source of: SipReq: INVITE 585@192.168.10.31 tid=1b5b3caa cseq=INVITE contact=skhq-lync.contoso.com:5068 / 1 from(wire)
-
Thursday, January 20, 2011 6:43 PM
I have tested 3CX back in days. While it does have it's own place as platform of choice, integration with OCS/Lync is not an easy task and furthermore add great deal of complication for support and maintenance.
If the service provider is the sole reason that you guys looking at this scenario, I would advice to take a look at the new gateway the partners are now offering. I now have Mediant 1000 SBC in production. My provider does SIP over TCP and my trunks are fixed IP, but this piece of equipment could do a translation SIP UDP to TCP as well as supports SIP Trunk Registration. With other words, you can now connect Lync to ANY provider out there via Certified Gateway.
Drago
http://ocsdude.blogspot.com | MVP Snom OCS Edition -
Friday, January 21, 2011 6:33 AM
As you can see on the Lync Open Interoperability page, your 3CX IP-PBX is not on the support IP-PBX'es for Direct SIP Connections.
As Drago indicated, you'll need to purchase a certified gateway to put in between both. It will offer you a supported configuration and more flexibility for the future (you can later on attach the gateway directly to your PSTN outbreak point or SIP trunk provider). Please talk to a gateway provider for more information and which device is best for you and your budget.
Technical Specialist Microsoft OCS/Lync & UC Voice Specialisation - http://www.uwictpartner.be
If you think my post is the answer to your question, please mark it as answer so future visitors can easily find it. -
Friday, January 21, 2011 7:38 AM
"Not officially supporting" in not the same as "not working at all". Maybe somebody has workaround or special settings something else.
I understand that certified gateway could be solution butt I wonder if we can do that without it.
-
Friday, January 21, 2011 7:50 AMI would recommend contacting your PBX partner or vendor and see if they have that specific information. If it is known to work, they should have that information. If they have no such information, I wouldn't recommend deploying a mission critical voice solution in an unsupported way.
Technical Specialist Microsoft OCS/Lync & UC Voice Specialisation - http://www.uwictpartner.be
If you think my post is the answer to your question, please mark it as answer so future visitors can easily find it. -
Friday, January 21, 2011 10:40 AMRuben, 3CX and MS are in some sense competitors (IP-PBX manufactures) - so 3CX not willing to support and help with Lync integration...
-
Friday, January 21, 2011 11:29 AM
Yeah I noticed that too :) Not feeling a good vibe in their forums when you mention Lync hehe...
Drago: I have been reading through your tutorial on how to set up Freeswitch as a Sip-TCP/UDP gateway to communicate with UDP-based providers (and I guess PBX too). Would you think it'd be a viable option to get 3CX working with Freeswitch as a bridge? http://social.microsoft.com/Forums/en-US/communicationsservertelephony/thread/0d5e8ca6-1b8a-4ed7-ac4f-816e5c814921
Mind you, for me it wouldn't be mission critical to get voice out of Lync, as the main pbx for the time being will still be 3CX (we have about 100 Linksys SPA-941 phones which are not going to work with Lync anyways, and I can't just replace them all with supported phones), that said, it'd be good if people could make calls with it...
Max
-
Friday, January 21, 2011 11:55 AMI would be interested in the outcome as well as I currently have 3CX deployed and I would love to see it integrated with Lync somehow. As of right now I have the two completely separate and I've been trying to figure out a way to use my Skype account with Lync (without needing to run AsteriskNOW).
-
Friday, January 21, 2011 12:52 PMWe have Snom phones and they are compatible with Lync, so we would like to replace 3CX by Lync. But we can not connect it to our provider, so we need some "proxy" (we would like it to be 3CX because we have already bought it).
- Edited by TrustyM Friday, January 21, 2011 2:41 PM
-
Friday, January 21, 2011 1:05 PM
You should not be satisfied when you get that answer from them. Cisco & Alcatel are also competitors of Microsoft and yet they deliver multiple integration options.
Technical Specialist Microsoft OCS/Lync & UC Voice Specialisation - http://www.uwictpartner.be
If you think my post is the answer to your question, please mark it as answer so future visitors can easily find it. -
Friday, January 21, 2011 1:09 PM
You can try to get it working using 3CX, but you might spend more money in lost working hours for a non-guaranteed solution then deploying a certified solution.
If you find out how to get it working, feel free to post your findings in this topic so others will be helped
Technical Specialist Microsoft OCS/Lync & UC Voice Specialisation - http://www.uwictpartner.be
If you think my post is the answer to your question, please mark it as answer so future visitors can easily find it. -
Friday, January 21, 2011 1:58 PM
“Just when I thought I was out (having philosophical rampage on a technical forum), they pull me back in” You gotta love The Godfather J
First, can’t blame the guys from 3CX for lack of support. Unified Communications is addictive. What we had yesterday is not enough today. Your coke dealer will not offer you meth unless he sales it tooJ. So, if they offer the tiniest way to interconnect, tomorrow you will demand presence, the next day integration with Communicator, then support for Exchange email. Then Exchange AA… and soon on later they will have to stop developing and turn Microsoft UC sidekick.
No offence, but I cannot see a clear vision of your goal. If you want to use your ATA’s and SIP Phones with Lync, the only solution I am aware of is SmartSIP: http://www.net.com/Pages/Solution.aspx?pgid=229. Even if you connect 3CX to Lync (and you probably can, I have seen post about integration with OCS, and Lync is no different here), think of what you will get – a phone call (perhaps). Neither presence nor any of the other UC goodies.
Please, do take time and lay down what is exactly that you want to achieve. We will debunk J the impossible and might be able to help with what is doable
Drago
P.S. This is just the beginning of a long conversation on the topic, I sense…
http://ocsdude.blogspot.com | MVP Snom OCS Edition -
Friday, January 21, 2011 2:24 PM
Drago, now we need to connect Lync to our VOIP providers. It can't be done direct (because of special Lync requirements which can't be met by current VOIP Providers), so we need something between them and with minimum extra money. We already have 3CX and we want to find the way to use it as proxy between Lync and current VOIP providers.
Phones are used only internaly (office Lan) and will be connected directly to Lync (we do not need external (from internet) connected phones), so all the goodies of Lync and UC will be used (this was the main reason to go to Lync).
-
Friday, January 21, 2011 2:30 PMAll I'm looking for is some way to route inbound/outbound calls through 3CX. I would be happy using Lync for all internal calls, I just want to use my Skype integration in 3CX for external calling. My deployment is used in our organization which is fairly small at this point and all expenses are out-of-pocket.
-
Friday, January 21, 2011 2:30 PMRuben, we understand what you are talking about and we are going to test possible solution for some time before deploying for production.
-
Friday, January 21, 2011 2:49 PM
Please make sure that the 3CX accepts INVITE's using TCP, as most SIP implementations tend to work over UDP. Based on the log file you provide, I would say that this is already OK.
If this is the error you get on the 3CX system:
15:50:58.904 [CM302001]: Authorization system can not identify source of: SipReq: INVITE 585@192.168.10.31 tid=1b5b3caa cseq=INVITE contact=skhq-lync.contoso.com:5068 / 1 from(wire)
Then my understanding is you need to add the IPaddress:port combination as a trusted source in the 3CX system. It does not accept calls from that IP or IP:port combination => "authorization system cannot identify...".
If you already configured the FQDN of the mediation server as trusted in 3CX, it is not used as the logs clearly indicate that the mediation server is adding the IP address instead of the SIP domain name to the INVITE. Remove the FQDN and add the IP address instead.
I'm not familiar with a 3CX system so cannot help on that.
Technical Specialist Microsoft OCS/Lync & UC Voice Specialisation - http://www.uwictpartner.be
If you think my post is the answer to your question, please mark it as answer so future visitors can easily find it. -
Friday, January 21, 2011 4:04 PM
Thanks for all the answers so far, you guys have surely been helpful already. As Ruben says, that'd be the logic thing to do, too bad I can't figure out for my life where the heck in 3CX you're supposed to trust something that is not a local extension.
@Drago: I perfectly know what you mean, although we'd rather keep our UC cocaine consumption within recreational limits lol, which is, like Trusty said: use our current voip provider which won't support Lync until next year when they'll complete testing, use the normal desk phones in the office, but progressively get people to love lync and enterprise voice, and they could use it nicely when they're out, while I save money by routing calls through 3CX for the time being.
At the moment we deployed the 3CX softphone, but it's a very flakey solution, even using their proprietary TCP tunnel, sometimes it won't work, or audio won't get through, if the clients don't configure RTP ports correctly in the phone etc. I can't expect a salesman to be familiar with RTP ports which are never default and don't get provisioned correctly by 3CX.
Next week (really can't find the will this afternoon), I'll try to check if there's any way to make 3CX trust Lync without being hooked to an extension. If that fails, I'll deploy Freeswitch and try to connect it to an udp tunnel, which should be fairly easier for 3CX to understand...
Have a nice weekend guys.
@Drago: yes, I can see this is going to become a LONG discussion hehe
-
Friday, January 21, 2011 4:14 PM
Trusty,
You are in the best position so far J, since you are looking for a way to eliminate 3CX completely. What you (and others) need is either SBC (session Border Controller) or B2BUA (Back to Back User Agent). I have mentioned already AudioCodes MSBG with SBC. It works and it works well. It is, however, priced above the “acceptable affordability” of a small deployment (on my own opinion).
So, what we can do? Indeed - FreeSwitch. I have spent months playing with it and all I can tell – you can connect it to a toaster and make a phone call. I was able to interconnect OCS R2, Lync and Exchange UM, i.e. use it as B2BUA. On the PSTN leg, got it to work with CallCentric, Boradvox, MagicJack, Vonage and others.
The concept is simple – FS supports trunk registration and does SIP over TCP or UDP and so, who is our provider is irrelevant (I see the latest build fully supports Skype as well…) and on the other leg – OCS or Lync (SIP over TCP only). You can set it to transcode RTP (G.729 to G7.11) or pass-through (if your provider does G.711)
FS can be installed on standalone server (or windows XP or 7 if you want) and/or can happily stay on top of the Lync server (a lot more complex installation and configuration).
I can hear you subconsciously screaming – “stop talking and give the solution…” Eh, it is not so simple. FS is an open source. The support sucks (if there is any) and requires dedication and understanding of the concepts, configuration and possible implications. Because of so many providers, there is no “out of the box” or “unified” setup. I am willing to help anyone who wants to go there, but not “support” it.
Here is the dev. web site: http://www.freeswitch.org . Read, test and ask whatever is not clear.
Frankly, I decided NOT to blog about this solution mainly because I have seen a lot of people jumping on it and wreaking havoc in their Production Environments.
Having said all this, FS is still a valuable option… and yeah – SmartSip form .NET is built on the base of FS source code J
Drago
http://ocsdude.blogspot.com | MVP Snom OCS Edition -
Friday, January 21, 2011 4:27 PM
Stims,
I your case, you might want to consider placing FS between your provider and 3CX/Lync. You can setup FS to “fork” the incoming call to both systems and the call can be picked on either (FS will close the other channel).
Drago
http://ocsdude.blogspot.com | MVP Snom OCS Edition -
Friday, January 21, 2011 4:51 PM
Stims, let us know if you'll be successful in connecting Lync and 3CX to each other.
-
Friday, January 21, 2011 4:56 PM
Thanks Drago,
sounds exactly like what I want, a hacky solution to keep everything together until I'll manage to get rid of 3CX as well.
PS: wanna know the funny bit? 3CX *fully* supports Exchange UM, so I could host the voicemail on exchange in minutes, and even have the "play on phone" function in outlook work fine and send the feed from exchange to 3cx and into the phone.
I didn't do it yet because I'd rather hook up exchange UM with Lync than with 3CX once I'm ready.
There it is then: on monday I'll deploy a new server with freeswitch, and will keep you posted on my progress. I'll use your (drago's) guide as a starting point for the configuration, and tweak as needed.
If I come up with something that works I'll definitely post every detail here!
Max
-
Friday, January 21, 2011 4:56 PM
Drago, thank you for your advices, now we need some time to look and feel Freeswitch. :)
-
Friday, January 21, 2011 5:18 PM
The “guide” is overcomplicated. Start by installing it on your workstation (single IP). Walk through the Trunk registration. Trunk to Lync is even easier. When gets to forking, ask if it is not clear.
On another note... I am curious when MSFT will run out of patience watching us discussing non-supported solutions here… Just kidding J
Good luck!
Drago
http://ocsdude.blogspot.com | MVP Snom OCS Edition -
Friday, January 21, 2011 5:48 PMDrago, I think MSFT appreciate everything that helps someone to move on their products from competitors' products, so do not worry ;)
-
Saturday, January 22, 2011 5:41 PM
I created basic FreeSwitch – Lync integration guide. Grab it here, tell your wife or girlfriend to leave you alone and have a fun.
Drago
http://ocsdude.blogspot.com | MVP Snom OCS Edition -
Sunday, January 23, 2011 9:12 AM
Stims,
If you don't mind me asking, what steps did you take to get your current setup working? I'm somewhat of a newb to Lync (and OCS) and I'm not really sure where to begin with integrating 3CX with Lync.
Thanks!
-
Wednesday, January 26, 2011 1:42 PMStims, do you have any success?
-
Thursday, January 27, 2011 11:42 AM
Hello!
Just a quick update so far, using Drago's awesome guide, yesterday I managed very easily to hook up Lync to a test trunk I created with Skype for SIP (I find it very useful, since I can get the trunk for just a month, for the numbers I need to test with and when I'm done I can just let it expire).
Just in this moment, after only a couple of hours of fiddling I managed to get both inbound and outbound calls working from Lync.
So this side is fine now. Next steps:
- Create another trunk from Freeswitch to 3CX and vice versa
- Create an extension in 3CX with the same DID as the Skype trunk
- Enable forking in Freeswitch, so that in theory, I can generate outbound calls from both 3CX and Lync, and inbound calls will make both systems ring.
- When everything works fine I'll probably have to come in one weekend, and replace the Skype test trunk with our normal trunk, fix the various dialplans etc. and make sure everything is working fine.
Can't wait to get this working!!! If it works, I promise I'll create a detailed guide on how to implement it, as I see a lot of people willing to use 3CX with Lync out there.
Max
-
Thursday, January 27, 2011 11:43 AM
Btw, sorry for the confusion, Stims is actually me, Maxesse. I was logged on by error with another account I use for MS partnership tasks :/
Max
-
Thursday, January 27, 2011 11:56 AM
Max, well done!
We are waiting for your guide! :)
-
Thursday, January 27, 2011 2:31 PM
While possible, forking to two internal gateways is bit overkillJ. Why would you want to maintain two systems when Lync alone is sufficient?
If it is because of the endpoints… since the only way users to pick or place a call (w/o Lync hardware endpoint) is via the client, I will take that they (your users) accept to use microphone and speakers. If this is the case, 3CX would stay until the users are trained and ready for the switch. The beauty here is that you can capture the migrated DID’s with RegEx and send the call to Lync, while non-migrated users will receive calls via 3CX.
Still, 100% Lync users can call 3CX and vice versa via FS (some more work on the dialplan), and so no business operations will be interrupted during the transition.
Drago
http://ocsdude.blogspot.com | MVP Snom OCS Edition -
Thursday, January 27, 2011 3:40 PM
Hello Drago,
yeah that would be the plan for me in the long run. It's just that users are scared of change, and somehow I think they don't want to lose their deskphone just yet.
Lync is a very new thing for them, they have no idea of what UC is/will bring to them, but they're gonna love it. And we're still in experimental phase with it.
If I can keep the two systems in co-existence for a while they will have time to familiarise with Lync's interface and (hopefully) use it more than their deskphone, as it'll be instantly available wherever they are (whereas now... the 3CXPhone is an exercise in patience to get it working, and it's well out of the reach of many of my users).
About internal extension calls, I'm planning to leave the internal route for Lync users and for 3CX users, so if they call an internal extension, the call will remain within its system, I don't want to create confusing routes (e.g. a 3 number ext called from Lync rings on 3CX, and stuff like that).
The other reason is that to get a completely workable MS based UC system, I also need voicemail, and for that I'll need to deploy exchange UM which I haven't got round to do yet, so at the moment I'd like for voicemail to remain in 3CX.
So fingers crossed, and let's hope my users will see the advantage of using Lync rather than 3CX...
I also have another issue to solve, I've got PIC provisioning by MS correctly, my edge passes all the tests on testocsconnectivity.com, but if I try to message any external contact I get a SIP 504 Timeout error from MSN and presence status is unknown for the external contacts. I'm a bit baffled with that issue, so I may have to open a support ticket to get it fixed (unless somebody has got any cool suggestion to try out?)
Max
-
Thursday, January 27, 2011 3:53 PM
You absolutely correct, my friend. Each environment is unique and no “boxed” solution will ever be available for this same reason. While in GMC we transitioned to OCS R2 voice in 45 days (due to overexcitement of the potential savings), we did not accounted for the “psychology of change on work place” factor and still having problems here and there.
On PIC… when did you initiate the provisioning? My own experience shows this is VERY slow procedure on MS side. Took a month to provision and activate. “SIP 504 Timeout” means the activation is not completed and their servers refuse to talk back due to ACL (or lack of “allowed domain” entry rather).
Drago
http://ocsdude.blogspot.com | MVP Snom OCS Edition -
Thursday, January 27, 2011 4:08 PM
Re the PIC problem, I did the request last thursday, exactly one week ago. By saturday I got an email saying that the provisioning was completed and working, but I was receiving those errors.
Then I wrote to the PIC provisioning team and they double checked everything and told me that all was fine on their end and that if I had further problems I should open a paid-for support ticket with MS.
Now, I haven't got problems in doing that, but I have been reading on a lots of forum posts of people with my very same issue, and then it magically worked without doing anything a few days later (up to 10 days apparently), so I'm holding back a bit since I don't want to waste money for something that might fix itself.
Therefore I decided to crack on with the enterprise voice while (hopefully) PIC will start working on its own. Wishful thinking I guess :)
Anyways, I'll probably have another week of fiddling with integrating the old 3CX and Lync, I'll keep you posted if PIC starts working, otherwise it'll be ticket time :)
Max
-
Thursday, January 27, 2011 7:39 PM
Guys, when I install Lync Server in order to use it with FreeSwitch and 3CX, in Planning tool how should I answer on questions in "Voice Infrastructure" part:
Inftrastructure
- I plant to deploy gateways using direct PSTN connection
- I plan to use SIP Trunking
- I have an existing voice inftrastructure with PBX deployedand how to answer further in this part?
-
Thursday, January 27, 2011 7:48 PM
Sip Trunking is the correct option. FS will bridge Lync, 3CX and the SIP Trunk provider via... SIP trunks :-)
Drago
http://ocsdude.blogspot.com | MVP Snom OCS Edition -
Thursday, January 27, 2011 7:56 PMThanks, Drago! :))
-
Thursday, January 27, 2011 7:58 PM
Isn't this fun?
Sometimes I think so much fun must be declared illegal, thou J
Drago
http://ocsdude.blogspot.com | MVP Snom OCS Edition -
Thursday, January 27, 2011 8:00 PM
And what for Network Line
T1 or E1? -
Thursday, January 27, 2011 8:11 PM
Don’t bother. T1 (DS-1) is the US implementation (23 voice channels + 1 for signaling), E1 (DS0) is the European (30 voice channels + 64Kbs for signaling +64Kbps for framing).
This is needed to calculate the number of call throughput, furthermore the number of circuits one needs (if this type of connectivity to PSTN will be used).
With SIP Trunking, we must pay attention on the Data bandwidth (and of course, proper handling of QoS).
Just select one and move on.
Drago
http://ocsdude.blogspot.com | MVP Snom OCS Edition -
Thursday, January 27, 2011 9:10 PM
Drago - you said "we did not accounted for the 'psychology of change on work place' factor and still having problems here and there"
I know EXACTLY what you mean. Some people embraced OCS and it's made a real improvement on the way they work.
Others fight it & refuse to learn anything new. It's really been the hardest thing with regards to OCS.
For them - we got Snom 300 phones (and thanks for your advice on config for them). Thank goodness a 'plain' regular desk phone was available at the time we implemented.
Regards
Paul Adams
pauladamsit.com -
Friday, January 28, 2011 12:56 PM
OMG I did it!
It's all working perfectly, I can hardly believe my eyes!!
Outbound calls work both from Lync and 3CX, inbound calls make both systems ring at the same time, if you don't answer after 15 seconds, 3CX's voicemail kicks in.
It's _exactly_ what I wanted to achieve for ages! Thanks so much to Drago for his help!
Now, I only have to write down the guide for you guys. It's easy really, although everybody will have to work out their own kinks in the dial plans, since every provider works differently. E.g. now that I'm testing out stuff using a Skype SIP trunk, it sends numbers in +441231234121 whereas my normal trunk sends the number without the +, and Skype requires the outbound DID to be the username, etc.
But it's all workable stuff. Also, during this troubleshooting I had to overcome the biggest obstacle: make 3CX accept the INVITE coming from an external system, to do this I found in their forums (finally) the answer, basically in the VOIP Providers section, edit the provider you created, go to Source ID, and tick the box to identify the source using DIDs, then add to the list all the DIDs associated with the provider and inbound calls will work.
This suggests me that I could actually connect Lync directly to 3CX, as I did last week (then I gave up because of all the INVITE errors). The downside of doing so (although it'd lead to a more simple setup), is that while outbound calls will work fine, inbound calls won't traverse 3CX as it won't allow you to bridge to other VOIP trunks like Freeswitch does unless they're other 3CX systems (eugh).
Happy days!!
Max
-
Friday, January 28, 2011 1:17 PM
Btw Drago, is it ok if I re-use some parts from your pdf guide to make it comprehensive? I'll rewrite everything anyways, but clearly some bits will be identical :)
Of course you'll be given big credit, I couldn't have done it without your guidance.
-
Friday, January 28, 2011 1:56 PM
Absolutely, my friend. I just threw random pieces for very basic guidance (reading the entire Wiki takes weeks)… The entire community would benefit from a well written guide (on English English J)
Glad you got it, man!
Drago
http://ocsdude.blogspot.com | MVP Snom OCS Edition -
Tuesday, February 01, 2011 5:04 PM
Hello everybody!
Here I am, I finally finished the guide, thanks so much to Drago, as I reused 3/4 of his guide to do this finalised one.
You can find it here, enjoy!!
http://blog.skinkers.com/2011/02/01/integrating-microsoft-lync-2010-and-3cx-using-freeswitch/
PS: if you have any suggestions or gotchas I forgot about while writing it, please let me know and I'll happily update it with the missing info. I'm not such a SIP guru after all :)
Max
Max Sanna IT Manager- Proposed As Answer by maxesse Tuesday, February 01, 2011 5:05 PM
-
Tuesday, February 01, 2011 7:57 PM
Great job!
Now we know how you spent your weekend :-)
Drago
http://ocsdude.blogspot.com | MVP Snom OCS Edition -
Wednesday, February 02, 2011 12:50 AM
Uh Drago, I see my post and your answer magically disappeared, do you think I violated the forum policy by posting the link to the guide?
Max
Max Sanna IT Manager -
Thursday, February 03, 2011 7:36 AM
Can I start FreeSwitch as a service in Windows 2008 R2? If yes, how that can be done?
(If a FS server will be rebooted, FreeSwitch must start automatically)
-
Thursday, February 03, 2011 10:21 AM
Hello Trusty!
You sure can, it's very easy, just shutdown the running console freeswitch, and from an elevated prompt do this:
From the directory you installed FreeSWITCH - run: freeswitch -install
That'll create a windows service.
Also, remember to put back the loglevel at INFO after finalising your setup, so it logs less useless junk.
Max
Max Sanna IT Manager -
Tuesday, March 29, 2011 12:52 PM
Hello!
I use 3CX phone system, and I connected a webphone to it. The name of the webphone is Ozeki Webphone. Since using it with the 3CX phone system I receive more calls from the website visitors. For them to call the website is completely free of charge. Check it out if you want.
http://www.ozekiphone.com/index.php?owpn=108 -
Wednesday, August 31, 2011 7:34 AM
Hello Drago and Max!
It is really direct instruction. But I had some questions, I did all accurately under the instruction, replacing only SIP options and ip addresses with mine. But it doesn't works at all
In term of I very badly understand in freeswitch I can't understand from what to diagnose a problem. I don't understand nothing in FS logs,
I would like to ask: at sofia status lync and 3cx should be shown as REGED?Can I use Registar-Based SIP for this purposes?
Drago,Can you tell me you e-mail or other contact info? i have so much questions to you
Kindly from Russia,
Mirzakhmedov Rustam
-
Wednesday, August 31, 2011 12:52 PM
As an author of a book about 3CX, this is a very interesting thread to read for "old times". ;-)
For SIP trunking at the lowest cost possible with "supported" gateway I understand Patton 4114 ($400 gateway) allows you to do plain SIP trunks into Lync. I want to write a blog guide on it.
http://windowspbx.blogspot.com -
Wednesday, August 31, 2011 1:09 PM
Hi Rustam,
sofia status should only be reged with the external SIP trunk, the internal Lync and 3CX ones should be NOREG.
You can definitely use Registrar-based SIP too.
I suggest you to turn up the level of verbosity of freeswitch's console to debug, and look thoroughly to what happens, and eventually turn on the SIP tracing in freeswitch too (sofia profile external siptrace on)
Most likely, the cause of problems can lie in the normalisation the sip provider expects, which varies for every SIP provider unfortunately.
Some expect the number to be in +442071234567 format, others want 2071234567, others want the number in different header fields.
What I suggest you to do is to connect with X-Lite straight to the SIP trunk, see if you can successfully make phone calls, and use wireshark to see what the numbers look like when forwarded and what the SIP packet looks like. This can give you lots of clues on how to tweak Freeswitch's expressions and fields to match your configuration.
Of course, this is not an easy thing to do, and if it's beyond your capabilities, I suggest you to go with a supported gateway that does all the hard work for you.
Also, if the system you're building is a production one, please, definitely go with a supported gateway, this was a one off solution I had to put together because the client was stubborn on forking to 3CX for a few months and didn't want to buy a gateway straight away, but now that they decommissioned 3CX they finally got an Audiocodes.
Hope this gives you some hints on what to look for...
Max
-
Wednesday, August 31, 2011 1:37 PM
Hi Max! you give me really nice hints. from now i'll be trying to find problem.
and one more question:it doesn't matter what my mediation server installed with front end?(I use standard Lync edition)
Lync Snooper writes me when Lync attempting to call:
TL_INFO(TF_PROTOCOL) [0]017C.1648::08/31/2011-13:36:20.181.0005632d (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(125))$$begin_record
Trace-Correlation-Id: 2452969791
Instance-Id: 00000315
Direction: incoming
Peer: lync.mars.local:5070
Message-Type: response
Start-Line: SIP/2.0 503 Service Unavailable
From: "user"<sip:user@mars.local>;tag=651421dd43;epid=4882cdc60d
To: <sip:88126600808;phone-context=defaultprofile@mars.local;user=phone>;epid=4A20581838;tag=bdfc33a16f
CSeq: 1 INVITE
Call-ID: 79d80b5c61ff4fccaa6b070ce5bd126e
VIA: SIP/2.0/TLS 192.168.0.41:49926;branch=z9hG4bK88503470.88B21BCD3C9C2884;branched=FALSE,SIP/2.0/TLS 192.168.0.51:62065;ms-received-port=62065;ms-received-cid=2900
CONTENT-LENGTH: 0
SERVER: RTCC/4.0.0.0 MediationServer
ms-endpoint-location-data: NetworkScope;ms-media-location-type=intranet
ms-diagnostics: 10025;source="Lync.Mars.local";reason="Gateway peer in outbound call is not found in topology document";component="MediationServer"
ms-diagnostics-public: 10025;reason="Gateway peer in outbound call is not found in topology document";component="MediationServer"
Message-Body: –
$$end_recordWhy it use 5070 port if 5060 is needed?
Can I tell with you into some IM messenger? icq or skype?
sorry for my little english
I'm also had read this article http://social.microsoft.com/Forums/en/communicationsservertelephony/thread/0d5e8ca6-1b8a-4ed7-ac4f-816e5c814921
But in this situation I also have questions about external mediation server and 3 network adapters. Why 3?
-
Friday, September 02, 2011 11:52 AM
Great thanks to Drago & Max cause my lync calling through FS ti PSTN,It's Great!
P.S.
I love you guys)
-
Tuesday, September 06, 2011 2:36 PM
Good Evening Everyone!
I have new problem for today,it is a big delay over 2 seconds and short interruption of sound when calling to pstn(mobile phones for instance)
What is it can be? maybe codecs?
P.S. Calls from user to user inside lync exists with very excellent quality
Thanks in advance
-
Friday, December 16, 2011 4:16 PM
social.technet.microsoft.com is a highly content site. If you want to take any information you should read this site with attentively.
<a href="http://www.voip-sip-sdk.com/p_43-how-to-setup-ozeki-voip-sip-sdk-with-freeswitch-voip.html">How to setup Ozeki VoIP SIP SDK with FreeSWITCH</a>
.png){kind=spacer}
