Administrator's Guide

Chapter 10. SIP Services
Signaling Order of Re-INVITEs
When the Telecommuting Module acts as a B2BUA (e.g. almost always when performing
SIP Trunking), it normally handles re-INVITEs by forwarding them and waiting for a re-
sponse, just as for the original INVITE.
With some SIP devices, this can cause problems. For these situations, the Telecommuting
Module can instead handle the re-INVITEs hop by hop, meaning that it sends a "200 OK"
response back before forwarding the INVITE to the next SIP device.
The consequence will be that the Telecommuting Module will re-use the old SDP from the
other end when sending the 200. For dialogs where the re-INVITE is used to change codec
or some other RTP parameter, the recommended way is to send re-INVITEs all the way
directly.
Select if the INVITEs should be sent all the way, or be processed hop by hop.
Loose Username Check
Normally, the Telecommuting Module checks that the authentication username equals the
username in the From header. Some clients use their whole address as authentication user-
name (ie: [e-mail]), which means that the username "user" in the From header is
compared with the authentication username "[e-mail]". This authentication will fail.
With this function, "@host.com" is stripped from the authentication username.
Select if the entire SIP address or only the username should be used as the authentication
name.
User Matching
Here, you can select to match on username only or username as well as domain.
If you match on username only, users with the same username will be treated as the same,
even when they are under different domains.
168