Ctrlk
ProSBC ProductLearning CenterHelptelcobridges.com
For the complete documentation index, see llms.txt. This page is also available as Markdown.

SIP subscribe notify publish forwarding

ProSBC forwards SIP Subscribe, Notify and Publish messages between users and registrars, following the same rules as SIP registration forwarding.

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 packages (independently).

SIP Subscribe/Publish forwarding

ProSBC will forward SUBSCRIBE or PUBLISH requests from users to Registrar (PBX)

Bob's phone sends SIP SUBSCRIBE to the SBC, which forwards it upstream to the SIP registrar or PBX.
SUBSCRIBE is acknowledged: 200 OK travels back from the registrar through the SBC to Bob's phone.

SIP Notify forwarding

ProSBC will forward NOTIFY requests from Registrar (PBX) back to users.

The registrar sends NOTIFY downstream through the SBC to Bob's phone.
NOTIFY is acknowledged: 200 OK travels up from Bob's phone through the SBC to the registrar.

Contact remapping

When forwarding a SIP Subscribe message from a user to the registrar, ProSBC will remap the contact to make itself the contact. This way, the Registrar will send response messages and Notify events through ProSBC, and thus make sure to "hide" private network topology from users (avoid messages being sent directly from registrar to users).

Because the contact's domain is being remapped, ProSBC will also remap the contact's user name to make sure there is not user name conflict between two domains that would have the same user name.

Contact remapping: the SBC rewrites each contact to an alias at its own IP, so bob@abc.com and bob@telco.com become bob_ALIAS-1 and bob_ALIAS-2.

SIP authorization

SIP authorization requests (401/407 Unauthorized) are forwarded from Registrar to users, allowing users to send the request again with appropriate credentials. ProSBC does not perform authorization by itself, only forwards between users and registrars.

NAT traversal

  • ProSBC handles SIP Subscribe NAT traversal to allow interaction between SIP User Agents from public and private networks.

    • ProSBC 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:

References

PreviousOperator Interconnection
NextSTIR/SHAKEN

Last updated

Was this helpful?