What is the best way to do number normalization in a dial plan to reformat call to e164 before processing? Is this the best way of doing it or is there a better way where I wouldn't need to loopback? <extension name="CleanUp"> <condition field="destination_number" expression="^(44|380)?(\d)$"> <action application="bridge" data="loopback/+$1"/> </condition> </extension>
You can transfer to the new number. That means it starts the dialplan again, so put this cleanup at the top of your dialplan to minimize wasted routing. -Avi On Sat, Sep 24, 2011 at 5:09 AM, Chad Vogel <cvogel@lyonl.com> wrote:
What is the best way to do number normalization in a dial plan to reformat call to e164 before processing? Is this the best way of doing it or is there a better way where I wouldn't need to loopback?
<extension name="CleanUp"> <condition field="destination_number" expression="^(44|380)?(\d)$"> <action application="bridge" data="loopback/+$1"/> </condition> </extension>
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
so how would rewrite the destination_number? On Sep 24, 2011, at 11:49 AM, Avi Marcus wrote: You can transfer to the new number. That means it starts the dialplan again, so put this cleanup at the top of your dialplan to minimize wasted routing. -Avi On Sat, Sep 24, 2011 at 5:09 AM, Chad Vogel <cvogel@lyonl.com<mailto:cvogel@lyonl.com>> wrote: What is the best way to do number normalization in a dial plan to reformat call to e164 before processing? Is this the best way of doing it or is there a better way where I wouldn't need to loopback? <extension name="CleanUp"> <condition field="destination_number" expression="^(44|380)?(\d)$"> <action application="bridge" data="loopback/+$1"/> </condition> </extension> FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org<mailto:FreeSWITCH-users@lists.freeswitch.org> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org<http://www.freeswitch.org/> FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org<mailto:FreeSWITCH-users@lists.freeswitch.org> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
Transfer to it, rather than bridge to loopback. -Avi On Sat, Sep 24, 2011 at 9:12 PM, Chad Vogel <cvogel@lyonl.com> wrote:
so how would rewrite the destination_number?
On Sep 24, 2011, at 11:49 AM, Avi Marcus wrote:
You can transfer to the new number. That means it starts the dialplan again, so put this cleanup at the top of your dialplan to minimize wasted routing. -Avi
On Sat, Sep 24, 2011 at 5:09 AM, Chad Vogel <cvogel@lyonl.com> wrote:
What is the best way to do number normalization in a dial plan to reformat call to e164 before processing? Is this the best way of doing it or is there a better way where I wouldn't need to loopback?
<extension name="CleanUp"> <condition field="destination_number" expression="^(44|380)?(\d)$"
<action application="bridge" data="loopback/+$1"/> </condition> </extension>
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
participants (2)
-
Avi Marcus
-
Chad Vogel