|Summary:||ASTERISK-04729: Problems with the # character|
|Reporter:||Knut-Håvard Aksnes (knut-haavard aksnes)||Labels:|
|Date Opened:||2005-08-01 03:45:13||Date Closed:||2005-08-01 05:30:16|
|Description:||In my extensions.conf i try to implement call forward coding and have a pattern|
ASTERISK-17# to disable call forwarding. I try to test this using
linphone using: sip:ASTERISKfirstname.lastname@example.org This fails to match the pattern ASTERISK-17#
as the uri is coded by linphone as sip:%email@example.com this is probably correct for linphone to do as # is an excluded character in RFC 2396. This kind of escaping must be undone by the asterisk sip driver before forwarding the data to the dial plan engine. The bug seems to be present both in CVS HEAD and in 1.0.9
|Comments:||By: xrobau (xrobau) 2005-08-01 04:50:40|
That's probably a bad idea. A lot of phones use '#' as a 'Send' button, and only a very few phones can actually send a # (Eg, Snom360 has a [tick] button that is use d as a 'Send'). So while that's not specifically relevant to the bug as such, it's something you should be aware of.
By: Olle Johansson (oej) 2005-08-01 05:27:20
This is a duplicate of ASTERISK-3833 - please check the patch in that issue report. It will solve the SIP issue, however, I can't really say whether Asterisk will accept the "#" character as part of an extensions string. It should, but it removes a few characters from "phone numbers" and is not really ready for full handling of SIP uri's in UTF-8.
By: Olle Johansson (oej) 2005-08-01 05:28:21
xrobau: You are right, that character is seldomly sent in a SIP uri.
By: Olle Johansson (oej) 2005-08-01 05:29:54
Move the discussion to ASTERISK-3833 which is the same issue.