- Adam

So say I want Lync users to utilize there client as there soft phone. That user wants to forward calls from Lync to their cell phone. That call will route out my Asterisk box.

I discovered that if you set a password on your Asterisk extension and have Lync set to Forward the call. It translates the call back to Asterisk as a known extension from an outside source (Lync) in this case that is attempting to say hey Im one of your extensions please forward this call.

The only work around I found wich is not ideal but does work is if you do not set a password on the extension. This way Asterisk does not try to validate a known extension from outside and allow it to pass the traffic.

Anyone try this or have a different way of engineering it to work with the Asterisk extension and having success forwarding Lync calls out?

Question: Subject SIP Trunks:
My current sip trunk has only one DID is it possible for a SIP provider to have mulitple DIDs supported on a single sip trunk?

If so whats the average capacity per sip trunk to support multiple call volume. I know its based off of internet bandwidth but that aside whats the ball park capacity?

- Adam

Where im at… Lync snooper logs simply state when placing a call to PIAF
Start-Line: SIP/2.0 503 Service Unavailable
CSeq: 1 INVITE
Call-ID: 37181e8685284502afb58faa5b279eb4
VIA: SIP/2.0/TLS 10.15.2.39:57786;branch=z9hG4bK62FB59E9.62B9C8E23E28080F;branched=FALSE,SIP/2.0/TLS 10.15.16.52:50364;ms-received-port=50364;ms-received-cid=3A49500
CONTENT-LENGTH: 0
SERVER: RTCC/4.0.0.0 MediationServer
ms-endpoint-location-data: NetworkScope;ms-media-location-type=intranet
ms-trunking-peer-state: down
ms-trunking-peer: 10.15.3.2
ms-enable-dns-failover: yes
ms-diagnostics: 10001;source=”site1pool”;reason=”Gateway did not respond in a timely manner (timeout)”;component=”MediationServer”
ms-diagnostics-public: 10001;reason=”Gateway did not respond in a timely manner (timeout)”;component=”MediationServer”
Message-Body: –
$$end_record

I have successful results in my sip peers that show OK in my Lync Trunk

My objective as it was before was to have all calls from lync route to either outside
if a public number dialed and be able to call PBX extensions as well.

Im not worried about anything right now but having the Lync be able to connect
I did switch my old ports from 5060 to 5068 triple checked Lync ports and config
patched and restarted Mediation services

As long as I can see traffic I can get through the rest. But for the life of me right now
I cant dechiper why Lync is stating the its trunking peer state is down.

Also in PIAF purple sip.conf is explicity stated not to edit it and to add your configs to sip_general_custom.conf instead

mine looks like this

tcpenable=yes
tcpbindaddr=0.0.0.0
alwaysauthreject=no

[Connect-with-Lync]
type=peer
host=10.15.2.39
qualify=yes
transport=tcp,udp
canreinvite=yes
allowexternalinvites=yes
port=5068
dtmfmode=rfc2833
disallow=all
allow=ulaw
context=from-lync

My Lync trunk has two entries as it did on my old pbx that was working just fine
except for the port change from 5060 to updated 5068

Connect-with-Lync

Outgoing settings
type=peer
host=10.15.2.39
qualify=yes
transport=tcp,udp
canreinvite=yes
allowexternalinvites=yes
port=5068
dtmfmode=rfc2833
disallow=all
allow=ulaw
context=from-lync

INCOMING Settings:
User context from-lync

type=peer
host=10.15.2.39
qualify=yes
transport=tcp,udp
canreinvite=yes
allowexternalinvites=yes
port=5068
disallow=all
allow=ulaw
context=from-lync

See manually configure Lync – here

- Adam

So, now on to the ADFS 2.0 proxy server and we are fully ready for Lync Online SSO.

Still curious on that registry setting.

So, registry settings? I don’t recall reading anything about registry settings. I’ve made all the necessary internal DNS changes… what the MS online portal works with the ADFS pass-thru.

- Adam