User Agent spoofing

Last Updated : Jan 12, 2024 |

The IP Office can vary the content of the auto-generated settings files based on the User Agent (UA) string of the device that requests the files. Therefore, viewing the files using a browser may not show the file exactly as received by a particular phone or application.

However, it is possible to configure a browser to temporarily use a different UA string. This is called UA spoofing.

Example User Agent strings

  • Goggle Chrome send a UA string like Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36.

  • The following are example UA strings sent by Avaya clients.

Regular Expression

Description

Avaya.*

Matches any UA beginning with Avaya. The . matches any character. The .* matches any number of characters.

Avaya J1.*

Matches the UA string of any J100 Series phone.

Avaya (J1|Communicator).*

Matches the UA string of both J100 Series phones and Avaya Workplace clients. The ( ) brackets enclose the potential matches, each potential match separated by a | character.

  • As shown in the examples above, the UA string can vary depending on the software version and/or platform.

  • You can view the UA sent by a particular phone or softphone in SysMonitor by registering the phone or client.

Related information
The IP Office Settings Files
Changing the User Agent in Google Chrome
Changing the User Agent in Safari