Open GoogleCodeExporter opened 9 years ago
As far as I understand, PBXs that try to be traditional have many shourtcuts
like #XX. I don't think we should
support them via menus at the current stage of development. But we definitely
must support them via dialling
(traditional way). I suppose there could be a problem with the number sign (#)
in the SIP URI. Maybe it should be
escaped somehow for BPX to understand it.
Original comment by eofs...@gmail.com
on 5 Mar 2009 at 11:07
On the other hand, we could support the most common ones. I'll thinkg bout it.
Original comment by eofs...@gmail.com
on 5 Mar 2009 at 11:18
Polycom SoundPoints escapes hash sign as required by RFC 3261#19.1.2:
Here I dialed '#35' and CommuniGate Pro understood that:
10:42:48.737 5 SIPDATA-193630 inp: From: "polycom"
<sip:polycom@domain>;tag=8D12345B-1015E658
10:42:48.737 5 SIPDATA-193630 inp: To: <sip:%2335@domain>
...
10:42:48.737 1 ROUTER SYSTEM: '#35@domain' rejected. Error Code=unknown user
account
I have not asterisk around to try it but I believe it should work the same way.
So I'd suggest to follow polycom
here.
Original comment by alexey.n...@gmail.com
on 6 Mar 2009 at 7:52
Hash sign is already being escaped by Telephone, but it wasn't in the list of
valid characters while scanning the
phone number. Added in r634.
Original comment by eofs...@gmail.com
on 6 Mar 2009 at 10:31
Original comment by eofs...@gmail.com
on 6 Mar 2009 at 10:32
[deleted comment]
[deleted comment]
Hi
I think call forwarding would be very important (for me definitely).
Original comment by TREEINSP...@gmail.com
on 25 Jun 2009 at 9:33
Original issue reported on code.google.com by
motto.ui...@gmail.com
on 5 Mar 2009 at 10:32