Is security an issue? Or will all calls behave exactly the same? You can use acl.conf.xml for letting in only certain IP addrs if need be. In any case, you could add something like this in conf/dialplan/public.xml: <extension name="fwd to external profile"> <condition field="destination_number" expression="([your DID number])"> <action application="bridge" data="sofia/internal/$1@x.x.x.x:yyyy"/> </condition> </extension> Where x.x.x.x:yyyy is the IP address and port that Lync is listening on. Give that a try and see what happens... :) -MC On Wed, Dec 29, 2010 at 2:26 PM, Ralph Eckhard <ralph@eckhard.nl> wrote:
Hi there,
I’m trying to use FreeSwitch to connect my MS Lync (previously OCS) to a SIP-trunk. Problem is that Lync only works using TCP-based trunks, while my SIP-provider uses UDP.
I understand that by using FreeSwitch I can bridge these two protocols.
I installed FreeSwitch on my Lync server and configured both the external (to sip-provider) and internal (to Lync) sip profiles. These both work; when i dial in from remote to a DDI on my trunk, i can see the incoming call in the FS CLI. Same goes for outgoing calls; when dialing a number from my lync-client, the FS CLI logs the call.
Now, what do i config to bridge the two trunks? I don’t need any extra extensions or otherwise, all call handling is done by Lync. All calls coming in from my external sip trunk need to be forwarded to my internal sip, and all calls originating from my internal sip need to be forwarded to my external sip trunk.
Can someone point me in the right direction?
Thanks in advance ;)
Ralph
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org