SIP subscribe notify publish forwarding
(→Configuring) |
|||
| Line 28: | Line 28: | ||
TSBC will remap SIP headers (from/to/contact/via/route...) while forwarding messages between users Registrars/PBX to perform "topology hiding": | TSBC will remap SIP headers (from/to/contact/via/route...) while forwarding messages between users Registrars/PBX to perform "topology hiding": | ||
* Users always send SUBSCRIBE requests to TSBC, and receive NOTIFY from TSBC, even if there are multiple Registrars behind. | * Users always send SUBSCRIBE requests to TSBC, and receive NOTIFY from TSBC, even if there are multiple Registrars behind. | ||
| − | * Registrars/PBX addresses are hidden from the users by | + | * Registrars/PBX addresses are hidden from the users by TSBC (multiple registrars can be used for redundancy, and/or per domain name) |
* Multiple users with the same name but from different domains are remapped using "aliases" so they still can be distinguished after going through TSBC | * Multiple users with the same name but from different domains are remapped using "aliases" so they still can be distinguished after going through TSBC | ||
| Line 38: | Line 38: | ||
== NAT traversal == | == NAT traversal == | ||
| − | * | + | *TSBC handles SIP Subscribe NAT traversal to allow interaction between SIP User Agents from public and private networks. |
**TSBC detects the actual IP from which users are sending messages, so responses and Notify messages can be forwarded properly, even in case users are unaware that they are behind a NAT | **TSBC detects the actual IP from which users are sending messages, so responses and Notify messages can be forwarded properly, even in case users are unaware that they are behind a NAT | ||
Revision as of 09:47, 18 June 2018
TSBC can forward SIP Subscribe, Notify and Publish messages between users and registrars (PBX).
Forwarding of these messages follow the same rules as forwarding of SIP registration.
Contents |
SIP Subscribe overview
The SIP SUBSCRIBE method allows users to subscribe to various services, and get notified of events related to these services. Typical services (packages) that phones will register to are:
- Voice mail
- Presence
- Conference
Each user's device can register to various packages, then receive notifications for each of these package (independently).
SIP Subscribe/Publish forwarding
TSBC will forward SUBSCRIBE or PUBLISH requests from users to Registrar (PBX)
SIP Notify forwarding
TSBC will forward NOTIFY requests from Registrar (PBX) back to users.
Topology hiding (contact remapping)
TSBC will remap SIP headers (from/to/contact/via/route...) while forwarding messages between users Registrars/PBX to perform "topology hiding":
- Users always send SUBSCRIBE requests to TSBC, and receive NOTIFY from TSBC, even if there are multiple Registrars behind.
- Registrars/PBX addresses are hidden from the users by TSBC (multiple registrars can be used for redundancy, and/or per domain name)
- Multiple users with the same name but from different domains are remapped using "aliases" so they still can be distinguished after going through TSBC
SIP authorization
SIP authorization requests (401/407 Unauthorized) are forwarded from Registrar to users, allowing users to send request again with appropriate credentials.
TSBC does not perform authorization by itself, only forwards between users and registrars.
NAT traversal
- TSBC handles SIP Subscribe NAT traversal to allow interaction between SIP User Agents from public and private networks.
- TSBC detects the actual IP from which users are sending messages, so responses and Notify messages can be forwarded properly, even in case users are unaware that they are behind a NAT
Configuring
SIP Subscribe/Publish/Notify forwarding is automatically available when configuring SIP Domain for SIP Registration forwarding:
