On NethVoice 1.6.6, some inbound calls that reach voicemail are not recorded in the voicemail database when the computed callerid string exceeds the current field limit (default 40 chars). This happens with contacts where the resolved CallerID also includes the company name, producing values like 42–59 characters.
Steps to reproduce
- Configure/ensure an inbound caller lookup that resolves CallerID with contact name + company name (resulting string > 40 chars).
- Place an inbound call from that contact and let it reach voicemail (leave a message).
- Check the voicemail database records for the new message.
Expected behavior
Voicemail is saved in the DB even when CallerID is long (e.g., by increasing field size and/or safely truncating).
Actual behavior
Voicemail is not saved in the DB because callerid exceeds the allowed length (examples observed: 42 and 59 characters).
On NethVoice 1.6.6, some inbound calls that reach voicemail are not recorded in the voicemail database when the computed
calleridstring exceeds the current field limit (default 40 chars). This happens with contacts where the resolved CallerID also includes the company name, producing values like 42–59 characters.Steps to reproduce
Expected behavior
Voicemail is saved in the DB even when CallerID is long (e.g., by increasing field size and/or safely truncating).
Actual behavior
Voicemail is not saved in the DB because
calleridexceeds the allowed length (examples observed: 42 and 59 characters).See also