> For the complete documentation index, see [llms.txt](https://help.sipgate.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sipgate.de/cloud-telefonanlage/en/getting-started/readme/unterschiede-altes-neues-sipgate.md). # Old vs. new sipgate: what changes? In September 2025, sipgate launched a new telephony system, which all new customers are already using to make calls. Existing customers will also be migrated as soon as all previous features are available in the new web interface. To make it easier for you to get started, the following article provides an overview of all changes: #### Channels In the old web interface, users are created who have their own routings. At the same time, there are groups in which several users are bundled together and reachable via a phone number, and channels. In the new web interface, all users have a **personal channel**. In addition, users can be logged into several **shared channels** as well. The group function will not be built into the new web interface. One advantage of shared channels compared to groups is the number of users: groups are limited to a maximum of 25 users / group. Shared channels can include any number of users. Furthermore, the event list is visible to all members of a channel. In addition, the status of channel members is visible. Admins can also **ringing rules** activate. This makes it possible, for example, for a call to ring at all users at the same time or to be forwarded in a certain order if the first available user does not answer the call. #### Routing The **assignment** **of phone numbers and extensions** in the routing of individual users are in the new web interface only possible through a **Admin** possible. Users without admin rights can continue to define the forwarding rules for no answer in the new web interface. In addition, the display for all routings is adapted to the channel routings. {% hint style="warning" %} Exception: Admins can grant editor rights to individual users. The corresponding editors can make additional changes in shared channels that are withheld from users. {% endhint %} #### End devices In the old web interface, users can create their own routings with up to three connectable end devices free of charge. In the new web interface, users have the option of registering **any number of end devices** in the personal channels. In addition, both the **personal channel** as well as **all shared channels** are displayed in the sipgate app and can be individually activated or deactivated there. firewall The firewall settings change slightly. You can find all current settings in the following [article](https://help.sipgate.de/cloud-telefonanlage/erste-schritte/alles-fur-den-start-mit-sipgate/nutzung-von-sipgate-mit-einer-firewall). #### Statistics Until now, in the group statistics, admins could view a summary of calls for the past 30 days for the entire group, in addition to the live display of the number of callers in the queue. With the introduction of channels, admins have access to **daily up-to-date statistics** and can, if needed, perform **individual evaluations** of users in a channel. Furthermore, admins are authorized to individually grant access to statistics to any user, for example the team lead. The retrospective period for statistics has also been extended, so the statistics can now be viewed retrospectively over several months. In addition, the KPI display has been expanded with additional parameters. #### Sender number With the new web interface, it is now possible in the sipgate app to set a **any sender number** . This can be individually adjusted for each personal and shared channel. Setting a free sender number is also possible. #### event list The event list is divided into two sections in the new web interface. All incoming and outgoing faxes and SMS are still visible in the logged-in area in the section **My Telephony → Fax and SMS** visible. All incoming and outgoing calls are now displayed with the new web interface only in the sipgate app in the respective channels. #### Voice quality The new platform offers improved voice quality across all end devices (app, desk phone, SIM). #### Migration and costs The upgrade from sipgate classic to sipgate neo is free of charge and gradual. All new customers start directly on sipgate neo. #### REST API All changes that affect the REST API as well as sipgate.io are found in a separate [article](https://help.sipgate.de/hc/de/articles/31396429731357-Was-%C3%A4ndert-sich-mit-dem-neuen-System-in-der-sipgate-REST-API-und-bei-sipgate-io). #### What changes in the app? * **Setting the caller ID number** The sender number is now stored individually for each channel and no longer needs to be assigned to a phone. The individual channels can be selected in the app's Omnibar. * **Muting the sipgate app** The desktop app can be disabled as an extension in a channel. Connected external phones are not affected by this setting. * **Display of forwards** Forwards are displayed as event type "Forwarding" in the call screen. There you can see who the call is forwarded to. The same applies to a manually initiated transfer. * **DND** When DND status is set, users remain logged into their channels. The DND setting is applied to all end devices. * **Presence** In the personal channel, users can set the status "not available". They can continue to be available in shared channels without being reachable via their direct phone number. Logging in and out takes place via the **on/off**button in the channel header or by right-clicking the channel in the sidebar. The status is visible to all members of the account via the app. * **Groups become channels** Each user has a personal channel. Existing groups are converted into shared channels. * **Voicemails also in the inbox** Notifications about incoming voicemails are now also visible in the inbox in the app. * **settings** The app no longer has its own phone list. Reachability is determined via the channels. Webhooks are now an integral part of the AI features in the new version. Existing beta testers of Smart Answers must switch to the AI features. * **30-day storage period for calls also applies to the inbox** All events in the inbox are stored for 30 days. * **Team contacts** Team contacts are preferably called on their personal channel, but can still have multiple phone numbers. The respective contact is selected via the Omnibar. If a contact has additional phone numbers, the Omnibar shows them with a counter (e.g. "+2"). * **Call Logging** Missed calls in personal channels are logged. Missed calls in shared channels are not logged. No logging takes place for forwards and voicemails. * **AI for all calls when activated** If users have activated the AI features in the app and use another end device to make calls, AI summaries and transcriptions are now also created for those calls. * **CRM integration** All calls run through the channel system, thereby avoiding duplicate entries in the CRM. Each conversation is transmitted only once. * **Mobile app** Users on sipgate neo use the satellite app for their mobile connection to the sipgate account. After the upgrade to sipgate neo, the previous sipgate app no longer works. Users must switch to the satellite app and log in there with their existing sipgate login data. We have summarized the most important settings and information about the satellite app in a [Help Center article ](https://help.sipgate.de/cloud-telefonanlage/sipgate-nutzen/die-sipgate-app/welche-einstellungen-benotige-ich-fur-die-satellite-app)summarized. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.sipgate.de/cloud-telefonanlage/en/getting-started/readme/unterschiede-altes-neues-sipgate.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.