using ampersand (&) in the caller id?

This section is for general discussions surrounding digital phone service.
jgionet76
Active Poster
Posts: 81
Joined: 01/14/2010
SIP Device Name: Linksys PAP2T
Firmware Version: 5.1.6(LS)
ISP Name: Vianet.ca
Computer OS: Win7-Pro
Location: Sudbury, Ontario

using ampersand (&) in the caller id?

Post by jgionet76 »

is there a way to use a ampersand (&) in my display name?
right now I know if I put it my phone stops working (can't dial our or receive calls). This has been reported by other users already.
I would like to put: "J&J Gionet"

thanks
User avatar
FONGO_kris
Site Moderator
Posts: 1937
Joined: 05/06/2009
SIP Device Name: Polycom 550 IP Phone
Firmware Version: 4.2.0.0310
ISP Name: Rogers Cable
Computer OS: Ubuntu 11.10
Router: Cisco E1200-N
Smartphone Model: Samsung Galaxy S2
Android Version: 4.0.3
Location: Cambridge, Ontario, Canada

Re: using ampersand (&) in the caller id?

Post by FONGO_kris »

This is a restriction with most caller id services (especially VOIP) and is not necessarily the service itself but the limitations of caller display on the far end. (handsets etc...)
Kris
Logistics & International Purchasing | Fongo
Call us toll-free! 611 from your fongo phone or 1-855-836-3355
Please advise I will no longer be contributing to this forum for the time being. Please feel free to email me.
-----------------------------------------------------------------------------------------------------------------------------------------------
Samsung Galaxy S2 [GT-I9100] / 3.0.15-I9100XXLPH / Thebyani v3.2
jgionet76
Active Poster
Posts: 81
Joined: 01/14/2010
SIP Device Name: Linksys PAP2T
Firmware Version: 5.1.6(LS)
ISP Name: Vianet.ca
Computer OS: Win7-Pro
Location: Sudbury, Ontario

Re: using ampersand (&) in the caller id?

Post by jgionet76 »

admin wrote:This is a restriction with most caller id services (especially VOIP) and is not necessarily the service itself but the limitations of caller display on the far end. (handsets etc...)
that's what I thought.. just wanted to see if there was a workaround.. thxs for the reply!