|
|
Line 1: |
Line 1: |
− | {{ComponentRN
| + | #REDIRECT [[Draft:RN/GenesysSoftphone/9.0.021.08]] |
− | |ComponentId=d694a3aa-8d50-43d7-b587-d985c73e122d
| |
− | |JQL=key=SOFTPHONE-1339
| |
− | |DeploymentTypeId=ec194bf2-b79a-436d-8ff6-eaff94d9f43a, 5439f1be-1868-4091-b058-1667389b6ce1
| |
− | |ReleaseDate=2022-11-03
| |
− | |Highlight=Resolved issues.
| |
− | }}
| |
− | {{Issue
| |
− | |TicketNumber=SOFTPHONE-1339
| |
− | |IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
| |
− | |Content=[CLOUD][NEW_DEV]In SIP environments where Genesys Softphone sends SIP registration based on a DNS SRV record, Genesys Softphone no longer adds the primary SIP address specified in the DNS SRV record to the deny list. Previously, such unexpected deny-listing of the primary SIP Address could occur at Genesys Softphone initialization time, which resulted in an unexpected registration against the secondary SIP address.[PREMISE][NEW_DEV]In SIP environments where Genesys Softphone sends SIP registration based on a DNS SRV record, Genesys Softphone no longer adds the primary SIP address specified in the DNS SRV record to the deny list. Previously, such unexpected deny-listing of the primary SIP Address could occur at Genesys Softphone initialization time, which resulted in an unexpected registration against the secondary SIP address.
| |
− | |LocalContent=In SIP environments where Genesys Softphone sends a SIP registration based on a DNS SRV record, Genesys Softphone no longer adds the primary SIP address specified in the DNS SRV record to the deny list. Previously, such unexpected deny-listing of the primary SIP Address could occur during Genesys Softphone initialization and resulted in an unexpected registration against the secondary SIP address.
| |
− | }}
| |
Latest revision as of 10:31, November 2, 2022
This is a draft page; it has not yet been published.