> For the complete documentation index, see [llms.txt](https://tmediadocs.telcobridges.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tmediadocs.telcobridges.com/telecom-references/sip-and-voip/sip/sip-subscribe-notify-publish-forwarding.md). # SIP subscribe notify publish forwarding How ProSBC and FreeSBC forward SIP SUBSCRIBE, NOTIFY and PUBLISH between users and a registrar, and which event packages phones typically subscribe to. ProSBC/FreeSBC can forward SIP Subscribe, Notify and Publish messages between users and registrars (PBX). Forwarding of these messages follows the same rules as forwarding of [SIP registration](/telecom-references/sip-and-voip/sip/sip-registration.md). ### 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/FreeSBC will forward SUBSCRIBE or PUBLISH requests from users to Registrar (PBX) ![subscribe request overview](https://docs.telcobridges.com/w/images/5/5f/Subscribe_request_overview.png) ![subscribe response overview](https://docs.telcobridges.com/w/images/5/54/Subscribe_response_overview.png) ### SIP Notify forwarding ProSBC/FreeSBC will forward NOTIFY requests from Registrar (PBX) back to users. ![notify request overview](https://docs.telcobridges.com/w/images/e/e8/Notify_request_overview.png) ![notify response overview](https://docs.telcobridges.com/w/images/a/a8/Notify_response_overview.png) ### Contact remapping When forwarding a SIP Subscribe message from a user to the registrar, ProSBC/FreeSBC will remap the contact to make itself the contact. This way, the Registrar will send response messages and Notify events through ProSBC/FreeSBC, 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/FreeSBC 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. ![subscribe topology hiding](https://docs.telcobridges.com/w/images/0/04/Subscribe_topology_hiding.png) ### 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/FreeSBC does not perform authorization by itself, only forwards between users and registrars. ### NAT traversal * ProSBC/FreeSBC handles SIP Subscribe NAT traversal to allow interaction between SIP User Agents from public and private networks. * ProSBC/FreeSBC 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](https://telcobridges.com/learning/session-border-controller/softphone-and-the-sbc/): * [Creating a SIP domain](https://tmediadocs.telcobridges.com/other-pages/protocol-stacks-sip/creating-a-sip-domain) ### References * [Understanding SIP Subscribe](https://andrewjprokop.wordpress.com/2015/03/11/a-deep-dive-into-sip-subscriptions/) * [IANA SIP Event types](https://www.iana.org/assignments/sip-events/sip-events.xhtml) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://tmediadocs.telcobridges.com/telecom-references/sip-and-voip/sip/sip-subscribe-notify-publish-forwarding.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.