<!-- INSTRUCTIONS What not to report - Bugs in unofficial builds or anything not downloaded from our official portal - Missing Builds - Problems with the website - Asking for device support - Feature requests If you need help please see https://www.lineageos.org/community/ Anything between <!- - and - -> won't be shown when your issue is created. --> ## Expected Behavior <!--- Tell us what should happen --> After sending a VVM Activate SMS to an AT&T service number, the returned STATUS SMS should be parsed correctly so that IMAP or SMTP transactions can occur with the returned server, port, username, password, etc. ## Current Behavior <!--- Tell us what happens instead of the expected behavior --> The Activation SMS is sent and acknowledged by the VVM server hosted by AT&T. In the "srv" field of the STATUS SMS, the value is returned correctly per the GSM Specification as "srv=2:vvm.mobile.att.net;". However, from logcat, it appears the OMTP parser is parsing the FQDN as "2:vvm.mobile.att.net" instead of the expected "vvm.mobile.att.net" value. Dialer will throw an exception with the following error: "com.android.voicemail.impl.mail.MessagingException: java.net.UnknownHostException: Unable to resolve host "2:vvm.mobile.att.net": No address associated with hostname". Using the Dialer, it is possible to Enable Visual Voicemail, but messages cannot be retrieved since the FQDN is not correctly parsed. ## Possible Solution <!--- Not obligatory, but suggest a fix/reason for the bug, --> Verify the OMTP parser is correctly accounting for the fact the "srv" field contains two values, [NUM]:FQDN/IP where [NUM] == 1 to signify data following the colon represents an IP address and [NUM] == 2 signifies the data following the colon represents a FQDN. Attached is the VVM STATUS SMS received by the AT&T system. Personal information has been masked with the '#' character. There are a few other peculiarities in the message, but not sure if it's an ASCII to Unicode error or something else. [logcat_dialer.txt](/uploads/7324af67abdebcdf0747f29d3aac4c8a/logcat_dialer.txt) [VVM_STATUS.txt](/uploads/fa8b79300e0b5e44be316896686a3580/VVM_STATUS.txt) ## Steps to Reproduce <!--- Provide a link to a live example, or an unambiguous set of steps to --> <!--- reproduce this bug. Include code to reproduce, if relevant --> 1. Connect to the U.S. AT&T Cellular network with an active subscriber account. Wi-Fi should be disabled to guarantee cellular data connection. 2. Enter the "VVM config override" in the "VoicemailSecretCodeActivity" window: destination number = 94183567, prefetch = on, cellular data required = on. This is required because by default there is apparently no AT&T Carrier Config with this information. 3. Go back one page to the main "VoicemailSecretCodeActivity" window and click the "Sync" button 4. Open Dialer, go to Settings->Voicemail and toggle Visual voicemail "On". The "Activating voicemail" text under the toggle button should disappear in a few seconds, indicating the VVM STATUS SMS was received 5. View logcat as the Dialer repeatedly attempts to query an invalid FQDN. Alternatively, the Voicemail inbox will show an error after a timeout stating "Can't update visual voicemail" and "you can still call to check voicemail". <!-- THIS SECTION IS MANDATORY. If it is not filled out correctly, your issue will be marked as invalid. --> <!-- Example: /device mako (found at https://wiki.lineageos.org/devices/) /version lineage-15.1 /date 2017-12-15 /kernel /baseband /mods Google Apps, F-Droid --> /device blueline /version lineage-19.1 /date 2022-08-30 /kernel 4.9.317 /baseband SQ3A.220705.004 /mods Magisk, F-Droid <!-- Replace the following line with "I have read the directions" --> I have read the directions