# Special char in SMS notification block are not correct

**URL:** <https://forum.inductiveautomation.com/t/special-char-in-sms-notification-block-are-not-correct/15623>\
**Category:** Ignition\
**Created:** [October 10, 2017, 2:59pm UTC](https://forum.inductiveautomation.com/t/special-char-in-sms-notification-block-are-not-correct/15623 "2017-10-10T14:59:32Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![mazeyrat](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mazeyrat/32/10955_2.png) [@mazeyrat](https://forum.inductiveautomation.com/u/mazeyrat)\
**Post date:** [October 10, 2017, 2:59pm UTC](https://forum.inductiveautomation.com/t/special-char-in-sms-notification-block-are-not-correct/15623/1 "2017-10-10T14:59:32Z")

</div>

Ignition 7.9.4  
I have **alarms name** with spécial car like ’ or é or ê

Example : Alarm name : `Arrêt d' urgence zone 0`  
tagpath : Eaux/Energie/AU\_ZONE\_0

In SMS notification block message is : `APPARITION {activeTime|yyyy-MM-dd HH:mm:ss} : {displayPathOrSource} - {name} `

on my Phone the message send by the Airlink LS 300 is :

`APPARITION 2017-10-10 08:56:11 : Eaux/Energie/AU_ZONE_0 - Arrè d' urgence zone 0 
Code ack : 'mnlipc' `

In Email, the name is ok, in Alarm table components the name is ok too. Any Idea ???

 ![](https://us1.discourse-cdn.com/inductiveautomation/original/2X/5/5da61976c553eadf071ab11fd89a3a91ece2267b.png) ![](https://us1.discourse-cdn.com/inductiveautomation/original/2X/7/77d7e31da9d14d223f82d02445298cebae5abb75.png) ![](https://us1.discourse-cdn.com/inductiveautomation/original/2X/6/663aec2c54ea9d63deda4bdece8a4a0171311a99.png)

---

<div class="post-metadata">

**Author:** ![mazeyrat](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mazeyrat/32/10955_2.png) [@mazeyrat](https://forum.inductiveautomation.com/u/mazeyrat)\
**Post date:** [October 10, 2017, 4:22pm UTC](https://forum.inductiveautomation.com/t/special-char-in-sms-notification-block-are-not-correct/15623/2 "2017-10-10T16:22:01Z")

</div>

Air Link LS300 mention message Body format : ASCII HEX, does Ignition make some char conversion ?

---

<div class="post-metadata">

**Author:** ![KathyApplebaum](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kathyapplebaum/32/7261_2.png) [@KathyApplebaum](https://forum.inductiveautomation.com/u/KathyApplebaum)\
**Post date:** [October 11, 2017, 1:29pm UTC](https://forum.inductiveautomation.com/t/special-char-in-sms-notification-block-are-not-correct/15623/3 "2017-10-11T13:29:42Z")

</div>

We looked at this issue back in 2013, because it appeared we should be able to successfully use things outside of 7-bit ASCII. However, Sierra Wireless told us that their modems “probably don’t support that”, and we couldn’t get any further support on the issue from them. We eventually gave up trying to make it work. :\

You might look into the Twilio module instead. Twilio’s service offers full Unicode support, so your 8-bit ASCII will work as well.

---

<div class="post-metadata">

**Author:** ![mazeyrat](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mazeyrat/32/10955_2.png) [@mazeyrat](https://forum.inductiveautomation.com/u/mazeyrat)\
**Post date:** [October 11, 2017, 1:44pm UTC](https://forum.inductiveautomation.com/t/special-char-in-sms-notification-block-are-not-correct/15623/4 "2017-10-11T13:44:27Z")

</div>

Thanks Kathy,  
I stay with LS300, but for the sms message I clean the text with :

```auto
import unicodedata
def normalize():
  s=unicodedata.normalize('NFKD', s).encode('ASCII', 'ignore')
  return s.upper()
```