FAQ - User agent
Valid for: | N530 | N610 | N670 | N770 | N870 | N870E | Embedded Integrator | Virtual Integrator |
Introduction
See below for a user-agent example.
This is seen in:
- SIP messages
- HTTP(s) messages
Device | User-Agent: |
|---|---|
Virtual Integrator | Gigaset N870 VI PRO/83.V2.43.0+build.5f0a106;7C2F80XXXXXX |
N870 | Gigaset N870 IP PRO/83.V2.43.0+build.5f0a106;7C2F80XXXXXX |
N870E | Gigaset N870E IP PRO/83.V2.43.0+build.5f0a106;7C2F80XXXXXX |
N770 | Gigaset N770 IP PRO/83.V2.62.0+build.c358757;7C2F80XXXXXX |
N670 | Gigaset N670 IP PRO/83.V2.43.0+build.5f0a106;7C2F80XXXXXX |
N610 | Gigaset N610 IP PRO/83.V2.43.0+build.5f0a106;7C2F80XXXXXX |
N530 | Gigaset N530 IP PRO/83.V2.62.0+build.c358757;7C2F80XXXXXX |
From software 2.26 we have added capacity information to the HTTP(s) user agent only.
Platforms that do auto-provisioning can use this information to block the administrator to add more handsets than supported by the system.
Device | User-Agent: | ||
|---|---|---|---|
N870 | Single Cell / Small | User-Agent: Gigaset N870 IP PRO/83.V2.43.0+build.5f0a106;7C2F80XXXXXX;Handset=50 | |
Medium | User-Agent: Gigaset N870 IP PRO/83.V2.43.0+build.5f0a106;7C2F80XXXXXX;Handset=250 | ||
Embedded Integrator | 0 DM | User-Agent: Gigaset N870 IP PRO/83.V2.43.0+build.5f0a106;7C2F80XXXXXX;Handset=0 | |
1 DM | User-Agent: Gigaset N870 IP PRO/83.V2.43.0+build.5f0a106;7C2F80XXXXXX;Handset=250 | ||
2 DM | User-Agent: Gigaset N870 IP PRO/83.V2.43.0+build.5f0a106;7C2F80XXXXXX;Handset=500 | ||
... | ... | ||
N870 E | Same as N870 (Above) but with "E" | User-Agent: Gigaset N870E IP PRO/83.V2.43.0+build.5f0a106;7C2F80XXXXXX;Handset=250 | |
N770 | Single Cell / Small | User-Agent: Gigaset N770 IP PRO/83.V2.62.0+build.c358757;7C2F80XXXXXX;Handset=50 | |
Medium | User-Agent: Gigaset N770 IP PRO/83.V2.62.0+build.c358757;7C2F80XXXXXX;Handset=100 | ||
N670 | Single Cell | User-Agent: Gigaset N670 IP PRO/83.V2.43.0+build.5f0a106;7C2F80XXXXXX;Handset=20 | |
N610 | Single Cell | User-Agent: Gigaset N610 IP PRO/83.V2.64.0-160-g758db0bf;589EC67C2479;Handset=20 | |
N530 | Single Cell | User-Agent: Gigaset N530 IP PRO/83.V2.62.0+build.c358757;7C2F80XXXXXX;Handset=8 | |
N870 | Virtual Integrator | 0 DM | User-Agent: Gigaset N870 VI PRO/83.V2.43.0+build.5f0a106;7C2F80XXXXXX;Handset=0 |
1 DM | User-Agent: Gigaset N870 VI PRO/83.V2.43.0+build.5f0a106;7C2F80XXXXXX;Handset=250 | ||
... | ... | ||
Remove Handset capacity information
Via auto-provisioning, it is possible to disable the capacity information in the HTTP(s) user-agent.
Auto-provisioning example | User agent |
|---|---|
Disable Handset capacity information <?xml version="1.0" encoding="UTF-8"?> <provisioning version="1.1" productID="e2"> <nvm> <!-- 0 = Do not add capacity information, 1 = Add capacity information --> <param name="Provisioning.global.CapacityInformation" value="0" /> </nvm> </provisioning> | User-Agent: Gigaset N610 IP PRO/83.V2.43.0+build.5f0a106;7C2F80XXXXXX |
Enable Handset capacity information <?xml version="1.0" encoding="UTF-8"?> <provisioning version="1.1" productID="e2"> <nvm> <!-- 0 = Do not add capacity information, 1 = Add capacity information --> <param name="Provisioning.global.CapacityInformation" value="1" /> </nvm> </provisioning> | User-Agent: Gigaset N610 IP PRO/83.V2.43.0+build.5f0a106;7C2F80XXXXXX;Handset=8 |
Remove MAC address and Handset capacity information
Via auto-provisioning, it is possible to remove the MAC address and the Handset capacity information in the SIP / HTTP(s) user-agent.
Auto-provisioning example | User agent |
|---|---|
Disable capacity information <?xml version="1.0" encoding="UTF-8"?> <provisioning version="1.1" productID="e2"> <nvm> <param name="SystemSettings.global.UseCommonUA" value="1" /> <param name="Provisioning.global.MACAddressInformation" value="0" /> <param name="Provisioning.global.CapacityInformation" value="0" /> </nvm> </provisioning> | User-Agent: Gigaset N610 IP PRO/83.V2.43.0+build.5f0a106 |