SIP Authentication failed - Realm mismatch

our Yeti Rollout was a success, everything worked, except one thing, ONE Client is using a Realm for SIP Auth. So far as I can see, the realm is hardcoded in sems.conf, is there a possibility to allow more than one realm?

Currently it is not possible to use multiple realms. Also it is not clear how it may be implemented because realm offered to client in 401 response by server(yeti in this case). So better to reconfigure client to use right realm.