Hi All,

When the contacts with special characters in the telephone numbers for instance, +41 (0) 58 2221862 , 080-2345632 ,+91.9008987678 are imported into end user phone book from Gmail address book /CSV /vCard, currently telephone numbers are imported along with special characters. But "click to call" panel which has different phone options display numbers WITHOUT special characters hence, calls are established successfully.

At the same time, when these contacts are seen on the phones screens, telephone numbers are downloaded by the phones along with special characters which has different effects on Polycom , Avaya 12xx and SMC 3456 phones. Below are the observations :

1.POLYCOM : Polycom downloads all the telephone numbers with special characters and characters ( ) - in the numbers are parsed correctly and the calls are established but Polycom fails to parse if there is *.*(dot) in the number and calls fail with 404 Not Found.

2.AVAYA 12xx : Avaya 12xx phone downloads all the telephone numbers with special characters such as ( ) - but when tried to dial these numbers with characters from PHONE's phone book, calls fail with 404 Not Found and if there is a *.*(dot) in one telephone number, 12xx phone fails to download all the contacts.

3.SMC 3456 : Telephone numbers are seen with special characters ( ) - . (dot)on the softphone UI and calls are established successfully when these numbers are dialed from SMC UI.

My query is, should sipXconfig parse all the characters while importing from Gmail address book, CSV, vCard OR respective phones should parse them when numbers are dialed?

Please let me know whether I should raise bugs for the above mentioned characters or an Improvement stating sipXconfig should parse special characters while importing?

Thanks in Advance,
Vani I.H.
_______________________________________________
sipx-dev mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
sipXecs IP PBX -- http://www.sipfoundry.org/

Reply via email to