APP CTI registration fails if hostname starts with an uppercase letter

[Ilvo]

Steps to reproduce

• Initialize Nethvoice and CTI hostnames with with at least one uppercase letter

     exmp: Xyz.nethvoice.it
  

Expected behavior

The app should register successfully once the process is complete

Actual behavior

The app fails to register (it does not complete the registration) after generating the QR code in CTI.

Components

Nethvoice version 1.7.9
APP CTI @ last version from google store

[Amygos]

QA Tests Cases

Related changes: NethVoice Proxy #222 and NethVoice #995.

Deploy the proxy build first, then the NethVoice build. Use test hostnames with working DNS and certificates; replace the example domains below with your test domains.

Status: the full NS8 deployment and mobile-app checks below remain pending.

• Initial setup and Settings: enter Voice.Example.org and CTI.Example.org. Confirm saved configuration and HTTP/SIP routes are lowercase. Save again with different casing and confirm no duplicate route is created.
• Restore: restore a backup containing mixed-case NethVoice and CTI hostnames. Confirm saved configuration and HTTP/SIP routes are lowercase and repeated saves do not duplicate routes.
• Hostname validation: submit case-equivalent NethVoice and CTI hostnames in both forms and through configure-module. Confirm validation fails before HTTP or SIP routes change.
• Provisioning tokens: record a phone provisioning token, save a case-only hostname change, and confirm the token is preserved. Change to a different hostname and verify the existing provisioning reset still occurs.
• SIP route casing and legacy records: on an upgraded proxy, verify an untouched mixed-case route still works with its original spelling. Add, read, save, and remove routes using different casing. Saving a legacy route must retain its dispatcher set and normalize the related route, domain, and dialplan records.
• Ambiguous records: in a disposable test database, create duplicate route records that differ only in case. Confirm add/get/remove fail, leave all records unchanged, and do not select a backend automatically.
• Failed writes: in the disposable test database, cause a route write to fail. Confirm all related changes are rolled back and Kamailio is not reloaded.
• Mobile QR-code registration and calls: after configuring mixed-case hostnames, generate the QR code in CTI and scan it with the mobile app. Confirm registration completes, then test a call and an inbound trunk call with the paired builds.