Wenpeng Song (559e7eb6) at 27 Mar 09:31
Update feed openwrt_telephony
Wenpeng Song (f1d105c0) at 27 Mar 09:24
Wenpeng Song (f1d105c0) at 27 Mar 09:07
update comment
Wenpeng Song (a0a70d27) at 27 Mar 08:52
Update file config_asterisk.sh
Wenpeng Song (64d4596e) at 25 Mar 16:54
Update feed openwrt_telephony
Wenpeng Song (4c220f04) at 25 Mar 16:46
Wenpeng Song (4c220f04) at 25 Mar 16:26
update
fixed with single bracket
fixed with single bracket
nope, it works fine if start with a number as well
Wenpeng Song (4daeed8e) at 25 Mar 16:08
update
yes, all incoming calls that go through the identification from pjsip will goto the call_line with the correspond endpoint(sip0) as the extension. Then we don't need to do another pattern matching here again for the user number.
yes, that's what this changes aimed to do.
And yes, asterisk dial plan support this "name" as extension
they were just checking in sequence(all sections) with the order from pjsip_indentifies.conf.
In this case, it will first check sip:user, then tel:user, then check with the regular expression
nope, this is just a section name.
regular expression determinate by the /
in the value
this is just in case if the user
is start with +
which need to have the \
before it.
this is just in case if the user
is start with +
which need to have the \
before it.