baresip-studio: Some ASCII symbols got wrong encoding in incoming chat/messages "From" header

Asterisk/freePBX @ chan_dongle is used for SMS/USSD manipulations (sending to softphone).

There is obviously a problem with character encoding in incoming chat (for example, Linphone do it right). symbol “^” is displayed as “%5e” symbol “>” is displayed as “%3e” Most probably bunch of others also are crippled. symbol “/” is displayed as “/”

Dialplan row generating that:: exten => ussd,n,MessageSend(pjsip:trunk_name/sip:name@sip.antisip.com,${CALLERID(num)}^${DONGLENAME:6})

Result (senders name/row) IS “ussd%5e1” “ussd%3e1” and “ussd/1” Result (senders name/row) SHOULD BE “ussd^1” “ussd>1” and “ussd/1”

I just tested by sending this message from Linux baresip cli app to Android baresip app:

Here comes some characters: ^ > /

and it appeared exactly the same on baresip Android app.

The problem is with character in “senders name”/From header, not in “message body”.

About this issue

  • Original URL
  • State: closed
  • Created a year ago
  • Comments: 26 (16 by maintainers)

Most upvoted comments

It turned that there is bug in baresip lib regarding @ char. I’ll try to get it fixed.

OK, so the issue is that characters, such as >, that must be escaped when they appear in SIP URI userpart are not un-escaped when baresip app shows them. Thanks for reporting, I’ll take a look.