OXE to Lync via SIP Trunk

[cavagnaro]

Maybe a patch?

Sent from my XPeria Z

[agiftel]

What you mean?

[cavagnaro]

Which OXE patch are you using

[agiftel]

I always used last patch of each version.

[torerk]

Hello,

I'am using Lync2010 and OXE 10.1.1 (260315a) in my lab and stil have no ringbacktone (direct siptrunk), when calling from internal user in oxe towards Lync client. Could it be that this is working in Lync2010, but not in Lync2013? Have anyone made this work in lync 2010?

[mag3rquark]

Hello,

as i can see, it is possible to connect the OXE and Lync 2013 directly. Which things are working and which not? Is there a special configuration needed in the trunk config on our OXE?
Could someone post an example configuration?

best reagards,
Daniel

[agiftel]

Not particular configuration.

Node Number (reserved) : 1 │
│ Instance (reserved) : 1 │
│ Instance : 11 │
│ │
│ Gateway Name : Microsoft Lync 2013 │
│ Remote domain : lync2013.domain.local │
│ PCS IP address : ----------------------------------------------- │
│ Port number : 5068 │
│ Transport type + TCP │
│ Belonging domain : -------------------------------------------------- │
│ Registration Id : -------------------------------------------------- │
│ Registration ID in P_Asserted + False │
│ Registration timer : 0 │
│ Outbound Proxy : 172.16.55.201 │
│ Supervision timer : 0 │
│ Trunk group number : 2 │
│ Pool Number : -1 │
│ Outgoing realm : -------------------------------------------------- │
│ Outgoing username : -------------------------------------------------- │
│ │
│ Outgoing Password : ---------- │
│ Confirm : ---------- │
│ │
│ Incoming username : -------------------------------------------------- │
│ │
│ Incoming Password : ---------- │
│ Confirm : ---------- │
│ │
│ RFC 3325 supported by the distant + True │
│ DNS type + DNS A │
│ First DNS IP Address : ----------------------------------------------- │
│ Second DNS IP Address : ----------------------------------------------- │
│ SDP in 18x + False │
│ Minimal authentication method + None │
│ INFO method for remote extension + False │
│ Send only trunk group algo + True │
│ To EMS + False │
│ SRTP + RTP only │
│ Routing Application + False │
│ Ignore inactive/black hole + False │
│ Contact with IP address + False │
│ Dynamic Payload type for dtmf : 97 │
│ 100 REL for Outbound Calls + Not Supported
100 REL for Incoming Calls + Not Requested │
│ Gateway type + Standard type │
│ Re-Trans No. for REGISTER/OPTIONS : 2 │
│ P-Asserted-ID in Calling Number + True │
│ Trusted P-Asserted-ID header + False │
│ Diversion Info to provide through + Diversion │
│ Trusted From header + True

[butor]

Hello Does mwi working with your configuration? We have a configuration with Exchange UM and Sonus Gateway (SIP to exchange , Qsig to OXE) and MWI is not working.

Regards