Errores #82

Just ASCII allowed for availability note?

Added by Iñaki Baz Castillo over 2 years ago. Updated over 2 years ago.

Status:Resuelta Start:07/21/2009
Priority:Normal Due date:
Assigned to:Saúl Ibarra Corretgé % Done:

0%
Category:PJSIP
Target version:0.5.1

Description

This error occurs if I set an availability message containing "strange" chars as á, é, €...

Traceback (most recent call last):
  File "/home/ibc/Proyectos/YASS/trunk/debian/yass/usr/lib/python2.5/site-packages/yass/gui/useravaildlg_c.py", line 31, in change_availability
UnicodeEncodeError: 'ascii' codec can't encode characters in position 8-12: ordinal not in range(128)

History

Updated by Saúl Ibarra Corretgé over 2 years ago

Seems like a Python enconding issue, look:

a = "€"

str(a)
'\xe2\x82\xac' unicode(a)
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 0: ordinal not in range(128)

Encondign is correctly set at the top of the file though... I'll look into it!

Updated by Saúl Ibarra Corretgé over 2 years ago

Please, try rev 130. It includes a really dirty fix which works for the Plone project and at least it does the job :-/ Let me know if it works as expected.

Updated by Iñaki Baz Castillo over 2 years ago

  • Status changed from Nueva to Cerrada

It works now :)
Thanks.

Updated by Saúl Ibarra Corretgé over 2 years ago

  • Category changed from YASS - core to PJSIP
  • Status changed from Cerrada to Comentarios
  • Target version changed from 0.5.1 to Nice to have

The PUBLISH doen't fail now, but I don't see the message in the <note> tags. It seems like a pjsua python binding bug...

I'm moving it to 'Nice to have' because it's not completely fixed, but it's not a YASS issue :-/

Updated by Iñaki Baz Castillo over 2 years ago

Saúl Ibarra wrote:

The PUBLISH doen't fail now, but I don't see the message in the <note> tags. It seems like a pjsua python binding bug...

I'm moving it to 'Nice to have' because it's not completely fixed, but it's not a YASS issue :-/

If you are using ngrep-sip to capture it, note that ngrep-sip doesn't show "strange" chars (and they are replaced by "" empty char). A workaround is changing "/usr/bin/ngrep-sip" the line:

ngrep -d $interface -P "" -W byline -T -i -t "$match" $filter

by:
ngrep -d $interface -P "¬" -W byline -T -i -t "$match" $filter

BTE I can sure that the full text is sent as Eyebem displays it correctly :)

Updated by Saúl Ibarra Corretgé over 2 years ago

  • Status changed from Comentarios to Resuelta
  • Target version changed from Nice to have to 0.5.1

Cool! It's fixed then :)

Updated by Iñaki Baz Castillo over 2 years ago

A new version of ngrep-sip-1.0.2-2 is available fixing this issue.

Also available in: Atom PDF