SIPServer

  1. Bug #1463943
  2. Comment #2

Comment 2 for bug 1463943

Revision history for this message
Jason Stephenson (jstephenson) wrote : Re: Non-ascii Unicode characters in messages cause client problems

    To reproduce this bug:

    1) Add an accented or other non-ACII unicode character to the call
    number associated with a copy.

    2) Connect with a SIP client and send an item information message
    (64) to the server.

    3) Your SIP client should do 1 of 3 things:
       a) It will choke on the response.
       b) It will display gibberish for the UTF-8 sequence in the respones.
       c) It will correctly display the call number.

    After applying this patch, your client should handle the same item
    information message response with no trouble. If you inspect the
    call number information, the UTF-8 sequences that potentially caused
    trouble before, should now be replaced by XML-escaped numeric
    entities: © for a copyright symbol.