You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today I use Asterisk as a Gateway to Microsoft Teams with success.
To achieve this result, I statically modify the res_pjsip_nat.c file by replacing :
ast_sockaddr_stringify_host(&transport_state->external_signaling_address) with the FQDN of my server :
In function static pj_status_t nat_on_tx_message(pjsip_tx_data *tdata)
replace this line pj_strdup2(tdata->pool, &uri->host, ast_sockaddr_stringify_host(&transport_state->external_signaling_address));
with this line pj_strdup2(tdata->pool, &uri->host, "<your asterisk FQDN>");
and this line pj_strdup2(tdata->pool, &via->sent_by.host, ast_sockaddr_stringify_host(&transport_state->external_signaling_address));
with this line pj_strdup2(tdata->pool, &via->sent_by.host, "<your asterisk FQDN>");
The FQDN is in fact used by Microsoft within the SIP:TLS frame to identify the client (Microsoft Tenant) in Teams direct routing use. The problem is that it is defined statically, compiled, and only valid for one Microsoft 365 Tenant.
Multi-Tenant is therefore not supported.
Would it be possible via the pjsip.conf configuration file to prevent the resolution of the FQDN, or specified manualy a client domain name, in certain desired cases?
The text was updated successfully, but these errors were encountered:
Improvement Description
Hi,
Today I use Asterisk as a Gateway to Microsoft Teams with success.
To achieve this result, I statically modify the res_pjsip_nat.c file by replacing :
ast_sockaddr_stringify_host(&transport_state->external_signaling_address) with the FQDN of my server :
The FQDN is in fact used by Microsoft within the SIP:TLS frame to identify the client (Microsoft Tenant) in Teams direct routing use. The problem is that it is defined statically, compiled, and only valid for one Microsoft 365 Tenant.
Multi-Tenant is therefore not supported.
Would it be possible via the pjsip.conf configuration file to prevent the resolution of the FQDN, or specified manualy a client domain name, in certain desired cases?
The text was updated successfully, but these errors were encountered: