Re: [Freeswitch-users] Freeswitch and twilio
if you have a deep look at inbound gateway it is for receiving calls from Twilio as you can see below, this line informing freeswitch where to route inkling call. <param name="extension" value="1000"/>
From: Michael Nielsen <mic.niel84@gmail.com> Date: October 2, 2015 at 11:24:51 PM GMT+3 To: FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org> Subject: Re: [Freeswitch-users] Freeswitch and twilio
Outbound works fine.
Without having the inbound gateway calls are still routed to my FS to my public context from Twilio. Adding the twilio-inbound doesn't seem to change anything...?
On Friday, October 2, 2015, Brian West <brian@freeswitch.org <mailto:brian@freeswitch.org>> wrote: Well you'd send outbound calls out the outbound and the inbound one is just to register with twilio so they know where to send your inbound calls. Nothing more.
On Fri, Oct 2, 2015 at 1:46 PM, Michael Nielsen <mic.niel84@gmail.com <javascript:_e(%7B%7D,'cvml','mic.niel84@gmail.com');>> wrote: I'm trying to setup twilio as gateway following this guide: https://www.twilio.com/docs/sip-trunking/sample-configuration#freeswitch <https://www.twilio.com/docs/sip-trunking/sample-configuration#freeswitch>
In their example of twiliotrunk.xml they have twilio-inbound and twilio-outbound.
What is the difference between the two gateways? I know their names indicate inbound and outbound calling, but how can Freeswitch tell the difference between them. Especially how can Freeswitch now to use twilio-inbound for incoming calls from twilio and not just twilit-outbound as the only difference is register-proxy and expire-seconds between the two?
Make sense?
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org <javascript:_e(%7B%7D,'cvml','consulting@freeswitch.org');> http://www.freeswitchsolutions.com <http://www.freeswitchsolutions.com/>
Official FreeSWITCH Sites http://www.freeswitch.org <http://www.freeswitch.org/> http://confluence.freeswitch.org <http://confluence.freeswitch.org/> http://www.cluecon.com <http://www.cluecon.com/>
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org <javascript:_e(%7B%7D,'cvml','FreeSWITCH-users@lists.freeswitch.org');> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users <http://lists.freeswitch.org/mailman/listinfo/freeswitch-users> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users <http://lists.freeswitch.org/mailman/options/freeswitch-users> http://www.freeswitch.org <http://www.freeswitch.org/>
-- Brian West brian@freeswitch.org <javascript:_e(%7B%7D,'cvml','brian@freeswitch.org');>
Twitter: @FreeSWITCH , @briankwest http://www.freeswitchbook.com <http://www.freeswitchbook.com/> http://www.freeswitchcookbook.com <http://www.freeswitchcookbook.com/> Got Bugs? Report them here <https://freeswitch.org/jira>! | Reddit: /r/freeswitch <https://www.reddit.com/r/freeswitch> T:+19184209001 | F:+19184209002 | M:+1918424WEST (9378) iNUM:+883 5100 1420 9001 | ISN:410*543 | Skype:briankwest
_______________________________________________ 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
I see. Does it matter that I don't have an extension called 1000 in my FS, nor in my Twilio account? On Fri, Oct 2, 2015 at 11:34 PM, Ahmed Habiba <ahabiba@gmail.com> wrote:
if you have a deep look at inbound gateway it is for receiving calls from Twilio as you can see below, this line informing freeswitch where to route inkling call.
<param name="extension" value="1000"/>
*From: *Michael Nielsen <mic.niel84@gmail.com> *Date: *October 2, 2015 at 11:24:51 PM GMT+3 *To: *FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org> *Subject: **Re: [Freeswitch-users] Freeswitch and twilio*
Outbound works fine.
Without having the inbound gateway calls are still routed to my FS to my public context from Twilio. Adding the twilio-inbound doesn't seem to change anything...?
On Friday, October 2, 2015, Brian West <brian@freeswitch.org> wrote:
Well you'd send outbound calls out the outbound and the inbound one is just to register with twilio so they know where to send your inbound calls. Nothing more.
On Fri, Oct 2, 2015 at 1:46 PM, Michael Nielsen <mic.niel84@gmail.com> wrote:
I'm trying to setup twilio as gateway following this guide: https://www.twilio.com/docs/sip-trunking/sample-configuration#freeswitch
In their example of twiliotrunk.xml they have twilio-inbound and twilio-outbound.
What is the difference between the two gateways? I know their names indicate inbound and outbound calling, but how can Freeswitch tell the difference between them. Especially how can Freeswitch now to use twilio-inbound for incoming calls from twilio and not just twilit-outbound as the only difference is register-proxy and expire-seconds between the two?
Make sense?
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
--
*Brian West* brian@freeswitch.org
*Twitter: @FreeSWITCH , @briankwest* http://www.freeswitchbook.com http://www.freeswitchcookbook.com
Got Bugs? Report them here <https://freeswitch.org/jira>! | Reddit: /r/freeswitch <https://www.reddit.com/r/freeswitch>
*T:*+19184209001 | *F:*+19184209002 | *M:*+1918424WEST (9378) *iNUM:*+883 5100 1420 9001 | *ISN:*410*543 | *Skype:*briankwest
_______________________________________________ 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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
When adding the extension, I get the following - even though my username and password etc. are correct as they work for the outbound gateway...: twilio-inbound Failed Registration [908] On Sat, Oct 3, 2015 at 11:57 AM, Michael Nielsen <mic.niel84@gmail.com> wrote:
I see. Does it matter that I don't have an extension called 1000 in my FS, nor in my Twilio account?
On Fri, Oct 2, 2015 at 11:34 PM, Ahmed Habiba <ahabiba@gmail.com> wrote:
if you have a deep look at inbound gateway it is for receiving calls from Twilio as you can see below, this line informing freeswitch where to route inkling call.
<param name="extension" value="1000"/>
*From: *Michael Nielsen <mic.niel84@gmail.com> *Date: *October 2, 2015 at 11:24:51 PM GMT+3 *To: *FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org> *Subject: **Re: [Freeswitch-users] Freeswitch and twilio*
Outbound works fine.
Without having the inbound gateway calls are still routed to my FS to my public context from Twilio. Adding the twilio-inbound doesn't seem to change anything...?
On Friday, October 2, 2015, Brian West <brian@freeswitch.org> wrote:
Well you'd send outbound calls out the outbound and the inbound one is just to register with twilio so they know where to send your inbound calls. Nothing more.
On Fri, Oct 2, 2015 at 1:46 PM, Michael Nielsen <mic.niel84@gmail.com> wrote:
I'm trying to setup twilio as gateway following this guide: https://www.twilio.com/docs/sip-trunking/sample-configuration#freeswitch
In their example of twiliotrunk.xml they have twilio-inbound and twilio-outbound.
What is the difference between the two gateways? I know their names indicate inbound and outbound calling, but how can Freeswitch tell the difference between them. Especially how can Freeswitch now to use twilio-inbound for incoming calls from twilio and not just twilit-outbound as the only difference is register-proxy and expire-seconds between the two?
Make sense?
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
--
*Brian West* brian@freeswitch.org
*Twitter: @FreeSWITCH , @briankwest* http://www.freeswitchbook.com http://www.freeswitchcookbook.com
Got Bugs? Report them here <https://freeswitch.org/jira>! | Reddit: /r/freeswitch <https://www.reddit.com/r/freeswitch>
*T:*+19184209001 | *F:*+19184209002 | *M:*+1918424WEST (9378) *iNUM:*+883 5100 1420 9001 | *ISN:*410*543 | *Skype:*briankwest
_______________________________________________ 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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
Looking at their guide for secure setup: https://www.twilio.com/resources/images/docs/Twilio-Freeswitch.pdf they've added <param name="register" value="false"/> When I do this, registering doesn't fail (obviously), but inbound calls are still not registered as coming from twilio... They still land directly in the public context without the variables set correctly. On Sat, Oct 3, 2015 at 11:58 AM, Michael Nielsen <mic.niel84@gmail.com> wrote:
When adding the extension, I get the following - even though my username and password etc. are correct as they work for the outbound gateway...:
twilio-inbound Failed Registration [908]
On Sat, Oct 3, 2015 at 11:57 AM, Michael Nielsen <mic.niel84@gmail.com> wrote:
I see. Does it matter that I don't have an extension called 1000 in my FS, nor in my Twilio account?
On Fri, Oct 2, 2015 at 11:34 PM, Ahmed Habiba <ahabiba@gmail.com> wrote:
if you have a deep look at inbound gateway it is for receiving calls from Twilio as you can see below, this line informing freeswitch where to route inkling call.
<param name="extension" value="1000"/>
*From: *Michael Nielsen <mic.niel84@gmail.com> *Date: *October 2, 2015 at 11:24:51 PM GMT+3 *To: *FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org> *Subject: **Re: [Freeswitch-users] Freeswitch and twilio*
Outbound works fine.
Without having the inbound gateway calls are still routed to my FS to my public context from Twilio. Adding the twilio-inbound doesn't seem to change anything...?
On Friday, October 2, 2015, Brian West <brian@freeswitch.org> wrote:
Well you'd send outbound calls out the outbound and the inbound one is just to register with twilio so they know where to send your inbound calls. Nothing more.
On Fri, Oct 2, 2015 at 1:46 PM, Michael Nielsen <mic.niel84@gmail.com> wrote:
I'm trying to setup twilio as gateway following this guide:
https://www.twilio.com/docs/sip-trunking/sample-configuration#freeswitch
In their example of twiliotrunk.xml they have twilio-inbound and twilio-outbound.
What is the difference between the two gateways? I know their names indicate inbound and outbound calling, but how can Freeswitch tell the difference between them. Especially how can Freeswitch now to use twilio-inbound for incoming calls from twilio and not just twilit-outbound as the only difference is register-proxy and expire-seconds between the two?
Make sense?
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
--
*Brian West* brian@freeswitch.org
*Twitter: @FreeSWITCH , @briankwest* http://www.freeswitchbook.com http://www.freeswitchcookbook.com
Got Bugs? Report them here <https://freeswitch.org/jira>! | Reddit: /r/freeswitch <https://www.reddit.com/r/freeswitch>
*T:*+19184209001 | *F:*+19184209002 | *M:*+1918424WEST (9378) *iNUM:*+883 5100 1420 9001 | *ISN:*410*543 | *Skype:*briankwest
_______________________________________________ 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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
Still no luck. Any other ideas on how to "catch" the calls from the public context in FS? My goal is to transfer all calls from Twilio to my default context. On Saturday, October 3, 2015, Michael Nielsen <mic.niel84@gmail.com> wrote:
Looking at their guide for secure setup: https://www.twilio.com/resources/images/docs/Twilio-Freeswitch.pdf they've added <param name="register" value="false"/> When I do this, registering doesn't fail (obviously), but inbound calls are still not registered as coming from twilio... They still land directly in the public context without the variables set correctly.
On Sat, Oct 3, 2015 at 11:58 AM, Michael Nielsen <mic.niel84@gmail.com <javascript:_e(%7B%7D,'cvml','mic.niel84@gmail.com');>> wrote:
When adding the extension, I get the following - even though my username and password etc. are correct as they work for the outbound gateway...:
twilio-inbound Failed Registration [908]
On Sat, Oct 3, 2015 at 11:57 AM, Michael Nielsen <mic.niel84@gmail.com <javascript:_e(%7B%7D,'cvml','mic.niel84@gmail.com');>> wrote:
I see. Does it matter that I don't have an extension called 1000 in my FS, nor in my Twilio account?
On Fri, Oct 2, 2015 at 11:34 PM, Ahmed Habiba <ahabiba@gmail.com <javascript:_e(%7B%7D,'cvml','ahabiba@gmail.com');>> wrote:
if you have a deep look at inbound gateway it is for receiving calls from Twilio as you can see below, this line informing freeswitch where to route inkling call.
<param name="extension" value="1000"/>
*From: *Michael Nielsen <mic.niel84@gmail.com <javascript:_e(%7B%7D,'cvml','mic.niel84@gmail.com');>> *Date: *October 2, 2015 at 11:24:51 PM GMT+3 *To: *FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org <javascript:_e(%7B%7D,'cvml','freeswitch-users@lists.freeswitch.org');>
*Subject: **Re: [Freeswitch-users] Freeswitch and twilio*
Outbound works fine.
Without having the inbound gateway calls are still routed to my FS to my public context from Twilio. Adding the twilio-inbound doesn't seem to change anything...?
On Friday, October 2, 2015, Brian West <brian@freeswitch.org <javascript:_e(%7B%7D,'cvml','brian@freeswitch.org');>> wrote:
Well you'd send outbound calls out the outbound and the inbound one is just to register with twilio so they know where to send your inbound calls. Nothing more.
On Fri, Oct 2, 2015 at 1:46 PM, Michael Nielsen <mic.niel84@gmail.com> wrote:
I'm trying to setup twilio as gateway following this guide:
https://www.twilio.com/docs/sip-trunking/sample-configuration#freeswitch
In their example of twiliotrunk.xml they have twilio-inbound and twilio-outbound.
What is the difference between the two gateways? I know their names indicate inbound and outbound calling, but how can Freeswitch tell the difference between them. Especially how can Freeswitch now to use twilio-inbound for incoming calls from twilio and not just twilit-outbound as the only difference is register-proxy and expire-seconds between the two?
Make sense?
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
--
*Brian West* brian@freeswitch.org
*Twitter: @FreeSWITCH , @briankwest* http://www.freeswitchbook.com http://www.freeswitchcookbook.com
Got Bugs? Report them here <https://freeswitch.org/jira>! | Reddit: /r/freeswitch <https://www.reddit.com/r/freeswitch>
*T:*+19184209001 | *F:*+19184209002 | *M:*+1918424WEST (9378) *iNUM:*+883 5100 1420 9001 | *ISN:*410*543 | *Skype:*briankwest
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org <javascript:_e(%7B%7D,'cvml','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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org <javascript:_e(%7B%7D,'cvml','consulting@freeswitch.org');> http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org <javascript:_e(%7B%7D,'cvml','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
Inbound call can be received 1) if twillio guys configure gateway to route incomes calls to you 2) or if FS provide information how to route call for you After reading gateway config files, I has found that used second case "FS provides information how to route calls via registration mechanism". Please: - configure clean FS host as described in twilio manuals; - enable siptrace; - enable debug log; - make incoming call; - attach debug log in respond to this message. I try help you On Sun, Oct 4, 2015 at 2:37 PM, Michael Nielsen <mic.niel84@gmail.com> wrote:
Still no luck. Any other ideas on how to "catch" the calls from the public context in FS? My goal is to transfer all calls from Twilio to my default context.
On Saturday, October 3, 2015, Michael Nielsen <mic.niel84@gmail.com> wrote:
Looking at their guide for secure setup: https://www.twilio.com/resources/images/docs/Twilio-Freeswitch.pdf they've added <param name="register" value="false"/> When I do this, registering doesn't fail (obviously), but inbound calls are still not registered as coming from twilio... They still land directly in the public context without the variables set correctly.
On Sat, Oct 3, 2015 at 11:58 AM, Michael Nielsen <mic.niel84@gmail.com> wrote:
When adding the extension, I get the following - even though my username and password etc. are correct as they work for the outbound gateway...:
twilio-inbound Failed Registration [908]
On Sat, Oct 3, 2015 at 11:57 AM, Michael Nielsen <mic.niel84@gmail.com> wrote:
I see. Does it matter that I don't have an extension called 1000 in my FS, nor in my Twilio account?
On Fri, Oct 2, 2015 at 11:34 PM, Ahmed Habiba <ahabiba@gmail.com> wrote:
if you have a deep look at inbound gateway it is for receiving calls from Twilio as you can see below, this line informing freeswitch where to route inkling call.
<param name="extension" value="1000"/>
*From: *Michael Nielsen <mic.niel84@gmail.com> *Date: *October 2, 2015 at 11:24:51 PM GMT+3 *To: *FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org> *Subject: **Re: [Freeswitch-users] Freeswitch and twilio*
Outbound works fine.
Without having the inbound gateway calls are still routed to my FS to my public context from Twilio. Adding the twilio-inbound doesn't seem to change anything...?
On Friday, October 2, 2015, Brian West <brian@freeswitch.org> wrote:
Well you'd send outbound calls out the outbound and the inbound one is just to register with twilio so they know where to send your inbound calls. Nothing more.
On Fri, Oct 2, 2015 at 1:46 PM, Michael Nielsen <mic.niel84@gmail.com > wrote:
> I'm trying to setup twilio as gateway following this guide: > > https://www.twilio.com/docs/sip-trunking/sample-configuration#freeswitch > > In their example of twiliotrunk.xml they have twilio-inbound and > twilio-outbound. > > What is the difference between the two gateways? I know their names > indicate inbound and outbound calling, but how can Freeswitch tell the > difference between them. Especially how can Freeswitch now to use > twilio-inbound for incoming calls from twilio and not just twilit-outbound > as the only difference is register-proxy and expire-seconds between the two? > > Make sense? > > > _________________________________________________________________________ > Professional FreeSWITCH Consulting Services: > consulting@freeswitch.org > http://www.freeswitchsolutions.com > > Official FreeSWITCH Sites > http://www.freeswitch.org > http://confluence.freeswitch.org > http://www.cluecon.com > > 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 >
--
*Brian West* brian@freeswitch.org
*Twitter: @FreeSWITCH , @briankwest* http://www.freeswitchbook.com http://www.freeswitchcookbook.com
Got Bugs? Report them here <https://freeswitch.org/jira>! | Reddit: /r/freeswitch <https://www.reddit.com/r/freeswitch>
*T:*+19184209001 | *F:*+19184209002 | *M:*+1918424WEST (9378) *iNUM:*+883 5100 1420 9001 | *ISN:*410*543 | *Skype:*briankwest
_______________________________________________ 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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
I'll create some logs tomorrow. Just to clarify: - Calls are routes from Twilio to my FS - My FS is a clean installation, 1.6.2 - I've used Twilio's guide for setting up gateways, inbound and outbound - Outbound calls are routed correctly - Inbound calls are as mentioned routes to my FS, but my Twilio-inbound doesn't seem to have anything to do with it, therefor, I'm not able to set any variables in incoming calls from Twilio so I can detect them in my public context and transfer them to my default context. I don't want to route all calls in my public context to my default context, this would open a security issue. Only Twilio calls should be handled in such a manner. That's my challenge. On Sunday, October 4, 2015, Sergey Safarov <s.safarov@gmail.com> wrote:
Inbound call can be received 1) if twillio guys configure gateway to route incomes calls to you 2) or if FS provide information how to route call for you
After reading gateway config files, I has found that used second case "FS provides information how to route calls via registration mechanism".
Please: - configure clean FS host as described in twilio manuals; - enable siptrace; - enable debug log; - make incoming call; - attach debug log in respond to this message.
I try help you
On Sun, Oct 4, 2015 at 2:37 PM, Michael Nielsen <mic.niel84@gmail.com <javascript:_e(%7B%7D,'cvml','mic.niel84@gmail.com');>> wrote:
Still no luck. Any other ideas on how to "catch" the calls from the public context in FS? My goal is to transfer all calls from Twilio to my default context.
On Saturday, October 3, 2015, Michael Nielsen <mic.niel84@gmail.com <javascript:_e(%7B%7D,'cvml','mic.niel84@gmail.com');>> wrote:
Looking at their guide for secure setup: https://www.twilio.com/resources/images/docs/Twilio-Freeswitch.pdf they've added <param name="register" value="false"/> When I do this, registering doesn't fail (obviously), but inbound calls are still not registered as coming from twilio... They still land directly in the public context without the variables set correctly.
On Sat, Oct 3, 2015 at 11:58 AM, Michael Nielsen <mic.niel84@gmail.com> wrote:
When adding the extension, I get the following - even though my username and password etc. are correct as they work for the outbound gateway...:
twilio-inbound Failed Registration [908]
On Sat, Oct 3, 2015 at 11:57 AM, Michael Nielsen <mic.niel84@gmail.com> wrote:
I see. Does it matter that I don't have an extension called 1000 in my FS, nor in my Twilio account?
On Fri, Oct 2, 2015 at 11:34 PM, Ahmed Habiba <ahabiba@gmail.com> wrote:
if you have a deep look at inbound gateway it is for receiving calls from Twilio as you can see below, this line informing freeswitch where to route inkling call.
<param name="extension" value="1000"/>
*From: *Michael Nielsen <mic.niel84@gmail.com> *Date: *October 2, 2015 at 11:24:51 PM GMT+3 *To: *FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org> *Subject: **Re: [Freeswitch-users] Freeswitch and twilio*
Outbound works fine.
Without having the inbound gateway calls are still routed to my FS to my public context from Twilio. Adding the twilio-inbound doesn't seem to change anything...?
On Friday, October 2, 2015, Brian West <brian@freeswitch.org> wrote:
> Well you'd send outbound calls out the outbound and the inbound one > is just to register with twilio so they know where to send your inbound > calls. Nothing more. > > On Fri, Oct 2, 2015 at 1:46 PM, Michael Nielsen < > mic.niel84@gmail.com> wrote: > >> I'm trying to setup twilio as gateway following this guide: >> >> https://www.twilio.com/docs/sip-trunking/sample-configuration#freeswitch >> >> In their example of twiliotrunk.xml they have twilio-inbound and >> twilio-outbound. >> >> What is the difference between the two gateways? I know their names >> indicate inbound and outbound calling, but how can Freeswitch tell the >> difference between them. Especially how can Freeswitch now to use >> twilio-inbound for incoming calls from twilio and not just twilit-outbound >> as the only difference is register-proxy and expire-seconds between the two? >> >> Make sense? >> >> >> _________________________________________________________________________ >> Professional FreeSWITCH Consulting Services: >> consulting@freeswitch.org >> http://www.freeswitchsolutions.com >> >> Official FreeSWITCH Sites >> http://www.freeswitch.org >> http://confluence.freeswitch.org >> http://www.cluecon.com >> >> 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 >> > > > > -- > > *Brian West* > brian@freeswitch.org > > > *Twitter: @FreeSWITCH , @briankwest* > http://www.freeswitchbook.com > http://www.freeswitchcookbook.com > > Got Bugs? Report them here <https://freeswitch.org/jira>! | Reddit: > /r/freeswitch <https://www.reddit.com/r/freeswitch> > > *T:*+19184209001 | *F:*+19184209002 | *M:*+1918424WEST (9378) > *iNUM:*+883 5100 1420 9001 | *ISN:*410*543 | *Skype:*briankwest >
_______________________________________________ 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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org <javascript:_e(%7B%7D,'cvml','consulting@freeswitch.org');> http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org <javascript:_e(%7B%7D,'cvml','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
Here's as log from an incoming call from Twilio: http://pastebin.com/n0de7jhv My guess is the problem is with line 33: "Processing +4432445867 <+4432445867>->+44213395867 in context public" and it fails on line 40: "Regex (FAIL) [gateway_inbound] ${target_context}() =~ /^[a-z]/ break=on-false" due to the fact that there aren't set any ${target_context} variable. I've added the Twilio inbound gateway as described in the Twilio guide, but adding it, removing it etc. doesn't change anything at all. To the Twilio-Inbound gateway I've added the variable ${target_context} according to this guide: https://github.com/voxserv/freeswitch_conf_minimal/blob/master/docs/tutorial... So my guess is that the Twilio-Inbound gateway aren't being used - however - calls are routed to my FS. On Sun, Oct 4, 2015 at 10:15 PM, Michael Nielsen <mic.niel84@gmail.com> wrote:
I'll create some logs tomorrow.
Just to clarify: - Calls are routes from Twilio to my FS - My FS is a clean installation, 1.6.2 - I've used Twilio's guide for setting up gateways, inbound and outbound - Outbound calls are routed correctly - Inbound calls are as mentioned routes to my FS, but my Twilio-inbound doesn't seem to have anything to do with it, therefor, I'm not able to set any variables in incoming calls from Twilio so I can detect them in my public context and transfer them to my default context.
I don't want to route all calls in my public context to my default context, this would open a security issue. Only Twilio calls should be handled in such a manner. That's my challenge.
On Sunday, October 4, 2015, Sergey Safarov <s.safarov@gmail.com> wrote:
Inbound call can be received 1) if twillio guys configure gateway to route incomes calls to you 2) or if FS provide information how to route call for you
After reading gateway config files, I has found that used second case "FS provides information how to route calls via registration mechanism".
Please: - configure clean FS host as described in twilio manuals; - enable siptrace; - enable debug log; - make incoming call; - attach debug log in respond to this message.
I try help you
On Sun, Oct 4, 2015 at 2:37 PM, Michael Nielsen <mic.niel84@gmail.com> wrote:
Still no luck. Any other ideas on how to "catch" the calls from the public context in FS? My goal is to transfer all calls from Twilio to my default context.
On Saturday, October 3, 2015, Michael Nielsen <mic.niel84@gmail.com> wrote:
Looking at their guide for secure setup: https://www.twilio.com/resources/images/docs/Twilio-Freeswitch.pdf they've added <param name="register" value="false"/> When I do this, registering doesn't fail (obviously), but inbound calls are still not registered as coming from twilio... They still land directly in the public context without the variables set correctly.
On Sat, Oct 3, 2015 at 11:58 AM, Michael Nielsen <mic.niel84@gmail.com> wrote:
When adding the extension, I get the following - even though my username and password etc. are correct as they work for the outbound gateway...:
twilio-inbound Failed Registration [908]
On Sat, Oct 3, 2015 at 11:57 AM, Michael Nielsen <mic.niel84@gmail.com
wrote:
I see. Does it matter that I don't have an extension called 1000 in my FS, nor in my Twilio account?
On Fri, Oct 2, 2015 at 11:34 PM, Ahmed Habiba <ahabiba@gmail.com> wrote:
> if you have a deep look at inbound gateway it is for receiving > calls from Twilio as you can see below, this line informing freeswitch > where to route inkling call. > > <param name="extension" value="1000"/> > > > > *From: *Michael Nielsen <mic.niel84@gmail.com> > *Date: *October 2, 2015 at 11:24:51 PM GMT+3 > *To: *FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org> > *Subject: **Re: [Freeswitch-users] Freeswitch and twilio* > > > Outbound works fine. > > Without having the inbound gateway calls are still routed to my FS > to my public context from Twilio. > Adding the twilio-inbound doesn't seem to change anything...? > > > > On Friday, October 2, 2015, Brian West <brian@freeswitch.org> wrote: > >> Well you'd send outbound calls out the outbound and the inbound >> one is just to register with twilio so they know where to send your inbound >> calls. Nothing more. >> >> On Fri, Oct 2, 2015 at 1:46 PM, Michael Nielsen < >> mic.niel84@gmail.com> wrote: >> >>> I'm trying to setup twilio as gateway following this guide: >>> >>> https://www.twilio.com/docs/sip-trunking/sample-configuration#freeswitch >>> >>> In their example of twiliotrunk.xml they have twilio-inbound and >>> twilio-outbound. >>> >>> What is the difference between the two gateways? I know their >>> names indicate inbound and outbound calling, but how can Freeswitch tell >>> the difference between them. Especially how can Freeswitch now to use >>> twilio-inbound for incoming calls from twilio and not just twilit-outbound >>> as the only difference is register-proxy and expire-seconds between the two? >>> >>> Make sense? >>> >>> >>> _________________________________________________________________________ >>> Professional FreeSWITCH Consulting Services: >>> consulting@freeswitch.org >>> http://www.freeswitchsolutions.com >>> >>> Official FreeSWITCH Sites >>> http://www.freeswitch.org >>> http://confluence.freeswitch.org >>> http://www.cluecon.com >>> >>> 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 >>> >> >> >> >> -- >> >> *Brian West* >> brian@freeswitch.org >> >> >> *Twitter: @FreeSWITCH , @briankwest* >> http://www.freeswitchbook.com >> http://www.freeswitchcookbook.com >> >> Got Bugs? Report them here <https://freeswitch.org/jira>! | >> Reddit: /r/freeswitch <https://www.reddit.com/r/freeswitch> >> >> *T:*+19184209001 | *F:*+19184209002 | *M:*+1918424WEST (9378) >> *iNUM:*+883 5100 1420 9001 | *ISN:*410*543 | *Skype:*briankwest >> > > > _______________________________________________ > 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 > > > > > _________________________________________________________________________ > Professional FreeSWITCH Consulting Services: > consulting@freeswitch.org > http://www.freeswitchsolutions.com > > Official FreeSWITCH Sites > http://www.freeswitch.org > http://confluence.freeswitch.org > http://www.cluecon.com > > 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 >
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
in your pastebin, you seem to receive the call on your internal profile (port 5060): 11:18:58.277709 [DEBUG] sofia.c:9229 sofia/internal/+ 4432445867@sip.ie1.twilio.com receiving invite from 54.171.127.192:5060 so, what exactly is configured on both sides? The external profile is usually on the port 5080. On Mon, Oct 5, 2015 at 6:26 PM, Michael Nielsen <mic.niel84@gmail.com> wrote:
Here's as log from an incoming call from Twilio: http://pastebin.com/n0de7jhv
My guess is the problem is with line 33: "Processing +4432445867 <+4432445867>->+44213395867 in context public" and it fails on line 40: "Regex (FAIL) [gateway_inbound] ${target_context}() =~ /^[a-z]/ break=on-false" due to the fact that there aren't set any ${target_context} variable.
I've added the Twilio inbound gateway as described in the Twilio guide, but adding it, removing it etc. doesn't change anything at all. To the Twilio-Inbound gateway I've added the variable ${target_context} according to this guide: https://github.com/voxserv/freeswitch_conf_minimal/blob/master/docs/tutorial...
So my guess is that the Twilio-Inbound gateway aren't being used - however - calls are routed to my FS.
On Sun, Oct 4, 2015 at 10:15 PM, Michael Nielsen <mic.niel84@gmail.com> wrote:
I'll create some logs tomorrow.
Just to clarify: - Calls are routes from Twilio to my FS - My FS is a clean installation, 1.6.2 - I've used Twilio's guide for setting up gateways, inbound and outbound - Outbound calls are routed correctly - Inbound calls are as mentioned routes to my FS, but my Twilio-inbound doesn't seem to have anything to do with it, therefor, I'm not able to set any variables in incoming calls from Twilio so I can detect them in my public context and transfer them to my default context.
I don't want to route all calls in my public context to my default context, this would open a security issue. Only Twilio calls should be handled in such a manner. That's my challenge.
On Sunday, October 4, 2015, Sergey Safarov <s.safarov@gmail.com> wrote:
Inbound call can be received 1) if twillio guys configure gateway to route incomes calls to you 2) or if FS provide information how to route call for you
After reading gateway config files, I has found that used second case "FS provides information how to route calls via registration mechanism".
Please: - configure clean FS host as described in twilio manuals; - enable siptrace; - enable debug log; - make incoming call; - attach debug log in respond to this message.
I try help you
On Sun, Oct 4, 2015 at 2:37 PM, Michael Nielsen <mic.niel84@gmail.com> wrote:
Still no luck. Any other ideas on how to "catch" the calls from the public context in FS? My goal is to transfer all calls from Twilio to my default context.
On Saturday, October 3, 2015, Michael Nielsen <mic.niel84@gmail.com> wrote:
Looking at their guide for secure setup: https://www.twilio.com/resources/images/docs/Twilio-Freeswitch.pdf they've added <param name="register" value="false"/> When I do this, registering doesn't fail (obviously), but inbound calls are still not registered as coming from twilio... They still land directly in the public context without the variables set correctly.
On Sat, Oct 3, 2015 at 11:58 AM, Michael Nielsen <mic.niel84@gmail.com
wrote:
When adding the extension, I get the following - even though my username and password etc. are correct as they work for the outbound gateway...:
twilio-inbound Failed Registration [908]
On Sat, Oct 3, 2015 at 11:57 AM, Michael Nielsen < mic.niel84@gmail.com> wrote:
> I see. > Does it matter that I don't have an extension called 1000 in my FS, > nor in my Twilio account? > > On Fri, Oct 2, 2015 at 11:34 PM, Ahmed Habiba <ahabiba@gmail.com> > wrote: > >> if you have a deep look at inbound gateway it is for receiving >> calls from Twilio as you can see below, this line informing freeswitch >> where to route inkling call. >> >> <param name="extension" value="1000"/> >> >> >> >> *From: *Michael Nielsen <mic.niel84@gmail.com> >> *Date: *October 2, 2015 at 11:24:51 PM GMT+3 >> *To: *FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org> >> *Subject: **Re: [Freeswitch-users] Freeswitch and twilio* >> >> >> Outbound works fine. >> >> Without having the inbound gateway calls are still routed to my FS >> to my public context from Twilio. >> Adding the twilio-inbound doesn't seem to change anything...? >> >> >> >> On Friday, October 2, 2015, Brian West <brian@freeswitch.org> >> wrote: >> >>> Well you'd send outbound calls out the outbound and the inbound >>> one is just to register with twilio so they know where to send your inbound >>> calls. Nothing more. >>> >>> On Fri, Oct 2, 2015 at 1:46 PM, Michael Nielsen < >>> mic.niel84@gmail.com> wrote: >>> >>>> I'm trying to setup twilio as gateway following this guide: >>>> >>>> https://www.twilio.com/docs/sip-trunking/sample-configuration#freeswitch >>>> >>>> In their example of twiliotrunk.xml they have twilio-inbound and >>>> twilio-outbound. >>>> >>>> What is the difference between the two gateways? I know their >>>> names indicate inbound and outbound calling, but how can Freeswitch tell >>>> the difference between them. Especially how can Freeswitch now to use >>>> twilio-inbound for incoming calls from twilio and not just twilit-outbound >>>> as the only difference is register-proxy and expire-seconds between the two? >>>> >>>> Make sense? >>>> >>>> >>>> _________________________________________________________________________ >>>> Professional FreeSWITCH Consulting Services: >>>> consulting@freeswitch.org >>>> http://www.freeswitchsolutions.com >>>> >>>> Official FreeSWITCH Sites >>>> http://www.freeswitch.org >>>> http://confluence.freeswitch.org >>>> http://www.cluecon.com >>>> >>>> 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 >>>> >>> >>> >>> >>> -- >>> >>> *Brian West* >>> brian@freeswitch.org >>> >>> >>> *Twitter: @FreeSWITCH , @briankwest* >>> http://www.freeswitchbook.com >>> http://www.freeswitchcookbook.com >>> >>> Got Bugs? Report them here <https://freeswitch.org/jira>! | >>> Reddit: /r/freeswitch <https://www.reddit.com/r/freeswitch> >>> >>> *T:*+19184209001 | *F:*+19184209002 | *M:*+1918424WEST (9378) >>> *iNUM:*+883 5100 1420 9001 | *ISN:*410*543 | *Skype:*briankwest >>> >> >> >> _______________________________________________ >> 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 >> >> >> >> >> _________________________________________________________________________ >> Professional FreeSWITCH Consulting Services: >> consulting@freeswitch.org >> http://www.freeswitchsolutions.com >> >> Official FreeSWITCH Sites >> http://www.freeswitch.org >> http://confluence.freeswitch.org >> http://www.cluecon.com >> >> 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 >> > >
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
Twilio is just taking a sip address as termination address. In this case my domain which FS runs on. Apparently, Twilio is sending calls to the standard 5060 port - which then lands in my public context. On Monday, October 5, 2015, Stanislav Sinyagin <ssinyagin@gmail.com> wrote:
in your pastebin, you seem to receive the call on your internal profile (port 5060): 11:18:58.277709 [DEBUG] sofia.c:9229 sofia/internal/+ 4432445867@sip.ie1.twilio.com <javascript:_e(%7B%7D,'cvml','4432445867@sip.ie1.twilio.com');> receiving invite from 54.171.127.192:5060
so, what exactly is configured on both sides? The external profile is usually on the port 5080.
On Mon, Oct 5, 2015 at 6:26 PM, Michael Nielsen <mic.niel84@gmail.com <javascript:_e(%7B%7D,'cvml','mic.niel84@gmail.com');>> wrote:
Here's as log from an incoming call from Twilio: http://pastebin.com/n0de7jhv
My guess is the problem is with line 33: "Processing +4432445867 <+4432445867>->+44213395867 in context public" and it fails on line 40: "Regex (FAIL) [gateway_inbound] ${target_context}() =~ /^[a-z]/ break=on-false" due to the fact that there aren't set any ${target_context} variable.
I've added the Twilio inbound gateway as described in the Twilio guide, but adding it, removing it etc. doesn't change anything at all. To the Twilio-Inbound gateway I've added the variable ${target_context} according to this guide: https://github.com/voxserv/freeswitch_conf_minimal/blob/master/docs/tutorial...
So my guess is that the Twilio-Inbound gateway aren't being used - however - calls are routed to my FS.
On Sun, Oct 4, 2015 at 10:15 PM, Michael Nielsen <mic.niel84@gmail.com <javascript:_e(%7B%7D,'cvml','mic.niel84@gmail.com');>> wrote:
I'll create some logs tomorrow.
Just to clarify: - Calls are routes from Twilio to my FS - My FS is a clean installation, 1.6.2 - I've used Twilio's guide for setting up gateways, inbound and outbound - Outbound calls are routed correctly - Inbound calls are as mentioned routes to my FS, but my Twilio-inbound doesn't seem to have anything to do with it, therefor, I'm not able to set any variables in incoming calls from Twilio so I can detect them in my public context and transfer them to my default context.
I don't want to route all calls in my public context to my default context, this would open a security issue. Only Twilio calls should be handled in such a manner. That's my challenge.
On Sunday, October 4, 2015, Sergey Safarov <s.safarov@gmail.com <javascript:_e(%7B%7D,'cvml','s.safarov@gmail.com');>> wrote:
Inbound call can be received 1) if twillio guys configure gateway to route incomes calls to you 2) or if FS provide information how to route call for you
After reading gateway config files, I has found that used second case "FS provides information how to route calls via registration mechanism".
Please: - configure clean FS host as described in twilio manuals; - enable siptrace; - enable debug log; - make incoming call; - attach debug log in respond to this message.
I try help you
On Sun, Oct 4, 2015 at 2:37 PM, Michael Nielsen <mic.niel84@gmail.com> wrote:
Still no luck. Any other ideas on how to "catch" the calls from the public context in FS? My goal is to transfer all calls from Twilio to my default context.
On Saturday, October 3, 2015, Michael Nielsen <mic.niel84@gmail.com> wrote:
Looking at their guide for secure setup: https://www.twilio.com/resources/images/docs/Twilio-Freeswitch.pdf they've added <param name="register" value="false"/> When I do this, registering doesn't fail (obviously), but inbound calls are still not registered as coming from twilio... They still land directly in the public context without the variables set correctly.
On Sat, Oct 3, 2015 at 11:58 AM, Michael Nielsen < mic.niel84@gmail.com> wrote:
> When adding the extension, I get the following - even though my > username and password etc. are correct as they work for the outbound > gateway...: > > twilio-inbound Failed Registration [908] > > On Sat, Oct 3, 2015 at 11:57 AM, Michael Nielsen < > mic.niel84@gmail.com> wrote: > >> I see. >> Does it matter that I don't have an extension called 1000 in my FS, >> nor in my Twilio account? >> >> On Fri, Oct 2, 2015 at 11:34 PM, Ahmed Habiba <ahabiba@gmail.com> >> wrote: >> >>> if you have a deep look at inbound gateway it is for receiving >>> calls from Twilio as you can see below, this line informing freeswitch >>> where to route inkling call. >>> >>> <param name="extension" value="1000"/> >>> >>> >>> >>> *From: *Michael Nielsen <mic.niel84@gmail.com> >>> *Date: *October 2, 2015 at 11:24:51 PM GMT+3 >>> *To: *FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org >>> > >>> *Subject: **Re: [Freeswitch-users] Freeswitch and twilio* >>> >>> >>> Outbound works fine. >>> >>> Without having the inbound gateway calls are still routed to my FS >>> to my public context from Twilio. >>> Adding the twilio-inbound doesn't seem to change anything...? >>> >>> >>> >>> On Friday, October 2, 2015, Brian West <brian@freeswitch.org> >>> wrote: >>> >>>> Well you'd send outbound calls out the outbound and the inbound >>>> one is just to register with twilio so they know where to send your inbound >>>> calls. Nothing more. >>>> >>>> On Fri, Oct 2, 2015 at 1:46 PM, Michael Nielsen < >>>> mic.niel84@gmail.com> wrote: >>>> >>>>> I'm trying to setup twilio as gateway following this guide: >>>>> >>>>> https://www.twilio.com/docs/sip-trunking/sample-configuration#freeswitch >>>>> >>>>> In their example of twiliotrunk.xml they have twilio-inbound and >>>>> twilio-outbound. >>>>> >>>>> What is the difference between the two gateways? I know their >>>>> names indicate inbound and outbound calling, but how can Freeswitch tell >>>>> the difference between them. Especially how can Freeswitch now to use >>>>> twilio-inbound for incoming calls from twilio and not just twilit-outbound >>>>> as the only difference is register-proxy and expire-seconds between the two? >>>>> >>>>> Make sense? >>>>> >>>>> >>>>> _________________________________________________________________________ >>>>> Professional FreeSWITCH Consulting Services: >>>>> consulting@freeswitch.org >>>>> http://www.freeswitchsolutions.com >>>>> >>>>> Official FreeSWITCH Sites >>>>> http://www.freeswitch.org >>>>> http://confluence.freeswitch.org >>>>> http://www.cluecon.com >>>>> >>>>> 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 >>>>> >>>> >>>> >>>> >>>> -- >>>> >>>> *Brian West* >>>> brian@freeswitch.org >>>> >>>> >>>> *Twitter: @FreeSWITCH , @briankwest* >>>> http://www.freeswitchbook.com >>>> http://www.freeswitchcookbook.com >>>> >>>> Got Bugs? Report them here <https://freeswitch.org/jira>! | >>>> Reddit: /r/freeswitch <https://www.reddit.com/r/freeswitch> >>>> >>>> *T:*+19184209001 | *F:*+19184209002 | *M:*+1918424WEST (9378) >>>> *iNUM:*+883 5100 1420 9001 | *ISN:*410*543 | *Skype:*briankwest >>>> >>> >>> >>> _______________________________________________ >>> 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 >>> >>> >>> >>> >>> _________________________________________________________________________ >>> Professional FreeSWITCH Consulting Services: >>> consulting@freeswitch.org >>> http://www.freeswitchsolutions.com >>> >>> Official FreeSWITCH Sites >>> http://www.freeswitch.org >>> http://confluence.freeswitch.org >>> http://www.cluecon.com >>> >>> 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 >>> >> >> >
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org <javascript:_e(%7B%7D,'cvml','consulting@freeswitch.org');> http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org <javascript:_e(%7B%7D,'cvml','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
If disable registration on inbound gateway, then is possible receive inbound call? On Mon, Oct 5, 2015, 22:45 Michael Nielsen <mic.niel84@gmail.com> wrote:
Twilio is just taking a sip address as termination address. In this case my domain which FS runs on. Apparently, Twilio is sending calls to the standard 5060 port - which then lands in my public context.
On Monday, October 5, 2015, Stanislav Sinyagin <ssinyagin@gmail.com> wrote:
in your pastebin, you seem to receive the call on your internal profile (port 5060): 11:18:58.277709 [DEBUG] sofia.c:9229 sofia/internal/+ 4432445867@sip.ie1.twilio.com receiving invite from 54.171.127.192:5060
so, what exactly is configured on both sides? The external profile is usually on the port 5080.
On Mon, Oct 5, 2015 at 6:26 PM, Michael Nielsen <mic.niel84@gmail.com> wrote:
Here's as log from an incoming call from Twilio: http://pastebin.com/n0de7jhv
My guess is the problem is with line 33: "Processing +4432445867 <+4432445867>->+44213395867 in context public" and it fails on line 40: "Regex (FAIL) [gateway_inbound] ${target_context}() =~ /^[a-z]/ break=on-false" due to the fact that there aren't set any ${target_context} variable.
I've added the Twilio inbound gateway as described in the Twilio guide, but adding it, removing it etc. doesn't change anything at all. To the Twilio-Inbound gateway I've added the variable ${target_context} according to this guide: https://github.com/voxserv/freeswitch_conf_minimal/blob/master/docs/tutorial...
So my guess is that the Twilio-Inbound gateway aren't being used - however - calls are routed to my FS.
On Sun, Oct 4, 2015 at 10:15 PM, Michael Nielsen <mic.niel84@gmail.com> wrote:
I'll create some logs tomorrow.
Just to clarify: - Calls are routes from Twilio to my FS - My FS is a clean installation, 1.6.2 - I've used Twilio's guide for setting up gateways, inbound and outbound - Outbound calls are routed correctly - Inbound calls are as mentioned routes to my FS, but my Twilio-inbound doesn't seem to have anything to do with it, therefor, I'm not able to set any variables in incoming calls from Twilio so I can detect them in my public context and transfer them to my default context.
I don't want to route all calls in my public context to my default context, this would open a security issue. Only Twilio calls should be handled in such a manner. That's my challenge.
On Sunday, October 4, 2015, Sergey Safarov <s.safarov@gmail.com> wrote:
Inbound call can be received 1) if twillio guys configure gateway to route incomes calls to you 2) or if FS provide information how to route call for you
After reading gateway config files, I has found that used second case "FS provides information how to route calls via registration mechanism".
Please: - configure clean FS host as described in twilio manuals; - enable siptrace; - enable debug log; - make incoming call; - attach debug log in respond to this message.
I try help you
On Sun, Oct 4, 2015 at 2:37 PM, Michael Nielsen <mic.niel84@gmail.com> wrote:
Still no luck. Any other ideas on how to "catch" the calls from the public context in FS? My goal is to transfer all calls from Twilio to my default context.
On Saturday, October 3, 2015, Michael Nielsen <mic.niel84@gmail.com> wrote:
> Looking at their guide for secure setup: > https://www.twilio.com/resources/images/docs/Twilio-Freeswitch.pdf > they've added <param name="register" value="false"/> > When I do this, registering doesn't fail (obviously), but inbound > calls are still not registered as coming from twilio... They still land > directly in the public context without the variables set correctly. > > On Sat, Oct 3, 2015 at 11:58 AM, Michael Nielsen < > mic.niel84@gmail.com> wrote: > >> When adding the extension, I get the following - even though my >> username and password etc. are correct as they work for the outbound >> gateway...: >> >> twilio-inbound Failed Registration [908] >> >> On Sat, Oct 3, 2015 at 11:57 AM, Michael Nielsen < >> mic.niel84@gmail.com> wrote: >> >>> I see. >>> Does it matter that I don't have an extension called 1000 in my >>> FS, nor in my Twilio account? >>> >>> On Fri, Oct 2, 2015 at 11:34 PM, Ahmed Habiba <ahabiba@gmail.com> >>> wrote: >>> >>>> if you have a deep look at inbound gateway it is for receiving >>>> calls from Twilio as you can see below, this line informing freeswitch >>>> where to route inkling call. >>>> >>>> <param name="extension" value="1000"/> >>>> >>>> >>>> >>>> *From: *Michael Nielsen <mic.niel84@gmail.com> >>>> *Date: *October 2, 2015 at 11:24:51 PM GMT+3 >>>> *To: *FreeSWITCH Users Help < >>>> freeswitch-users@lists.freeswitch.org> >>>> *Subject: **Re: [Freeswitch-users] Freeswitch and twilio* >>>> >>>> >>>> Outbound works fine. >>>> >>>> Without having the inbound gateway calls are still routed to my >>>> FS to my public context from Twilio. >>>> Adding the twilio-inbound doesn't seem to change anything...? >>>> >>>> >>>> >>>> On Friday, October 2, 2015, Brian West <brian@freeswitch.org> >>>> wrote: >>>> >>>>> Well you'd send outbound calls out the outbound and the inbound >>>>> one is just to register with twilio so they know where to send your inbound >>>>> calls. Nothing more. >>>>> >>>>> On Fri, Oct 2, 2015 at 1:46 PM, Michael Nielsen < >>>>> mic.niel84@gmail.com> wrote: >>>>> >>>>>> I'm trying to setup twilio as gateway following this guide: >>>>>> >>>>>> https://www.twilio.com/docs/sip-trunking/sample-configuration#freeswitch >>>>>> >>>>>> In their example of twiliotrunk.xml they have twilio-inbound >>>>>> and twilio-outbound. >>>>>> >>>>>> What is the difference between the two gateways? I know their >>>>>> names indicate inbound and outbound calling, but how can Freeswitch tell >>>>>> the difference between them. Especially how can Freeswitch now to use >>>>>> twilio-inbound for incoming calls from twilio and not just twilit-outbound >>>>>> as the only difference is register-proxy and expire-seconds between the two? >>>>>> >>>>>> Make sense? >>>>>> >>>>>> >>>>>> _________________________________________________________________________ >>>>>> Professional FreeSWITCH Consulting Services: >>>>>> consulting@freeswitch.org >>>>>> http://www.freeswitchsolutions.com >>>>>> >>>>>> Official FreeSWITCH Sites >>>>>> http://www.freeswitch.org >>>>>> http://confluence.freeswitch.org >>>>>> http://www.cluecon.com >>>>>> >>>>>> 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 >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> >>>>> *Brian West* >>>>> brian@freeswitch.org >>>>> >>>>> >>>>> *Twitter: @FreeSWITCH , @briankwest* >>>>> http://www.freeswitchbook.com >>>>> http://www.freeswitchcookbook.com >>>>> >>>>> Got Bugs? Report them here <https://freeswitch.org/jira>! | >>>>> Reddit: /r/freeswitch <https://www.reddit.com/r/freeswitch> >>>>> >>>>> *T:*+19184209001 | *F:*+19184209002 | *M:*+1918424WEST (9378) >>>>> *iNUM:*+883 5100 1420 9001 | *ISN:*410*543 | *Skype:*briankwest >>>>> >>>> >>>> >>>> _______________________________________________ >>>> 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 >>>> >>>> >>>> >>>> >>>> _________________________________________________________________________ >>>> Professional FreeSWITCH Consulting Services: >>>> consulting@freeswitch.org >>>> http://www.freeswitchsolutions.com >>>> >>>> Official FreeSWITCH Sites >>>> http://www.freeswitch.org >>>> http://confluence.freeswitch.org >>>> http://www.cluecon.com >>>> >>>> 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 >>>> >>> >>> >> >
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
If I disable registration on my twilio-inbound, it does not fail - however - incoming calls are still not "catched" by my twilio-inbound gateway profile. It still lands in the public context without any variables set. On Tue, Oct 6, 2015 at 5:57 AM, Sergey Safarov <s.safarov@gmail.com> wrote:
If disable registration on inbound gateway, then is possible receive inbound call?
On Mon, Oct 5, 2015, 22:45 Michael Nielsen <mic.niel84@gmail.com> wrote:
Twilio is just taking a sip address as termination address. In this case my domain which FS runs on. Apparently, Twilio is sending calls to the standard 5060 port - which then lands in my public context.
On Monday, October 5, 2015, Stanislav Sinyagin <ssinyagin@gmail.com> wrote:
in your pastebin, you seem to receive the call on your internal profile (port 5060): 11:18:58.277709 [DEBUG] sofia.c:9229 sofia/internal/+ 4432445867@sip.ie1.twilio.com receiving invite from 54.171.127.192:5060
so, what exactly is configured on both sides? The external profile is usually on the port 5080.
On Mon, Oct 5, 2015 at 6:26 PM, Michael Nielsen <mic.niel84@gmail.com> wrote:
Here's as log from an incoming call from Twilio: http://pastebin.com/n0de7jhv
My guess is the problem is with line 33: "Processing +4432445867 <+4432445867>->+44213395867 in context public" and it fails on line 40: "Regex (FAIL) [gateway_inbound] ${target_context}() =~ /^[a-z]/ break=on-false" due to the fact that there aren't set any ${target_context} variable.
I've added the Twilio inbound gateway as described in the Twilio guide, but adding it, removing it etc. doesn't change anything at all. To the Twilio-Inbound gateway I've added the variable ${target_context} according to this guide: https://github.com/voxserv/freeswitch_conf_minimal/blob/master/docs/tutorial...
So my guess is that the Twilio-Inbound gateway aren't being used - however - calls are routed to my FS.
On Sun, Oct 4, 2015 at 10:15 PM, Michael Nielsen <mic.niel84@gmail.com> wrote:
I'll create some logs tomorrow.
Just to clarify: - Calls are routes from Twilio to my FS - My FS is a clean installation, 1.6.2 - I've used Twilio's guide for setting up gateways, inbound and outbound - Outbound calls are routed correctly - Inbound calls are as mentioned routes to my FS, but my Twilio-inbound doesn't seem to have anything to do with it, therefor, I'm not able to set any variables in incoming calls from Twilio so I can detect them in my public context and transfer them to my default context.
I don't want to route all calls in my public context to my default context, this would open a security issue. Only Twilio calls should be handled in such a manner. That's my challenge.
On Sunday, October 4, 2015, Sergey Safarov <s.safarov@gmail.com> wrote:
Inbound call can be received 1) if twillio guys configure gateway to route incomes calls to you 2) or if FS provide information how to route call for you
After reading gateway config files, I has found that used second case "FS provides information how to route calls via registration mechanism".
Please: - configure clean FS host as described in twilio manuals; - enable siptrace; - enable debug log; - make incoming call; - attach debug log in respond to this message.
I try help you
On Sun, Oct 4, 2015 at 2:37 PM, Michael Nielsen <mic.niel84@gmail.com > wrote:
> Still no luck. > Any other ideas on how to "catch" the calls from the public context > in FS? > My goal is to transfer all calls from Twilio to my default context. > > > On Saturday, October 3, 2015, Michael Nielsen <mic.niel84@gmail.com> > wrote: > >> Looking at their guide for secure setup: >> https://www.twilio.com/resources/images/docs/Twilio-Freeswitch.pdf >> they've added <param name="register" value="false"/> >> When I do this, registering doesn't fail (obviously), but inbound >> calls are still not registered as coming from twilio... They still land >> directly in the public context without the variables set correctly. >> >> On Sat, Oct 3, 2015 at 11:58 AM, Michael Nielsen < >> mic.niel84@gmail.com> wrote: >> >>> When adding the extension, I get the following - even though my >>> username and password etc. are correct as they work for the outbound >>> gateway...: >>> >>> twilio-inbound Failed Registration [908] >>> >>> On Sat, Oct 3, 2015 at 11:57 AM, Michael Nielsen < >>> mic.niel84@gmail.com> wrote: >>> >>>> I see. >>>> Does it matter that I don't have an extension called 1000 in my >>>> FS, nor in my Twilio account? >>>> >>>> On Fri, Oct 2, 2015 at 11:34 PM, Ahmed Habiba <ahabiba@gmail.com> >>>> wrote: >>>> >>>>> if you have a deep look at inbound gateway it is for receiving >>>>> calls from Twilio as you can see below, this line informing freeswitch >>>>> where to route inkling call. >>>>> >>>>> <param name="extension" value="1000"/> >>>>> >>>>> >>>>> >>>>> *From: *Michael Nielsen <mic.niel84@gmail.com> >>>>> *Date: *October 2, 2015 at 11:24:51 PM GMT+3 >>>>> *To: *FreeSWITCH Users Help < >>>>> freeswitch-users@lists.freeswitch.org> >>>>> *Subject: **Re: [Freeswitch-users] Freeswitch and twilio* >>>>> >>>>> >>>>> Outbound works fine. >>>>> >>>>> Without having the inbound gateway calls are still routed to my >>>>> FS to my public context from Twilio. >>>>> Adding the twilio-inbound doesn't seem to change anything...? >>>>> >>>>> >>>>> >>>>> On Friday, October 2, 2015, Brian West <brian@freeswitch.org> >>>>> wrote: >>>>> >>>>>> Well you'd send outbound calls out the outbound and the >>>>>> inbound one is just to register with twilio so they know where to send your >>>>>> inbound calls. Nothing more. >>>>>> >>>>>> On Fri, Oct 2, 2015 at 1:46 PM, Michael Nielsen < >>>>>> mic.niel84@gmail.com> wrote: >>>>>> >>>>>>> I'm trying to setup twilio as gateway following this guide: >>>>>>> >>>>>>> https://www.twilio.com/docs/sip-trunking/sample-configuration#freeswitch >>>>>>> >>>>>>> In their example of twiliotrunk.xml they have twilio-inbound >>>>>>> and twilio-outbound. >>>>>>> >>>>>>> What is the difference between the two gateways? I know their >>>>>>> names indicate inbound and outbound calling, but how can Freeswitch tell >>>>>>> the difference between them. Especially how can Freeswitch now to use >>>>>>> twilio-inbound for incoming calls from twilio and not just twilit-outbound >>>>>>> as the only difference is register-proxy and expire-seconds between the two? >>>>>>> >>>>>>> Make sense? >>>>>>> >>>>>>> >>>>>>> _________________________________________________________________________ >>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>> consulting@freeswitch.org >>>>>>> http://www.freeswitchsolutions.com >>>>>>> >>>>>>> Official FreeSWITCH Sites >>>>>>> http://www.freeswitch.org >>>>>>> http://confluence.freeswitch.org >>>>>>> http://www.cluecon.com >>>>>>> >>>>>>> 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 >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> >>>>>> *Brian West* >>>>>> brian@freeswitch.org >>>>>> >>>>>> >>>>>> *Twitter: @FreeSWITCH , @briankwest* >>>>>> http://www.freeswitchbook.com >>>>>> http://www.freeswitchcookbook.com >>>>>> >>>>>> Got Bugs? Report them here <https://freeswitch.org/jira>! | >>>>>> Reddit: /r/freeswitch <https://www.reddit.com/r/freeswitch> >>>>>> >>>>>> *T:*+19184209001 | *F:*+19184209002 | *M:*+1918424WEST (9378) >>>>>> *iNUM:*+883 5100 1420 9001 | *ISN:*410*543 | *Skype:*briankwest >>>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> 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 >>>>> >>>>> >>>>> >>>>> >>>>> _________________________________________________________________________ >>>>> Professional FreeSWITCH Consulting Services: >>>>> consulting@freeswitch.org >>>>> http://www.freeswitchsolutions.com >>>>> >>>>> Official FreeSWITCH Sites >>>>> http://www.freeswitch.org >>>>> http://confluence.freeswitch.org >>>>> http://www.cluecon.com >>>>> >>>>> 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 >>>>> >>>> >>>> >>> >> > > _________________________________________________________________________ > Professional FreeSWITCH Consulting Services: > consulting@freeswitch.org > http://www.freeswitchsolutions.com > > Official FreeSWITCH Sites > http://www.freeswitch.org > http://confluence.freeswitch.org > http://www.cluecon.com > > 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 >
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
but what exactly is configured on twilio side? I guess it should be configurable where it should send calls On Tue, Oct 6, 2015 at 9:27 AM, Michael Nielsen <mic.niel84@gmail.com> wrote:
If I disable registration on my twilio-inbound, it does not fail - however - incoming calls are still not "catched" by my twilio-inbound gateway profile. It still lands in the public context without any variables set.
On Tue, Oct 6, 2015 at 5:57 AM, Sergey Safarov <s.safarov@gmail.com> wrote:
If disable registration on inbound gateway, then is possible receive inbound call?
On Mon, Oct 5, 2015, 22:45 Michael Nielsen <mic.niel84@gmail.com> wrote:
Twilio is just taking a sip address as termination address. In this case my domain which FS runs on. Apparently, Twilio is sending calls to the standard 5060 port - which then lands in my public context.
On Monday, October 5, 2015, Stanislav Sinyagin <ssinyagin@gmail.com> wrote:
in your pastebin, you seem to receive the call on your internal profile (port 5060): 11:18:58.277709 [DEBUG] sofia.c:9229 sofia/internal/+ 4432445867@sip.ie1.twilio.com receiving invite from 54.171.127.192:5060
so, what exactly is configured on both sides? The external profile is usually on the port 5080.
On Mon, Oct 5, 2015 at 6:26 PM, Michael Nielsen <mic.niel84@gmail.com> wrote:
Here's as log from an incoming call from Twilio: http://pastebin.com/n0de7jhv
My guess is the problem is with line 33: "Processing +4432445867 <+4432445867>->+44213395867 in context public" and it fails on line 40: "Regex (FAIL) [gateway_inbound] ${target_context}() =~ /^[a-z]/ break=on-false" due to the fact that there aren't set any ${target_context} variable.
I've added the Twilio inbound gateway as described in the Twilio guide, but adding it, removing it etc. doesn't change anything at all. To the Twilio-Inbound gateway I've added the variable ${target_context} according to this guide: https://github.com/voxserv/freeswitch_conf_minimal/blob/master/docs/tutorial...
So my guess is that the Twilio-Inbound gateway aren't being used - however - calls are routed to my FS.
On Sun, Oct 4, 2015 at 10:15 PM, Michael Nielsen <mic.niel84@gmail.com
wrote:
I'll create some logs tomorrow.
Just to clarify: - Calls are routes from Twilio to my FS - My FS is a clean installation, 1.6.2 - I've used Twilio's guide for setting up gateways, inbound and outbound - Outbound calls are routed correctly - Inbound calls are as mentioned routes to my FS, but my Twilio-inbound doesn't seem to have anything to do with it, therefor, I'm not able to set any variables in incoming calls from Twilio so I can detect them in my public context and transfer them to my default context.
I don't want to route all calls in my public context to my default context, this would open a security issue. Only Twilio calls should be handled in such a manner. That's my challenge.
On Sunday, October 4, 2015, Sergey Safarov <s.safarov@gmail.com> wrote:
> Inbound call can be received > 1) if twillio guys configure gateway to route incomes calls to you > 2) or if FS provide information how to route call for you > > After reading gateway config files, I has found that used second > case "FS provides information how to route calls via registration > mechanism". > > Please: > - configure clean FS host as described in twilio manuals; > - enable siptrace; > - enable debug log; > - make incoming call; > - attach debug log in respond to this message. > > I try help you > > > On Sun, Oct 4, 2015 at 2:37 PM, Michael Nielsen < > mic.niel84@gmail.com> wrote: > >> Still no luck. >> Any other ideas on how to "catch" the calls from the public context >> in FS? >> My goal is to transfer all calls from Twilio to my default context. >> >> >> On Saturday, October 3, 2015, Michael Nielsen <mic.niel84@gmail.com> >> wrote: >> >>> Looking at their guide for secure setup: >>> https://www.twilio.com/resources/images/docs/Twilio-Freeswitch.pdf >>> they've added <param name="register" value="false"/> >>> When I do this, registering doesn't fail (obviously), but inbound >>> calls are still not registered as coming from twilio... They still land >>> directly in the public context without the variables set correctly. >>> >>> On Sat, Oct 3, 2015 at 11:58 AM, Michael Nielsen < >>> mic.niel84@gmail.com> wrote: >>> >>>> When adding the extension, I get the following - even though my >>>> username and password etc. are correct as they work for the outbound >>>> gateway...: >>>> >>>> twilio-inbound Failed Registration [908] >>>> >>>> On Sat, Oct 3, 2015 at 11:57 AM, Michael Nielsen < >>>> mic.niel84@gmail.com> wrote: >>>> >>>>> I see. >>>>> Does it matter that I don't have an extension called 1000 in my >>>>> FS, nor in my Twilio account? >>>>> >>>>> On Fri, Oct 2, 2015 at 11:34 PM, Ahmed Habiba <ahabiba@gmail.com >>>>> > wrote: >>>>> >>>>>> if you have a deep look at inbound gateway it is for receiving >>>>>> calls from Twilio as you can see below, this line informing freeswitch >>>>>> where to route inkling call. >>>>>> >>>>>> <param name="extension" value="1000"/> >>>>>> >>>>>> >>>>>> >>>>>> *From: *Michael Nielsen <mic.niel84@gmail.com> >>>>>> *Date: *October 2, 2015 at 11:24:51 PM GMT+3 >>>>>> *To: *FreeSWITCH Users Help < >>>>>> freeswitch-users@lists.freeswitch.org> >>>>>> *Subject: **Re: [Freeswitch-users] Freeswitch and twilio* >>>>>> >>>>>> >>>>>> Outbound works fine. >>>>>> >>>>>> Without having the inbound gateway calls are still routed to my >>>>>> FS to my public context from Twilio. >>>>>> Adding the twilio-inbound doesn't seem to change anything...? >>>>>> >>>>>> >>>>>> >>>>>> On Friday, October 2, 2015, Brian West <brian@freeswitch.org> >>>>>> wrote: >>>>>> >>>>>>> Well you'd send outbound calls out the outbound and the >>>>>>> inbound one is just to register with twilio so they know where to send your >>>>>>> inbound calls. Nothing more. >>>>>>> >>>>>>> On Fri, Oct 2, 2015 at 1:46 PM, Michael Nielsen < >>>>>>> mic.niel84@gmail.com> wrote: >>>>>>> >>>>>>>> I'm trying to setup twilio as gateway following this guide: >>>>>>>> >>>>>>>> https://www.twilio.com/docs/sip-trunking/sample-configuration#freeswitch >>>>>>>> >>>>>>>> In their example of twiliotrunk.xml they have twilio-inbound >>>>>>>> and twilio-outbound. >>>>>>>> >>>>>>>> What is the difference between the two gateways? I know their >>>>>>>> names indicate inbound and outbound calling, but how can Freeswitch tell >>>>>>>> the difference between them. Especially how can Freeswitch now to use >>>>>>>> twilio-inbound for incoming calls from twilio and not just twilit-outbound >>>>>>>> as the only difference is register-proxy and expire-seconds between the two? >>>>>>>> >>>>>>>> Make sense? >>>>>>>> >>>>>>>> >>>>>>>> _________________________________________________________________________ >>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>> consulting@freeswitch.org >>>>>>>> http://www.freeswitchsolutions.com >>>>>>>> >>>>>>>> Official FreeSWITCH Sites >>>>>>>> http://www.freeswitch.org >>>>>>>> http://confluence.freeswitch.org >>>>>>>> http://www.cluecon.com >>>>>>>> >>>>>>>> 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 >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> >>>>>>> *Brian West* >>>>>>> brian@freeswitch.org >>>>>>> >>>>>>> >>>>>>> *Twitter: @FreeSWITCH , @briankwest* >>>>>>> http://www.freeswitchbook.com >>>>>>> http://www.freeswitchcookbook.com >>>>>>> >>>>>>> Got Bugs? Report them here <https://freeswitch.org/jira>! | >>>>>>> Reddit: /r/freeswitch <https://www.reddit.com/r/freeswitch> >>>>>>> >>>>>>> *T:*+19184209001 | *F:*+19184209002 | *M:*+1918424WEST (9378) >>>>>>> *iNUM:*+883 5100 1420 9001 | *ISN:*410*543 | *Skype:* >>>>>>> briankwest >>>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> 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 >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> _________________________________________________________________________ >>>>>> Professional FreeSWITCH Consulting Services: >>>>>> consulting@freeswitch.org >>>>>> http://www.freeswitchsolutions.com >>>>>> >>>>>> Official FreeSWITCH Sites >>>>>> http://www.freeswitch.org >>>>>> http://confluence.freeswitch.org >>>>>> http://www.cluecon.com >>>>>> >>>>>> 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 >>>>>> >>>>> >>>>> >>>> >>> >> >> _________________________________________________________________________ >> Professional FreeSWITCH Consulting Services: >> consulting@freeswitch.org >> http://www.freeswitchsolutions.com >> >> Official FreeSWITCH Sites >> http://www.freeswitch.org >> http://confluence.freeswitch.org >> http://www.cluecon.com >> >> 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 >> > >
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
I can only give Twilio an url. But I am able to change the default Twilio uses, as an example to 5080. Would that trigger the external gateway perhaps? On Tuesday, October 6, 2015, Stanislav Sinyagin <ssinyagin@gmail.com> wrote:
but what exactly is configured on twilio side? I guess it should be configurable where it should send calls
On Tue, Oct 6, 2015 at 9:27 AM, Michael Nielsen <mic.niel84@gmail.com <javascript:_e(%7B%7D,'cvml','mic.niel84@gmail.com');>> wrote:
If I disable registration on my twilio-inbound, it does not fail - however - incoming calls are still not "catched" by my twilio-inbound gateway profile. It still lands in the public context without any variables set.
On Tue, Oct 6, 2015 at 5:57 AM, Sergey Safarov <s.safarov@gmail.com <javascript:_e(%7B%7D,'cvml','s.safarov@gmail.com');>> wrote:
If disable registration on inbound gateway, then is possible receive inbound call?
On Mon, Oct 5, 2015, 22:45 Michael Nielsen <mic.niel84@gmail.com <javascript:_e(%7B%7D,'cvml','mic.niel84@gmail.com');>> wrote:
Twilio is just taking a sip address as termination address. In this case my domain which FS runs on. Apparently, Twilio is sending calls to the standard 5060 port - which then lands in my public context.
On Monday, October 5, 2015, Stanislav Sinyagin <ssinyagin@gmail.com <javascript:_e(%7B%7D,'cvml','ssinyagin@gmail.com');>> wrote:
in your pastebin, you seem to receive the call on your internal profile (port 5060): 11:18:58.277709 [DEBUG] sofia.c:9229 sofia/internal/+ 4432445867@sip.ie1.twilio.com receiving invite from 54.171.127.192:5060
so, what exactly is configured on both sides? The external profile is usually on the port 5080.
On Mon, Oct 5, 2015 at 6:26 PM, Michael Nielsen <mic.niel84@gmail.com> wrote:
Here's as log from an incoming call from Twilio: http://pastebin.com/n0de7jhv
My guess is the problem is with line 33: "Processing +4432445867 <+4432445867>->+44213395867 in context public" and it fails on line 40: "Regex (FAIL) [gateway_inbound] ${target_context}() =~ /^[a-z]/ break=on-false" due to the fact that there aren't set any ${target_context} variable.
I've added the Twilio inbound gateway as described in the Twilio guide, but adding it, removing it etc. doesn't change anything at all. To the Twilio-Inbound gateway I've added the variable ${target_context} according to this guide: https://github.com/voxserv/freeswitch_conf_minimal/blob/master/docs/tutorial...
So my guess is that the Twilio-Inbound gateway aren't being used - however - calls are routed to my FS.
On Sun, Oct 4, 2015 at 10:15 PM, Michael Nielsen < mic.niel84@gmail.com> wrote:
> I'll create some logs tomorrow. > > Just to clarify: > - Calls are routes from Twilio to my FS > - My FS is a clean installation, 1.6.2 > - I've used Twilio's guide for setting up gateways, inbound and > outbound > - Outbound calls are routed correctly > - Inbound calls are as mentioned routes to my FS, but my > Twilio-inbound doesn't seem to have anything to do with it, therefor, I'm > not able to set any variables in incoming calls from Twilio so I can detect > them in my public context and transfer them to my default context. > > I don't want to route all calls in my public context to my default > context, this would open a security issue. Only Twilio calls should be > handled in such a manner. > That's my challenge. > > > On Sunday, October 4, 2015, Sergey Safarov <s.safarov@gmail.com> > wrote: > >> Inbound call can be received >> 1) if twillio guys configure gateway to route incomes calls to you >> 2) or if FS provide information how to route call for you >> >> After reading gateway config files, I has found that used second >> case "FS provides information how to route calls via registration >> mechanism". >> >> Please: >> - configure clean FS host as described in twilio manuals; >> - enable siptrace; >> - enable debug log; >> - make incoming call; >> - attach debug log in respond to this message. >> >> I try help you >> >> >> On Sun, Oct 4, 2015 at 2:37 PM, Michael Nielsen < >> mic.niel84@gmail.com> wrote: >> >>> Still no luck. >>> Any other ideas on how to "catch" the calls from the public >>> context in FS? >>> My goal is to transfer all calls from Twilio to my default >>> context. >>> >>> >>> On Saturday, October 3, 2015, Michael Nielsen < >>> mic.niel84@gmail.com> wrote: >>> >>>> Looking at their guide for secure setup: >>>> https://www.twilio.com/resources/images/docs/Twilio-Freeswitch.pdf >>>> they've added <param name="register" value="false"/> >>>> When I do this, registering doesn't fail (obviously), but inbound >>>> calls are still not registered as coming from twilio... They still land >>>> directly in the public context without the variables set correctly. >>>> >>>> On Sat, Oct 3, 2015 at 11:58 AM, Michael Nielsen < >>>> mic.niel84@gmail.com> wrote: >>>> >>>>> When adding the extension, I get the following - even though my >>>>> username and password etc. are correct as they work for the outbound >>>>> gateway...: >>>>> >>>>> twilio-inbound Failed Registration [908] >>>>> >>>>> On Sat, Oct 3, 2015 at 11:57 AM, Michael Nielsen < >>>>> mic.niel84@gmail.com> wrote: >>>>> >>>>>> I see. >>>>>> Does it matter that I don't have an extension called 1000 in my >>>>>> FS, nor in my Twilio account? >>>>>> >>>>>> On Fri, Oct 2, 2015 at 11:34 PM, Ahmed Habiba < >>>>>> ahabiba@gmail.com> wrote: >>>>>> >>>>>>> if you have a deep look at inbound gateway it is for >>>>>>> receiving calls from Twilio as you can see below, this line informing >>>>>>> freeswitch where to route inkling call. >>>>>>> >>>>>>> <param name="extension" value="1000"/> >>>>>>> >>>>>>> >>>>>>> >>>>>>> *From: *Michael Nielsen <mic.niel84@gmail.com> >>>>>>> *Date: *October 2, 2015 at 11:24:51 PM GMT+3 >>>>>>> *To: *FreeSWITCH Users Help < >>>>>>> freeswitch-users@lists.freeswitch.org> >>>>>>> *Subject: **Re: [Freeswitch-users] Freeswitch and twilio* >>>>>>> >>>>>>> >>>>>>> Outbound works fine. >>>>>>> >>>>>>> Without having the inbound gateway calls are still routed to >>>>>>> my FS to my public context from Twilio. >>>>>>> Adding the twilio-inbound doesn't seem to change anything...? >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Friday, October 2, 2015, Brian West <brian@freeswitch.org> >>>>>>> wrote: >>>>>>> >>>>>>>> Well you'd send outbound calls out the outbound and the >>>>>>>> inbound one is just to register with twilio so they know where to send your >>>>>>>> inbound calls. Nothing more. >>>>>>>> >>>>>>>> On Fri, Oct 2, 2015 at 1:46 PM, Michael Nielsen < >>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>> >>>>>>>>> I'm trying to setup twilio as gateway following this guide: >>>>>>>>> >>>>>>>>> https://www.twilio.com/docs/sip-trunking/sample-configuration#freeswitch >>>>>>>>> >>>>>>>>> In their example of twiliotrunk.xml they have twilio-inbound >>>>>>>>> and twilio-outbound. >>>>>>>>> >>>>>>>>> What is the difference between the two gateways? I know >>>>>>>>> their names indicate inbound and outbound calling, but how can Freeswitch >>>>>>>>> tell the difference between them. Especially how can Freeswitch now to use >>>>>>>>> twilio-inbound for incoming calls from twilio and not just twilit-outbound >>>>>>>>> as the only difference is register-proxy and expire-seconds between the two? >>>>>>>>> >>>>>>>>> Make sense? >>>>>>>>> >>>>>>>>> >>>>>>>>> _________________________________________________________________________ >>>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>>> consulting@freeswitch.org >>>>>>>>> http://www.freeswitchsolutions.com >>>>>>>>> >>>>>>>>> Official FreeSWITCH Sites >>>>>>>>> http://www.freeswitch.org >>>>>>>>> http://confluence.freeswitch.org >>>>>>>>> http://www.cluecon.com >>>>>>>>> >>>>>>>>> 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 >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> >>>>>>>> *Brian West* >>>>>>>> brian@freeswitch.org >>>>>>>> >>>>>>>> >>>>>>>> *Twitter: @FreeSWITCH , @briankwest* >>>>>>>> http://www.freeswitchbook.com >>>>>>>> http://www.freeswitchcookbook.com >>>>>>>> >>>>>>>> Got Bugs? Report them here <https://freeswitch.org/jira>! | >>>>>>>> Reddit: /r/freeswitch <https://www.reddit.com/r/freeswitch> >>>>>>>> >>>>>>>> *T:*+19184209001 | *F:*+19184209002 | *M:*+1918424WEST (9378) >>>>>>>> *iNUM:*+883 5100 1420 9001 | *ISN:*410*543 | *Skype:* >>>>>>>> briankwest >>>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> 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 >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> _________________________________________________________________________ >>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>> consulting@freeswitch.org >>>>>>> http://www.freeswitchsolutions.com >>>>>>> >>>>>>> Official FreeSWITCH Sites >>>>>>> http://www.freeswitch.org >>>>>>> http://confluence.freeswitch.org >>>>>>> http://www.cluecon.com >>>>>>> >>>>>>> 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 >>>>>>> >>>>>> >>>>>> >>>>> >>>> >>> >>> _________________________________________________________________________ >>> Professional FreeSWITCH Consulting Services: >>> consulting@freeswitch.org >>> http://www.freeswitchsolutions.com >>> >>> Official FreeSWITCH Sites >>> http://www.freeswitch.org >>> http://confluence.freeswitch.org >>> http://www.cluecon.com >>> >>> 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 >>> >> >>
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org <javascript:_e(%7B%7D,'cvml','consulting@freeswitch.org');> http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org <javascript:_e(%7B%7D,'cvml','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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org <javascript:_e(%7B%7D,'cvml','consulting@freeswitch.org');> http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org <javascript:_e(%7B%7D,'cvml','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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org <javascript:_e(%7B%7D,'cvml','consulting@freeswitch.org');> http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org <javascript:_e(%7B%7D,'cvml','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
Well, if your URL points to 5060, then yes, you need to change it to 5080 :-)) On Tue, Oct 6, 2015 at 9:47 AM, Michael Nielsen <mic.niel84@gmail.com> wrote:
I can only give Twilio an url. But I am able to change the default Twilio uses, as an example to 5080. Would that trigger the external gateway perhaps?
On Tuesday, October 6, 2015, Stanislav Sinyagin <ssinyagin@gmail.com> wrote:
but what exactly is configured on twilio side? I guess it should be configurable where it should send calls
On Tue, Oct 6, 2015 at 9:27 AM, Michael Nielsen <mic.niel84@gmail.com> wrote:
If I disable registration on my twilio-inbound, it does not fail - however - incoming calls are still not "catched" by my twilio-inbound gateway profile. It still lands in the public context without any variables set.
On Tue, Oct 6, 2015 at 5:57 AM, Sergey Safarov <s.safarov@gmail.com> wrote:
If disable registration on inbound gateway, then is possible receive inbound call?
On Mon, Oct 5, 2015, 22:45 Michael Nielsen <mic.niel84@gmail.com> wrote:
Twilio is just taking a sip address as termination address. In this case my domain which FS runs on. Apparently, Twilio is sending calls to the standard 5060 port - which then lands in my public context.
On Monday, October 5, 2015, Stanislav Sinyagin <ssinyagin@gmail.com> wrote:
in your pastebin, you seem to receive the call on your internal profile (port 5060): 11:18:58.277709 [DEBUG] sofia.c:9229 sofia/internal/+ 4432445867@sip.ie1.twilio.com receiving invite from 54.171.127.192:5060
so, what exactly is configured on both sides? The external profile is usually on the port 5080.
On Mon, Oct 5, 2015 at 6:26 PM, Michael Nielsen <mic.niel84@gmail.com > wrote:
> Here's as log from an incoming call from Twilio: > http://pastebin.com/n0de7jhv > > My guess is the problem is with line 33: "Processing +4432445867 > <+4432445867>->+44213395867 in context public" > and it fails on line 40: "Regex (FAIL) [gateway_inbound] > ${target_context}() =~ /^[a-z]/ break=on-false" > due to the fact that there aren't set any ${target_context} variable. > > I've added the Twilio inbound gateway as described in the Twilio > guide, but adding it, removing it etc. doesn't change anything at all. > To the Twilio-Inbound gateway I've added the variable > ${target_context} according to this guide: > https://github.com/voxserv/freeswitch_conf_minimal/blob/master/docs/tutorial... > > So my guess is that the Twilio-Inbound gateway aren't being used - > however - calls are routed to my FS. > > On Sun, Oct 4, 2015 at 10:15 PM, Michael Nielsen < > mic.niel84@gmail.com> wrote: > >> I'll create some logs tomorrow. >> >> Just to clarify: >> - Calls are routes from Twilio to my FS >> - My FS is a clean installation, 1.6.2 >> - I've used Twilio's guide for setting up gateways, inbound and >> outbound >> - Outbound calls are routed correctly >> - Inbound calls are as mentioned routes to my FS, but my >> Twilio-inbound doesn't seem to have anything to do with it, therefor, I'm >> not able to set any variables in incoming calls from Twilio so I can detect >> them in my public context and transfer them to my default context. >> >> I don't want to route all calls in my public context to my default >> context, this would open a security issue. Only Twilio calls should be >> handled in such a manner. >> That's my challenge. >> >> >> On Sunday, October 4, 2015, Sergey Safarov <s.safarov@gmail.com> >> wrote: >> >>> Inbound call can be received >>> 1) if twillio guys configure gateway to route incomes calls to you >>> 2) or if FS provide information how to route call for you >>> >>> After reading gateway config files, I has found that used second >>> case "FS provides information how to route calls via registration >>> mechanism". >>> >>> Please: >>> - configure clean FS host as described in twilio manuals; >>> - enable siptrace; >>> - enable debug log; >>> - make incoming call; >>> - attach debug log in respond to this message. >>> >>> I try help you >>> >>> >>> On Sun, Oct 4, 2015 at 2:37 PM, Michael Nielsen < >>> mic.niel84@gmail.com> wrote: >>> >>>> Still no luck. >>>> Any other ideas on how to "catch" the calls from the public >>>> context in FS? >>>> My goal is to transfer all calls from Twilio to my default >>>> context. >>>> >>>> >>>> On Saturday, October 3, 2015, Michael Nielsen < >>>> mic.niel84@gmail.com> wrote: >>>> >>>>> Looking at their guide for secure setup: >>>>> https://www.twilio.com/resources/images/docs/Twilio-Freeswitch.pdf >>>>> they've added <param name="register" value="false"/> >>>>> When I do this, registering doesn't fail (obviously), but >>>>> inbound calls are still not registered as coming from twilio... They still >>>>> land directly in the public context without the variables set correctly. >>>>> >>>>> On Sat, Oct 3, 2015 at 11:58 AM, Michael Nielsen < >>>>> mic.niel84@gmail.com> wrote: >>>>> >>>>>> When adding the extension, I get the following - even though my >>>>>> username and password etc. are correct as they work for the outbound >>>>>> gateway...: >>>>>> >>>>>> twilio-inbound Failed Registration [908] >>>>>> >>>>>> On Sat, Oct 3, 2015 at 11:57 AM, Michael Nielsen < >>>>>> mic.niel84@gmail.com> wrote: >>>>>> >>>>>>> I see. >>>>>>> Does it matter that I don't have an extension called 1000 in >>>>>>> my FS, nor in my Twilio account? >>>>>>> >>>>>>> On Fri, Oct 2, 2015 at 11:34 PM, Ahmed Habiba < >>>>>>> ahabiba@gmail.com> wrote: >>>>>>> >>>>>>>> if you have a deep look at inbound gateway it is for >>>>>>>> receiving calls from Twilio as you can see below, this line informing >>>>>>>> freeswitch where to route inkling call. >>>>>>>> >>>>>>>> <param name="extension" value="1000"/> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> *From: *Michael Nielsen <mic.niel84@gmail.com> >>>>>>>> *Date: *October 2, 2015 at 11:24:51 PM GMT+3 >>>>>>>> *To: *FreeSWITCH Users Help < >>>>>>>> freeswitch-users@lists.freeswitch.org> >>>>>>>> *Subject: **Re: [Freeswitch-users] Freeswitch and twilio* >>>>>>>> >>>>>>>> >>>>>>>> Outbound works fine. >>>>>>>> >>>>>>>> Without having the inbound gateway calls are still routed to >>>>>>>> my FS to my public context from Twilio. >>>>>>>> Adding the twilio-inbound doesn't seem to change anything...? >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Friday, October 2, 2015, Brian West <brian@freeswitch.org> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Well you'd send outbound calls out the outbound and the >>>>>>>>> inbound one is just to register with twilio so they know where to send your >>>>>>>>> inbound calls. Nothing more. >>>>>>>>> >>>>>>>>> On Fri, Oct 2, 2015 at 1:46 PM, Michael Nielsen < >>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>> >>>>>>>>>> I'm trying to setup twilio as gateway following this guide: >>>>>>>>>> >>>>>>>>>> https://www.twilio.com/docs/sip-trunking/sample-configuration#freeswitch >>>>>>>>>> >>>>>>>>>> In their example of twiliotrunk.xml they have >>>>>>>>>> twilio-inbound and twilio-outbound. >>>>>>>>>> >>>>>>>>>> What is the difference between the two gateways? I know >>>>>>>>>> their names indicate inbound and outbound calling, but how can Freeswitch >>>>>>>>>> tell the difference between them. Especially how can Freeswitch now to use >>>>>>>>>> twilio-inbound for incoming calls from twilio and not just twilit-outbound >>>>>>>>>> as the only difference is register-proxy and expire-seconds between the two? >>>>>>>>>> >>>>>>>>>> Make sense? >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> _________________________________________________________________________ >>>>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>>>> consulting@freeswitch.org >>>>>>>>>> http://www.freeswitchsolutions.com >>>>>>>>>> >>>>>>>>>> Official FreeSWITCH Sites >>>>>>>>>> http://www.freeswitch.org >>>>>>>>>> http://confluence.freeswitch.org >>>>>>>>>> http://www.cluecon.com >>>>>>>>>> >>>>>>>>>> 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 >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> >>>>>>>>> *Brian West* >>>>>>>>> brian@freeswitch.org >>>>>>>>> >>>>>>>>> >>>>>>>>> *Twitter: @FreeSWITCH , @briankwest* >>>>>>>>> http://www.freeswitchbook.com >>>>>>>>> http://www.freeswitchcookbook.com >>>>>>>>> >>>>>>>>> Got Bugs? Report them here <https://freeswitch.org/jira>! | >>>>>>>>> Reddit: /r/freeswitch <https://www.reddit.com/r/freeswitch> >>>>>>>>> >>>>>>>>> *T:*+19184209001 | *F:*+19184209002 | *M:*+1918424WEST >>>>>>>>> (9378) >>>>>>>>> *iNUM:*+883 5100 1420 9001 | *ISN:*410*543 | *Skype:* >>>>>>>>> briankwest >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> 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 >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> _________________________________________________________________________ >>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>> consulting@freeswitch.org >>>>>>>> http://www.freeswitchsolutions.com >>>>>>>> >>>>>>>> Official FreeSWITCH Sites >>>>>>>> http://www.freeswitch.org >>>>>>>> http://confluence.freeswitch.org >>>>>>>> http://www.cluecon.com >>>>>>>> >>>>>>>> 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 >>>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>>> _________________________________________________________________________ >>>> Professional FreeSWITCH Consulting Services: >>>> consulting@freeswitch.org >>>> http://www.freeswitchsolutions.com >>>> >>>> Official FreeSWITCH Sites >>>> http://www.freeswitch.org >>>> http://confluence.freeswitch.org >>>> http://www.cluecon.com >>>> >>>> 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 >>>> >>> >>> > > > _________________________________________________________________________ > Professional FreeSWITCH Consulting Services: > consulting@freeswitch.org > http://www.freeswitchsolutions.com > > Official FreeSWITCH Sites > http://www.freeswitch.org > http://confluence.freeswitch.org > http://www.cluecon.com > > 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 >
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
Think it may be related to ACL. I will test FS config in short time On Tue, Oct 6, 2015 at 10:59 AM, Stanislav Sinyagin <ssinyagin@gmail.com> wrote:
Well, if your URL points to 5060, then yes, you need to change it to 5080 :-))
On Tue, Oct 6, 2015 at 9:47 AM, Michael Nielsen <mic.niel84@gmail.com> wrote:
I can only give Twilio an url. But I am able to change the default Twilio uses, as an example to 5080. Would that trigger the external gateway perhaps?
On Tuesday, October 6, 2015, Stanislav Sinyagin <ssinyagin@gmail.com> wrote:
but what exactly is configured on twilio side? I guess it should be configurable where it should send calls
On Tue, Oct 6, 2015 at 9:27 AM, Michael Nielsen <mic.niel84@gmail.com> wrote:
If I disable registration on my twilio-inbound, it does not fail - however - incoming calls are still not "catched" by my twilio-inbound gateway profile. It still lands in the public context without any variables set.
On Tue, Oct 6, 2015 at 5:57 AM, Sergey Safarov <s.safarov@gmail.com> wrote:
If disable registration on inbound gateway, then is possible receive inbound call?
On Mon, Oct 5, 2015, 22:45 Michael Nielsen <mic.niel84@gmail.com> wrote:
Twilio is just taking a sip address as termination address. In this case my domain which FS runs on. Apparently, Twilio is sending calls to the standard 5060 port - which then lands in my public context.
On Monday, October 5, 2015, Stanislav Sinyagin <ssinyagin@gmail.com> wrote:
> in your pastebin, you seem to receive the call on your internal > profile (port 5060): > 11:18:58.277709 [DEBUG] sofia.c:9229 sofia/internal/+ > 4432445867@sip.ie1.twilio.com receiving invite from > 54.171.127.192:5060 > > > so, what exactly is configured on both sides? The external profile > is usually on the port 5080. > > > > On Mon, Oct 5, 2015 at 6:26 PM, Michael Nielsen < > mic.niel84@gmail.com> wrote: > >> Here's as log from an incoming call from Twilio: >> http://pastebin.com/n0de7jhv >> >> My guess is the problem is with line 33: "Processing +4432445867 >> <+4432445867>->+44213395867 in context public" >> and it fails on line 40: "Regex (FAIL) [gateway_inbound] >> ${target_context}() =~ /^[a-z]/ break=on-false" >> due to the fact that there aren't set any ${target_context} >> variable. >> >> I've added the Twilio inbound gateway as described in the Twilio >> guide, but adding it, removing it etc. doesn't change anything at all. >> To the Twilio-Inbound gateway I've added the variable >> ${target_context} according to this guide: >> https://github.com/voxserv/freeswitch_conf_minimal/blob/master/docs/tutorial... >> >> So my guess is that the Twilio-Inbound gateway aren't being used - >> however - calls are routed to my FS. >> >> On Sun, Oct 4, 2015 at 10:15 PM, Michael Nielsen < >> mic.niel84@gmail.com> wrote: >> >>> I'll create some logs tomorrow. >>> >>> Just to clarify: >>> - Calls are routes from Twilio to my FS >>> - My FS is a clean installation, 1.6.2 >>> - I've used Twilio's guide for setting up gateways, inbound and >>> outbound >>> - Outbound calls are routed correctly >>> - Inbound calls are as mentioned routes to my FS, but my >>> Twilio-inbound doesn't seem to have anything to do with it, therefor, I'm >>> not able to set any variables in incoming calls from Twilio so I can detect >>> them in my public context and transfer them to my default context. >>> >>> I don't want to route all calls in my public context to my default >>> context, this would open a security issue. Only Twilio calls should be >>> handled in such a manner. >>> That's my challenge. >>> >>> >>> On Sunday, October 4, 2015, Sergey Safarov <s.safarov@gmail.com> >>> wrote: >>> >>>> Inbound call can be received >>>> 1) if twillio guys configure gateway to route incomes calls to you >>>> 2) or if FS provide information how to route call for you >>>> >>>> After reading gateway config files, I has found that used second >>>> case "FS provides information how to route calls via registration >>>> mechanism". >>>> >>>> Please: >>>> - configure clean FS host as described in twilio manuals; >>>> - enable siptrace; >>>> - enable debug log; >>>> - make incoming call; >>>> - attach debug log in respond to this message. >>>> >>>> I try help you >>>> >>>> >>>> On Sun, Oct 4, 2015 at 2:37 PM, Michael Nielsen < >>>> mic.niel84@gmail.com> wrote: >>>> >>>>> Still no luck. >>>>> Any other ideas on how to "catch" the calls from the public >>>>> context in FS? >>>>> My goal is to transfer all calls from Twilio to my default >>>>> context. >>>>> >>>>> >>>>> On Saturday, October 3, 2015, Michael Nielsen < >>>>> mic.niel84@gmail.com> wrote: >>>>> >>>>>> Looking at their guide for secure setup: >>>>>> https://www.twilio.com/resources/images/docs/Twilio-Freeswitch.pdf >>>>>> they've added <param name="register" value="false"/> >>>>>> When I do this, registering doesn't fail (obviously), but >>>>>> inbound calls are still not registered as coming from twilio... They still >>>>>> land directly in the public context without the variables set correctly. >>>>>> >>>>>> On Sat, Oct 3, 2015 at 11:58 AM, Michael Nielsen < >>>>>> mic.niel84@gmail.com> wrote: >>>>>> >>>>>>> When adding the extension, I get the following - even though >>>>>>> my username and password etc. are correct as they work for the outbound >>>>>>> gateway...: >>>>>>> >>>>>>> twilio-inbound Failed Registration [908] >>>>>>> >>>>>>> On Sat, Oct 3, 2015 at 11:57 AM, Michael Nielsen < >>>>>>> mic.niel84@gmail.com> wrote: >>>>>>> >>>>>>>> I see. >>>>>>>> Does it matter that I don't have an extension called 1000 in >>>>>>>> my FS, nor in my Twilio account? >>>>>>>> >>>>>>>> On Fri, Oct 2, 2015 at 11:34 PM, Ahmed Habiba < >>>>>>>> ahabiba@gmail.com> wrote: >>>>>>>> >>>>>>>>> if you have a deep look at inbound gateway it is for >>>>>>>>> receiving calls from Twilio as you can see below, this line informing >>>>>>>>> freeswitch where to route inkling call. >>>>>>>>> >>>>>>>>> <param name="extension" value="1000"/> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> *From: *Michael Nielsen <mic.niel84@gmail.com> >>>>>>>>> *Date: *October 2, 2015 at 11:24:51 PM GMT+3 >>>>>>>>> *To: *FreeSWITCH Users Help < >>>>>>>>> freeswitch-users@lists.freeswitch.org> >>>>>>>>> *Subject: **Re: [Freeswitch-users] Freeswitch and twilio* >>>>>>>>> >>>>>>>>> >>>>>>>>> Outbound works fine. >>>>>>>>> >>>>>>>>> Without having the inbound gateway calls are still routed to >>>>>>>>> my FS to my public context from Twilio. >>>>>>>>> Adding the twilio-inbound doesn't seem to change anything...? >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On Friday, October 2, 2015, Brian West <brian@freeswitch.org> >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> Well you'd send outbound calls out the outbound and the >>>>>>>>>> inbound one is just to register with twilio so they know where to send your >>>>>>>>>> inbound calls. Nothing more. >>>>>>>>>> >>>>>>>>>> On Fri, Oct 2, 2015 at 1:46 PM, Michael Nielsen < >>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>> >>>>>>>>>>> I'm trying to setup twilio as gateway following this guide: >>>>>>>>>>> >>>>>>>>>>> https://www.twilio.com/docs/sip-trunking/sample-configuration#freeswitch >>>>>>>>>>> >>>>>>>>>>> In their example of twiliotrunk.xml they have >>>>>>>>>>> twilio-inbound and twilio-outbound. >>>>>>>>>>> >>>>>>>>>>> What is the difference between the two gateways? I know >>>>>>>>>>> their names indicate inbound and outbound calling, but how can Freeswitch >>>>>>>>>>> tell the difference between them. Especially how can Freeswitch now to use >>>>>>>>>>> twilio-inbound for incoming calls from twilio and not just twilit-outbound >>>>>>>>>>> as the only difference is register-proxy and expire-seconds between the two? >>>>>>>>>>> >>>>>>>>>>> Make sense? >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> _________________________________________________________________________ >>>>>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>>>>> consulting@freeswitch.org >>>>>>>>>>> http://www.freeswitchsolutions.com >>>>>>>>>>> >>>>>>>>>>> Official FreeSWITCH Sites >>>>>>>>>>> http://www.freeswitch.org >>>>>>>>>>> http://confluence.freeswitch.org >>>>>>>>>>> http://www.cluecon.com >>>>>>>>>>> >>>>>>>>>>> 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 >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> >>>>>>>>>> *Brian West* >>>>>>>>>> brian@freeswitch.org >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> *Twitter: @FreeSWITCH , @briankwest* >>>>>>>>>> http://www.freeswitchbook.com >>>>>>>>>> http://www.freeswitchcookbook.com >>>>>>>>>> >>>>>>>>>> Got Bugs? Report them here <https://freeswitch.org/jira>! >>>>>>>>>> | Reddit: /r/freeswitch >>>>>>>>>> <https://www.reddit.com/r/freeswitch> >>>>>>>>>> >>>>>>>>>> *T:*+19184209001 | *F:*+19184209002 | *M:*+1918424WEST >>>>>>>>>> (9378) >>>>>>>>>> *iNUM:*+883 5100 1420 9001 | *ISN:*410*543 | *Skype:* >>>>>>>>>> briankwest >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> 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 >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> _________________________________________________________________________ >>>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>>> consulting@freeswitch.org >>>>>>>>> http://www.freeswitchsolutions.com >>>>>>>>> >>>>>>>>> Official FreeSWITCH Sites >>>>>>>>> http://www.freeswitch.org >>>>>>>>> http://confluence.freeswitch.org >>>>>>>>> http://www.cluecon.com >>>>>>>>> >>>>>>>>> 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 >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>>> _________________________________________________________________________ >>>>> Professional FreeSWITCH Consulting Services: >>>>> consulting@freeswitch.org >>>>> http://www.freeswitchsolutions.com >>>>> >>>>> Official FreeSWITCH Sites >>>>> http://www.freeswitch.org >>>>> http://confluence.freeswitch.org >>>>> http://www.cluecon.com >>>>> >>>>> 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 >>>>> >>>> >>>> >> >> >> _________________________________________________________________________ >> Professional FreeSWITCH Consulting Services: >> consulting@freeswitch.org >> http://www.freeswitchsolutions.com >> >> Official FreeSWITCH Sites >> http://www.freeswitch.org >> http://confluence.freeswitch.org >> http://www.cluecon.com >> >> 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 >> > > _________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
I just did - change to 5080 - and nothing else happens. It still gets routed directly to the public context - without getting "catched" by the gateway-config. I've tried to use the extension parameter in the gateway and route calls from Twilio directly to 1000@my-domain.com:5080, still nothing else happens. On Tue, Oct 6, 2015 at 9:59 AM, Stanislav Sinyagin <ssinyagin@gmail.com> wrote:
Well, if your URL points to 5060, then yes, you need to change it to 5080 :-))
On Tue, Oct 6, 2015 at 9:47 AM, Michael Nielsen <mic.niel84@gmail.com> wrote:
I can only give Twilio an url. But I am able to change the default Twilio uses, as an example to 5080. Would that trigger the external gateway perhaps?
On Tuesday, October 6, 2015, Stanislav Sinyagin <ssinyagin@gmail.com> wrote:
but what exactly is configured on twilio side? I guess it should be configurable where it should send calls
On Tue, Oct 6, 2015 at 9:27 AM, Michael Nielsen <mic.niel84@gmail.com> wrote:
If I disable registration on my twilio-inbound, it does not fail - however - incoming calls are still not "catched" by my twilio-inbound gateway profile. It still lands in the public context without any variables set.
On Tue, Oct 6, 2015 at 5:57 AM, Sergey Safarov <s.safarov@gmail.com> wrote:
If disable registration on inbound gateway, then is possible receive inbound call?
On Mon, Oct 5, 2015, 22:45 Michael Nielsen <mic.niel84@gmail.com> wrote:
Twilio is just taking a sip address as termination address. In this case my domain which FS runs on. Apparently, Twilio is sending calls to the standard 5060 port - which then lands in my public context.
On Monday, October 5, 2015, Stanislav Sinyagin <ssinyagin@gmail.com> wrote:
> in your pastebin, you seem to receive the call on your internal > profile (port 5060): > 11:18:58.277709 [DEBUG] sofia.c:9229 sofia/internal/+ > 4432445867@sip.ie1.twilio.com receiving invite from > 54.171.127.192:5060 > > > so, what exactly is configured on both sides? The external profile > is usually on the port 5080. > > > > On Mon, Oct 5, 2015 at 6:26 PM, Michael Nielsen < > mic.niel84@gmail.com> wrote: > >> Here's as log from an incoming call from Twilio: >> http://pastebin.com/n0de7jhv >> >> My guess is the problem is with line 33: "Processing +4432445867 >> <+4432445867>->+44213395867 in context public" >> and it fails on line 40: "Regex (FAIL) [gateway_inbound] >> ${target_context}() =~ /^[a-z]/ break=on-false" >> due to the fact that there aren't set any ${target_context} >> variable. >> >> I've added the Twilio inbound gateway as described in the Twilio >> guide, but adding it, removing it etc. doesn't change anything at all. >> To the Twilio-Inbound gateway I've added the variable >> ${target_context} according to this guide: >> https://github.com/voxserv/freeswitch_conf_minimal/blob/master/docs/tutorial... >> >> So my guess is that the Twilio-Inbound gateway aren't being used - >> however - calls are routed to my FS. >> >> On Sun, Oct 4, 2015 at 10:15 PM, Michael Nielsen < >> mic.niel84@gmail.com> wrote: >> >>> I'll create some logs tomorrow. >>> >>> Just to clarify: >>> - Calls are routes from Twilio to my FS >>> - My FS is a clean installation, 1.6.2 >>> - I've used Twilio's guide for setting up gateways, inbound and >>> outbound >>> - Outbound calls are routed correctly >>> - Inbound calls are as mentioned routes to my FS, but my >>> Twilio-inbound doesn't seem to have anything to do with it, therefor, I'm >>> not able to set any variables in incoming calls from Twilio so I can detect >>> them in my public context and transfer them to my default context. >>> >>> I don't want to route all calls in my public context to my default >>> context, this would open a security issue. Only Twilio calls should be >>> handled in such a manner. >>> That's my challenge. >>> >>> >>> On Sunday, October 4, 2015, Sergey Safarov <s.safarov@gmail.com> >>> wrote: >>> >>>> Inbound call can be received >>>> 1) if twillio guys configure gateway to route incomes calls to you >>>> 2) or if FS provide information how to route call for you >>>> >>>> After reading gateway config files, I has found that used second >>>> case "FS provides information how to route calls via registration >>>> mechanism". >>>> >>>> Please: >>>> - configure clean FS host as described in twilio manuals; >>>> - enable siptrace; >>>> - enable debug log; >>>> - make incoming call; >>>> - attach debug log in respond to this message. >>>> >>>> I try help you >>>> >>>> >>>> On Sun, Oct 4, 2015 at 2:37 PM, Michael Nielsen < >>>> mic.niel84@gmail.com> wrote: >>>> >>>>> Still no luck. >>>>> Any other ideas on how to "catch" the calls from the public >>>>> context in FS? >>>>> My goal is to transfer all calls from Twilio to my default >>>>> context. >>>>> >>>>> >>>>> On Saturday, October 3, 2015, Michael Nielsen < >>>>> mic.niel84@gmail.com> wrote: >>>>> >>>>>> Looking at their guide for secure setup: >>>>>> https://www.twilio.com/resources/images/docs/Twilio-Freeswitch.pdf >>>>>> they've added <param name="register" value="false"/> >>>>>> When I do this, registering doesn't fail (obviously), but >>>>>> inbound calls are still not registered as coming from twilio... They still >>>>>> land directly in the public context without the variables set correctly. >>>>>> >>>>>> On Sat, Oct 3, 2015 at 11:58 AM, Michael Nielsen < >>>>>> mic.niel84@gmail.com> wrote: >>>>>> >>>>>>> When adding the extension, I get the following - even though >>>>>>> my username and password etc. are correct as they work for the outbound >>>>>>> gateway...: >>>>>>> >>>>>>> twilio-inbound Failed Registration [908] >>>>>>> >>>>>>> On Sat, Oct 3, 2015 at 11:57 AM, Michael Nielsen < >>>>>>> mic.niel84@gmail.com> wrote: >>>>>>> >>>>>>>> I see. >>>>>>>> Does it matter that I don't have an extension called 1000 in >>>>>>>> my FS, nor in my Twilio account? >>>>>>>> >>>>>>>> On Fri, Oct 2, 2015 at 11:34 PM, Ahmed Habiba < >>>>>>>> ahabiba@gmail.com> wrote: >>>>>>>> >>>>>>>>> if you have a deep look at inbound gateway it is for >>>>>>>>> receiving calls from Twilio as you can see below, this line informing >>>>>>>>> freeswitch where to route inkling call. >>>>>>>>> >>>>>>>>> <param name="extension" value="1000"/> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> *From: *Michael Nielsen <mic.niel84@gmail.com> >>>>>>>>> *Date: *October 2, 2015 at 11:24:51 PM GMT+3 >>>>>>>>> *To: *FreeSWITCH Users Help < >>>>>>>>> freeswitch-users@lists.freeswitch.org> >>>>>>>>> *Subject: **Re: [Freeswitch-users] Freeswitch and twilio* >>>>>>>>> >>>>>>>>> >>>>>>>>> Outbound works fine. >>>>>>>>> >>>>>>>>> Without having the inbound gateway calls are still routed to >>>>>>>>> my FS to my public context from Twilio. >>>>>>>>> Adding the twilio-inbound doesn't seem to change anything...? >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On Friday, October 2, 2015, Brian West <brian@freeswitch.org> >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> Well you'd send outbound calls out the outbound and the >>>>>>>>>> inbound one is just to register with twilio so they know where to send your >>>>>>>>>> inbound calls. Nothing more. >>>>>>>>>> >>>>>>>>>> On Fri, Oct 2, 2015 at 1:46 PM, Michael Nielsen < >>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>> >>>>>>>>>>> I'm trying to setup twilio as gateway following this guide: >>>>>>>>>>> >>>>>>>>>>> https://www.twilio.com/docs/sip-trunking/sample-configuration#freeswitch >>>>>>>>>>> >>>>>>>>>>> In their example of twiliotrunk.xml they have >>>>>>>>>>> twilio-inbound and twilio-outbound. >>>>>>>>>>> >>>>>>>>>>> What is the difference between the two gateways? I know >>>>>>>>>>> their names indicate inbound and outbound calling, but how can Freeswitch >>>>>>>>>>> tell the difference between them. Especially how can Freeswitch now to use >>>>>>>>>>> twilio-inbound for incoming calls from twilio and not just twilit-outbound >>>>>>>>>>> as the only difference is register-proxy and expire-seconds between the two? >>>>>>>>>>> >>>>>>>>>>> Make sense? >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> _________________________________________________________________________ >>>>>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>>>>> consulting@freeswitch.org >>>>>>>>>>> http://www.freeswitchsolutions.com >>>>>>>>>>> >>>>>>>>>>> Official FreeSWITCH Sites >>>>>>>>>>> http://www.freeswitch.org >>>>>>>>>>> http://confluence.freeswitch.org >>>>>>>>>>> http://www.cluecon.com >>>>>>>>>>> >>>>>>>>>>> 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 >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> >>>>>>>>>> *Brian West* >>>>>>>>>> brian@freeswitch.org >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> *Twitter: @FreeSWITCH , @briankwest* >>>>>>>>>> http://www.freeswitchbook.com >>>>>>>>>> http://www.freeswitchcookbook.com >>>>>>>>>> >>>>>>>>>> Got Bugs? Report them here <https://freeswitch.org/jira>! >>>>>>>>>> | Reddit: /r/freeswitch >>>>>>>>>> <https://www.reddit.com/r/freeswitch> >>>>>>>>>> >>>>>>>>>> *T:*+19184209001 | *F:*+19184209002 | *M:*+1918424WEST >>>>>>>>>> (9378) >>>>>>>>>> *iNUM:*+883 5100 1420 9001 | *ISN:*410*543 | *Skype:* >>>>>>>>>> briankwest >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> 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 >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> _________________________________________________________________________ >>>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>>> consulting@freeswitch.org >>>>>>>>> http://www.freeswitchsolutions.com >>>>>>>>> >>>>>>>>> Official FreeSWITCH Sites >>>>>>>>> http://www.freeswitch.org >>>>>>>>> http://confluence.freeswitch.org >>>>>>>>> http://www.cluecon.com >>>>>>>>> >>>>>>>>> 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 >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>>> _________________________________________________________________________ >>>>> Professional FreeSWITCH Consulting Services: >>>>> consulting@freeswitch.org >>>>> http://www.freeswitchsolutions.com >>>>> >>>>> Official FreeSWITCH Sites >>>>> http://www.freeswitch.org >>>>> http://confluence.freeswitch.org >>>>> http://www.cluecon.com >>>>> >>>>> 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 >>>>> >>>> >>>> >> >> >> _________________________________________________________________________ >> Professional FreeSWITCH Consulting Services: >> consulting@freeswitch.org >> http://www.freeswitchsolutions.com >> >> Official FreeSWITCH Sites >> http://www.freeswitch.org >> http://confluence.freeswitch.org >> http://www.cluecon.com >> >> 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 >> > > _________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
Hi Michael, If you are using Twilio Elastic SIP trunking you configure what we called *Origination URI *where you configure the IP address (or FQDN) of the network element entry point into your communications infrastructure (e.g. IP-PBX, SBC). Meaning you dial: +4432445867 and we will ring the URI you define. Example: sip:1.1.1.1 sip:+4432445867@1.1.1.1 sip:1000@1.1.1.1 sip:1000@mysb.com?X-myheader=foo Information here: https://www.twilio.com/docs/sip-trunking/getting-started#origination When I looked at your pastebin, I see that you most likely configured something like first example (sip:1.1.1.1) as we are routing the call to +4432445867. Per my understanding, calls received by Freeswitch will be directed to the context of the associated port and IP that a call comes in. For example calls received on port 5060 may be directed to the default context. In our sample guide we are using the US datacenter. In some scenarios this inbound Gateway is not used, for example in my Lab I'm handling calls in public context and this inbound gateway is just ignored. Since your number is in UK most likely you will get a call from the following IP Addresses: - 54.171.127.192 - 54.171.127.193 - 54.171.127.194 Maybe you can try setting it: business.pstn.ie1.twilio.com to match the European Zone IPs and see what happens? HTH -Gonzalo On Tue, Oct 6, 2015 at 2:05 AM, Michael Nielsen <mic.niel84@gmail.com> wrote:
I just did - change to 5080 - and nothing else happens. It still gets routed directly to the public context - without getting "catched" by the gateway-config.
I've tried to use the extension parameter in the gateway and route calls from Twilio directly to 1000@my-domain.com:5080, still nothing else happens.
On Tue, Oct 6, 2015 at 9:59 AM, Stanislav Sinyagin <ssinyagin@gmail.com> wrote:
Well, if your URL points to 5060, then yes, you need to change it to 5080 :-))
On Tue, Oct 6, 2015 at 9:47 AM, Michael Nielsen <mic.niel84@gmail.com> wrote:
I can only give Twilio an url. But I am able to change the default Twilio uses, as an example to 5080. Would that trigger the external gateway perhaps?
On Tuesday, October 6, 2015, Stanislav Sinyagin <ssinyagin@gmail.com> wrote:
but what exactly is configured on twilio side? I guess it should be configurable where it should send calls
On Tue, Oct 6, 2015 at 9:27 AM, Michael Nielsen <mic.niel84@gmail.com> wrote:
If I disable registration on my twilio-inbound, it does not fail - however - incoming calls are still not "catched" by my twilio-inbound gateway profile. It still lands in the public context without any variables set.
On Tue, Oct 6, 2015 at 5:57 AM, Sergey Safarov <s.safarov@gmail.com> wrote:
If disable registration on inbound gateway, then is possible receive inbound call?
On Mon, Oct 5, 2015, 22:45 Michael Nielsen <mic.niel84@gmail.com> wrote:
> Twilio is just taking a sip address as termination address. In this > case my domain which FS runs on. > Apparently, Twilio is sending calls to the standard 5060 port - > which then lands in my public context. > > On Monday, October 5, 2015, Stanislav Sinyagin <ssinyagin@gmail.com> > wrote: > >> in your pastebin, you seem to receive the call on your internal >> profile (port 5060): >> 11:18:58.277709 [DEBUG] sofia.c:9229 sofia/internal/+ >> 4432445867@sip.ie1.twilio.com receiving invite from >> 54.171.127.192:5060 >> >> >> so, what exactly is configured on both sides? The external profile >> is usually on the port 5080. >> >> >> >> On Mon, Oct 5, 2015 at 6:26 PM, Michael Nielsen < >> mic.niel84@gmail.com> wrote: >> >>> Here's as log from an incoming call from Twilio: >>> http://pastebin.com/n0de7jhv >>> >>> My guess is the problem is with line 33: "Processing +4432445867 >>> <+4432445867>->+44213395867 in context public" >>> and it fails on line 40: "Regex (FAIL) [gateway_inbound] >>> ${target_context}() =~ /^[a-z]/ break=on-false" >>> due to the fact that there aren't set any ${target_context} >>> variable. >>> >>> I've added the Twilio inbound gateway as described in the Twilio >>> guide, but adding it, removing it etc. doesn't change anything at all. >>> To the Twilio-Inbound gateway I've added the variable >>> ${target_context} according to this guide: >>> https://github.com/voxserv/freeswitch_conf_minimal/blob/master/docs/tutorial... >>> >>> So my guess is that the Twilio-Inbound gateway aren't being used - >>> however - calls are routed to my FS. >>> >>> On Sun, Oct 4, 2015 at 10:15 PM, Michael Nielsen < >>> mic.niel84@gmail.com> wrote: >>> >>>> I'll create some logs tomorrow. >>>> >>>> Just to clarify: >>>> - Calls are routes from Twilio to my FS >>>> - My FS is a clean installation, 1.6.2 >>>> - I've used Twilio's guide for setting up gateways, inbound and >>>> outbound >>>> - Outbound calls are routed correctly >>>> - Inbound calls are as mentioned routes to my FS, but my >>>> Twilio-inbound doesn't seem to have anything to do with it, therefor, I'm >>>> not able to set any variables in incoming calls from Twilio so I can detect >>>> them in my public context and transfer them to my default context. >>>> >>>> I don't want to route all calls in my public context to my >>>> default context, this would open a security issue. Only Twilio calls should >>>> be handled in such a manner. >>>> That's my challenge. >>>> >>>> >>>> On Sunday, October 4, 2015, Sergey Safarov <s.safarov@gmail.com> >>>> wrote: >>>> >>>>> Inbound call can be received >>>>> 1) if twillio guys configure gateway to route incomes calls to >>>>> you >>>>> 2) or if FS provide information how to route call for you >>>>> >>>>> After reading gateway config files, I has found that used second >>>>> case "FS provides information how to route calls via registration >>>>> mechanism". >>>>> >>>>> Please: >>>>> - configure clean FS host as described in twilio manuals; >>>>> - enable siptrace; >>>>> - enable debug log; >>>>> - make incoming call; >>>>> - attach debug log in respond to this message. >>>>> >>>>> I try help you >>>>> >>>>> >>>>> On Sun, Oct 4, 2015 at 2:37 PM, Michael Nielsen < >>>>> mic.niel84@gmail.com> wrote: >>>>> >>>>>> Still no luck. >>>>>> Any other ideas on how to "catch" the calls from the public >>>>>> context in FS? >>>>>> My goal is to transfer all calls from Twilio to my default >>>>>> context. >>>>>> >>>>>> >>>>>> On Saturday, October 3, 2015, Michael Nielsen < >>>>>> mic.niel84@gmail.com> wrote: >>>>>> >>>>>>> Looking at their guide for secure setup: >>>>>>> https://www.twilio.com/resources/images/docs/Twilio-Freeswitch.pdf >>>>>>> they've added <param name="register" value="false"/> >>>>>>> When I do this, registering doesn't fail (obviously), but >>>>>>> inbound calls are still not registered as coming from twilio... They still >>>>>>> land directly in the public context without the variables set correctly. >>>>>>> >>>>>>> On Sat, Oct 3, 2015 at 11:58 AM, Michael Nielsen < >>>>>>> mic.niel84@gmail.com> wrote: >>>>>>> >>>>>>>> When adding the extension, I get the following - even though >>>>>>>> my username and password etc. are correct as they work for the outbound >>>>>>>> gateway...: >>>>>>>> >>>>>>>> twilio-inbound Failed Registration [908] >>>>>>>> >>>>>>>> On Sat, Oct 3, 2015 at 11:57 AM, Michael Nielsen < >>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>> >>>>>>>>> I see. >>>>>>>>> Does it matter that I don't have an extension called 1000 in >>>>>>>>> my FS, nor in my Twilio account? >>>>>>>>> >>>>>>>>> On Fri, Oct 2, 2015 at 11:34 PM, Ahmed Habiba < >>>>>>>>> ahabiba@gmail.com> wrote: >>>>>>>>> >>>>>>>>>> if you have a deep look at inbound gateway it is for >>>>>>>>>> receiving calls from Twilio as you can see below, this line informing >>>>>>>>>> freeswitch where to route inkling call. >>>>>>>>>> >>>>>>>>>> <param name="extension" value="1000"/> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> *From: *Michael Nielsen <mic.niel84@gmail.com> >>>>>>>>>> *Date: *October 2, 2015 at 11:24:51 PM GMT+3 >>>>>>>>>> *To: *FreeSWITCH Users Help < >>>>>>>>>> freeswitch-users@lists.freeswitch.org> >>>>>>>>>> *Subject: **Re: [Freeswitch-users] Freeswitch and twilio* >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Outbound works fine. >>>>>>>>>> >>>>>>>>>> Without having the inbound gateway calls are still routed >>>>>>>>>> to my FS to my public context from Twilio. >>>>>>>>>> Adding the twilio-inbound doesn't seem to change >>>>>>>>>> anything...? >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Friday, October 2, 2015, Brian West < >>>>>>>>>> brian@freeswitch.org> wrote: >>>>>>>>>> >>>>>>>>>>> Well you'd send outbound calls out the outbound and the >>>>>>>>>>> inbound one is just to register with twilio so they know where to send your >>>>>>>>>>> inbound calls. Nothing more. >>>>>>>>>>> >>>>>>>>>>> On Fri, Oct 2, 2015 at 1:46 PM, Michael Nielsen < >>>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>>> >>>>>>>>>>>> I'm trying to setup twilio as gateway following this >>>>>>>>>>>> guide: >>>>>>>>>>>> >>>>>>>>>>>> https://www.twilio.com/docs/sip-trunking/sample-configuration#freeswitch >>>>>>>>>>>> >>>>>>>>>>>> In their example of twiliotrunk.xml they have >>>>>>>>>>>> twilio-inbound and twilio-outbound. >>>>>>>>>>>> >>>>>>>>>>>> What is the difference between the two gateways? I know >>>>>>>>>>>> their names indicate inbound and outbound calling, but how can Freeswitch >>>>>>>>>>>> tell the difference between them. Especially how can Freeswitch now to use >>>>>>>>>>>> twilio-inbound for incoming calls from twilio and not just twilit-outbound >>>>>>>>>>>> as the only difference is register-proxy and expire-seconds between the two? >>>>>>>>>>>> >>>>>>>>>>>> Make sense? >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> _________________________________________________________________________ >>>>>>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>>>>>> consulting@freeswitch.org >>>>>>>>>>>> http://www.freeswitchsolutions.com >>>>>>>>>>>> >>>>>>>>>>>> Official FreeSWITCH Sites >>>>>>>>>>>> http://www.freeswitch.org >>>>>>>>>>>> http://confluence.freeswitch.org >>>>>>>>>>>> http://www.cluecon.com >>>>>>>>>>>> >>>>>>>>>>>> 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 >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> >>>>>>>>>>> *Brian West* >>>>>>>>>>> brian@freeswitch.org >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> *Twitter: @FreeSWITCH , @briankwest* >>>>>>>>>>> http://www.freeswitchbook.com >>>>>>>>>>> http://www.freeswitchcookbook.com >>>>>>>>>>> >>>>>>>>>>> Got Bugs? Report them here <https://freeswitch.org/jira>! >>>>>>>>>>> | Reddit: /r/freeswitch >>>>>>>>>>> <https://www.reddit.com/r/freeswitch> >>>>>>>>>>> >>>>>>>>>>> *T:*+19184209001 | *F:*+19184209002 | *M:*+1918424WEST >>>>>>>>>>> (9378) >>>>>>>>>>> *iNUM:*+883 5100 1420 9001 | *ISN:*410*543 | *Skype:* >>>>>>>>>>> briankwest >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> 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 >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> _________________________________________________________________________ >>>>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>>>> consulting@freeswitch.org >>>>>>>>>> http://www.freeswitchsolutions.com >>>>>>>>>> >>>>>>>>>> Official FreeSWITCH Sites >>>>>>>>>> http://www.freeswitch.org >>>>>>>>>> http://confluence.freeswitch.org >>>>>>>>>> http://www.cluecon.com >>>>>>>>>> >>>>>>>>>> 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 >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>>> _________________________________________________________________________ >>>>>> Professional FreeSWITCH Consulting Services: >>>>>> consulting@freeswitch.org >>>>>> http://www.freeswitchsolutions.com >>>>>> >>>>>> Official FreeSWITCH Sites >>>>>> http://www.freeswitch.org >>>>>> http://confluence.freeswitch.org >>>>>> http://www.cluecon.com >>>>>> >>>>>> 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 >>>>>> >>>>> >>>>> >>> >>> >>> _________________________________________________________________________ >>> Professional FreeSWITCH Consulting Services: >>> consulting@freeswitch.org >>> http://www.freeswitchsolutions.com >>> >>> Official FreeSWITCH Sites >>> http://www.freeswitch.org >>> http://confluence.freeswitch.org >>> http://www.cluecon.com >>> >>> 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 >>> >> >> > _________________________________________________________________________ > Professional FreeSWITCH Consulting Services: > consulting@freeswitch.org > http://www.freeswitchsolutions.com > > Official FreeSWITCH Sites > http://www.freeswitch.org > http://confluence.freeswitch.org > http://www.cluecon.com > > 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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
I has two FS serves "client" and provider. On client configired gateway. On server user in directory. On servers I take command "originate user/fs2@gateways.rcsnet.ru &park()" Below two string from FS log 10:31:55.818435 [NOTICE] switch_channel.c:1055 New Channel sofia/external/ 0000000000@gateways.rcsnet.ru [6bc096cb-b903-4b47-9a9b-3fba54c10d6a] [INFO] mod_dialplan_xml.c:635 Processing <0000000000>->fs2 in context target_context "target_context" is value of '<param name="context" value="target_context"/>' in gateway config file. Tested on 7add4b2 commit Think you has disable authorization or configure twilio server IP addess in ACL. Locate this changes and revert it back. On Tue, Oct 6, 2015 at 12:05 PM, Michael Nielsen <mic.niel84@gmail.com> wrote:
I just did - change to 5080 - and nothing else happens. It still gets routed directly to the public context - without getting "catched" by the gateway-config.
I've tried to use the extension parameter in the gateway and route calls from Twilio directly to 1000@my-domain.com:5080, still nothing else happens.
On Tue, Oct 6, 2015 at 9:59 AM, Stanislav Sinyagin <ssinyagin@gmail.com> wrote:
Well, if your URL points to 5060, then yes, you need to change it to 5080 :-))
On Tue, Oct 6, 2015 at 9:47 AM, Michael Nielsen <mic.niel84@gmail.com> wrote:
I can only give Twilio an url. But I am able to change the default Twilio uses, as an example to 5080. Would that trigger the external gateway perhaps?
On Tuesday, October 6, 2015, Stanislav Sinyagin <ssinyagin@gmail.com> wrote:
but what exactly is configured on twilio side? I guess it should be configurable where it should send calls
On Tue, Oct 6, 2015 at 9:27 AM, Michael Nielsen <mic.niel84@gmail.com> wrote:
If I disable registration on my twilio-inbound, it does not fail - however - incoming calls are still not "catched" by my twilio-inbound gateway profile. It still lands in the public context without any variables set.
On Tue, Oct 6, 2015 at 5:57 AM, Sergey Safarov <s.safarov@gmail.com> wrote:
If disable registration on inbound gateway, then is possible receive inbound call?
On Mon, Oct 5, 2015, 22:45 Michael Nielsen <mic.niel84@gmail.com> wrote:
> Twilio is just taking a sip address as termination address. In this > case my domain which FS runs on. > Apparently, Twilio is sending calls to the standard 5060 port - > which then lands in my public context. > > On Monday, October 5, 2015, Stanislav Sinyagin <ssinyagin@gmail.com> > wrote: > >> in your pastebin, you seem to receive the call on your internal >> profile (port 5060): >> 11:18:58.277709 [DEBUG] sofia.c:9229 sofia/internal/+ >> 4432445867@sip.ie1.twilio.com receiving invite from >> 54.171.127.192:5060 >> >> >> so, what exactly is configured on both sides? The external profile >> is usually on the port 5080. >> >> >> >> On Mon, Oct 5, 2015 at 6:26 PM, Michael Nielsen < >> mic.niel84@gmail.com> wrote: >> >>> Here's as log from an incoming call from Twilio: >>> http://pastebin.com/n0de7jhv >>> >>> My guess is the problem is with line 33: "Processing +4432445867 >>> <+4432445867>->+44213395867 in context public" >>> and it fails on line 40: "Regex (FAIL) [gateway_inbound] >>> ${target_context}() =~ /^[a-z]/ break=on-false" >>> due to the fact that there aren't set any ${target_context} >>> variable. >>> >>> I've added the Twilio inbound gateway as described in the Twilio >>> guide, but adding it, removing it etc. doesn't change anything at all. >>> To the Twilio-Inbound gateway I've added the variable >>> ${target_context} according to this guide: >>> https://github.com/voxserv/freeswitch_conf_minimal/blob/master/docs/tutorial... >>> >>> So my guess is that the Twilio-Inbound gateway aren't being used - >>> however - calls are routed to my FS. >>> >>> On Sun, Oct 4, 2015 at 10:15 PM, Michael Nielsen < >>> mic.niel84@gmail.com> wrote: >>> >>>> I'll create some logs tomorrow. >>>> >>>> Just to clarify: >>>> - Calls are routes from Twilio to my FS >>>> - My FS is a clean installation, 1.6.2 >>>> - I've used Twilio's guide for setting up gateways, inbound and >>>> outbound >>>> - Outbound calls are routed correctly >>>> - Inbound calls are as mentioned routes to my FS, but my >>>> Twilio-inbound doesn't seem to have anything to do with it, therefor, I'm >>>> not able to set any variables in incoming calls from Twilio so I can detect >>>> them in my public context and transfer them to my default context. >>>> >>>> I don't want to route all calls in my public context to my >>>> default context, this would open a security issue. Only Twilio calls should >>>> be handled in such a manner. >>>> That's my challenge. >>>> >>>> >>>> On Sunday, October 4, 2015, Sergey Safarov <s.safarov@gmail.com> >>>> wrote: >>>> >>>>> Inbound call can be received >>>>> 1) if twillio guys configure gateway to route incomes calls to >>>>> you >>>>> 2) or if FS provide information how to route call for you >>>>> >>>>> After reading gateway config files, I has found that used second >>>>> case "FS provides information how to route calls via registration >>>>> mechanism". >>>>> >>>>> Please: >>>>> - configure clean FS host as described in twilio manuals; >>>>> - enable siptrace; >>>>> - enable debug log; >>>>> - make incoming call; >>>>> - attach debug log in respond to this message. >>>>> >>>>> I try help you >>>>> >>>>> >>>>> On Sun, Oct 4, 2015 at 2:37 PM, Michael Nielsen < >>>>> mic.niel84@gmail.com> wrote: >>>>> >>>>>> Still no luck. >>>>>> Any other ideas on how to "catch" the calls from the public >>>>>> context in FS? >>>>>> My goal is to transfer all calls from Twilio to my default >>>>>> context. >>>>>> >>>>>> >>>>>> On Saturday, October 3, 2015, Michael Nielsen < >>>>>> mic.niel84@gmail.com> wrote: >>>>>> >>>>>>> Looking at their guide for secure setup: >>>>>>> https://www.twilio.com/resources/images/docs/Twilio-Freeswitch.pdf >>>>>>> they've added <param name="register" value="false"/> >>>>>>> When I do this, registering doesn't fail (obviously), but >>>>>>> inbound calls are still not registered as coming from twilio... They still >>>>>>> land directly in the public context without the variables set correctly. >>>>>>> >>>>>>> On Sat, Oct 3, 2015 at 11:58 AM, Michael Nielsen < >>>>>>> mic.niel84@gmail.com> wrote: >>>>>>> >>>>>>>> When adding the extension, I get the following - even though >>>>>>>> my username and password etc. are correct as they work for the outbound >>>>>>>> gateway...: >>>>>>>> >>>>>>>> twilio-inbound Failed Registration [908] >>>>>>>> >>>>>>>> On Sat, Oct 3, 2015 at 11:57 AM, Michael Nielsen < >>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>> >>>>>>>>> I see. >>>>>>>>> Does it matter that I don't have an extension called 1000 in >>>>>>>>> my FS, nor in my Twilio account? >>>>>>>>> >>>>>>>>> On Fri, Oct 2, 2015 at 11:34 PM, Ahmed Habiba < >>>>>>>>> ahabiba@gmail.com> wrote: >>>>>>>>> >>>>>>>>>> if you have a deep look at inbound gateway it is for >>>>>>>>>> receiving calls from Twilio as you can see below, this line informing >>>>>>>>>> freeswitch where to route inkling call. >>>>>>>>>> >>>>>>>>>> <param name="extension" value="1000"/> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> *From: *Michael Nielsen <mic.niel84@gmail.com> >>>>>>>>>> *Date: *October 2, 2015 at 11:24:51 PM GMT+3 >>>>>>>>>> *To: *FreeSWITCH Users Help < >>>>>>>>>> freeswitch-users@lists.freeswitch.org> >>>>>>>>>> *Subject: **Re: [Freeswitch-users] Freeswitch and twilio* >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Outbound works fine. >>>>>>>>>> >>>>>>>>>> Without having the inbound gateway calls are still routed >>>>>>>>>> to my FS to my public context from Twilio. >>>>>>>>>> Adding the twilio-inbound doesn't seem to change >>>>>>>>>> anything...? >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Friday, October 2, 2015, Brian West < >>>>>>>>>> brian@freeswitch.org> wrote: >>>>>>>>>> >>>>>>>>>>> Well you'd send outbound calls out the outbound and the >>>>>>>>>>> inbound one is just to register with twilio so they know where to send your >>>>>>>>>>> inbound calls. Nothing more. >>>>>>>>>>> >>>>>>>>>>> On Fri, Oct 2, 2015 at 1:46 PM, Michael Nielsen < >>>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>>> >>>>>>>>>>>> I'm trying to setup twilio as gateway following this >>>>>>>>>>>> guide: >>>>>>>>>>>> >>>>>>>>>>>> https://www.twilio.com/docs/sip-trunking/sample-configuration#freeswitch >>>>>>>>>>>> >>>>>>>>>>>> In their example of twiliotrunk.xml they have >>>>>>>>>>>> twilio-inbound and twilio-outbound. >>>>>>>>>>>> >>>>>>>>>>>> What is the difference between the two gateways? I know >>>>>>>>>>>> their names indicate inbound and outbound calling, but how can Freeswitch >>>>>>>>>>>> tell the difference between them. Especially how can Freeswitch now to use >>>>>>>>>>>> twilio-inbound for incoming calls from twilio and not just twilit-outbound >>>>>>>>>>>> as the only difference is register-proxy and expire-seconds between the two? >>>>>>>>>>>> >>>>>>>>>>>> Make sense? >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> _________________________________________________________________________ >>>>>>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>>>>>> consulting@freeswitch.org >>>>>>>>>>>> http://www.freeswitchsolutions.com >>>>>>>>>>>> >>>>>>>>>>>> Official FreeSWITCH Sites >>>>>>>>>>>> http://www.freeswitch.org >>>>>>>>>>>> http://confluence.freeswitch.org >>>>>>>>>>>> http://www.cluecon.com >>>>>>>>>>>> >>>>>>>>>>>> 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 >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> >>>>>>>>>>> *Brian West* >>>>>>>>>>> brian@freeswitch.org >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> *Twitter: @FreeSWITCH , @briankwest* >>>>>>>>>>> http://www.freeswitchbook.com >>>>>>>>>>> http://www.freeswitchcookbook.com >>>>>>>>>>> >>>>>>>>>>> Got Bugs? Report them here <https://freeswitch.org/jira>! >>>>>>>>>>> | Reddit: /r/freeswitch >>>>>>>>>>> <https://www.reddit.com/r/freeswitch> >>>>>>>>>>> >>>>>>>>>>> *T:*+19184209001 | *F:*+19184209002 | *M:*+1918424WEST >>>>>>>>>>> (9378) >>>>>>>>>>> *iNUM:*+883 5100 1420 9001 | *ISN:*410*543 | *Skype:* >>>>>>>>>>> briankwest >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> 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 >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> _________________________________________________________________________ >>>>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>>>> consulting@freeswitch.org >>>>>>>>>> http://www.freeswitchsolutions.com >>>>>>>>>> >>>>>>>>>> Official FreeSWITCH Sites >>>>>>>>>> http://www.freeswitch.org >>>>>>>>>> http://confluence.freeswitch.org >>>>>>>>>> http://www.cluecon.com >>>>>>>>>> >>>>>>>>>> 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 >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>>> _________________________________________________________________________ >>>>>> Professional FreeSWITCH Consulting Services: >>>>>> consulting@freeswitch.org >>>>>> http://www.freeswitchsolutions.com >>>>>> >>>>>> Official FreeSWITCH Sites >>>>>> http://www.freeswitch.org >>>>>> http://confluence.freeswitch.org >>>>>> http://www.cluecon.com >>>>>> >>>>>> 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 >>>>>> >>>>> >>>>> >>> >>> >>> _________________________________________________________________________ >>> Professional FreeSWITCH Consulting Services: >>> consulting@freeswitch.org >>> http://www.freeswitchsolutions.com >>> >>> Official FreeSWITCH Sites >>> http://www.freeswitch.org >>> http://confluence.freeswitch.org >>> http://www.cluecon.com >>> >>> 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 >>> >> >> > _________________________________________________________________________ > Professional FreeSWITCH Consulting Services: > consulting@freeswitch.org > http://www.freeswitchsolutions.com > > Official FreeSWITCH Sites > http://www.freeswitch.org > http://confluence.freeswitch.org > http://www.cluecon.com > > 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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
I did have Twilio IP's in ACL - as their guide told me to. Removing them gives me the following error: "Rejected by acl "domains". Falling back to Digest auth." I do have a twilio.xml in my /sip_profiles/external/ directory and this does work for outbound calls. On Tue, Oct 6, 2015 at 12:57 PM, Sergey Safarov <s.safarov@gmail.com> wrote:
I has two FS serves "client" and provider. On client configired gateway. On server user in directory.
On servers I take command "originate user/fs2@gateways.rcsnet.ru &park()" Below two string from FS log
10:31:55.818435 [NOTICE] switch_channel.c:1055 New Channel sofia/external/ 0000000000@gateways.rcsnet.ru [6bc096cb-b903-4b47-9a9b-3fba54c10d6a] [INFO] mod_dialplan_xml.c:635 Processing <0000000000>->fs2 in context target_context
"target_context" is value of '<param name="context" value="target_context"/>' in gateway config file.
Tested on 7add4b2 commit
Think you has disable authorization or configure twilio server IP addess in ACL. Locate this changes and revert it back.
On Tue, Oct 6, 2015 at 12:05 PM, Michael Nielsen <mic.niel84@gmail.com> wrote:
I just did - change to 5080 - and nothing else happens. It still gets routed directly to the public context - without getting "catched" by the gateway-config.
I've tried to use the extension parameter in the gateway and route calls from Twilio directly to 1000@my-domain.com:5080, still nothing else happens.
On Tue, Oct 6, 2015 at 9:59 AM, Stanislav Sinyagin <ssinyagin@gmail.com> wrote:
Well, if your URL points to 5060, then yes, you need to change it to 5080 :-))
On Tue, Oct 6, 2015 at 9:47 AM, Michael Nielsen <mic.niel84@gmail.com> wrote:
I can only give Twilio an url. But I am able to change the default Twilio uses, as an example to 5080. Would that trigger the external gateway perhaps?
On Tuesday, October 6, 2015, Stanislav Sinyagin <ssinyagin@gmail.com> wrote:
but what exactly is configured on twilio side? I guess it should be configurable where it should send calls
On Tue, Oct 6, 2015 at 9:27 AM, Michael Nielsen <mic.niel84@gmail.com> wrote:
If I disable registration on my twilio-inbound, it does not fail - however - incoming calls are still not "catched" by my twilio-inbound gateway profile. It still lands in the public context without any variables set.
On Tue, Oct 6, 2015 at 5:57 AM, Sergey Safarov <s.safarov@gmail.com> wrote:
> If disable registration on inbound gateway, then is possible receive > inbound call? > > On Mon, Oct 5, 2015, 22:45 Michael Nielsen <mic.niel84@gmail.com> > wrote: > >> Twilio is just taking a sip address as termination address. In this >> case my domain which FS runs on. >> Apparently, Twilio is sending calls to the standard 5060 port - >> which then lands in my public context. >> >> On Monday, October 5, 2015, Stanislav Sinyagin <ssinyagin@gmail.com> >> wrote: >> >>> in your pastebin, you seem to receive the call on your internal >>> profile (port 5060): >>> 11:18:58.277709 [DEBUG] sofia.c:9229 sofia/internal/+ >>> 4432445867@sip.ie1.twilio.com receiving invite from >>> 54.171.127.192:5060 >>> >>> >>> so, what exactly is configured on both sides? The external profile >>> is usually on the port 5080. >>> >>> >>> >>> On Mon, Oct 5, 2015 at 6:26 PM, Michael Nielsen < >>> mic.niel84@gmail.com> wrote: >>> >>>> Here's as log from an incoming call from Twilio: >>>> http://pastebin.com/n0de7jhv >>>> >>>> My guess is the problem is with line 33: "Processing +4432445867 >>>> <+4432445867>->+44213395867 in context public" >>>> and it fails on line 40: "Regex (FAIL) [gateway_inbound] >>>> ${target_context}() =~ /^[a-z]/ break=on-false" >>>> due to the fact that there aren't set any ${target_context} >>>> variable. >>>> >>>> I've added the Twilio inbound gateway as described in the Twilio >>>> guide, but adding it, removing it etc. doesn't change anything at all. >>>> To the Twilio-Inbound gateway I've added the variable >>>> ${target_context} according to this guide: >>>> https://github.com/voxserv/freeswitch_conf_minimal/blob/master/docs/tutorial... >>>> >>>> So my guess is that the Twilio-Inbound gateway aren't being used >>>> - however - calls are routed to my FS. >>>> >>>> On Sun, Oct 4, 2015 at 10:15 PM, Michael Nielsen < >>>> mic.niel84@gmail.com> wrote: >>>> >>>>> I'll create some logs tomorrow. >>>>> >>>>> Just to clarify: >>>>> - Calls are routes from Twilio to my FS >>>>> - My FS is a clean installation, 1.6.2 >>>>> - I've used Twilio's guide for setting up gateways, inbound and >>>>> outbound >>>>> - Outbound calls are routed correctly >>>>> - Inbound calls are as mentioned routes to my FS, but my >>>>> Twilio-inbound doesn't seem to have anything to do with it, therefor, I'm >>>>> not able to set any variables in incoming calls from Twilio so I can detect >>>>> them in my public context and transfer them to my default context. >>>>> >>>>> I don't want to route all calls in my public context to my >>>>> default context, this would open a security issue. Only Twilio calls should >>>>> be handled in such a manner. >>>>> That's my challenge. >>>>> >>>>> >>>>> On Sunday, October 4, 2015, Sergey Safarov <s.safarov@gmail.com> >>>>> wrote: >>>>> >>>>>> Inbound call can be received >>>>>> 1) if twillio guys configure gateway to route incomes calls to >>>>>> you >>>>>> 2) or if FS provide information how to route call for you >>>>>> >>>>>> After reading gateway config files, I has found that used >>>>>> second case "FS provides information how to route calls via registration >>>>>> mechanism". >>>>>> >>>>>> Please: >>>>>> - configure clean FS host as described in twilio manuals; >>>>>> - enable siptrace; >>>>>> - enable debug log; >>>>>> - make incoming call; >>>>>> - attach debug log in respond to this message. >>>>>> >>>>>> I try help you >>>>>> >>>>>> >>>>>> On Sun, Oct 4, 2015 at 2:37 PM, Michael Nielsen < >>>>>> mic.niel84@gmail.com> wrote: >>>>>> >>>>>>> Still no luck. >>>>>>> Any other ideas on how to "catch" the calls from the public >>>>>>> context in FS? >>>>>>> My goal is to transfer all calls from Twilio to my default >>>>>>> context. >>>>>>> >>>>>>> >>>>>>> On Saturday, October 3, 2015, Michael Nielsen < >>>>>>> mic.niel84@gmail.com> wrote: >>>>>>> >>>>>>>> Looking at their guide for secure setup: >>>>>>>> https://www.twilio.com/resources/images/docs/Twilio-Freeswitch.pdf >>>>>>>> they've added <param name="register" value="false"/> >>>>>>>> When I do this, registering doesn't fail (obviously), but >>>>>>>> inbound calls are still not registered as coming from twilio... They still >>>>>>>> land directly in the public context without the variables set correctly. >>>>>>>> >>>>>>>> On Sat, Oct 3, 2015 at 11:58 AM, Michael Nielsen < >>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>> >>>>>>>>> When adding the extension, I get the following - even though >>>>>>>>> my username and password etc. are correct as they work for the outbound >>>>>>>>> gateway...: >>>>>>>>> >>>>>>>>> twilio-inbound Failed Registration [908] >>>>>>>>> >>>>>>>>> On Sat, Oct 3, 2015 at 11:57 AM, Michael Nielsen < >>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>> >>>>>>>>>> I see. >>>>>>>>>> Does it matter that I don't have an extension called 1000 >>>>>>>>>> in my FS, nor in my Twilio account? >>>>>>>>>> >>>>>>>>>> On Fri, Oct 2, 2015 at 11:34 PM, Ahmed Habiba < >>>>>>>>>> ahabiba@gmail.com> wrote: >>>>>>>>>> >>>>>>>>>>> if you have a deep look at inbound gateway it is for >>>>>>>>>>> receiving calls from Twilio as you can see below, this line informing >>>>>>>>>>> freeswitch where to route inkling call. >>>>>>>>>>> >>>>>>>>>>> <param name="extension" value="1000"/> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> *From: *Michael Nielsen <mic.niel84@gmail.com> >>>>>>>>>>> *Date: *October 2, 2015 at 11:24:51 PM GMT+3 >>>>>>>>>>> *To: *FreeSWITCH Users Help < >>>>>>>>>>> freeswitch-users@lists.freeswitch.org> >>>>>>>>>>> *Subject: **Re: [Freeswitch-users] Freeswitch and twilio* >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Outbound works fine. >>>>>>>>>>> >>>>>>>>>>> Without having the inbound gateway calls are still routed >>>>>>>>>>> to my FS to my public context from Twilio. >>>>>>>>>>> Adding the twilio-inbound doesn't seem to change >>>>>>>>>>> anything...? >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Friday, October 2, 2015, Brian West < >>>>>>>>>>> brian@freeswitch.org> wrote: >>>>>>>>>>> >>>>>>>>>>>> Well you'd send outbound calls out the outbound and the >>>>>>>>>>>> inbound one is just to register with twilio so they know where to send your >>>>>>>>>>>> inbound calls. Nothing more. >>>>>>>>>>>> >>>>>>>>>>>> On Fri, Oct 2, 2015 at 1:46 PM, Michael Nielsen < >>>>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> I'm trying to setup twilio as gateway following this >>>>>>>>>>>>> guide: >>>>>>>>>>>>> >>>>>>>>>>>>> https://www.twilio.com/docs/sip-trunking/sample-configuration#freeswitch >>>>>>>>>>>>> >>>>>>>>>>>>> In their example of twiliotrunk.xml they have >>>>>>>>>>>>> twilio-inbound and twilio-outbound. >>>>>>>>>>>>> >>>>>>>>>>>>> What is the difference between the two gateways? I know >>>>>>>>>>>>> their names indicate inbound and outbound calling, but how can Freeswitch >>>>>>>>>>>>> tell the difference between them. Especially how can Freeswitch now to use >>>>>>>>>>>>> twilio-inbound for incoming calls from twilio and not just twilit-outbound >>>>>>>>>>>>> as the only difference is register-proxy and expire-seconds between the two? >>>>>>>>>>>>> >>>>>>>>>>>>> Make sense? >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> _________________________________________________________________________ >>>>>>>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>>>>>>> consulting@freeswitch.org >>>>>>>>>>>>> http://www.freeswitchsolutions.com >>>>>>>>>>>>> >>>>>>>>>>>>> Official FreeSWITCH Sites >>>>>>>>>>>>> http://www.freeswitch.org >>>>>>>>>>>>> http://confluence.freeswitch.org >>>>>>>>>>>>> http://www.cluecon.com >>>>>>>>>>>>> >>>>>>>>>>>>> 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 >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> >>>>>>>>>>>> *Brian West* >>>>>>>>>>>> brian@freeswitch.org >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> *Twitter: @FreeSWITCH , @briankwest* >>>>>>>>>>>> http://www.freeswitchbook.com >>>>>>>>>>>> http://www.freeswitchcookbook.com >>>>>>>>>>>> >>>>>>>>>>>> Got Bugs? Report them here <https://freeswitch.org/jira>! >>>>>>>>>>>> | Reddit: /r/freeswitch >>>>>>>>>>>> <https://www.reddit.com/r/freeswitch> >>>>>>>>>>>> >>>>>>>>>>>> *T:*+19184209001 | *F:*+19184209002 | *M:*+1918424WEST >>>>>>>>>>>> (9378) >>>>>>>>>>>> *iNUM:*+883 5100 1420 9001 | *ISN:*410*543 | *Skype:* >>>>>>>>>>>> briankwest >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> 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 >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> _________________________________________________________________________ >>>>>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>>>>> consulting@freeswitch.org >>>>>>>>>>> http://www.freeswitchsolutions.com >>>>>>>>>>> >>>>>>>>>>> Official FreeSWITCH Sites >>>>>>>>>>> http://www.freeswitch.org >>>>>>>>>>> http://confluence.freeswitch.org >>>>>>>>>>> http://www.cluecon.com >>>>>>>>>>> >>>>>>>>>>> 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 >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>>> _________________________________________________________________________ >>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>> consulting@freeswitch.org >>>>>>> http://www.freeswitchsolutions.com >>>>>>> >>>>>>> Official FreeSWITCH Sites >>>>>>> http://www.freeswitch.org >>>>>>> http://confluence.freeswitch.org >>>>>>> http://www.cluecon.com >>>>>>> >>>>>>> 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 >>>>>>> >>>>>> >>>>>> >>>> >>>> >>>> _________________________________________________________________________ >>>> Professional FreeSWITCH Consulting Services: >>>> consulting@freeswitch.org >>>> http://www.freeswitchsolutions.com >>>> >>>> Official FreeSWITCH Sites >>>> http://www.freeswitch.org >>>> http://confluence.freeswitch.org >>>> http://www.cluecon.com >>>> >>>> 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 >>>> >>> >>> >> _________________________________________________________________________ >> Professional FreeSWITCH Consulting Services: >> consulting@freeswitch.org >> http://www.freeswitchsolutions.com >> >> Official FreeSWITCH Sites >> http://www.freeswitch.org >> http://confluence.freeswitch.org >> http://www.cluecon.com >> >> 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 > > > > _________________________________________________________________________ > Professional FreeSWITCH Consulting Services: > consulting@freeswitch.org > http://www.freeswitchsolutions.com > > Official FreeSWITCH Sites > http://www.freeswitch.org > http://confluence.freeswitch.org > http://www.cluecon.com > > 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 >
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
My external_auth_calls in vars.xml is set to false. Should this be true so FS would use my external gateway config? On Tue, Oct 6, 2015 at 3:07 PM, Michael Nielsen <mic.niel84@gmail.com> wrote:
I did have Twilio IP's in ACL - as their guide told me to. Removing them gives me the following error: "Rejected by acl "domains". Falling back to Digest auth."
I do have a twilio.xml in my /sip_profiles/external/ directory and this does work for outbound calls.
On Tue, Oct 6, 2015 at 12:57 PM, Sergey Safarov <s.safarov@gmail.com> wrote:
I has two FS serves "client" and provider. On client configired gateway. On server user in directory.
On servers I take command "originate user/fs2@gateways.rcsnet.ru &park()" Below two string from FS log
10:31:55.818435 [NOTICE] switch_channel.c:1055 New Channel sofia/external/ 0000000000@gateways.rcsnet.ru [6bc096cb-b903-4b47-9a9b-3fba54c10d6a] [INFO] mod_dialplan_xml.c:635 Processing <0000000000>->fs2 in context target_context
"target_context" is value of '<param name="context" value="target_context"/>' in gateway config file.
Tested on 7add4b2 commit
Think you has disable authorization or configure twilio server IP addess in ACL. Locate this changes and revert it back.
On Tue, Oct 6, 2015 at 12:05 PM, Michael Nielsen <mic.niel84@gmail.com> wrote:
I just did - change to 5080 - and nothing else happens. It still gets routed directly to the public context - without getting "catched" by the gateway-config.
I've tried to use the extension parameter in the gateway and route calls from Twilio directly to 1000@my-domain.com:5080, still nothing else happens.
On Tue, Oct 6, 2015 at 9:59 AM, Stanislav Sinyagin <ssinyagin@gmail.com> wrote:
Well, if your URL points to 5060, then yes, you need to change it to 5080 :-))
On Tue, Oct 6, 2015 at 9:47 AM, Michael Nielsen <mic.niel84@gmail.com> wrote:
I can only give Twilio an url. But I am able to change the default Twilio uses, as an example to 5080. Would that trigger the external gateway perhaps?
On Tuesday, October 6, 2015, Stanislav Sinyagin <ssinyagin@gmail.com> wrote:
but what exactly is configured on twilio side? I guess it should be configurable where it should send calls
On Tue, Oct 6, 2015 at 9:27 AM, Michael Nielsen <mic.niel84@gmail.com > wrote:
> If I disable registration on my twilio-inbound, it does not fail - > however - incoming calls are still not "catched" by my twilio-inbound > gateway profile. It still lands in the public context without any variables > set. > > On Tue, Oct 6, 2015 at 5:57 AM, Sergey Safarov <s.safarov@gmail.com> > wrote: > >> If disable registration on inbound gateway, then is possible >> receive inbound call? >> >> On Mon, Oct 5, 2015, 22:45 Michael Nielsen <mic.niel84@gmail.com> >> wrote: >> >>> Twilio is just taking a sip address as termination address. In >>> this case my domain which FS runs on. >>> Apparently, Twilio is sending calls to the standard 5060 port - >>> which then lands in my public context. >>> >>> On Monday, October 5, 2015, Stanislav Sinyagin < >>> ssinyagin@gmail.com> wrote: >>> >>>> in your pastebin, you seem to receive the call on your internal >>>> profile (port 5060): >>>> 11:18:58.277709 [DEBUG] sofia.c:9229 sofia/internal/+ >>>> 4432445867@sip.ie1.twilio.com receiving invite from >>>> 54.171.127.192:5060 >>>> >>>> >>>> so, what exactly is configured on both sides? The external >>>> profile is usually on the port 5080. >>>> >>>> >>>> >>>> On Mon, Oct 5, 2015 at 6:26 PM, Michael Nielsen < >>>> mic.niel84@gmail.com> wrote: >>>> >>>>> Here's as log from an incoming call from Twilio: >>>>> http://pastebin.com/n0de7jhv >>>>> >>>>> My guess is the problem is with line 33: "Processing >>>>> +4432445867 <+4432445867>->+44213395867 in context public" >>>>> and it fails on line 40: "Regex (FAIL) [gateway_inbound] >>>>> ${target_context}() =~ /^[a-z]/ break=on-false" >>>>> due to the fact that there aren't set any ${target_context} >>>>> variable. >>>>> >>>>> I've added the Twilio inbound gateway as described in the Twilio >>>>> guide, but adding it, removing it etc. doesn't change anything at all. >>>>> To the Twilio-Inbound gateway I've added the variable >>>>> ${target_context} according to this guide: >>>>> https://github.com/voxserv/freeswitch_conf_minimal/blob/master/docs/tutorial... >>>>> >>>>> So my guess is that the Twilio-Inbound gateway aren't being used >>>>> - however - calls are routed to my FS. >>>>> >>>>> On Sun, Oct 4, 2015 at 10:15 PM, Michael Nielsen < >>>>> mic.niel84@gmail.com> wrote: >>>>> >>>>>> I'll create some logs tomorrow. >>>>>> >>>>>> Just to clarify: >>>>>> - Calls are routes from Twilio to my FS >>>>>> - My FS is a clean installation, 1.6.2 >>>>>> - I've used Twilio's guide for setting up gateways, inbound and >>>>>> outbound >>>>>> - Outbound calls are routed correctly >>>>>> - Inbound calls are as mentioned routes to my FS, but my >>>>>> Twilio-inbound doesn't seem to have anything to do with it, therefor, I'm >>>>>> not able to set any variables in incoming calls from Twilio so I can detect >>>>>> them in my public context and transfer them to my default context. >>>>>> >>>>>> I don't want to route all calls in my public context to my >>>>>> default context, this would open a security issue. Only Twilio calls should >>>>>> be handled in such a manner. >>>>>> That's my challenge. >>>>>> >>>>>> >>>>>> On Sunday, October 4, 2015, Sergey Safarov <s.safarov@gmail.com> >>>>>> wrote: >>>>>> >>>>>>> Inbound call can be received >>>>>>> 1) if twillio guys configure gateway to route incomes calls to >>>>>>> you >>>>>>> 2) or if FS provide information how to route call for you >>>>>>> >>>>>>> After reading gateway config files, I has found that used >>>>>>> second case "FS provides information how to route calls via registration >>>>>>> mechanism". >>>>>>> >>>>>>> Please: >>>>>>> - configure clean FS host as described in twilio manuals; >>>>>>> - enable siptrace; >>>>>>> - enable debug log; >>>>>>> - make incoming call; >>>>>>> - attach debug log in respond to this message. >>>>>>> >>>>>>> I try help you >>>>>>> >>>>>>> >>>>>>> On Sun, Oct 4, 2015 at 2:37 PM, Michael Nielsen < >>>>>>> mic.niel84@gmail.com> wrote: >>>>>>> >>>>>>>> Still no luck. >>>>>>>> Any other ideas on how to "catch" the calls from the public >>>>>>>> context in FS? >>>>>>>> My goal is to transfer all calls from Twilio to my default >>>>>>>> context. >>>>>>>> >>>>>>>> >>>>>>>> On Saturday, October 3, 2015, Michael Nielsen < >>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>> >>>>>>>>> Looking at their guide for secure setup: >>>>>>>>> https://www.twilio.com/resources/images/docs/Twilio-Freeswitch.pdf >>>>>>>>> they've added <param name="register" value="false"/> >>>>>>>>> When I do this, registering doesn't fail (obviously), but >>>>>>>>> inbound calls are still not registered as coming from twilio... They still >>>>>>>>> land directly in the public context without the variables set correctly. >>>>>>>>> >>>>>>>>> On Sat, Oct 3, 2015 at 11:58 AM, Michael Nielsen < >>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>> >>>>>>>>>> When adding the extension, I get the following - even >>>>>>>>>> though my username and password etc. are correct as they work for the >>>>>>>>>> outbound gateway...: >>>>>>>>>> >>>>>>>>>> twilio-inbound Failed Registration [908] >>>>>>>>>> >>>>>>>>>> On Sat, Oct 3, 2015 at 11:57 AM, Michael Nielsen < >>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>> >>>>>>>>>>> I see. >>>>>>>>>>> Does it matter that I don't have an extension called 1000 >>>>>>>>>>> in my FS, nor in my Twilio account? >>>>>>>>>>> >>>>>>>>>>> On Fri, Oct 2, 2015 at 11:34 PM, Ahmed Habiba < >>>>>>>>>>> ahabiba@gmail.com> wrote: >>>>>>>>>>> >>>>>>>>>>>> if you have a deep look at inbound gateway it is for >>>>>>>>>>>> receiving calls from Twilio as you can see below, this line informing >>>>>>>>>>>> freeswitch where to route inkling call. >>>>>>>>>>>> >>>>>>>>>>>> <param name="extension" value="1000"/> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> *From: *Michael Nielsen <mic.niel84@gmail.com> >>>>>>>>>>>> *Date: *October 2, 2015 at 11:24:51 PM GMT+3 >>>>>>>>>>>> *To: *FreeSWITCH Users Help < >>>>>>>>>>>> freeswitch-users@lists.freeswitch.org> >>>>>>>>>>>> *Subject: **Re: [Freeswitch-users] Freeswitch and twilio* >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Outbound works fine. >>>>>>>>>>>> >>>>>>>>>>>> Without having the inbound gateway calls are still routed >>>>>>>>>>>> to my FS to my public context from Twilio. >>>>>>>>>>>> Adding the twilio-inbound doesn't seem to change >>>>>>>>>>>> anything...? >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Friday, October 2, 2015, Brian West < >>>>>>>>>>>> brian@freeswitch.org> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Well you'd send outbound calls out the outbound and the >>>>>>>>>>>>> inbound one is just to register with twilio so they know where to send your >>>>>>>>>>>>> inbound calls. Nothing more. >>>>>>>>>>>>> >>>>>>>>>>>>> On Fri, Oct 2, 2015 at 1:46 PM, Michael Nielsen < >>>>>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> I'm trying to setup twilio as gateway following this >>>>>>>>>>>>>> guide: >>>>>>>>>>>>>> >>>>>>>>>>>>>> https://www.twilio.com/docs/sip-trunking/sample-configuration#freeswitch >>>>>>>>>>>>>> >>>>>>>>>>>>>> In their example of twiliotrunk.xml they have >>>>>>>>>>>>>> twilio-inbound and twilio-outbound. >>>>>>>>>>>>>> >>>>>>>>>>>>>> What is the difference between the two gateways? I know >>>>>>>>>>>>>> their names indicate inbound and outbound calling, but how can Freeswitch >>>>>>>>>>>>>> tell the difference between them. Especially how can Freeswitch now to use >>>>>>>>>>>>>> twilio-inbound for incoming calls from twilio and not just twilit-outbound >>>>>>>>>>>>>> as the only difference is register-proxy and expire-seconds between the two? >>>>>>>>>>>>>> >>>>>>>>>>>>>> Make sense? >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> _________________________________________________________________________ >>>>>>>>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>>>>>>>> consulting@freeswitch.org >>>>>>>>>>>>>> http://www.freeswitchsolutions.com >>>>>>>>>>>>>> >>>>>>>>>>>>>> Official FreeSWITCH Sites >>>>>>>>>>>>>> http://www.freeswitch.org >>>>>>>>>>>>>> http://confluence.freeswitch.org >>>>>>>>>>>>>> http://www.cluecon.com >>>>>>>>>>>>>> >>>>>>>>>>>>>> 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 >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> -- >>>>>>>>>>>>> >>>>>>>>>>>>> *Brian West* >>>>>>>>>>>>> brian@freeswitch.org >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> *Twitter: @FreeSWITCH , @briankwest* >>>>>>>>>>>>> http://www.freeswitchbook.com >>>>>>>>>>>>> http://www.freeswitchcookbook.com >>>>>>>>>>>>> >>>>>>>>>>>>> Got Bugs? Report them here <https://freeswitch.org/jira>! >>>>>>>>>>>>> | Reddit: /r/freeswitch >>>>>>>>>>>>> <https://www.reddit.com/r/freeswitch> >>>>>>>>>>>>> >>>>>>>>>>>>> *T:*+19184209001 | *F:*+19184209002 | *M:*+1918424WEST >>>>>>>>>>>>> (9378) >>>>>>>>>>>>> *iNUM:*+883 5100 1420 9001 | *ISN:*410*543 | *Skype:* >>>>>>>>>>>>> briankwest >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> 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 >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> _________________________________________________________________________ >>>>>>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>>>>>> consulting@freeswitch.org >>>>>>>>>>>> http://www.freeswitchsolutions.com >>>>>>>>>>>> >>>>>>>>>>>> Official FreeSWITCH Sites >>>>>>>>>>>> http://www.freeswitch.org >>>>>>>>>>>> http://confluence.freeswitch.org >>>>>>>>>>>> http://www.cluecon.com >>>>>>>>>>>> >>>>>>>>>>>> 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 >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> _________________________________________________________________________ >>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>> consulting@freeswitch.org >>>>>>>> http://www.freeswitchsolutions.com >>>>>>>> >>>>>>>> Official FreeSWITCH Sites >>>>>>>> http://www.freeswitch.org >>>>>>>> http://confluence.freeswitch.org >>>>>>>> http://www.cluecon.com >>>>>>>> >>>>>>>> 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 >>>>>>>> >>>>>>> >>>>>>> >>>>> >>>>> >>>>> _________________________________________________________________________ >>>>> Professional FreeSWITCH Consulting Services: >>>>> consulting@freeswitch.org >>>>> http://www.freeswitchsolutions.com >>>>> >>>>> Official FreeSWITCH Sites >>>>> http://www.freeswitch.org >>>>> http://confluence.freeswitch.org >>>>> http://www.cluecon.com >>>>> >>>>> 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 >>>>> >>>> >>>> >>> _________________________________________________________________________ >>> Professional FreeSWITCH Consulting Services: >>> consulting@freeswitch.org >>> http://www.freeswitchsolutions.com >>> >>> Official FreeSWITCH Sites >>> http://www.freeswitch.org >>> http://confluence.freeswitch.org >>> http://www.cluecon.com >>> >>> 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 >> >> >> >> _________________________________________________________________________ >> Professional FreeSWITCH Consulting Services: >> consulting@freeswitch.org >> http://www.freeswitchsolutions.com >> >> Official FreeSWITCH Sites >> http://www.freeswitch.org >> http://confluence.freeswitch.org >> http://www.cluecon.com >> >> 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 >> > > > > _________________________________________________________________________ > Professional FreeSWITCH Consulting Services: > consulting@freeswitch.org > http://www.freeswitchsolutions.com > > Official FreeSWITCH Sites > http://www.freeswitch.org > http://confluence.freeswitch.org > http://www.cluecon.com > > 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 >
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
It say that twillio is not use your inbound gaeway. It may be deleted. If you want route call via inbound gateway, then configure call routing on twilio side. In your case incoming call is processed in context configured in sip_profile '<param name="context" value="public"/>' Alternative it can be setted in directory via '<variable name="user_context" value="targed_context"/>' On Tue, Oct 6, 2015 at 4:07 PM, Michael Nielsen <mic.niel84@gmail.com> wrote:
I did have Twilio IP's in ACL - as their guide told me to. Removing them gives me the following error: "Rejected by acl "domains". Falling back to Digest auth."
I do have a twilio.xml in my /sip_profiles/external/ directory and this does work for outbound calls.
On Tue, Oct 6, 2015 at 12:57 PM, Sergey Safarov <s.safarov@gmail.com> wrote:
I has two FS serves "client" and provider. On client configired gateway. On server user in directory.
On servers I take command "originate user/fs2@gateways.rcsnet.ru &park()" Below two string from FS log
10:31:55.818435 [NOTICE] switch_channel.c:1055 New Channel sofia/external/ 0000000000@gateways.rcsnet.ru [6bc096cb-b903-4b47-9a9b-3fba54c10d6a] [INFO] mod_dialplan_xml.c:635 Processing <0000000000>->fs2 in context target_context
"target_context" is value of '<param name="context" value="target_context"/>' in gateway config file.
Tested on 7add4b2 commit
Think you has disable authorization or configure twilio server IP addess in ACL. Locate this changes and revert it back.
On Tue, Oct 6, 2015 at 12:05 PM, Michael Nielsen <mic.niel84@gmail.com> wrote:
I just did - change to 5080 - and nothing else happens. It still gets routed directly to the public context - without getting "catched" by the gateway-config.
I've tried to use the extension parameter in the gateway and route calls from Twilio directly to 1000@my-domain.com:5080, still nothing else happens.
On Tue, Oct 6, 2015 at 9:59 AM, Stanislav Sinyagin <ssinyagin@gmail.com> wrote:
Well, if your URL points to 5060, then yes, you need to change it to 5080 :-))
On Tue, Oct 6, 2015 at 9:47 AM, Michael Nielsen <mic.niel84@gmail.com> wrote:
I can only give Twilio an url. But I am able to change the default Twilio uses, as an example to 5080. Would that trigger the external gateway perhaps?
On Tuesday, October 6, 2015, Stanislav Sinyagin <ssinyagin@gmail.com> wrote:
but what exactly is configured on twilio side? I guess it should be configurable where it should send calls
On Tue, Oct 6, 2015 at 9:27 AM, Michael Nielsen <mic.niel84@gmail.com > wrote:
> If I disable registration on my twilio-inbound, it does not fail - > however - incoming calls are still not "catched" by my twilio-inbound > gateway profile. It still lands in the public context without any variables > set. > > On Tue, Oct 6, 2015 at 5:57 AM, Sergey Safarov <s.safarov@gmail.com> > wrote: > >> If disable registration on inbound gateway, then is possible >> receive inbound call? >> >> On Mon, Oct 5, 2015, 22:45 Michael Nielsen <mic.niel84@gmail.com> >> wrote: >> >>> Twilio is just taking a sip address as termination address. In >>> this case my domain which FS runs on. >>> Apparently, Twilio is sending calls to the standard 5060 port - >>> which then lands in my public context. >>> >>> On Monday, October 5, 2015, Stanislav Sinyagin < >>> ssinyagin@gmail.com> wrote: >>> >>>> in your pastebin, you seem to receive the call on your internal >>>> profile (port 5060): >>>> 11:18:58.277709 [DEBUG] sofia.c:9229 sofia/internal/+ >>>> 4432445867@sip.ie1.twilio.com receiving invite from >>>> 54.171.127.192:5060 >>>> >>>> >>>> so, what exactly is configured on both sides? The external >>>> profile is usually on the port 5080. >>>> >>>> >>>> >>>> On Mon, Oct 5, 2015 at 6:26 PM, Michael Nielsen < >>>> mic.niel84@gmail.com> wrote: >>>> >>>>> Here's as log from an incoming call from Twilio: >>>>> http://pastebin.com/n0de7jhv >>>>> >>>>> My guess is the problem is with line 33: "Processing >>>>> +4432445867 <+4432445867>->+44213395867 in context public" >>>>> and it fails on line 40: "Regex (FAIL) [gateway_inbound] >>>>> ${target_context}() =~ /^[a-z]/ break=on-false" >>>>> due to the fact that there aren't set any ${target_context} >>>>> variable. >>>>> >>>>> I've added the Twilio inbound gateway as described in the Twilio >>>>> guide, but adding it, removing it etc. doesn't change anything at all. >>>>> To the Twilio-Inbound gateway I've added the variable >>>>> ${target_context} according to this guide: >>>>> https://github.com/voxserv/freeswitch_conf_minimal/blob/master/docs/tutorial... >>>>> >>>>> So my guess is that the Twilio-Inbound gateway aren't being used >>>>> - however - calls are routed to my FS. >>>>> >>>>> On Sun, Oct 4, 2015 at 10:15 PM, Michael Nielsen < >>>>> mic.niel84@gmail.com> wrote: >>>>> >>>>>> I'll create some logs tomorrow. >>>>>> >>>>>> Just to clarify: >>>>>> - Calls are routes from Twilio to my FS >>>>>> - My FS is a clean installation, 1.6.2 >>>>>> - I've used Twilio's guide for setting up gateways, inbound and >>>>>> outbound >>>>>> - Outbound calls are routed correctly >>>>>> - Inbound calls are as mentioned routes to my FS, but my >>>>>> Twilio-inbound doesn't seem to have anything to do with it, therefor, I'm >>>>>> not able to set any variables in incoming calls from Twilio so I can detect >>>>>> them in my public context and transfer them to my default context. >>>>>> >>>>>> I don't want to route all calls in my public context to my >>>>>> default context, this would open a security issue. Only Twilio calls should >>>>>> be handled in such a manner. >>>>>> That's my challenge. >>>>>> >>>>>> >>>>>> On Sunday, October 4, 2015, Sergey Safarov <s.safarov@gmail.com> >>>>>> wrote: >>>>>> >>>>>>> Inbound call can be received >>>>>>> 1) if twillio guys configure gateway to route incomes calls to >>>>>>> you >>>>>>> 2) or if FS provide information how to route call for you >>>>>>> >>>>>>> After reading gateway config files, I has found that used >>>>>>> second case "FS provides information how to route calls via registration >>>>>>> mechanism". >>>>>>> >>>>>>> Please: >>>>>>> - configure clean FS host as described in twilio manuals; >>>>>>> - enable siptrace; >>>>>>> - enable debug log; >>>>>>> - make incoming call; >>>>>>> - attach debug log in respond to this message. >>>>>>> >>>>>>> I try help you >>>>>>> >>>>>>> >>>>>>> On Sun, Oct 4, 2015 at 2:37 PM, Michael Nielsen < >>>>>>> mic.niel84@gmail.com> wrote: >>>>>>> >>>>>>>> Still no luck. >>>>>>>> Any other ideas on how to "catch" the calls from the public >>>>>>>> context in FS? >>>>>>>> My goal is to transfer all calls from Twilio to my default >>>>>>>> context. >>>>>>>> >>>>>>>> >>>>>>>> On Saturday, October 3, 2015, Michael Nielsen < >>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>> >>>>>>>>> Looking at their guide for secure setup: >>>>>>>>> https://www.twilio.com/resources/images/docs/Twilio-Freeswitch.pdf >>>>>>>>> they've added <param name="register" value="false"/> >>>>>>>>> When I do this, registering doesn't fail (obviously), but >>>>>>>>> inbound calls are still not registered as coming from twilio... They still >>>>>>>>> land directly in the public context without the variables set correctly. >>>>>>>>> >>>>>>>>> On Sat, Oct 3, 2015 at 11:58 AM, Michael Nielsen < >>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>> >>>>>>>>>> When adding the extension, I get the following - even >>>>>>>>>> though my username and password etc. are correct as they work for the >>>>>>>>>> outbound gateway...: >>>>>>>>>> >>>>>>>>>> twilio-inbound Failed Registration [908] >>>>>>>>>> >>>>>>>>>> On Sat, Oct 3, 2015 at 11:57 AM, Michael Nielsen < >>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>> >>>>>>>>>>> I see. >>>>>>>>>>> Does it matter that I don't have an extension called 1000 >>>>>>>>>>> in my FS, nor in my Twilio account? >>>>>>>>>>> >>>>>>>>>>> On Fri, Oct 2, 2015 at 11:34 PM, Ahmed Habiba < >>>>>>>>>>> ahabiba@gmail.com> wrote: >>>>>>>>>>> >>>>>>>>>>>> if you have a deep look at inbound gateway it is for >>>>>>>>>>>> receiving calls from Twilio as you can see below, this line informing >>>>>>>>>>>> freeswitch where to route inkling call. >>>>>>>>>>>> >>>>>>>>>>>> <param name="extension" value="1000"/> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> *From: *Michael Nielsen <mic.niel84@gmail.com> >>>>>>>>>>>> *Date: *October 2, 2015 at 11:24:51 PM GMT+3 >>>>>>>>>>>> *To: *FreeSWITCH Users Help < >>>>>>>>>>>> freeswitch-users@lists.freeswitch.org> >>>>>>>>>>>> *Subject: **Re: [Freeswitch-users] Freeswitch and twilio* >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Outbound works fine. >>>>>>>>>>>> >>>>>>>>>>>> Without having the inbound gateway calls are still routed >>>>>>>>>>>> to my FS to my public context from Twilio. >>>>>>>>>>>> Adding the twilio-inbound doesn't seem to change >>>>>>>>>>>> anything...? >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Friday, October 2, 2015, Brian West < >>>>>>>>>>>> brian@freeswitch.org> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Well you'd send outbound calls out the outbound and the >>>>>>>>>>>>> inbound one is just to register with twilio so they know where to send your >>>>>>>>>>>>> inbound calls. Nothing more. >>>>>>>>>>>>> >>>>>>>>>>>>> On Fri, Oct 2, 2015 at 1:46 PM, Michael Nielsen < >>>>>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> I'm trying to setup twilio as gateway following this >>>>>>>>>>>>>> guide: >>>>>>>>>>>>>> >>>>>>>>>>>>>> https://www.twilio.com/docs/sip-trunking/sample-configuration#freeswitch >>>>>>>>>>>>>> >>>>>>>>>>>>>> In their example of twiliotrunk.xml they have >>>>>>>>>>>>>> twilio-inbound and twilio-outbound. >>>>>>>>>>>>>> >>>>>>>>>>>>>> What is the difference between the two gateways? I know >>>>>>>>>>>>>> their names indicate inbound and outbound calling, but how can Freeswitch >>>>>>>>>>>>>> tell the difference between them. Especially how can Freeswitch now to use >>>>>>>>>>>>>> twilio-inbound for incoming calls from twilio and not just twilit-outbound >>>>>>>>>>>>>> as the only difference is register-proxy and expire-seconds between the two? >>>>>>>>>>>>>> >>>>>>>>>>>>>> Make sense? >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> _________________________________________________________________________ >>>>>>>>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>>>>>>>> consulting@freeswitch.org >>>>>>>>>>>>>> http://www.freeswitchsolutions.com >>>>>>>>>>>>>> >>>>>>>>>>>>>> Official FreeSWITCH Sites >>>>>>>>>>>>>> http://www.freeswitch.org >>>>>>>>>>>>>> http://confluence.freeswitch.org >>>>>>>>>>>>>> http://www.cluecon.com >>>>>>>>>>>>>> >>>>>>>>>>>>>> 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 >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> -- >>>>>>>>>>>>> >>>>>>>>>>>>> *Brian West* >>>>>>>>>>>>> brian@freeswitch.org >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> *Twitter: @FreeSWITCH , @briankwest* >>>>>>>>>>>>> http://www.freeswitchbook.com >>>>>>>>>>>>> http://www.freeswitchcookbook.com >>>>>>>>>>>>> >>>>>>>>>>>>> Got Bugs? Report them here <https://freeswitch.org/jira>! >>>>>>>>>>>>> | Reddit: /r/freeswitch >>>>>>>>>>>>> <https://www.reddit.com/r/freeswitch> >>>>>>>>>>>>> >>>>>>>>>>>>> *T:*+19184209001 | *F:*+19184209002 | *M:*+1918424WEST >>>>>>>>>>>>> (9378) >>>>>>>>>>>>> *iNUM:*+883 5100 1420 9001 | *ISN:*410*543 | *Skype:* >>>>>>>>>>>>> briankwest >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> 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 >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> _________________________________________________________________________ >>>>>>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>>>>>> consulting@freeswitch.org >>>>>>>>>>>> http://www.freeswitchsolutions.com >>>>>>>>>>>> >>>>>>>>>>>> Official FreeSWITCH Sites >>>>>>>>>>>> http://www.freeswitch.org >>>>>>>>>>>> http://confluence.freeswitch.org >>>>>>>>>>>> http://www.cluecon.com >>>>>>>>>>>> >>>>>>>>>>>> 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 >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> _________________________________________________________________________ >>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>> consulting@freeswitch.org >>>>>>>> http://www.freeswitchsolutions.com >>>>>>>> >>>>>>>> Official FreeSWITCH Sites >>>>>>>> http://www.freeswitch.org >>>>>>>> http://confluence.freeswitch.org >>>>>>>> http://www.cluecon.com >>>>>>>> >>>>>>>> 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 >>>>>>>> >>>>>>> >>>>>>> >>>>> >>>>> >>>>> _________________________________________________________________________ >>>>> Professional FreeSWITCH Consulting Services: >>>>> consulting@freeswitch.org >>>>> http://www.freeswitchsolutions.com >>>>> >>>>> Official FreeSWITCH Sites >>>>> http://www.freeswitch.org >>>>> http://confluence.freeswitch.org >>>>> http://www.cluecon.com >>>>> >>>>> 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 >>>>> >>>> >>>> >>> _________________________________________________________________________ >>> Professional FreeSWITCH Consulting Services: >>> consulting@freeswitch.org >>> http://www.freeswitchsolutions.com >>> >>> Official FreeSWITCH Sites >>> http://www.freeswitch.org >>> http://confluence.freeswitch.org >>> http://www.cluecon.com >>> >>> 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 >> >> >> >> _________________________________________________________________________ >> Professional FreeSWITCH Consulting Services: >> consulting@freeswitch.org >> http://www.freeswitchsolutions.com >> >> Official FreeSWITCH Sites >> http://www.freeswitch.org >> http://confluence.freeswitch.org >> http://www.cluecon.com >> >> 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 >> > > > > _________________________________________________________________________ > Professional FreeSWITCH Consulting Services: > consulting@freeswitch.org > http://www.freeswitchsolutions.com > > Official FreeSWITCH Sites > http://www.freeswitch.org > http://confluence.freeswitch.org > http://www.cluecon.com > > 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 >
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
If used directory, then add "cidr" attribute to user record. Example <user id="twilio" cidr="27.12.2.5/32"> On Tue, Oct 6, 2015 at 4:43 PM, Sergey Safarov <s.safarov@gmail.com> wrote:
It say that twillio is not use your inbound gaeway. It may be deleted. If you want route call via inbound gateway, then configure call routing on twilio side.
In your case incoming call is processed in context configured in sip_profile '<param name="context" value="public"/>'
Alternative it can be setted in directory via '<variable name="user_context" value="targed_context"/>'
On Tue, Oct 6, 2015 at 4:07 PM, Michael Nielsen <mic.niel84@gmail.com> wrote:
I did have Twilio IP's in ACL - as their guide told me to. Removing them gives me the following error: "Rejected by acl "domains". Falling back to Digest auth."
I do have a twilio.xml in my /sip_profiles/external/ directory and this does work for outbound calls.
On Tue, Oct 6, 2015 at 12:57 PM, Sergey Safarov <s.safarov@gmail.com> wrote:
I has two FS serves "client" and provider. On client configired gateway. On server user in directory.
On servers I take command "originate user/fs2@gateways.rcsnet.ru &park()" Below two string from FS log
10:31:55.818435 [NOTICE] switch_channel.c:1055 New Channel sofia/external/0000000000@gateways.rcsnet.ru [6bc096cb-b903-4b47-9a9b-3fba54c10d6a] [INFO] mod_dialplan_xml.c:635 Processing <0000000000>->fs2 in context target_context
"target_context" is value of '<param name="context" value="target_context"/>' in gateway config file.
Tested on 7add4b2 commit
Think you has disable authorization or configure twilio server IP addess in ACL. Locate this changes and revert it back.
On Tue, Oct 6, 2015 at 12:05 PM, Michael Nielsen <mic.niel84@gmail.com> wrote:
I just did - change to 5080 - and nothing else happens. It still gets routed directly to the public context - without getting "catched" by the gateway-config.
I've tried to use the extension parameter in the gateway and route calls from Twilio directly to 1000@my-domain.com:5080, still nothing else happens.
On Tue, Oct 6, 2015 at 9:59 AM, Stanislav Sinyagin <ssinyagin@gmail.com
wrote:
Well, if your URL points to 5060, then yes, you need to change it to 5080 :-))
On Tue, Oct 6, 2015 at 9:47 AM, Michael Nielsen <mic.niel84@gmail.com> wrote:
I can only give Twilio an url. But I am able to change the default Twilio uses, as an example to 5080. Would that trigger the external gateway perhaps?
On Tuesday, October 6, 2015, Stanislav Sinyagin <ssinyagin@gmail.com> wrote:
> but what exactly is configured on twilio side? I guess it should be > configurable where it should send calls > > On Tue, Oct 6, 2015 at 9:27 AM, Michael Nielsen < > mic.niel84@gmail.com> wrote: > >> If I disable registration on my twilio-inbound, it does not fail - >> however - incoming calls are still not "catched" by my twilio-inbound >> gateway profile. It still lands in the public context without any variables >> set. >> >> On Tue, Oct 6, 2015 at 5:57 AM, Sergey Safarov <s.safarov@gmail.com >> > wrote: >> >>> If disable registration on inbound gateway, then is possible >>> receive inbound call? >>> >>> On Mon, Oct 5, 2015, 22:45 Michael Nielsen <mic.niel84@gmail.com> >>> wrote: >>> >>>> Twilio is just taking a sip address as termination address. In >>>> this case my domain which FS runs on. >>>> Apparently, Twilio is sending calls to the standard 5060 port - >>>> which then lands in my public context. >>>> >>>> On Monday, October 5, 2015, Stanislav Sinyagin < >>>> ssinyagin@gmail.com> wrote: >>>> >>>>> in your pastebin, you seem to receive the call on your internal >>>>> profile (port 5060): >>>>> 11:18:58.277709 [DEBUG] sofia.c:9229 sofia/internal/+ >>>>> 4432445867@sip.ie1.twilio.com receiving invite from >>>>> 54.171.127.192:5060 >>>>> >>>>> >>>>> so, what exactly is configured on both sides? The external >>>>> profile is usually on the port 5080. >>>>> >>>>> >>>>> >>>>> On Mon, Oct 5, 2015 at 6:26 PM, Michael Nielsen < >>>>> mic.niel84@gmail.com> wrote: >>>>> >>>>>> Here's as log from an incoming call from Twilio: >>>>>> http://pastebin.com/n0de7jhv >>>>>> >>>>>> My guess is the problem is with line 33: "Processing >>>>>> +4432445867 <+4432445867>->+44213395867 in context public" >>>>>> and it fails on line 40: "Regex (FAIL) [gateway_inbound] >>>>>> ${target_context}() =~ /^[a-z]/ break=on-false" >>>>>> due to the fact that there aren't set any ${target_context} >>>>>> variable. >>>>>> >>>>>> I've added the Twilio inbound gateway as described in the >>>>>> Twilio guide, but adding it, removing it etc. doesn't change anything at >>>>>> all. >>>>>> To the Twilio-Inbound gateway I've added the variable >>>>>> ${target_context} according to this guide: >>>>>> https://github.com/voxserv/freeswitch_conf_minimal/blob/master/docs/tutorial... >>>>>> >>>>>> So my guess is that the Twilio-Inbound gateway aren't being >>>>>> used - however - calls are routed to my FS. >>>>>> >>>>>> On Sun, Oct 4, 2015 at 10:15 PM, Michael Nielsen < >>>>>> mic.niel84@gmail.com> wrote: >>>>>> >>>>>>> I'll create some logs tomorrow. >>>>>>> >>>>>>> Just to clarify: >>>>>>> - Calls are routes from Twilio to my FS >>>>>>> - My FS is a clean installation, 1.6.2 >>>>>>> - I've used Twilio's guide for setting up gateways, inbound >>>>>>> and outbound >>>>>>> - Outbound calls are routed correctly >>>>>>> - Inbound calls are as mentioned routes to my FS, but my >>>>>>> Twilio-inbound doesn't seem to have anything to do with it, therefor, I'm >>>>>>> not able to set any variables in incoming calls from Twilio so I can detect >>>>>>> them in my public context and transfer them to my default context. >>>>>>> >>>>>>> I don't want to route all calls in my public context to my >>>>>>> default context, this would open a security issue. Only Twilio calls should >>>>>>> be handled in such a manner. >>>>>>> That's my challenge. >>>>>>> >>>>>>> >>>>>>> On Sunday, October 4, 2015, Sergey Safarov < >>>>>>> s.safarov@gmail.com> wrote: >>>>>>> >>>>>>>> Inbound call can be received >>>>>>>> 1) if twillio guys configure gateway to route incomes calls >>>>>>>> to you >>>>>>>> 2) or if FS provide information how to route call for you >>>>>>>> >>>>>>>> After reading gateway config files, I has found that used >>>>>>>> second case "FS provides information how to route calls via registration >>>>>>>> mechanism". >>>>>>>> >>>>>>>> Please: >>>>>>>> - configure clean FS host as described in twilio manuals; >>>>>>>> - enable siptrace; >>>>>>>> - enable debug log; >>>>>>>> - make incoming call; >>>>>>>> - attach debug log in respond to this message. >>>>>>>> >>>>>>>> I try help you >>>>>>>> >>>>>>>> >>>>>>>> On Sun, Oct 4, 2015 at 2:37 PM, Michael Nielsen < >>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>> >>>>>>>>> Still no luck. >>>>>>>>> Any other ideas on how to "catch" the calls from the public >>>>>>>>> context in FS? >>>>>>>>> My goal is to transfer all calls from Twilio to my default >>>>>>>>> context. >>>>>>>>> >>>>>>>>> >>>>>>>>> On Saturday, October 3, 2015, Michael Nielsen < >>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>> >>>>>>>>>> Looking at their guide for secure setup: >>>>>>>>>> https://www.twilio.com/resources/images/docs/Twilio-Freeswitch.pdf >>>>>>>>>> they've added <param name="register" value="false"/> >>>>>>>>>> When I do this, registering doesn't fail (obviously), but >>>>>>>>>> inbound calls are still not registered as coming from twilio... They still >>>>>>>>>> land directly in the public context without the variables set correctly. >>>>>>>>>> >>>>>>>>>> On Sat, Oct 3, 2015 at 11:58 AM, Michael Nielsen < >>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>> >>>>>>>>>>> When adding the extension, I get the following - even >>>>>>>>>>> though my username and password etc. are correct as they work for the >>>>>>>>>>> outbound gateway...: >>>>>>>>>>> >>>>>>>>>>> twilio-inbound Failed Registration [908] >>>>>>>>>>> >>>>>>>>>>> On Sat, Oct 3, 2015 at 11:57 AM, Michael Nielsen < >>>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>>> >>>>>>>>>>>> I see. >>>>>>>>>>>> Does it matter that I don't have an extension called 1000 >>>>>>>>>>>> in my FS, nor in my Twilio account? >>>>>>>>>>>> >>>>>>>>>>>> On Fri, Oct 2, 2015 at 11:34 PM, Ahmed Habiba < >>>>>>>>>>>> ahabiba@gmail.com> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> if you have a deep look at inbound gateway it is for >>>>>>>>>>>>> receiving calls from Twilio as you can see below, this line informing >>>>>>>>>>>>> freeswitch where to route inkling call. >>>>>>>>>>>>> >>>>>>>>>>>>> <param name="extension" value="1000"/> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> *From: *Michael Nielsen <mic.niel84@gmail.com> >>>>>>>>>>>>> *Date: *October 2, 2015 at 11:24:51 PM GMT+3 >>>>>>>>>>>>> *To: *FreeSWITCH Users Help < >>>>>>>>>>>>> freeswitch-users@lists.freeswitch.org> >>>>>>>>>>>>> *Subject: **Re: [Freeswitch-users] Freeswitch and >>>>>>>>>>>>> twilio* >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> Outbound works fine. >>>>>>>>>>>>> >>>>>>>>>>>>> Without having the inbound gateway calls are still >>>>>>>>>>>>> routed to my FS to my public context from Twilio. >>>>>>>>>>>>> Adding the twilio-inbound doesn't seem to change >>>>>>>>>>>>> anything...? >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> On Friday, October 2, 2015, Brian West < >>>>>>>>>>>>> brian@freeswitch.org> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> Well you'd send outbound calls out the outbound and >>>>>>>>>>>>>> the inbound one is just to register with twilio so they know where to send >>>>>>>>>>>>>> your inbound calls. Nothing more. >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Fri, Oct 2, 2015 at 1:46 PM, Michael Nielsen < >>>>>>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> I'm trying to setup twilio as gateway following this >>>>>>>>>>>>>>> guide: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> https://www.twilio.com/docs/sip-trunking/sample-configuration#freeswitch >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> In their example of twiliotrunk.xml they have >>>>>>>>>>>>>>> twilio-inbound and twilio-outbound. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> What is the difference between the two gateways? I >>>>>>>>>>>>>>> know their names indicate inbound and outbound calling, but how can >>>>>>>>>>>>>>> Freeswitch tell the difference between them. Especially how can Freeswitch >>>>>>>>>>>>>>> now to use twilio-inbound for incoming calls from twilio and not just >>>>>>>>>>>>>>> twilit-outbound as the only difference is register-proxy and expire-seconds >>>>>>>>>>>>>>> between the two? >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Make sense? >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> _________________________________________________________________________ >>>>>>>>>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>>>>>>>>> consulting@freeswitch.org >>>>>>>>>>>>>>> http://www.freeswitchsolutions.com >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Official FreeSWITCH Sites >>>>>>>>>>>>>>> http://www.freeswitch.org >>>>>>>>>>>>>>> http://confluence.freeswitch.org >>>>>>>>>>>>>>> http://www.cluecon.com >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> -- >>>>>>>>>>>>>> >>>>>>>>>>>>>> *Brian West* >>>>>>>>>>>>>> brian@freeswitch.org >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> *Twitter: @FreeSWITCH , @briankwest* >>>>>>>>>>>>>> http://www.freeswitchbook.com >>>>>>>>>>>>>> http://www.freeswitchcookbook.com >>>>>>>>>>>>>> >>>>>>>>>>>>>> Got Bugs? Report them here >>>>>>>>>>>>>> <https://freeswitch.org/jira>! | Reddit: /r/freeswitch >>>>>>>>>>>>>> <https://www.reddit.com/r/freeswitch> >>>>>>>>>>>>>> >>>>>>>>>>>>>> *T:*+19184209001 | *F:*+19184209002 | *M:*+1918424WEST >>>>>>>>>>>>>> (9378) >>>>>>>>>>>>>> *iNUM:*+883 5100 1420 9001 | *ISN:*410*543 | *Skype:* >>>>>>>>>>>>>> briankwest >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>> 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 >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> _________________________________________________________________________ >>>>>>>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>>>>>>> consulting@freeswitch.org >>>>>>>>>>>>> http://www.freeswitchsolutions.com >>>>>>>>>>>>> >>>>>>>>>>>>> Official FreeSWITCH Sites >>>>>>>>>>>>> http://www.freeswitch.org >>>>>>>>>>>>> http://confluence.freeswitch.org >>>>>>>>>>>>> http://www.cluecon.com >>>>>>>>>>>>> >>>>>>>>>>>>> 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 >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> _________________________________________________________________________ >>>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>>> consulting@freeswitch.org >>>>>>>>> http://www.freeswitchsolutions.com >>>>>>>>> >>>>>>>>> Official FreeSWITCH Sites >>>>>>>>> http://www.freeswitch.org >>>>>>>>> http://confluence.freeswitch.org >>>>>>>>> http://www.cluecon.com >>>>>>>>> >>>>>>>>> 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 >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>> >>>>>> >>>>>> _________________________________________________________________________ >>>>>> Professional FreeSWITCH Consulting Services: >>>>>> consulting@freeswitch.org >>>>>> http://www.freeswitchsolutions.com >>>>>> >>>>>> Official FreeSWITCH Sites >>>>>> http://www.freeswitch.org >>>>>> http://confluence.freeswitch.org >>>>>> http://www.cluecon.com >>>>>> >>>>>> 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 >>>>>> >>>>> >>>>> >>>> _________________________________________________________________________ >>>> Professional FreeSWITCH Consulting Services: >>>> consulting@freeswitch.org >>>> http://www.freeswitchsolutions.com >>>> >>>> Official FreeSWITCH Sites >>>> http://www.freeswitch.org >>>> http://confluence.freeswitch.org >>>> http://www.cluecon.com >>>> >>>> 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 >>> >>> >>> >>> _________________________________________________________________________ >>> Professional FreeSWITCH Consulting Services: >>> consulting@freeswitch.org >>> http://www.freeswitchsolutions.com >>> >>> Official FreeSWITCH Sites >>> http://www.freeswitch.org >>> http://confluence.freeswitch.org >>> http://www.cluecon.com >>> >>> 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 >>> >> >> >> >> _________________________________________________________________________ >> Professional FreeSWITCH Consulting Services: >> consulting@freeswitch.org >> http://www.freeswitchsolutions.com >> >> Official FreeSWITCH Sites >> http://www.freeswitch.org >> http://confluence.freeswitch.org >> http://www.cluecon.com >> >> 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 >> > >
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
I'm only able to have Twilio route calls to a URL (such as sip:my-domain.com or sip:1000@my-domain.com:port-number). Whatever I do, I'm not able to get a gateway to register to Twilio. Would it be a correct way to have my sip_profiles/internal.xml use context default instead of public, so I can catch it in that way? All internal should require authentication. Here is some info about Twilio and their trunk setup: https://www.twilio.com/docs/sip-trunking/getting-started My idea of perfect setup would of course to be able to have a sip_profiles/external/twilio.xml which automatically had all incoming calls routed/transfer directly to default context - so my directory-users could receive calls in that manner. On Tue, Oct 6, 2015 at 3:43 PM, Sergey Safarov <s.safarov@gmail.com> wrote:
It say that twillio is not use your inbound gaeway. It may be deleted. If you want route call via inbound gateway, then configure call routing on twilio side.
In your case incoming call is processed in context configured in sip_profile '<param name="context" value="public"/>'
Alternative it can be setted in directory via '<variable name="user_context" value="targed_context"/>'
On Tue, Oct 6, 2015 at 4:07 PM, Michael Nielsen <mic.niel84@gmail.com> wrote:
I did have Twilio IP's in ACL - as their guide told me to. Removing them gives me the following error: "Rejected by acl "domains". Falling back to Digest auth."
I do have a twilio.xml in my /sip_profiles/external/ directory and this does work for outbound calls.
On Tue, Oct 6, 2015 at 12:57 PM, Sergey Safarov <s.safarov@gmail.com> wrote:
I has two FS serves "client" and provider. On client configired gateway. On server user in directory.
On servers I take command "originate user/fs2@gateways.rcsnet.ru &park()" Below two string from FS log
10:31:55.818435 [NOTICE] switch_channel.c:1055 New Channel sofia/external/0000000000@gateways.rcsnet.ru [6bc096cb-b903-4b47-9a9b-3fba54c10d6a] [INFO] mod_dialplan_xml.c:635 Processing <0000000000>->fs2 in context target_context
"target_context" is value of '<param name="context" value="target_context"/>' in gateway config file.
Tested on 7add4b2 commit
Think you has disable authorization or configure twilio server IP addess in ACL. Locate this changes and revert it back.
On Tue, Oct 6, 2015 at 12:05 PM, Michael Nielsen <mic.niel84@gmail.com> wrote:
I just did - change to 5080 - and nothing else happens. It still gets routed directly to the public context - without getting "catched" by the gateway-config.
I've tried to use the extension parameter in the gateway and route calls from Twilio directly to 1000@my-domain.com:5080, still nothing else happens.
On Tue, Oct 6, 2015 at 9:59 AM, Stanislav Sinyagin <ssinyagin@gmail.com
wrote:
Well, if your URL points to 5060, then yes, you need to change it to 5080 :-))
On Tue, Oct 6, 2015 at 9:47 AM, Michael Nielsen <mic.niel84@gmail.com> wrote:
I can only give Twilio an url. But I am able to change the default Twilio uses, as an example to 5080. Would that trigger the external gateway perhaps?
On Tuesday, October 6, 2015, Stanislav Sinyagin <ssinyagin@gmail.com> wrote:
> but what exactly is configured on twilio side? I guess it should be > configurable where it should send calls > > On Tue, Oct 6, 2015 at 9:27 AM, Michael Nielsen < > mic.niel84@gmail.com> wrote: > >> If I disable registration on my twilio-inbound, it does not fail - >> however - incoming calls are still not "catched" by my twilio-inbound >> gateway profile. It still lands in the public context without any variables >> set. >> >> On Tue, Oct 6, 2015 at 5:57 AM, Sergey Safarov <s.safarov@gmail.com >> > wrote: >> >>> If disable registration on inbound gateway, then is possible >>> receive inbound call? >>> >>> On Mon, Oct 5, 2015, 22:45 Michael Nielsen <mic.niel84@gmail.com> >>> wrote: >>> >>>> Twilio is just taking a sip address as termination address. In >>>> this case my domain which FS runs on. >>>> Apparently, Twilio is sending calls to the standard 5060 port - >>>> which then lands in my public context. >>>> >>>> On Monday, October 5, 2015, Stanislav Sinyagin < >>>> ssinyagin@gmail.com> wrote: >>>> >>>>> in your pastebin, you seem to receive the call on your internal >>>>> profile (port 5060): >>>>> 11:18:58.277709 [DEBUG] sofia.c:9229 sofia/internal/+ >>>>> 4432445867@sip.ie1.twilio.com receiving invite from >>>>> 54.171.127.192:5060 >>>>> >>>>> >>>>> so, what exactly is configured on both sides? The external >>>>> profile is usually on the port 5080. >>>>> >>>>> >>>>> >>>>> On Mon, Oct 5, 2015 at 6:26 PM, Michael Nielsen < >>>>> mic.niel84@gmail.com> wrote: >>>>> >>>>>> Here's as log from an incoming call from Twilio: >>>>>> http://pastebin.com/n0de7jhv >>>>>> >>>>>> My guess is the problem is with line 33: "Processing >>>>>> +4432445867 <+4432445867>->+44213395867 in context public" >>>>>> and it fails on line 40: "Regex (FAIL) [gateway_inbound] >>>>>> ${target_context}() =~ /^[a-z]/ break=on-false" >>>>>> due to the fact that there aren't set any ${target_context} >>>>>> variable. >>>>>> >>>>>> I've added the Twilio inbound gateway as described in the >>>>>> Twilio guide, but adding it, removing it etc. doesn't change anything at >>>>>> all. >>>>>> To the Twilio-Inbound gateway I've added the variable >>>>>> ${target_context} according to this guide: >>>>>> https://github.com/voxserv/freeswitch_conf_minimal/blob/master/docs/tutorial... >>>>>> >>>>>> So my guess is that the Twilio-Inbound gateway aren't being >>>>>> used - however - calls are routed to my FS. >>>>>> >>>>>> On Sun, Oct 4, 2015 at 10:15 PM, Michael Nielsen < >>>>>> mic.niel84@gmail.com> wrote: >>>>>> >>>>>>> I'll create some logs tomorrow. >>>>>>> >>>>>>> Just to clarify: >>>>>>> - Calls are routes from Twilio to my FS >>>>>>> - My FS is a clean installation, 1.6.2 >>>>>>> - I've used Twilio's guide for setting up gateways, inbound >>>>>>> and outbound >>>>>>> - Outbound calls are routed correctly >>>>>>> - Inbound calls are as mentioned routes to my FS, but my >>>>>>> Twilio-inbound doesn't seem to have anything to do with it, therefor, I'm >>>>>>> not able to set any variables in incoming calls from Twilio so I can detect >>>>>>> them in my public context and transfer them to my default context. >>>>>>> >>>>>>> I don't want to route all calls in my public context to my >>>>>>> default context, this would open a security issue. Only Twilio calls should >>>>>>> be handled in such a manner. >>>>>>> That's my challenge. >>>>>>> >>>>>>> >>>>>>> On Sunday, October 4, 2015, Sergey Safarov < >>>>>>> s.safarov@gmail.com> wrote: >>>>>>> >>>>>>>> Inbound call can be received >>>>>>>> 1) if twillio guys configure gateway to route incomes calls >>>>>>>> to you >>>>>>>> 2) or if FS provide information how to route call for you >>>>>>>> >>>>>>>> After reading gateway config files, I has found that used >>>>>>>> second case "FS provides information how to route calls via registration >>>>>>>> mechanism". >>>>>>>> >>>>>>>> Please: >>>>>>>> - configure clean FS host as described in twilio manuals; >>>>>>>> - enable siptrace; >>>>>>>> - enable debug log; >>>>>>>> - make incoming call; >>>>>>>> - attach debug log in respond to this message. >>>>>>>> >>>>>>>> I try help you >>>>>>>> >>>>>>>> >>>>>>>> On Sun, Oct 4, 2015 at 2:37 PM, Michael Nielsen < >>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>> >>>>>>>>> Still no luck. >>>>>>>>> Any other ideas on how to "catch" the calls from the public >>>>>>>>> context in FS? >>>>>>>>> My goal is to transfer all calls from Twilio to my default >>>>>>>>> context. >>>>>>>>> >>>>>>>>> >>>>>>>>> On Saturday, October 3, 2015, Michael Nielsen < >>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>> >>>>>>>>>> Looking at their guide for secure setup: >>>>>>>>>> https://www.twilio.com/resources/images/docs/Twilio-Freeswitch.pdf >>>>>>>>>> they've added <param name="register" value="false"/> >>>>>>>>>> When I do this, registering doesn't fail (obviously), but >>>>>>>>>> inbound calls are still not registered as coming from twilio... They still >>>>>>>>>> land directly in the public context without the variables set correctly. >>>>>>>>>> >>>>>>>>>> On Sat, Oct 3, 2015 at 11:58 AM, Michael Nielsen < >>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>> >>>>>>>>>>> When adding the extension, I get the following - even >>>>>>>>>>> though my username and password etc. are correct as they work for the >>>>>>>>>>> outbound gateway...: >>>>>>>>>>> >>>>>>>>>>> twilio-inbound Failed Registration [908] >>>>>>>>>>> >>>>>>>>>>> On Sat, Oct 3, 2015 at 11:57 AM, Michael Nielsen < >>>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>>> >>>>>>>>>>>> I see. >>>>>>>>>>>> Does it matter that I don't have an extension called 1000 >>>>>>>>>>>> in my FS, nor in my Twilio account? >>>>>>>>>>>> >>>>>>>>>>>> On Fri, Oct 2, 2015 at 11:34 PM, Ahmed Habiba < >>>>>>>>>>>> ahabiba@gmail.com> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> if you have a deep look at inbound gateway it is for >>>>>>>>>>>>> receiving calls from Twilio as you can see below, this line informing >>>>>>>>>>>>> freeswitch where to route inkling call. >>>>>>>>>>>>> >>>>>>>>>>>>> <param name="extension" value="1000"/> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> *From: *Michael Nielsen <mic.niel84@gmail.com> >>>>>>>>>>>>> *Date: *October 2, 2015 at 11:24:51 PM GMT+3 >>>>>>>>>>>>> *To: *FreeSWITCH Users Help < >>>>>>>>>>>>> freeswitch-users@lists.freeswitch.org> >>>>>>>>>>>>> *Subject: **Re: [Freeswitch-users] Freeswitch and >>>>>>>>>>>>> twilio* >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> Outbound works fine. >>>>>>>>>>>>> >>>>>>>>>>>>> Without having the inbound gateway calls are still >>>>>>>>>>>>> routed to my FS to my public context from Twilio. >>>>>>>>>>>>> Adding the twilio-inbound doesn't seem to change >>>>>>>>>>>>> anything...? >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> On Friday, October 2, 2015, Brian West < >>>>>>>>>>>>> brian@freeswitch.org> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> Well you'd send outbound calls out the outbound and >>>>>>>>>>>>>> the inbound one is just to register with twilio so they know where to send >>>>>>>>>>>>>> your inbound calls. Nothing more. >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Fri, Oct 2, 2015 at 1:46 PM, Michael Nielsen < >>>>>>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> I'm trying to setup twilio as gateway following this >>>>>>>>>>>>>>> guide: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> https://www.twilio.com/docs/sip-trunking/sample-configuration#freeswitch >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> In their example of twiliotrunk.xml they have >>>>>>>>>>>>>>> twilio-inbound and twilio-outbound. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> What is the difference between the two gateways? I >>>>>>>>>>>>>>> know their names indicate inbound and outbound calling, but how can >>>>>>>>>>>>>>> Freeswitch tell the difference between them. Especially how can Freeswitch >>>>>>>>>>>>>>> now to use twilio-inbound for incoming calls from twilio and not just >>>>>>>>>>>>>>> twilit-outbound as the only difference is register-proxy and expire-seconds >>>>>>>>>>>>>>> between the two? >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Make sense? >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> _________________________________________________________________________ >>>>>>>>>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>>>>>>>>> consulting@freeswitch.org >>>>>>>>>>>>>>> http://www.freeswitchsolutions.com >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Official FreeSWITCH Sites >>>>>>>>>>>>>>> http://www.freeswitch.org >>>>>>>>>>>>>>> http://confluence.freeswitch.org >>>>>>>>>>>>>>> http://www.cluecon.com >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> -- >>>>>>>>>>>>>> >>>>>>>>>>>>>> *Brian West* >>>>>>>>>>>>>> brian@freeswitch.org >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> *Twitter: @FreeSWITCH , @briankwest* >>>>>>>>>>>>>> http://www.freeswitchbook.com >>>>>>>>>>>>>> http://www.freeswitchcookbook.com >>>>>>>>>>>>>> >>>>>>>>>>>>>> Got Bugs? Report them here >>>>>>>>>>>>>> <https://freeswitch.org/jira>! | Reddit: /r/freeswitch >>>>>>>>>>>>>> <https://www.reddit.com/r/freeswitch> >>>>>>>>>>>>>> >>>>>>>>>>>>>> *T:*+19184209001 | *F:*+19184209002 | *M:*+1918424WEST >>>>>>>>>>>>>> (9378) >>>>>>>>>>>>>> *iNUM:*+883 5100 1420 9001 | *ISN:*410*543 | *Skype:* >>>>>>>>>>>>>> briankwest >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>> 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 >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> _________________________________________________________________________ >>>>>>>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>>>>>>> consulting@freeswitch.org >>>>>>>>>>>>> http://www.freeswitchsolutions.com >>>>>>>>>>>>> >>>>>>>>>>>>> Official FreeSWITCH Sites >>>>>>>>>>>>> http://www.freeswitch.org >>>>>>>>>>>>> http://confluence.freeswitch.org >>>>>>>>>>>>> http://www.cluecon.com >>>>>>>>>>>>> >>>>>>>>>>>>> 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 >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> _________________________________________________________________________ >>>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>>> consulting@freeswitch.org >>>>>>>>> http://www.freeswitchsolutions.com >>>>>>>>> >>>>>>>>> Official FreeSWITCH Sites >>>>>>>>> http://www.freeswitch.org >>>>>>>>> http://confluence.freeswitch.org >>>>>>>>> http://www.cluecon.com >>>>>>>>> >>>>>>>>> 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 >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>> >>>>>> >>>>>> _________________________________________________________________________ >>>>>> Professional FreeSWITCH Consulting Services: >>>>>> consulting@freeswitch.org >>>>>> http://www.freeswitchsolutions.com >>>>>> >>>>>> Official FreeSWITCH Sites >>>>>> http://www.freeswitch.org >>>>>> http://confluence.freeswitch.org >>>>>> http://www.cluecon.com >>>>>> >>>>>> 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 >>>>>> >>>>> >>>>> >>>> _________________________________________________________________________ >>>> Professional FreeSWITCH Consulting Services: >>>> consulting@freeswitch.org >>>> http://www.freeswitchsolutions.com >>>> >>>> Official FreeSWITCH Sites >>>> http://www.freeswitch.org >>>> http://confluence.freeswitch.org >>>> http://www.cluecon.com >>>> >>>> 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 >>> >>> >>> >>> _________________________________________________________________________ >>> Professional FreeSWITCH Consulting Services: >>> consulting@freeswitch.org >>> http://www.freeswitchsolutions.com >>> >>> Official FreeSWITCH Sites >>> http://www.freeswitch.org >>> http://confluence.freeswitch.org >>> http://www.cluecon.com >>> >>> 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 >>> >> >> >> >> _________________________________________________________________________ >> Professional FreeSWITCH Consulting Services: >> consulting@freeswitch.org >> http://www.freeswitchsolutions.com >> >> Official FreeSWITCH Sites >> http://www.freeswitch.org >> http://confluence.freeswitch.org >> http://www.cluecon.com >> >> 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 >> > >
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
As I mentioned above we don't support sip registration. On Oct 6, 2015 6:32 PM, "Michael Nielsen" <mic.niel84@gmail.com> wrote:
I'm only able to have Twilio route calls to a URL (such as sip: my-domain.com or sip:1000@my-domain.com:port-number). Whatever I do, I'm not able to get a gateway to register to Twilio.
Would it be a correct way to have my sip_profiles/internal.xml use context default instead of public, so I can catch it in that way? All internal should require authentication.
Here is some info about Twilio and their trunk setup: https://www.twilio.com/docs/sip-trunking/getting-started
My idea of perfect setup would of course to be able to have a sip_profiles/external/twilio.xml which automatically had all incoming calls routed/transfer directly to default context - so my directory-users could receive calls in that manner.
On Tue, Oct 6, 2015 at 3:43 PM, Sergey Safarov <s.safarov@gmail.com> wrote:
It say that twillio is not use your inbound gaeway. It may be deleted. If you want route call via inbound gateway, then configure call routing on twilio side.
In your case incoming call is processed in context configured in sip_profile '<param name="context" value="public"/>'
Alternative it can be setted in directory via '<variable name="user_context" value="targed_context"/>'
On Tue, Oct 6, 2015 at 4:07 PM, Michael Nielsen <mic.niel84@gmail.com> wrote:
I did have Twilio IP's in ACL - as their guide told me to. Removing them gives me the following error: "Rejected by acl "domains". Falling back to Digest auth."
I do have a twilio.xml in my /sip_profiles/external/ directory and this does work for outbound calls.
On Tue, Oct 6, 2015 at 12:57 PM, Sergey Safarov <s.safarov@gmail.com> wrote:
I has two FS serves "client" and provider. On client configired gateway. On server user in directory.
On servers I take command "originate user/fs2@gateways.rcsnet.ru &park()" Below two string from FS log
10:31:55.818435 [NOTICE] switch_channel.c:1055 New Channel sofia/external/0000000000@gateways.rcsnet.ru [6bc096cb-b903-4b47-9a9b-3fba54c10d6a] [INFO] mod_dialplan_xml.c:635 Processing <0000000000>->fs2 in context target_context
"target_context" is value of '<param name="context" value="target_context"/>' in gateway config file.
Tested on 7add4b2 commit
Think you has disable authorization or configure twilio server IP addess in ACL. Locate this changes and revert it back.
On Tue, Oct 6, 2015 at 12:05 PM, Michael Nielsen <mic.niel84@gmail.com> wrote:
I just did - change to 5080 - and nothing else happens. It still gets routed directly to the public context - without getting "catched" by the gateway-config.
I've tried to use the extension parameter in the gateway and route calls from Twilio directly to 1000@my-domain.com:5080, still nothing else happens.
On Tue, Oct 6, 2015 at 9:59 AM, Stanislav Sinyagin < ssinyagin@gmail.com> wrote:
Well, if your URL points to 5060, then yes, you need to change it to 5080 :-))
On Tue, Oct 6, 2015 at 9:47 AM, Michael Nielsen <mic.niel84@gmail.com > wrote:
> I can only give Twilio an url. But I am able to change the default > Twilio uses, as an example to 5080. Would that trigger the external gateway > perhaps? > > > On Tuesday, October 6, 2015, Stanislav Sinyagin <ssinyagin@gmail.com> > wrote: > >> but what exactly is configured on twilio side? I guess it should be >> configurable where it should send calls >> >> On Tue, Oct 6, 2015 at 9:27 AM, Michael Nielsen < >> mic.niel84@gmail.com> wrote: >> >>> If I disable registration on my twilio-inbound, it does not fail - >>> however - incoming calls are still not "catched" by my twilio-inbound >>> gateway profile. It still lands in the public context without any variables >>> set. >>> >>> On Tue, Oct 6, 2015 at 5:57 AM, Sergey Safarov < >>> s.safarov@gmail.com> wrote: >>> >>>> If disable registration on inbound gateway, then is possible >>>> receive inbound call? >>>> >>>> On Mon, Oct 5, 2015, 22:45 Michael Nielsen <mic.niel84@gmail.com> >>>> wrote: >>>> >>>>> Twilio is just taking a sip address as termination address. In >>>>> this case my domain which FS runs on. >>>>> Apparently, Twilio is sending calls to the standard 5060 port - >>>>> which then lands in my public context. >>>>> >>>>> On Monday, October 5, 2015, Stanislav Sinyagin < >>>>> ssinyagin@gmail.com> wrote: >>>>> >>>>>> in your pastebin, you seem to receive the call on your internal >>>>>> profile (port 5060): >>>>>> 11:18:58.277709 [DEBUG] sofia.c:9229 sofia/internal/+ >>>>>> 4432445867@sip.ie1.twilio.com receiving invite from >>>>>> 54.171.127.192:5060 >>>>>> >>>>>> >>>>>> so, what exactly is configured on both sides? The external >>>>>> profile is usually on the port 5080. >>>>>> >>>>>> >>>>>> >>>>>> On Mon, Oct 5, 2015 at 6:26 PM, Michael Nielsen < >>>>>> mic.niel84@gmail.com> wrote: >>>>>> >>>>>>> Here's as log from an incoming call from Twilio: >>>>>>> http://pastebin.com/n0de7jhv >>>>>>> >>>>>>> My guess is the problem is with line 33: "Processing >>>>>>> +4432445867 <+4432445867>->+44213395867 in context public" >>>>>>> and it fails on line 40: "Regex (FAIL) [gateway_inbound] >>>>>>> ${target_context}() =~ /^[a-z]/ break=on-false" >>>>>>> due to the fact that there aren't set any ${target_context} >>>>>>> variable. >>>>>>> >>>>>>> I've added the Twilio inbound gateway as described in the >>>>>>> Twilio guide, but adding it, removing it etc. doesn't change anything at >>>>>>> all. >>>>>>> To the Twilio-Inbound gateway I've added the variable >>>>>>> ${target_context} according to this guide: >>>>>>> https://github.com/voxserv/freeswitch_conf_minimal/blob/master/docs/tutorial... >>>>>>> >>>>>>> So my guess is that the Twilio-Inbound gateway aren't being >>>>>>> used - however - calls are routed to my FS. >>>>>>> >>>>>>> On Sun, Oct 4, 2015 at 10:15 PM, Michael Nielsen < >>>>>>> mic.niel84@gmail.com> wrote: >>>>>>> >>>>>>>> I'll create some logs tomorrow. >>>>>>>> >>>>>>>> Just to clarify: >>>>>>>> - Calls are routes from Twilio to my FS >>>>>>>> - My FS is a clean installation, 1.6.2 >>>>>>>> - I've used Twilio's guide for setting up gateways, inbound >>>>>>>> and outbound >>>>>>>> - Outbound calls are routed correctly >>>>>>>> - Inbound calls are as mentioned routes to my FS, but my >>>>>>>> Twilio-inbound doesn't seem to have anything to do with it, therefor, I'm >>>>>>>> not able to set any variables in incoming calls from Twilio so I can detect >>>>>>>> them in my public context and transfer them to my default context. >>>>>>>> >>>>>>>> I don't want to route all calls in my public context to my >>>>>>>> default context, this would open a security issue. Only Twilio calls should >>>>>>>> be handled in such a manner. >>>>>>>> That's my challenge. >>>>>>>> >>>>>>>> >>>>>>>> On Sunday, October 4, 2015, Sergey Safarov < >>>>>>>> s.safarov@gmail.com> wrote: >>>>>>>> >>>>>>>>> Inbound call can be received >>>>>>>>> 1) if twillio guys configure gateway to route incomes calls >>>>>>>>> to you >>>>>>>>> 2) or if FS provide information how to route call for you >>>>>>>>> >>>>>>>>> After reading gateway config files, I has found that used >>>>>>>>> second case "FS provides information how to route calls via registration >>>>>>>>> mechanism". >>>>>>>>> >>>>>>>>> Please: >>>>>>>>> - configure clean FS host as described in twilio manuals; >>>>>>>>> - enable siptrace; >>>>>>>>> - enable debug log; >>>>>>>>> - make incoming call; >>>>>>>>> - attach debug log in respond to this message. >>>>>>>>> >>>>>>>>> I try help you >>>>>>>>> >>>>>>>>> >>>>>>>>> On Sun, Oct 4, 2015 at 2:37 PM, Michael Nielsen < >>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>> >>>>>>>>>> Still no luck. >>>>>>>>>> Any other ideas on how to "catch" the calls from the public >>>>>>>>>> context in FS? >>>>>>>>>> My goal is to transfer all calls from Twilio to my default >>>>>>>>>> context. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Saturday, October 3, 2015, Michael Nielsen < >>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>> >>>>>>>>>>> Looking at their guide for secure setup: >>>>>>>>>>> https://www.twilio.com/resources/images/docs/Twilio-Freeswitch.pdf >>>>>>>>>>> they've added <param name="register" value="false"/> >>>>>>>>>>> When I do this, registering doesn't fail (obviously), but >>>>>>>>>>> inbound calls are still not registered as coming from twilio... They still >>>>>>>>>>> land directly in the public context without the variables set correctly. >>>>>>>>>>> >>>>>>>>>>> On Sat, Oct 3, 2015 at 11:58 AM, Michael Nielsen < >>>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>>> >>>>>>>>>>>> When adding the extension, I get the following - even >>>>>>>>>>>> though my username and password etc. are correct as they work for the >>>>>>>>>>>> outbound gateway...: >>>>>>>>>>>> >>>>>>>>>>>> twilio-inbound Failed Registration [908] >>>>>>>>>>>> >>>>>>>>>>>> On Sat, Oct 3, 2015 at 11:57 AM, Michael Nielsen < >>>>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> I see. >>>>>>>>>>>>> Does it matter that I don't have an extension called >>>>>>>>>>>>> 1000 in my FS, nor in my Twilio account? >>>>>>>>>>>>> >>>>>>>>>>>>> On Fri, Oct 2, 2015 at 11:34 PM, Ahmed Habiba < >>>>>>>>>>>>> ahabiba@gmail.com> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> if you have a deep look at inbound gateway it is for >>>>>>>>>>>>>> receiving calls from Twilio as you can see below, this line informing >>>>>>>>>>>>>> freeswitch where to route inkling call. >>>>>>>>>>>>>> >>>>>>>>>>>>>> <param name="extension" value="1000"/> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> *From: *Michael Nielsen <mic.niel84@gmail.com> >>>>>>>>>>>>>> *Date: *October 2, 2015 at 11:24:51 PM GMT+3 >>>>>>>>>>>>>> *To: *FreeSWITCH Users Help < >>>>>>>>>>>>>> freeswitch-users@lists.freeswitch.org> >>>>>>>>>>>>>> *Subject: **Re: [Freeswitch-users] Freeswitch and >>>>>>>>>>>>>> twilio* >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> Outbound works fine. >>>>>>>>>>>>>> >>>>>>>>>>>>>> Without having the inbound gateway calls are still >>>>>>>>>>>>>> routed to my FS to my public context from Twilio. >>>>>>>>>>>>>> Adding the twilio-inbound doesn't seem to change >>>>>>>>>>>>>> anything...? >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Friday, October 2, 2015, Brian West < >>>>>>>>>>>>>> brian@freeswitch.org> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> Well you'd send outbound calls out the outbound and >>>>>>>>>>>>>>> the inbound one is just to register with twilio so they know where to send >>>>>>>>>>>>>>> your inbound calls. Nothing more. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Fri, Oct 2, 2015 at 1:46 PM, Michael Nielsen < >>>>>>>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> I'm trying to setup twilio as gateway following this >>>>>>>>>>>>>>>> guide: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> https://www.twilio.com/docs/sip-trunking/sample-configuration#freeswitch >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> In their example of twiliotrunk.xml they have >>>>>>>>>>>>>>>> twilio-inbound and twilio-outbound. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> What is the difference between the two gateways? I >>>>>>>>>>>>>>>> know their names indicate inbound and outbound calling, but how can >>>>>>>>>>>>>>>> Freeswitch tell the difference between them. Especially how can Freeswitch >>>>>>>>>>>>>>>> now to use twilio-inbound for incoming calls from twilio and not just >>>>>>>>>>>>>>>> twilit-outbound as the only difference is register-proxy and expire-seconds >>>>>>>>>>>>>>>> between the two? >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Make sense? >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> _________________________________________________________________________ >>>>>>>>>>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>>>>>>>>>> consulting@freeswitch.org >>>>>>>>>>>>>>>> http://www.freeswitchsolutions.com >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Official FreeSWITCH Sites >>>>>>>>>>>>>>>> http://www.freeswitch.org >>>>>>>>>>>>>>>> http://confluence.freeswitch.org >>>>>>>>>>>>>>>> http://www.cluecon.com >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> *Brian West* >>>>>>>>>>>>>>> brian@freeswitch.org >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> *Twitter: @FreeSWITCH , @briankwest* >>>>>>>>>>>>>>> http://www.freeswitchbook.com >>>>>>>>>>>>>>> http://www.freeswitchcookbook.com >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Got Bugs? Report them here >>>>>>>>>>>>>>> <https://freeswitch.org/jira>! | Reddit: /r/freeswitch >>>>>>>>>>>>>>> <https://www.reddit.com/r/freeswitch> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> *T:*+19184209001 | *F:*+19184209002 | *M:*+1918424WEST >>>>>>>>>>>>>>> (9378) >>>>>>>>>>>>>>> *iNUM:*+883 5100 1420 9001 | *ISN:*410*543 | *Skype:* >>>>>>>>>>>>>>> briankwest >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>> 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 >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> _________________________________________________________________________ >>>>>>>>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>>>>>>>> consulting@freeswitch.org >>>>>>>>>>>>>> http://www.freeswitchsolutions.com >>>>>>>>>>>>>> >>>>>>>>>>>>>> Official FreeSWITCH Sites >>>>>>>>>>>>>> http://www.freeswitch.org >>>>>>>>>>>>>> http://confluence.freeswitch.org >>>>>>>>>>>>>> http://www.cluecon.com >>>>>>>>>>>>>> >>>>>>>>>>>>>> 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 >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> _________________________________________________________________________ >>>>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>>>> consulting@freeswitch.org >>>>>>>>>> http://www.freeswitchsolutions.com >>>>>>>>>> >>>>>>>>>> Official FreeSWITCH Sites >>>>>>>>>> http://www.freeswitch.org >>>>>>>>>> http://confluence.freeswitch.org >>>>>>>>>> http://www.cluecon.com >>>>>>>>>> >>>>>>>>>> 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 >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>> >>>>>>> >>>>>>> _________________________________________________________________________ >>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>> consulting@freeswitch.org >>>>>>> http://www.freeswitchsolutions.com >>>>>>> >>>>>>> Official FreeSWITCH Sites >>>>>>> http://www.freeswitch.org >>>>>>> http://confluence.freeswitch.org >>>>>>> http://www.cluecon.com >>>>>>> >>>>>>> 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 >>>>>>> >>>>>> >>>>>> >>>>> _________________________________________________________________________ >>>>> Professional FreeSWITCH Consulting Services: >>>>> consulting@freeswitch.org >>>>> http://www.freeswitchsolutions.com >>>>> >>>>> Official FreeSWITCH Sites >>>>> http://www.freeswitch.org >>>>> http://confluence.freeswitch.org >>>>> http://www.cluecon.com >>>>> >>>>> 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 >>>> >>>> >>>> >>>> _________________________________________________________________________ >>>> Professional FreeSWITCH Consulting Services: >>>> consulting@freeswitch.org >>>> http://www.freeswitchsolutions.com >>>> >>>> Official FreeSWITCH Sites >>>> http://www.freeswitch.org >>>> http://confluence.freeswitch.org >>>> http://www.cluecon.com >>>> >>>> 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 >>>> >>> >>> >>> >>> _________________________________________________________________________ >>> Professional FreeSWITCH Consulting Services: >>> consulting@freeswitch.org >>> http://www.freeswitchsolutions.com >>> >>> Official FreeSWITCH Sites >>> http://www.freeswitch.org >>> http://confluence.freeswitch.org >>> http://www.cluecon.com >>> >>> 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 >>> >> >> > > _________________________________________________________________________ > Professional FreeSWITCH Consulting Services: > consulting@freeswitch.org > http://www.freeswitchsolutions.com > > Official FreeSWITCH Sites > http://www.freeswitch.org > http://confluence.freeswitch.org > http://www.cluecon.com > > 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 >
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
Just talked with Twilio. They do not support registration, so register should be set to false. I am able to route to port 5080. My log showed that the invite from Twilio came from port 5060 from Twilio but on my FS in landed on port 5080. Twilio also told me not to use 1234@my-domain.com:5080, just my-domain.com:5080. Does this help on how to setup FS external gateway to catch incoming calls from Twilio? I'm kinda stuck on this... On Tuesday, October 6, 2015, Michael Nielsen <mic.niel84@gmail.com> wrote:
I'm only able to have Twilio route calls to a URL (such as sip: my-domain.com or sip:1000@my-domain.com:port-number). Whatever I do, I'm not able to get a gateway to register to Twilio.
Would it be a correct way to have my sip_profiles/internal.xml use context default instead of public, so I can catch it in that way? All internal should require authentication.
Here is some info about Twilio and their trunk setup: https://www.twilio.com/docs/sip-trunking/getting-started
My idea of perfect setup would of course to be able to have a sip_profiles/external/twilio.xml which automatically had all incoming calls routed/transfer directly to default context - so my directory-users could receive calls in that manner.
On Tue, Oct 6, 2015 at 3:43 PM, Sergey Safarov <s.safarov@gmail.com <javascript:_e(%7B%7D,'cvml','s.safarov@gmail.com');>> wrote:
It say that twillio is not use your inbound gaeway. It may be deleted. If you want route call via inbound gateway, then configure call routing on twilio side.
In your case incoming call is processed in context configured in sip_profile '<param name="context" value="public"/>'
Alternative it can be setted in directory via '<variable name="user_context" value="targed_context"/>'
On Tue, Oct 6, 2015 at 4:07 PM, Michael Nielsen <mic.niel84@gmail.com <javascript:_e(%7B%7D,'cvml','mic.niel84@gmail.com');>> wrote:
I did have Twilio IP's in ACL - as their guide told me to. Removing them gives me the following error: "Rejected by acl "domains". Falling back to Digest auth."
I do have a twilio.xml in my /sip_profiles/external/ directory and this does work for outbound calls.
On Tue, Oct 6, 2015 at 12:57 PM, Sergey Safarov <s.safarov@gmail.com <javascript:_e(%7B%7D,'cvml','s.safarov@gmail.com');>> wrote:
I has two FS serves "client" and provider. On client configired gateway. On server user in directory.
On servers I take command "originate user/fs2@gateways.rcsnet.ru <javascript:_e(%7B%7D,'cvml','fs2@gateways.rcsnet.ru');> &park()" Below two string from FS log
10:31:55.818435 [NOTICE] switch_channel.c:1055 New Channel sofia/external/0000000000@gateways.rcsnet.ru <javascript:_e(%7B%7D,'cvml','0000000000@gateways.rcsnet.ru');> [6bc096cb-b903-4b47-9a9b-3fba54c10d6a] [INFO] mod_dialplan_xml.c:635 Processing <0000000000>->fs2 in context target_context
"target_context" is value of '<param name="context" value="target_context"/>' in gateway config file.
Tested on 7add4b2 commit
Think you has disable authorization or configure twilio server IP addess in ACL. Locate this changes and revert it back.
On Tue, Oct 6, 2015 at 12:05 PM, Michael Nielsen <mic.niel84@gmail.com <javascript:_e(%7B%7D,'cvml','mic.niel84@gmail.com');>> wrote:
I just did - change to 5080 - and nothing else happens. It still gets routed directly to the public context - without getting "catched" by the gateway-config.
I've tried to use the extension parameter in the gateway and route calls from Twilio directly to 1000@my-domain.com:5080, still nothing else happens.
On Tue, Oct 6, 2015 at 9:59 AM, Stanislav Sinyagin < ssinyagin@gmail.com <javascript:_e(%7B%7D,'cvml','ssinyagin@gmail.com');>> wrote:
Well, if your URL points to 5060, then yes, you need to change it to 5080 :-))
On Tue, Oct 6, 2015 at 9:47 AM, Michael Nielsen <mic.niel84@gmail.com <javascript:_e(%7B%7D,'cvml','mic.niel84@gmail.com');>> wrote:
> I can only give Twilio an url. But I am able to change the default > Twilio uses, as an example to 5080. Would that trigger the external gateway > perhaps? > > > On Tuesday, October 6, 2015, Stanislav Sinyagin <ssinyagin@gmail.com > <javascript:_e(%7B%7D,'cvml','ssinyagin@gmail.com');>> wrote: > >> but what exactly is configured on twilio side? I guess it should be >> configurable where it should send calls >> >> On Tue, Oct 6, 2015 at 9:27 AM, Michael Nielsen < >> mic.niel84@gmail.com> wrote: >> >>> If I disable registration on my twilio-inbound, it does not fail - >>> however - incoming calls are still not "catched" by my twilio-inbound >>> gateway profile. It still lands in the public context without any variables >>> set. >>> >>> On Tue, Oct 6, 2015 at 5:57 AM, Sergey Safarov < >>> s.safarov@gmail.com> wrote: >>> >>>> If disable registration on inbound gateway, then is possible >>>> receive inbound call? >>>> >>>> On Mon, Oct 5, 2015, 22:45 Michael Nielsen <mic.niel84@gmail.com> >>>> wrote: >>>> >>>>> Twilio is just taking a sip address as termination address. In >>>>> this case my domain which FS runs on. >>>>> Apparently, Twilio is sending calls to the standard 5060 port - >>>>> which then lands in my public context. >>>>> >>>>> On Monday, October 5, 2015, Stanislav Sinyagin < >>>>> ssinyagin@gmail.com> wrote: >>>>> >>>>>> in your pastebin, you seem to receive the call on your internal >>>>>> profile (port 5060): >>>>>> 11:18:58.277709 [DEBUG] sofia.c:9229 sofia/internal/+ >>>>>> 4432445867@sip.ie1.twilio.com receiving invite from >>>>>> 54.171.127.192:5060 >>>>>> >>>>>> >>>>>> so, what exactly is configured on both sides? The external >>>>>> profile is usually on the port 5080. >>>>>> >>>>>> >>>>>> >>>>>> On Mon, Oct 5, 2015 at 6:26 PM, Michael Nielsen < >>>>>> mic.niel84@gmail.com> wrote: >>>>>> >>>>>>> Here's as log from an incoming call from Twilio: >>>>>>> http://pastebin.com/n0de7jhv >>>>>>> >>>>>>> My guess is the problem is with line 33: "Processing >>>>>>> +4432445867 <+4432445867>->+44213395867 in context public" >>>>>>> and it fails on line 40: "Regex (FAIL) [gateway_inbound] >>>>>>> ${target_context}() =~ /^[a-z]/ break=on-false" >>>>>>> due to the fact that there aren't set any ${target_context} >>>>>>> variable. >>>>>>> >>>>>>> I've added the Twilio inbound gateway as described in the >>>>>>> Twilio guide, but adding it, removing it etc. doesn't change anything at >>>>>>> all. >>>>>>> To the Twilio-Inbound gateway I've added the variable >>>>>>> ${target_context} according to this guide: >>>>>>> https://github.com/voxserv/freeswitch_conf_minimal/blob/master/docs/tutorial... >>>>>>> >>>>>>> So my guess is that the Twilio-Inbound gateway aren't being >>>>>>> used - however - calls are routed to my FS. >>>>>>> >>>>>>> On Sun, Oct 4, 2015 at 10:15 PM, Michael Nielsen < >>>>>>> mic.niel84@gmail.com> wrote: >>>>>>> >>>>>>>> I'll create some logs tomorrow. >>>>>>>> >>>>>>>> Just to clarify: >>>>>>>> - Calls are routes from Twilio to my FS >>>>>>>> - My FS is a clean installation, 1.6.2 >>>>>>>> - I've used Twilio's guide for setting up gateways, inbound >>>>>>>> and outbound >>>>>>>> - Outbound calls are routed correctly >>>>>>>> - Inbound calls are as mentioned routes to my FS, but my >>>>>>>> Twilio-inbound doesn't seem to have anything to do with it, therefor, I'm >>>>>>>> not able to set any variables in incoming calls from Twilio so I can detect >>>>>>>> them in my public context and transfer them to my default context. >>>>>>>> >>>>>>>> I don't want to route all calls in my public context to my >>>>>>>> default context, this would open a security issue. Only Twilio calls should >>>>>>>> be handled in such a manner. >>>>>>>> That's my challenge. >>>>>>>> >>>>>>>> >>>>>>>> On Sunday, October 4, 2015, Sergey Safarov < >>>>>>>> s.safarov@gmail.com> wrote: >>>>>>>> >>>>>>>>> Inbound call can be received >>>>>>>>> 1) if twillio guys configure gateway to route incomes calls >>>>>>>>> to you >>>>>>>>> 2) or if FS provide information how to route call for you >>>>>>>>> >>>>>>>>> After reading gateway config files, I has found that used >>>>>>>>> second case "FS provides information how to route calls via registration >>>>>>>>> mechanism". >>>>>>>>> >>>>>>>>> Please: >>>>>>>>> - configure clean FS host as described in twilio manuals; >>>>>>>>> - enable siptrace; >>>>>>>>> - enable debug log; >>>>>>>>> - make incoming call; >>>>>>>>> - attach debug log in respond to this message. >>>>>>>>> >>>>>>>>> I try help you >>>>>>>>> >>>>>>>>> >>>>>>>>> On Sun, Oct 4, 2015 at 2:37 PM, Michael Nielsen < >>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>> >>>>>>>>>> Still no luck. >>>>>>>>>> Any other ideas on how to "catch" the calls from the public >>>>>>>>>> context in FS? >>>>>>>>>> My goal is to transfer all calls from Twilio to my default >>>>>>>>>> context. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Saturday, October 3, 2015, Michael Nielsen < >>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>> >>>>>>>>>>> Looking at their guide for secure setup: >>>>>>>>>>> https://www.twilio.com/resources/images/docs/Twilio-Freeswitch.pdf >>>>>>>>>>> they've added <param name="register" value="false"/> >>>>>>>>>>> When I do this, registering doesn't fail (obviously), but >>>>>>>>>>> inbound calls are still not registered as coming from twilio... They still >>>>>>>>>>> land directly in the public context without the variables set correctly. >>>>>>>>>>> >>>>>>>>>>> On Sat, Oct 3, 2015 at 11:58 AM, Michael Nielsen < >>>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>>> >>>>>>>>>>>> When adding the extension, I get the following - even >>>>>>>>>>>> though my username and password etc. are correct as they work for the >>>>>>>>>>>> outbound gateway...: >>>>>>>>>>>> >>>>>>>>>>>> twilio-inbound Failed Registration [908] >>>>>>>>>>>> >>>>>>>>>>>> On Sat, Oct 3, 2015 at 11:57 AM, Michael Nielsen < >>>>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> I see. >>>>>>>>>>>>> Does it matter that I don't have an extension called >>>>>>>>>>>>> 1000 in my FS, nor in my Twilio account? >>>>>>>>>>>>> >>>>>>>>>>>>> On Fri, Oct 2, 2015 at 11:34 PM, Ahmed Habiba < >>>>>>>>>>>>> ahabiba@gmail.com> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> if you have a deep look at inbound gateway it is for >>>>>>>>>>>>>> receiving calls from Twilio as you can see below, this line informing >>>>>>>>>>>>>> freeswitch where to route inkling call. >>>>>>>>>>>>>> >>>>>>>>>>>>>> <param name="extension" value="1000"/> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> *From: *Michael Nielsen <mic.niel84@gmail.com> >>>>>>>>>>>>>> *Date: *October 2, 2015 at 11:24:51 PM GMT+3 >>>>>>>>>>>>>> *To: *FreeSWITCH Users Help < >>>>>>>>>>>>>> freeswitch-users@lists.freeswitch.org> >>>>>>>>>>>>>> *Subject: **Re: [Freeswitch-users] Freeswitch and >>>>>>>>>>>>>> twilio* >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> Outbound works fine. >>>>>>>>>>>>>> >>>>>>>>>>>>>> Without having the inbound gateway calls are still >>>>>>>>>>>>>> routed to my FS to my public context from Twilio. >>>>>>>>>>>>>> Adding the twilio-inbound doesn't seem to change >>>>>>>>>>>>>> anything...? >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Friday, October 2, 2015, Brian West < >>>>>>>>>>>>>> brian@freeswitch.org> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> Well you'd send outbound calls out the outbound and >>>>>>>>>>>>>>> the inbound one is just to register with twilio so they know where to send >>>>>>>>>>>>>>> your inbound calls. Nothing more. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Fri, Oct 2, 2015 at 1:46 PM, Michael Nielsen < >>>>>>>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> I'm trying to setup twilio as gateway following this >>>>>>>>>>>>>>>> guide: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> https://www.twilio.com/docs/sip-trunking/sample-configuration#freeswitch >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> In their example of twiliotrunk.xml they have >>>>>>>>>>>>>>>> twilio-inbound and twilio-outbound. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> What is the difference between the two gateways? I >>>>>>>>>>>>>>>> know their names indicate inbound and outbound calling, but how can >>>>>>>>>>>>>>>> Freeswitch tell the difference between them. Especially how can Freeswitch >>>>>>>>>>>>>>>> now to use twilio-inbound for incoming calls from twilio and not just >>>>>>>>>>>>>>>> twilit-outbound as the only difference is register-proxy and expire-seconds >>>>>>>>>>>>>>>> between the two? >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Make sense? >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> _________________________________________________________________________ >>>>>>>>>>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>>>>>>>>>> consulting@freeswitch.org >>>>>>>>>>>>>>>> http://www.freeswitchsolutions.com >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Official FreeSWITCH Sites >>>>>>>>>>>>>>>> http://www.freeswitch.org >>>>>>>>>>>>>>>> http://confluence.freeswitch.org >>>>>>>>>>>>>>>> http://www.cluecon.com >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> *Brian West* >>>>>>>>>>>>>>> brian@freeswitch.org >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> *Twitter: @FreeSWITCH , @briankwest* >>>>>>>>>>>>>>> http://www.freeswitchbook.com >>>>>>>>>>>>>>> http://www.freeswitchcookbook.com >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Got Bugs? Report them here >>>>>>>>>>>>>>> <https://freeswitch.org/jira>! | Reddit: /r/freeswitch >>>>>>>>>>>>>>> <https://www.reddit.com/r/freeswitch> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> *T:*+19184209001 | *F:*+19184209002 | *M:*+1918424WEST >>>>>>>>>>>>>>> (9378) >>>>>>>>>>>>>>> *iNUM:*+883 5100 1420 9001 | *ISN:*410*543 | *Skype:* >>>>>>>>>>>>>>> briankwest >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>> 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 >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> _________________________________________________________________________ >>>>>>>>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>>>>>>>> consulting@freeswitch.org >>>>>>>>>>>>>> http://www.freeswitchsolutions.com >>>>>>>>>>>>>> >>>>>>>>>>>>>> Official FreeSWITCH Sites >>>>>>>>>>>>>> http://www.freeswitch.org >>>>>>>>>>>>>> http://confluence.freeswitch.org >>>>>>>>>>>>>> http://www.cluecon.com >>>>>>>>>>>>>> >>>>>>>>>>>>>> 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 >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> _________________________________________________________________________ >>>>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>>>> consulting@freeswitch.org >>>>>>>>>> http://www.freeswitchsolutions.com >>>>>>>>>> >>>>>>>>>> Official FreeSWITCH Sites >>>>>>>>>> http://www.freeswitch.org >>>>>>>>>> http://confluence.freeswitch.org >>>>>>>>>> http://www.cluecon.com >>>>>>>>>> >>>>>>>>>> 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 >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>> >>>>>>> >>>>>>> _________________________________________________________________________ >>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>> consulting@freeswitch.org >>>>>>> http://www.freeswitchsolutions.com >>>>>>> >>>>>>> Official FreeSWITCH Sites >>>>>>> http://www.freeswitch.org >>>>>>> http://confluence.freeswitch.org >>>>>>> http://www.cluecon.com >>>>>>> >>>>>>> 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 >>>>>>> >>>>>> >>>>>> >>>>> _________________________________________________________________________ >>>>> Professional FreeSWITCH Consulting Services: >>>>> consulting@freeswitch.org >>>>> http://www.freeswitchsolutions.com >>>>> >>>>> Official FreeSWITCH Sites >>>>> http://www.freeswitch.org >>>>> http://confluence.freeswitch.org >>>>> http://www.cluecon.com >>>>> >>>>> 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 >>>> >>>> >>>> >>>> _________________________________________________________________________ >>>> Professional FreeSWITCH Consulting Services: >>>> consulting@freeswitch.org >>>> http://www.freeswitchsolutions.com >>>> >>>> Official FreeSWITCH Sites >>>> http://www.freeswitch.org >>>> http://confluence.freeswitch.org >>>> http://www.cluecon.com >>>> >>>> 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 >>>> >>> >>> >>> >>> _________________________________________________________________________ >>> Professional FreeSWITCH Consulting Services: >>> consulting@freeswitch.org >>> http://www.freeswitchsolutions.com >>> >>> Official FreeSWITCH Sites >>> http://www.freeswitch.org >>> http://confluence.freeswitch.org >>> http://www.cluecon.com >>> >>> 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 >>> >> >> > > _________________________________________________________________________ > Professional FreeSWITCH Consulting Services: > consulting@freeswitch.org > <javascript:_e(%7B%7D,'cvml','consulting@freeswitch.org');> > http://www.freeswitchsolutions.com > > Official FreeSWITCH Sites > http://www.freeswitch.org > http://confluence.freeswitch.org > http://www.cluecon.com > > FreeSWITCH-users mailing list > FreeSWITCH-users@lists.freeswitch.org > <javascript:_e(%7B%7D,'cvml','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 >
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org <javascript:_e(%7B%7D,'cvml','consulting@freeswitch.org');> http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org <javascript:_e(%7B%7D,'cvml','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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org <javascript:_e(%7B%7D,'cvml','consulting@freeswitch.org');> http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org <javascript:_e(%7B%7D,'cvml','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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org <javascript:_e(%7B%7D,'cvml','consulting@freeswitch.org');> http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org <javascript:_e(%7B%7D,'cvml','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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org <javascript:_e(%7B%7D,'cvml','consulting@freeswitch.org');> http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org <javascript:_e(%7B%7D,'cvml','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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org <javascript:_e(%7B%7D,'cvml','consulting@freeswitch.org');> http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org <javascript:_e(%7B%7D,'cvml','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
probably some reading wouldn't be so bad :-) you saw the example for the public profile in my tutorial: <!-- File: dialplan/public/20_inbound_did.xml --> <extension name="0449999990"> <!-- Hotline --> <condition field="destination_number" expression="^0449999990$"> <action application="transfer" data="7000 XML int.example.net"/> </condition> </extension> if it's just a limited number of users, you can set a sequence of such extension statements. You can also combine it with user_exists call and transfer into the internal context after matching the pattern and checking that the user exists. it's no rocket science, really On Tue, Oct 6, 2015 at 9:35 PM, Michael Nielsen <mic.niel84@gmail.com> wrote:
Just talked with Twilio. They do not support registration, so register should be set to false.
I am able to route to port 5080. My log showed that the invite from Twilio came from port 5060 from Twilio but on my FS in landed on port 5080.
Twilio also told me not to use 1234@my-domain.com:5080, just my-domain.com:5080.
Does this help on how to setup FS external gateway to catch incoming calls from Twilio?
I'm kinda stuck on this...
On Tuesday, October 6, 2015, Michael Nielsen <mic.niel84@gmail.com> wrote:
I'm only able to have Twilio route calls to a URL (such as sip: my-domain.com or sip:1000@my-domain.com:port-number). Whatever I do, I'm not able to get a gateway to register to Twilio.
Would it be a correct way to have my sip_profiles/internal.xml use context default instead of public, so I can catch it in that way? All internal should require authentication.
Here is some info about Twilio and their trunk setup: https://www.twilio.com/docs/sip-trunking/getting-started
My idea of perfect setup would of course to be able to have a sip_profiles/external/twilio.xml which automatically had all incoming calls routed/transfer directly to default context - so my directory-users could receive calls in that manner.
On Tue, Oct 6, 2015 at 3:43 PM, Sergey Safarov <s.safarov@gmail.com> wrote:
It say that twillio is not use your inbound gaeway. It may be deleted. If you want route call via inbound gateway, then configure call routing on twilio side.
In your case incoming call is processed in context configured in sip_profile '<param name="context" value="public"/>'
Alternative it can be setted in directory via '<variable name="user_context" value="targed_context"/>'
On Tue, Oct 6, 2015 at 4:07 PM, Michael Nielsen <mic.niel84@gmail.com> wrote:
I did have Twilio IP's in ACL - as their guide told me to. Removing them gives me the following error: "Rejected by acl "domains". Falling back to Digest auth."
I do have a twilio.xml in my /sip_profiles/external/ directory and this does work for outbound calls.
On Tue, Oct 6, 2015 at 12:57 PM, Sergey Safarov <s.safarov@gmail.com> wrote:
I has two FS serves "client" and provider. On client configired gateway. On server user in directory.
On servers I take command "originate user/fs2@gateways.rcsnet.ru &park()" Below two string from FS log
10:31:55.818435 [NOTICE] switch_channel.c:1055 New Channel sofia/external/0000000000@gateways.rcsnet.ru [6bc096cb-b903-4b47-9a9b-3fba54c10d6a] [INFO] mod_dialplan_xml.c:635 Processing <0000000000>->fs2 in context target_context
"target_context" is value of '<param name="context" value="target_context"/>' in gateway config file.
Tested on 7add4b2 commit
Think you has disable authorization or configure twilio server IP addess in ACL. Locate this changes and revert it back.
On Tue, Oct 6, 2015 at 12:05 PM, Michael Nielsen <mic.niel84@gmail.com
wrote:
I just did - change to 5080 - and nothing else happens. It still gets routed directly to the public context - without getting "catched" by the gateway-config.
I've tried to use the extension parameter in the gateway and route calls from Twilio directly to 1000@my-domain.com:5080, still nothing else happens.
On Tue, Oct 6, 2015 at 9:59 AM, Stanislav Sinyagin < ssinyagin@gmail.com> wrote:
> Well, if your URL points to 5060, then yes, you need to change it to > 5080 :-)) > > > > On Tue, Oct 6, 2015 at 9:47 AM, Michael Nielsen < > mic.niel84@gmail.com> wrote: > >> I can only give Twilio an url. But I am able to change the default >> Twilio uses, as an example to 5080. Would that trigger the external gateway >> perhaps? >> >> >> On Tuesday, October 6, 2015, Stanislav Sinyagin < >> ssinyagin@gmail.com> wrote: >> >>> but what exactly is configured on twilio side? I guess it should >>> be configurable where it should send calls >>> >>> On Tue, Oct 6, 2015 at 9:27 AM, Michael Nielsen < >>> mic.niel84@gmail.com> wrote: >>> >>>> If I disable registration on my twilio-inbound, it does not fail >>>> - however - incoming calls are still not "catched" by my twilio-inbound >>>> gateway profile. It still lands in the public context without any variables >>>> set. >>>> >>>> On Tue, Oct 6, 2015 at 5:57 AM, Sergey Safarov < >>>> s.safarov@gmail.com> wrote: >>>> >>>>> If disable registration on inbound gateway, then is possible >>>>> receive inbound call? >>>>> >>>>> On Mon, Oct 5, 2015, 22:45 Michael Nielsen <mic.niel84@gmail.com> >>>>> wrote: >>>>> >>>>>> Twilio is just taking a sip address as termination address. In >>>>>> this case my domain which FS runs on. >>>>>> Apparently, Twilio is sending calls to the standard 5060 port - >>>>>> which then lands in my public context. >>>>>> >>>>>> On Monday, October 5, 2015, Stanislav Sinyagin < >>>>>> ssinyagin@gmail.com> wrote: >>>>>> >>>>>>> in your pastebin, you seem to receive the call on your >>>>>>> internal profile (port 5060): >>>>>>> 11:18:58.277709 [DEBUG] sofia.c:9229 sofia/internal/+ >>>>>>> 4432445867@sip.ie1.twilio.com receiving invite from >>>>>>> 54.171.127.192:5060 >>>>>>> >>>>>>> >>>>>>> so, what exactly is configured on both sides? The external >>>>>>> profile is usually on the port 5080. >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Mon, Oct 5, 2015 at 6:26 PM, Michael Nielsen < >>>>>>> mic.niel84@gmail.com> wrote: >>>>>>> >>>>>>>> Here's as log from an incoming call from Twilio: >>>>>>>> http://pastebin.com/n0de7jhv >>>>>>>> >>>>>>>> My guess is the problem is with line 33: "Processing >>>>>>>> +4432445867 <+4432445867>->+44213395867 in context public" >>>>>>>> and it fails on line 40: "Regex (FAIL) [gateway_inbound] >>>>>>>> ${target_context}() =~ /^[a-z]/ break=on-false" >>>>>>>> due to the fact that there aren't set any ${target_context} >>>>>>>> variable. >>>>>>>> >>>>>>>> I've added the Twilio inbound gateway as described in the >>>>>>>> Twilio guide, but adding it, removing it etc. doesn't change anything at >>>>>>>> all. >>>>>>>> To the Twilio-Inbound gateway I've added the variable >>>>>>>> ${target_context} according to this guide: >>>>>>>> https://github.com/voxserv/freeswitch_conf_minimal/blob/master/docs/tutorial... >>>>>>>> >>>>>>>> So my guess is that the Twilio-Inbound gateway aren't being >>>>>>>> used - however - calls are routed to my FS. >>>>>>>> >>>>>>>> On Sun, Oct 4, 2015 at 10:15 PM, Michael Nielsen < >>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>> >>>>>>>>> I'll create some logs tomorrow. >>>>>>>>> >>>>>>>>> Just to clarify: >>>>>>>>> - Calls are routes from Twilio to my FS >>>>>>>>> - My FS is a clean installation, 1.6.2 >>>>>>>>> - I've used Twilio's guide for setting up gateways, inbound >>>>>>>>> and outbound >>>>>>>>> - Outbound calls are routed correctly >>>>>>>>> - Inbound calls are as mentioned routes to my FS, but my >>>>>>>>> Twilio-inbound doesn't seem to have anything to do with it, therefor, I'm >>>>>>>>> not able to set any variables in incoming calls from Twilio so I can detect >>>>>>>>> them in my public context and transfer them to my default context. >>>>>>>>> >>>>>>>>> I don't want to route all calls in my public context to my >>>>>>>>> default context, this would open a security issue. Only Twilio calls should >>>>>>>>> be handled in such a manner. >>>>>>>>> That's my challenge. >>>>>>>>> >>>>>>>>> >>>>>>>>> On Sunday, October 4, 2015, Sergey Safarov < >>>>>>>>> s.safarov@gmail.com> wrote: >>>>>>>>> >>>>>>>>>> Inbound call can be received >>>>>>>>>> 1) if twillio guys configure gateway to route incomes calls >>>>>>>>>> to you >>>>>>>>>> 2) or if FS provide information how to route call for you >>>>>>>>>> >>>>>>>>>> After reading gateway config files, I has found that used >>>>>>>>>> second case "FS provides information how to route calls via registration >>>>>>>>>> mechanism". >>>>>>>>>> >>>>>>>>>> Please: >>>>>>>>>> - configure clean FS host as described in twilio manuals; >>>>>>>>>> - enable siptrace; >>>>>>>>>> - enable debug log; >>>>>>>>>> - make incoming call; >>>>>>>>>> - attach debug log in respond to this message. >>>>>>>>>> >>>>>>>>>> I try help you >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Sun, Oct 4, 2015 at 2:37 PM, Michael Nielsen < >>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>> >>>>>>>>>>> Still no luck. >>>>>>>>>>> Any other ideas on how to "catch" the calls from the >>>>>>>>>>> public context in FS? >>>>>>>>>>> My goal is to transfer all calls from Twilio to my default >>>>>>>>>>> context. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Saturday, October 3, 2015, Michael Nielsen < >>>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>>> >>>>>>>>>>>> Looking at their guide for secure setup: >>>>>>>>>>>> https://www.twilio.com/resources/images/docs/Twilio-Freeswitch.pdf >>>>>>>>>>>> they've added <param name="register" value="false"/> >>>>>>>>>>>> When I do this, registering doesn't fail (obviously), but >>>>>>>>>>>> inbound calls are still not registered as coming from twilio... They still >>>>>>>>>>>> land directly in the public context without the variables set correctly. >>>>>>>>>>>> >>>>>>>>>>>> On Sat, Oct 3, 2015 at 11:58 AM, Michael Nielsen < >>>>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> When adding the extension, I get the following - even >>>>>>>>>>>>> though my username and password etc. are correct as they work for the >>>>>>>>>>>>> outbound gateway...: >>>>>>>>>>>>> >>>>>>>>>>>>> twilio-inbound Failed Registration [908] >>>>>>>>>>>>> >>>>>>>>>>>>> On Sat, Oct 3, 2015 at 11:57 AM, Michael Nielsen < >>>>>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> I see. >>>>>>>>>>>>>> Does it matter that I don't have an extension called >>>>>>>>>>>>>> 1000 in my FS, nor in my Twilio account? >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Fri, Oct 2, 2015 at 11:34 PM, Ahmed Habiba < >>>>>>>>>>>>>> ahabiba@gmail.com> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> if you have a deep look at inbound gateway it is for >>>>>>>>>>>>>>> receiving calls from Twilio as you can see below, this line informing >>>>>>>>>>>>>>> freeswitch where to route inkling call. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> <param name="extension" value="1000"/> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> *From: *Michael Nielsen <mic.niel84@gmail.com> >>>>>>>>>>>>>>> *Date: *October 2, 2015 at 11:24:51 PM GMT+3 >>>>>>>>>>>>>>> *To: *FreeSWITCH Users Help < >>>>>>>>>>>>>>> freeswitch-users@lists.freeswitch.org> >>>>>>>>>>>>>>> *Subject: **Re: [Freeswitch-users] Freeswitch and >>>>>>>>>>>>>>> twilio* >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Outbound works fine. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Without having the inbound gateway calls are still >>>>>>>>>>>>>>> routed to my FS to my public context from Twilio. >>>>>>>>>>>>>>> Adding the twilio-inbound doesn't seem to change >>>>>>>>>>>>>>> anything...? >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Friday, October 2, 2015, Brian West < >>>>>>>>>>>>>>> brian@freeswitch.org> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Well you'd send outbound calls out the outbound and >>>>>>>>>>>>>>>> the inbound one is just to register with twilio so they know where to send >>>>>>>>>>>>>>>> your inbound calls. Nothing more. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Fri, Oct 2, 2015 at 1:46 PM, Michael Nielsen < >>>>>>>>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> I'm trying to setup twilio as gateway following this >>>>>>>>>>>>>>>>> guide: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> https://www.twilio.com/docs/sip-trunking/sample-configuration#freeswitch >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> In their example of twiliotrunk.xml they have >>>>>>>>>>>>>>>>> twilio-inbound and twilio-outbound. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> What is the difference between the two gateways? I >>>>>>>>>>>>>>>>> know their names indicate inbound and outbound calling, but how can >>>>>>>>>>>>>>>>> Freeswitch tell the difference between them. Especially how can Freeswitch >>>>>>>>>>>>>>>>> now to use twilio-inbound for incoming calls from twilio and not just >>>>>>>>>>>>>>>>> twilit-outbound as the only difference is register-proxy and expire-seconds >>>>>>>>>>>>>>>>> between the two? >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Make sense? >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> _________________________________________________________________________ >>>>>>>>>>>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>>>>>>>>>>> consulting@freeswitch.org >>>>>>>>>>>>>>>>> http://www.freeswitchsolutions.com >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Official FreeSWITCH Sites >>>>>>>>>>>>>>>>> http://www.freeswitch.org >>>>>>>>>>>>>>>>> http://confluence.freeswitch.org >>>>>>>>>>>>>>>>> http://www.cluecon.com >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> *Brian West* >>>>>>>>>>>>>>>> brian@freeswitch.org >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> *Twitter: @FreeSWITCH , @briankwest* >>>>>>>>>>>>>>>> http://www.freeswitchbook.com >>>>>>>>>>>>>>>> http://www.freeswitchcookbook.com >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Got Bugs? Report them here >>>>>>>>>>>>>>>> <https://freeswitch.org/jira>! | Reddit: >>>>>>>>>>>>>>>> /r/freeswitch <https://www.reddit.com/r/freeswitch> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> *T:*+19184209001 | *F:*+19184209002 | *M:*+1918424WEST >>>>>>>>>>>>>>>> (9378) >>>>>>>>>>>>>>>> *iNUM:*+883 5100 1420 9001 | *ISN:*410*543 | *Skype:* >>>>>>>>>>>>>>>> briankwest >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> _________________________________________________________________________ >>>>>>>>>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>>>>>>>>> consulting@freeswitch.org >>>>>>>>>>>>>>> http://www.freeswitchsolutions.com >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Official FreeSWITCH Sites >>>>>>>>>>>>>>> http://www.freeswitch.org >>>>>>>>>>>>>>> http://confluence.freeswitch.org >>>>>>>>>>>>>>> http://www.cluecon.com >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> _________________________________________________________________________ >>>>>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>>>>> consulting@freeswitch.org >>>>>>>>>>> http://www.freeswitchsolutions.com >>>>>>>>>>> >>>>>>>>>>> Official FreeSWITCH Sites >>>>>>>>>>> http://www.freeswitch.org >>>>>>>>>>> http://confluence.freeswitch.org >>>>>>>>>>> http://www.cluecon.com >>>>>>>>>>> >>>>>>>>>>> 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 >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> _________________________________________________________________________ >>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>> consulting@freeswitch.org >>>>>>>> http://www.freeswitchsolutions.com >>>>>>>> >>>>>>>> Official FreeSWITCH Sites >>>>>>>> http://www.freeswitch.org >>>>>>>> http://confluence.freeswitch.org >>>>>>>> http://www.cluecon.com >>>>>>>> >>>>>>>> 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 >>>>>>>> >>>>>>> >>>>>>> >>>>>> _________________________________________________________________________ >>>>>> Professional FreeSWITCH Consulting Services: >>>>>> consulting@freeswitch.org >>>>>> http://www.freeswitchsolutions.com >>>>>> >>>>>> Official FreeSWITCH Sites >>>>>> http://www.freeswitch.org >>>>>> http://confluence.freeswitch.org >>>>>> http://www.cluecon.com >>>>>> >>>>>> 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 >>>>> >>>>> >>>>> >>>>> _________________________________________________________________________ >>>>> Professional FreeSWITCH Consulting Services: >>>>> consulting@freeswitch.org >>>>> http://www.freeswitchsolutions.com >>>>> >>>>> Official FreeSWITCH Sites >>>>> http://www.freeswitch.org >>>>> http://confluence.freeswitch.org >>>>> http://www.cluecon.com >>>>> >>>>> 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 >>>>> >>>> >>>> >>>> >>>> _________________________________________________________________________ >>>> Professional FreeSWITCH Consulting Services: >>>> consulting@freeswitch.org >>>> http://www.freeswitchsolutions.com >>>> >>>> Official FreeSWITCH Sites >>>> http://www.freeswitch.org >>>> http://confluence.freeswitch.org >>>> http://www.cluecon.com >>>> >>>> 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 >>>> >>> >>> >> >> _________________________________________________________________________ >> Professional FreeSWITCH Consulting Services: >> consulting@freeswitch.org >> http://www.freeswitchsolutions.com >> >> Official FreeSWITCH Sites >> http://www.freeswitch.org >> http://confluence.freeswitch.org >> http://www.cluecon.com >> >> 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 >> > > > > _________________________________________________________________________ > Professional FreeSWITCH Consulting Services: > consulting@freeswitch.org > http://www.freeswitchsolutions.com > > Official FreeSWITCH Sites > http://www.freeswitch.org > http://confluence.freeswitch.org > http://www.cluecon.com > > 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 >
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
Just to clarify, by using user_exists things DOES work. But I'm not sure it's the best solution to do a lookup every time a call comes in. I would prefer to automatically having set that everything coming from Twilio should be placed in the default context. On Tue, Oct 6, 2015 at 10:27 PM, Stanislav Sinyagin <ssinyagin@gmail.com> wrote:
probably some reading wouldn't be so bad :-)
you saw the example for the public profile in my tutorial:
<!-- File: dialplan/public/20_inbound_did.xml --> <extension name="0449999990"> <!-- Hotline --> <condition field="destination_number" expression="^0449999990$"> <action application="transfer" data="7000 XML int.example.net"/> </condition> </extension>
if it's just a limited number of users, you can set a sequence of such extension statements. You can also combine it with user_exists call and transfer into the internal context after matching the pattern and checking that the user exists.
it's no rocket science, really
On Tue, Oct 6, 2015 at 9:35 PM, Michael Nielsen <mic.niel84@gmail.com> wrote:
Just talked with Twilio. They do not support registration, so register should be set to false.
I am able to route to port 5080. My log showed that the invite from Twilio came from port 5060 from Twilio but on my FS in landed on port 5080.
Twilio also told me not to use 1234@my-domain.com:5080, just my-domain.com:5080.
Does this help on how to setup FS external gateway to catch incoming calls from Twilio?
I'm kinda stuck on this...
On Tuesday, October 6, 2015, Michael Nielsen <mic.niel84@gmail.com> wrote:
I'm only able to have Twilio route calls to a URL (such as sip: my-domain.com or sip:1000@my-domain.com:port-number). Whatever I do, I'm not able to get a gateway to register to Twilio.
Would it be a correct way to have my sip_profiles/internal.xml use context default instead of public, so I can catch it in that way? All internal should require authentication.
Here is some info about Twilio and their trunk setup: https://www.twilio.com/docs/sip-trunking/getting-started
My idea of perfect setup would of course to be able to have a sip_profiles/external/twilio.xml which automatically had all incoming calls routed/transfer directly to default context - so my directory-users could receive calls in that manner.
On Tue, Oct 6, 2015 at 3:43 PM, Sergey Safarov <s.safarov@gmail.com> wrote:
It say that twillio is not use your inbound gaeway. It may be deleted. If you want route call via inbound gateway, then configure call routing on twilio side.
In your case incoming call is processed in context configured in sip_profile '<param name="context" value="public"/>'
Alternative it can be setted in directory via '<variable name="user_context" value="targed_context"/>'
On Tue, Oct 6, 2015 at 4:07 PM, Michael Nielsen <mic.niel84@gmail.com> wrote:
I did have Twilio IP's in ACL - as their guide told me to. Removing them gives me the following error: "Rejected by acl "domains". Falling back to Digest auth."
I do have a twilio.xml in my /sip_profiles/external/ directory and this does work for outbound calls.
On Tue, Oct 6, 2015 at 12:57 PM, Sergey Safarov <s.safarov@gmail.com> wrote:
I has two FS serves "client" and provider. On client configired gateway. On server user in directory.
On servers I take command "originate user/fs2@gateways.rcsnet.ru &park()" Below two string from FS log
10:31:55.818435 [NOTICE] switch_channel.c:1055 New Channel sofia/external/0000000000@gateways.rcsnet.ru [6bc096cb-b903-4b47-9a9b-3fba54c10d6a] [INFO] mod_dialplan_xml.c:635 Processing <0000000000>->fs2 in context target_context
"target_context" is value of '<param name="context" value="target_context"/>' in gateway config file.
Tested on 7add4b2 commit
Think you has disable authorization or configure twilio server IP addess in ACL. Locate this changes and revert it back.
On Tue, Oct 6, 2015 at 12:05 PM, Michael Nielsen < mic.niel84@gmail.com> wrote:
> I just did - change to 5080 - and nothing else happens. > It still gets routed directly to the public context - without > getting "catched" by the gateway-config. > > I've tried to use the extension parameter in the gateway and route > calls from Twilio directly to 1000@my-domain.com:5080, still > nothing else happens. > > > On Tue, Oct 6, 2015 at 9:59 AM, Stanislav Sinyagin < > ssinyagin@gmail.com> wrote: > >> Well, if your URL points to 5060, then yes, you need to change it >> to 5080 :-)) >> >> >> >> On Tue, Oct 6, 2015 at 9:47 AM, Michael Nielsen < >> mic.niel84@gmail.com> wrote: >> >>> I can only give Twilio an url. But I am able to change the default >>> Twilio uses, as an example to 5080. Would that trigger the external gateway >>> perhaps? >>> >>> >>> On Tuesday, October 6, 2015, Stanislav Sinyagin < >>> ssinyagin@gmail.com> wrote: >>> >>>> but what exactly is configured on twilio side? I guess it should >>>> be configurable where it should send calls >>>> >>>> On Tue, Oct 6, 2015 at 9:27 AM, Michael Nielsen < >>>> mic.niel84@gmail.com> wrote: >>>> >>>>> If I disable registration on my twilio-inbound, it does not fail >>>>> - however - incoming calls are still not "catched" by my twilio-inbound >>>>> gateway profile. It still lands in the public context without any variables >>>>> set. >>>>> >>>>> On Tue, Oct 6, 2015 at 5:57 AM, Sergey Safarov < >>>>> s.safarov@gmail.com> wrote: >>>>> >>>>>> If disable registration on inbound gateway, then is possible >>>>>> receive inbound call? >>>>>> >>>>>> On Mon, Oct 5, 2015, 22:45 Michael Nielsen < >>>>>> mic.niel84@gmail.com> wrote: >>>>>> >>>>>>> Twilio is just taking a sip address as termination address. In >>>>>>> this case my domain which FS runs on. >>>>>>> Apparently, Twilio is sending calls to the standard 5060 port >>>>>>> - which then lands in my public context. >>>>>>> >>>>>>> On Monday, October 5, 2015, Stanislav Sinyagin < >>>>>>> ssinyagin@gmail.com> wrote: >>>>>>> >>>>>>>> in your pastebin, you seem to receive the call on your >>>>>>>> internal profile (port 5060): >>>>>>>> 11:18:58.277709 [DEBUG] sofia.c:9229 sofia/internal/+ >>>>>>>> 4432445867@sip.ie1.twilio.com receiving invite from >>>>>>>> 54.171.127.192:5060 >>>>>>>> >>>>>>>> >>>>>>>> so, what exactly is configured on both sides? The external >>>>>>>> profile is usually on the port 5080. >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Mon, Oct 5, 2015 at 6:26 PM, Michael Nielsen < >>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>> >>>>>>>>> Here's as log from an incoming call from Twilio: >>>>>>>>> http://pastebin.com/n0de7jhv >>>>>>>>> >>>>>>>>> My guess is the problem is with line 33: "Processing >>>>>>>>> +4432445867 <+4432445867>->+44213395867 in context public" >>>>>>>>> and it fails on line 40: "Regex (FAIL) [gateway_inbound] >>>>>>>>> ${target_context}() =~ /^[a-z]/ break=on-false" >>>>>>>>> due to the fact that there aren't set any ${target_context} >>>>>>>>> variable. >>>>>>>>> >>>>>>>>> I've added the Twilio inbound gateway as described in the >>>>>>>>> Twilio guide, but adding it, removing it etc. doesn't change anything at >>>>>>>>> all. >>>>>>>>> To the Twilio-Inbound gateway I've added the variable >>>>>>>>> ${target_context} according to this guide: >>>>>>>>> https://github.com/voxserv/freeswitch_conf_minimal/blob/master/docs/tutorial... >>>>>>>>> >>>>>>>>> So my guess is that the Twilio-Inbound gateway aren't being >>>>>>>>> used - however - calls are routed to my FS. >>>>>>>>> >>>>>>>>> On Sun, Oct 4, 2015 at 10:15 PM, Michael Nielsen < >>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>> >>>>>>>>>> I'll create some logs tomorrow. >>>>>>>>>> >>>>>>>>>> Just to clarify: >>>>>>>>>> - Calls are routes from Twilio to my FS >>>>>>>>>> - My FS is a clean installation, 1.6.2 >>>>>>>>>> - I've used Twilio's guide for setting up gateways, inbound >>>>>>>>>> and outbound >>>>>>>>>> - Outbound calls are routed correctly >>>>>>>>>> - Inbound calls are as mentioned routes to my FS, but my >>>>>>>>>> Twilio-inbound doesn't seem to have anything to do with it, therefor, I'm >>>>>>>>>> not able to set any variables in incoming calls from Twilio so I can detect >>>>>>>>>> them in my public context and transfer them to my default context. >>>>>>>>>> >>>>>>>>>> I don't want to route all calls in my public context to my >>>>>>>>>> default context, this would open a security issue. Only Twilio calls should >>>>>>>>>> be handled in such a manner. >>>>>>>>>> That's my challenge. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Sunday, October 4, 2015, Sergey Safarov < >>>>>>>>>> s.safarov@gmail.com> wrote: >>>>>>>>>> >>>>>>>>>>> Inbound call can be received >>>>>>>>>>> 1) if twillio guys configure gateway to route incomes >>>>>>>>>>> calls to you >>>>>>>>>>> 2) or if FS provide information how to route call for you >>>>>>>>>>> >>>>>>>>>>> After reading gateway config files, I has found that used >>>>>>>>>>> second case "FS provides information how to route calls via registration >>>>>>>>>>> mechanism". >>>>>>>>>>> >>>>>>>>>>> Please: >>>>>>>>>>> - configure clean FS host as described in twilio manuals; >>>>>>>>>>> - enable siptrace; >>>>>>>>>>> - enable debug log; >>>>>>>>>>> - make incoming call; >>>>>>>>>>> - attach debug log in respond to this message. >>>>>>>>>>> >>>>>>>>>>> I try help you >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Sun, Oct 4, 2015 at 2:37 PM, Michael Nielsen < >>>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>>> >>>>>>>>>>>> Still no luck. >>>>>>>>>>>> Any other ideas on how to "catch" the calls from the >>>>>>>>>>>> public context in FS? >>>>>>>>>>>> My goal is to transfer all calls from Twilio to my >>>>>>>>>>>> default context. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Saturday, October 3, 2015, Michael Nielsen < >>>>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Looking at their guide for secure setup: >>>>>>>>>>>>> https://www.twilio.com/resources/images/docs/Twilio-Freeswitch.pdf >>>>>>>>>>>>> they've added <param name="register" value="false"/> >>>>>>>>>>>>> When I do this, registering doesn't fail (obviously), >>>>>>>>>>>>> but inbound calls are still not registered as coming from twilio... They >>>>>>>>>>>>> still land directly in the public context without the variables set >>>>>>>>>>>>> correctly. >>>>>>>>>>>>> >>>>>>>>>>>>> On Sat, Oct 3, 2015 at 11:58 AM, Michael Nielsen < >>>>>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> When adding the extension, I get the following - even >>>>>>>>>>>>>> though my username and password etc. are correct as they work for the >>>>>>>>>>>>>> outbound gateway...: >>>>>>>>>>>>>> >>>>>>>>>>>>>> twilio-inbound Failed Registration [908] >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Sat, Oct 3, 2015 at 11:57 AM, Michael Nielsen < >>>>>>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> I see. >>>>>>>>>>>>>>> Does it matter that I don't have an extension called >>>>>>>>>>>>>>> 1000 in my FS, nor in my Twilio account? >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Fri, Oct 2, 2015 at 11:34 PM, Ahmed Habiba < >>>>>>>>>>>>>>> ahabiba@gmail.com> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> if you have a deep look at inbound gateway it is for >>>>>>>>>>>>>>>> receiving calls from Twilio as you can see below, this line informing >>>>>>>>>>>>>>>> freeswitch where to route inkling call. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> <param name="extension" value="1000"/> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> *From: *Michael Nielsen <mic.niel84@gmail.com> >>>>>>>>>>>>>>>> *Date: *October 2, 2015 at 11:24:51 PM GMT+3 >>>>>>>>>>>>>>>> *To: *FreeSWITCH Users Help < >>>>>>>>>>>>>>>> freeswitch-users@lists.freeswitch.org> >>>>>>>>>>>>>>>> *Subject: **Re: [Freeswitch-users] Freeswitch and >>>>>>>>>>>>>>>> twilio* >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Outbound works fine. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Without having the inbound gateway calls are still >>>>>>>>>>>>>>>> routed to my FS to my public context from Twilio. >>>>>>>>>>>>>>>> Adding the twilio-inbound doesn't seem to change >>>>>>>>>>>>>>>> anything...? >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Friday, October 2, 2015, Brian West < >>>>>>>>>>>>>>>> brian@freeswitch.org> wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Well you'd send outbound calls out the outbound and >>>>>>>>>>>>>>>>> the inbound one is just to register with twilio so they know where to send >>>>>>>>>>>>>>>>> your inbound calls. Nothing more. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> On Fri, Oct 2, 2015 at 1:46 PM, Michael Nielsen < >>>>>>>>>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> I'm trying to setup twilio as gateway following >>>>>>>>>>>>>>>>>> this guide: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> https://www.twilio.com/docs/sip-trunking/sample-configuration#freeswitch >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> In their example of twiliotrunk.xml they have >>>>>>>>>>>>>>>>>> twilio-inbound and twilio-outbound. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> What is the difference between the two gateways? I >>>>>>>>>>>>>>>>>> know their names indicate inbound and outbound calling, but how can >>>>>>>>>>>>>>>>>> Freeswitch tell the difference between them. Especially how can Freeswitch >>>>>>>>>>>>>>>>>> now to use twilio-inbound for incoming calls from twilio and not just >>>>>>>>>>>>>>>>>> twilit-outbound as the only difference is register-proxy and expire-seconds >>>>>>>>>>>>>>>>>> between the two? >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Make sense? >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> _________________________________________________________________________ >>>>>>>>>>>>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>>>>>>>>>>>> consulting@freeswitch.org >>>>>>>>>>>>>>>>>> http://www.freeswitchsolutions.com >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Official FreeSWITCH Sites >>>>>>>>>>>>>>>>>> http://www.freeswitch.org >>>>>>>>>>>>>>>>>> http://confluence.freeswitch.org >>>>>>>>>>>>>>>>>> http://www.cluecon.com >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> *Brian West* >>>>>>>>>>>>>>>>> brian@freeswitch.org >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> *Twitter: @FreeSWITCH , @briankwest* >>>>>>>>>>>>>>>>> http://www.freeswitchbook.com >>>>>>>>>>>>>>>>> http://www.freeswitchcookbook.com >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Got Bugs? Report them here >>>>>>>>>>>>>>>>> <https://freeswitch.org/jira>! | Reddit: >>>>>>>>>>>>>>>>> /r/freeswitch <https://www.reddit.com/r/freeswitch> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> *T:*+19184209001 | *F:*+19184209002 | *M:*+1918424WEST >>>>>>>>>>>>>>>>> (9378) >>>>>>>>>>>>>>>>> *iNUM:*+883 5100 1420 9001 | *ISN:*410*543 | >>>>>>>>>>>>>>>>> *Skype:*briankwest >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> _________________________________________________________________________ >>>>>>>>>>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>>>>>>>>>> consulting@freeswitch.org >>>>>>>>>>>>>>>> http://www.freeswitchsolutions.com >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Official FreeSWITCH Sites >>>>>>>>>>>>>>>> http://www.freeswitch.org >>>>>>>>>>>>>>>> http://confluence.freeswitch.org >>>>>>>>>>>>>>>> http://www.cluecon.com >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> _________________________________________________________________________ >>>>>>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>>>>>> consulting@freeswitch.org >>>>>>>>>>>> http://www.freeswitchsolutions.com >>>>>>>>>>>> >>>>>>>>>>>> Official FreeSWITCH Sites >>>>>>>>>>>> http://www.freeswitch.org >>>>>>>>>>>> http://confluence.freeswitch.org >>>>>>>>>>>> http://www.cluecon.com >>>>>>>>>>>> >>>>>>>>>>>> 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 >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> _________________________________________________________________________ >>>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>>> consulting@freeswitch.org >>>>>>>>> http://www.freeswitchsolutions.com >>>>>>>>> >>>>>>>>> Official FreeSWITCH Sites >>>>>>>>> http://www.freeswitch.org >>>>>>>>> http://confluence.freeswitch.org >>>>>>>>> http://www.cluecon.com >>>>>>>>> >>>>>>>>> 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 >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> _________________________________________________________________________ >>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>> consulting@freeswitch.org >>>>>>> http://www.freeswitchsolutions.com >>>>>>> >>>>>>> Official FreeSWITCH Sites >>>>>>> http://www.freeswitch.org >>>>>>> http://confluence.freeswitch.org >>>>>>> http://www.cluecon.com >>>>>>> >>>>>>> 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 >>>>>> >>>>>> >>>>>> >>>>>> _________________________________________________________________________ >>>>>> Professional FreeSWITCH Consulting Services: >>>>>> consulting@freeswitch.org >>>>>> http://www.freeswitchsolutions.com >>>>>> >>>>>> Official FreeSWITCH Sites >>>>>> http://www.freeswitch.org >>>>>> http://confluence.freeswitch.org >>>>>> http://www.cluecon.com >>>>>> >>>>>> 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 >>>>>> >>>>> >>>>> >>>>> >>>>> _________________________________________________________________________ >>>>> Professional FreeSWITCH Consulting Services: >>>>> consulting@freeswitch.org >>>>> http://www.freeswitchsolutions.com >>>>> >>>>> Official FreeSWITCH Sites >>>>> http://www.freeswitch.org >>>>> http://confluence.freeswitch.org >>>>> http://www.cluecon.com >>>>> >>>>> 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 >>>>> >>>> >>>> >>> >>> _________________________________________________________________________ >>> Professional FreeSWITCH Consulting Services: >>> consulting@freeswitch.org >>> http://www.freeswitchsolutions.com >>> >>> Official FreeSWITCH Sites >>> http://www.freeswitch.org >>> http://confluence.freeswitch.org >>> http://www.cluecon.com >>> >>> 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 >>> >> >> >> >> _________________________________________________________________________ >> Professional FreeSWITCH Consulting Services: >> consulting@freeswitch.org >> http://www.freeswitchsolutions.com >> >> Official FreeSWITCH Sites >> http://www.freeswitch.org >> http://confluence.freeswitch.org >> http://www.cluecon.com >> >> 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 >> > > > > _________________________________________________________________________ > Professional FreeSWITCH Consulting Services: > consulting@freeswitch.org > http://www.freeswitchsolutions.com > > Official FreeSWITCH Sites > http://www.freeswitch.org > http://confluence.freeswitch.org > http://www.cluecon.com > > 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 >
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
On 6 October 2015 at 12:35, Michael Nielsen <mic.niel84@gmail.com> wrote:
I'm kinda stuck on this...
Once you get it all figured out, write out each and every step you took to get it working. The internet will thank you when they're trying, and also you'll be thankful when you need to correct something very late/early in the morning when it breaks. -- ------- inum: 883510009027723 sip: jungleboogie@sip2sip.info xmpp: jungle-boogie@jit.si
Incoming call can captured gateway if only this call for gateway. If you configure only hostname and port on twilio softswitch that call for sip_profile. You can simple remove incoming gateway. It useless for you. Sergey On Tue, Oct 6, 2015 at 10:35 PM, Michael Nielsen <mic.niel84@gmail.com> wrote:
Just talked with Twilio. They do not support registration, so register should be set to false.
I am able to route to port 5080. My log showed that the invite from Twilio came from port 5060 from Twilio but on my FS in landed on port 5080.
Twilio also told me not to use 1234@my-domain.com:5080, just my-domain.com:5080.
Does this help on how to setup FS external gateway to catch incoming calls from Twilio?
I'm kinda stuck on this...
On Tuesday, October 6, 2015, Michael Nielsen <mic.niel84@gmail.com> wrote:
I'm only able to have Twilio route calls to a URL (such as sip: my-domain.com or sip:1000@my-domain.com:port-number). Whatever I do, I'm not able to get a gateway to register to Twilio.
Would it be a correct way to have my sip_profiles/internal.xml use context default instead of public, so I can catch it in that way? All internal should require authentication.
Here is some info about Twilio and their trunk setup: https://www.twilio.com/docs/sip-trunking/getting-started
My idea of perfect setup would of course to be able to have a sip_profiles/external/twilio.xml which automatically had all incoming calls routed/transfer directly to default context - so my directory-users could receive calls in that manner.
On Tue, Oct 6, 2015 at 3:43 PM, Sergey Safarov <s.safarov@gmail.com> wrote:
It say that twillio is not use your inbound gaeway. It may be deleted. If you want route call via inbound gateway, then configure call routing on twilio side.
In your case incoming call is processed in context configured in sip_profile '<param name="context" value="public"/>'
Alternative it can be setted in directory via '<variable name="user_context" value="targed_context"/>'
On Tue, Oct 6, 2015 at 4:07 PM, Michael Nielsen <mic.niel84@gmail.com> wrote:
I did have Twilio IP's in ACL - as their guide told me to. Removing them gives me the following error: "Rejected by acl "domains". Falling back to Digest auth."
I do have a twilio.xml in my /sip_profiles/external/ directory and this does work for outbound calls.
On Tue, Oct 6, 2015 at 12:57 PM, Sergey Safarov <s.safarov@gmail.com> wrote:
I has two FS serves "client" and provider. On client configired gateway. On server user in directory.
On servers I take command "originate user/fs2@gateways.rcsnet.ru &park()" Below two string from FS log
10:31:55.818435 [NOTICE] switch_channel.c:1055 New Channel sofia/external/0000000000@gateways.rcsnet.ru [6bc096cb-b903-4b47-9a9b-3fba54c10d6a] [INFO] mod_dialplan_xml.c:635 Processing <0000000000>->fs2 in context target_context
"target_context" is value of '<param name="context" value="target_context"/>' in gateway config file.
Tested on 7add4b2 commit
Think you has disable authorization or configure twilio server IP addess in ACL. Locate this changes and revert it back.
On Tue, Oct 6, 2015 at 12:05 PM, Michael Nielsen <mic.niel84@gmail.com
wrote:
I just did - change to 5080 - and nothing else happens. It still gets routed directly to the public context - without getting "catched" by the gateway-config.
I've tried to use the extension parameter in the gateway and route calls from Twilio directly to 1000@my-domain.com:5080, still nothing else happens.
On Tue, Oct 6, 2015 at 9:59 AM, Stanislav Sinyagin < ssinyagin@gmail.com> wrote:
> Well, if your URL points to 5060, then yes, you need to change it to > 5080 :-)) > > > > On Tue, Oct 6, 2015 at 9:47 AM, Michael Nielsen < > mic.niel84@gmail.com> wrote: > >> I can only give Twilio an url. But I am able to change the default >> Twilio uses, as an example to 5080. Would that trigger the external gateway >> perhaps? >> >> >> On Tuesday, October 6, 2015, Stanislav Sinyagin < >> ssinyagin@gmail.com> wrote: >> >>> but what exactly is configured on twilio side? I guess it should >>> be configurable where it should send calls >>> >>> On Tue, Oct 6, 2015 at 9:27 AM, Michael Nielsen < >>> mic.niel84@gmail.com> wrote: >>> >>>> If I disable registration on my twilio-inbound, it does not fail >>>> - however - incoming calls are still not "catched" by my twilio-inbound >>>> gateway profile. It still lands in the public context without any variables >>>> set. >>>> >>>> On Tue, Oct 6, 2015 at 5:57 AM, Sergey Safarov < >>>> s.safarov@gmail.com> wrote: >>>> >>>>> If disable registration on inbound gateway, then is possible >>>>> receive inbound call? >>>>> >>>>> On Mon, Oct 5, 2015, 22:45 Michael Nielsen <mic.niel84@gmail.com> >>>>> wrote: >>>>> >>>>>> Twilio is just taking a sip address as termination address. In >>>>>> this case my domain which FS runs on. >>>>>> Apparently, Twilio is sending calls to the standard 5060 port - >>>>>> which then lands in my public context. >>>>>> >>>>>> On Monday, October 5, 2015, Stanislav Sinyagin < >>>>>> ssinyagin@gmail.com> wrote: >>>>>> >>>>>>> in your pastebin, you seem to receive the call on your >>>>>>> internal profile (port 5060): >>>>>>> 11:18:58.277709 [DEBUG] sofia.c:9229 sofia/internal/+ >>>>>>> 4432445867@sip.ie1.twilio.com receiving invite from >>>>>>> 54.171.127.192:5060 >>>>>>> >>>>>>> >>>>>>> so, what exactly is configured on both sides? The external >>>>>>> profile is usually on the port 5080. >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Mon, Oct 5, 2015 at 6:26 PM, Michael Nielsen < >>>>>>> mic.niel84@gmail.com> wrote: >>>>>>> >>>>>>>> Here's as log from an incoming call from Twilio: >>>>>>>> http://pastebin.com/n0de7jhv >>>>>>>> >>>>>>>> My guess is the problem is with line 33: "Processing >>>>>>>> +4432445867 <+4432445867>->+44213395867 in context public" >>>>>>>> and it fails on line 40: "Regex (FAIL) [gateway_inbound] >>>>>>>> ${target_context}() =~ /^[a-z]/ break=on-false" >>>>>>>> due to the fact that there aren't set any ${target_context} >>>>>>>> variable. >>>>>>>> >>>>>>>> I've added the Twilio inbound gateway as described in the >>>>>>>> Twilio guide, but adding it, removing it etc. doesn't change anything at >>>>>>>> all. >>>>>>>> To the Twilio-Inbound gateway I've added the variable >>>>>>>> ${target_context} according to this guide: >>>>>>>> https://github.com/voxserv/freeswitch_conf_minimal/blob/master/docs/tutorial... >>>>>>>> >>>>>>>> So my guess is that the Twilio-Inbound gateway aren't being >>>>>>>> used - however - calls are routed to my FS. >>>>>>>> >>>>>>>> On Sun, Oct 4, 2015 at 10:15 PM, Michael Nielsen < >>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>> >>>>>>>>> I'll create some logs tomorrow. >>>>>>>>> >>>>>>>>> Just to clarify: >>>>>>>>> - Calls are routes from Twilio to my FS >>>>>>>>> - My FS is a clean installation, 1.6.2 >>>>>>>>> - I've used Twilio's guide for setting up gateways, inbound >>>>>>>>> and outbound >>>>>>>>> - Outbound calls are routed correctly >>>>>>>>> - Inbound calls are as mentioned routes to my FS, but my >>>>>>>>> Twilio-inbound doesn't seem to have anything to do with it, therefor, I'm >>>>>>>>> not able to set any variables in incoming calls from Twilio so I can detect >>>>>>>>> them in my public context and transfer them to my default context. >>>>>>>>> >>>>>>>>> I don't want to route all calls in my public context to my >>>>>>>>> default context, this would open a security issue. Only Twilio calls should >>>>>>>>> be handled in such a manner. >>>>>>>>> That's my challenge. >>>>>>>>> >>>>>>>>> >>>>>>>>> On Sunday, October 4, 2015, Sergey Safarov < >>>>>>>>> s.safarov@gmail.com> wrote: >>>>>>>>> >>>>>>>>>> Inbound call can be received >>>>>>>>>> 1) if twillio guys configure gateway to route incomes calls >>>>>>>>>> to you >>>>>>>>>> 2) or if FS provide information how to route call for you >>>>>>>>>> >>>>>>>>>> After reading gateway config files, I has found that used >>>>>>>>>> second case "FS provides information how to route calls via registration >>>>>>>>>> mechanism". >>>>>>>>>> >>>>>>>>>> Please: >>>>>>>>>> - configure clean FS host as described in twilio manuals; >>>>>>>>>> - enable siptrace; >>>>>>>>>> - enable debug log; >>>>>>>>>> - make incoming call; >>>>>>>>>> - attach debug log in respond to this message. >>>>>>>>>> >>>>>>>>>> I try help you >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Sun, Oct 4, 2015 at 2:37 PM, Michael Nielsen < >>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>> >>>>>>>>>>> Still no luck. >>>>>>>>>>> Any other ideas on how to "catch" the calls from the >>>>>>>>>>> public context in FS? >>>>>>>>>>> My goal is to transfer all calls from Twilio to my default >>>>>>>>>>> context. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Saturday, October 3, 2015, Michael Nielsen < >>>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>>> >>>>>>>>>>>> Looking at their guide for secure setup: >>>>>>>>>>>> https://www.twilio.com/resources/images/docs/Twilio-Freeswitch.pdf >>>>>>>>>>>> they've added <param name="register" value="false"/> >>>>>>>>>>>> When I do this, registering doesn't fail (obviously), but >>>>>>>>>>>> inbound calls are still not registered as coming from twilio... They still >>>>>>>>>>>> land directly in the public context without the variables set correctly. >>>>>>>>>>>> >>>>>>>>>>>> On Sat, Oct 3, 2015 at 11:58 AM, Michael Nielsen < >>>>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> When adding the extension, I get the following - even >>>>>>>>>>>>> though my username and password etc. are correct as they work for the >>>>>>>>>>>>> outbound gateway...: >>>>>>>>>>>>> >>>>>>>>>>>>> twilio-inbound Failed Registration [908] >>>>>>>>>>>>> >>>>>>>>>>>>> On Sat, Oct 3, 2015 at 11:57 AM, Michael Nielsen < >>>>>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> I see. >>>>>>>>>>>>>> Does it matter that I don't have an extension called >>>>>>>>>>>>>> 1000 in my FS, nor in my Twilio account? >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Fri, Oct 2, 2015 at 11:34 PM, Ahmed Habiba < >>>>>>>>>>>>>> ahabiba@gmail.com> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> if you have a deep look at inbound gateway it is for >>>>>>>>>>>>>>> receiving calls from Twilio as you can see below, this line informing >>>>>>>>>>>>>>> freeswitch where to route inkling call. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> <param name="extension" value="1000"/> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> *From: *Michael Nielsen <mic.niel84@gmail.com> >>>>>>>>>>>>>>> *Date: *October 2, 2015 at 11:24:51 PM GMT+3 >>>>>>>>>>>>>>> *To: *FreeSWITCH Users Help < >>>>>>>>>>>>>>> freeswitch-users@lists.freeswitch.org> >>>>>>>>>>>>>>> *Subject: **Re: [Freeswitch-users] Freeswitch and >>>>>>>>>>>>>>> twilio* >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Outbound works fine. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Without having the inbound gateway calls are still >>>>>>>>>>>>>>> routed to my FS to my public context from Twilio. >>>>>>>>>>>>>>> Adding the twilio-inbound doesn't seem to change >>>>>>>>>>>>>>> anything...? >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Friday, October 2, 2015, Brian West < >>>>>>>>>>>>>>> brian@freeswitch.org> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Well you'd send outbound calls out the outbound and >>>>>>>>>>>>>>>> the inbound one is just to register with twilio so they know where to send >>>>>>>>>>>>>>>> your inbound calls. Nothing more. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Fri, Oct 2, 2015 at 1:46 PM, Michael Nielsen < >>>>>>>>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> I'm trying to setup twilio as gateway following this >>>>>>>>>>>>>>>>> guide: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> https://www.twilio.com/docs/sip-trunking/sample-configuration#freeswitch >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> In their example of twiliotrunk.xml they have >>>>>>>>>>>>>>>>> twilio-inbound and twilio-outbound. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> What is the difference between the two gateways? I >>>>>>>>>>>>>>>>> know their names indicate inbound and outbound calling, but how can >>>>>>>>>>>>>>>>> Freeswitch tell the difference between them. Especially how can Freeswitch >>>>>>>>>>>>>>>>> now to use twilio-inbound for incoming calls from twilio and not just >>>>>>>>>>>>>>>>> twilit-outbound as the only difference is register-proxy and expire-seconds >>>>>>>>>>>>>>>>> between the two? >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Make sense? >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> _________________________________________________________________________ >>>>>>>>>>>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>>>>>>>>>>> consulting@freeswitch.org >>>>>>>>>>>>>>>>> http://www.freeswitchsolutions.com >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Official FreeSWITCH Sites >>>>>>>>>>>>>>>>> http://www.freeswitch.org >>>>>>>>>>>>>>>>> http://confluence.freeswitch.org >>>>>>>>>>>>>>>>> http://www.cluecon.com >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> *Brian West* >>>>>>>>>>>>>>>> brian@freeswitch.org >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> *Twitter: @FreeSWITCH , @briankwest* >>>>>>>>>>>>>>>> http://www.freeswitchbook.com >>>>>>>>>>>>>>>> http://www.freeswitchcookbook.com >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Got Bugs? Report them here >>>>>>>>>>>>>>>> <https://freeswitch.org/jira>! | Reddit: >>>>>>>>>>>>>>>> /r/freeswitch <https://www.reddit.com/r/freeswitch> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> *T:*+19184209001 | *F:*+19184209002 | *M:*+1918424WEST >>>>>>>>>>>>>>>> (9378) >>>>>>>>>>>>>>>> *iNUM:*+883 5100 1420 9001 | *ISN:*410*543 | *Skype:* >>>>>>>>>>>>>>>> briankwest >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> _________________________________________________________________________ >>>>>>>>>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>>>>>>>>> consulting@freeswitch.org >>>>>>>>>>>>>>> http://www.freeswitchsolutions.com >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Official FreeSWITCH Sites >>>>>>>>>>>>>>> http://www.freeswitch.org >>>>>>>>>>>>>>> http://confluence.freeswitch.org >>>>>>>>>>>>>>> http://www.cluecon.com >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> _________________________________________________________________________ >>>>>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>>>>> consulting@freeswitch.org >>>>>>>>>>> http://www.freeswitchsolutions.com >>>>>>>>>>> >>>>>>>>>>> Official FreeSWITCH Sites >>>>>>>>>>> http://www.freeswitch.org >>>>>>>>>>> http://confluence.freeswitch.org >>>>>>>>>>> http://www.cluecon.com >>>>>>>>>>> >>>>>>>>>>> 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 >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> _________________________________________________________________________ >>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>> consulting@freeswitch.org >>>>>>>> http://www.freeswitchsolutions.com >>>>>>>> >>>>>>>> Official FreeSWITCH Sites >>>>>>>> http://www.freeswitch.org >>>>>>>> http://confluence.freeswitch.org >>>>>>>> http://www.cluecon.com >>>>>>>> >>>>>>>> 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 >>>>>>>> >>>>>>> >>>>>>> >>>>>> _________________________________________________________________________ >>>>>> Professional FreeSWITCH Consulting Services: >>>>>> consulting@freeswitch.org >>>>>> http://www.freeswitchsolutions.com >>>>>> >>>>>> Official FreeSWITCH Sites >>>>>> http://www.freeswitch.org >>>>>> http://confluence.freeswitch.org >>>>>> http://www.cluecon.com >>>>>> >>>>>> 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 >>>>> >>>>> >>>>> >>>>> _________________________________________________________________________ >>>>> Professional FreeSWITCH Consulting Services: >>>>> consulting@freeswitch.org >>>>> http://www.freeswitchsolutions.com >>>>> >>>>> Official FreeSWITCH Sites >>>>> http://www.freeswitch.org >>>>> http://confluence.freeswitch.org >>>>> http://www.cluecon.com >>>>> >>>>> 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 >>>>> >>>> >>>> >>>> >>>> _________________________________________________________________________ >>>> Professional FreeSWITCH Consulting Services: >>>> consulting@freeswitch.org >>>> http://www.freeswitchsolutions.com >>>> >>>> Official FreeSWITCH Sites >>>> http://www.freeswitch.org >>>> http://confluence.freeswitch.org >>>> http://www.cluecon.com >>>> >>>> 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 >>>> >>> >>> >> >> _________________________________________________________________________ >> Professional FreeSWITCH Consulting Services: >> consulting@freeswitch.org >> http://www.freeswitchsolutions.com >> >> Official FreeSWITCH Sites >> http://www.freeswitch.org >> http://confluence.freeswitch.org >> http://www.cluecon.com >> >> 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 >> > > > > _________________________________________________________________________ > Professional FreeSWITCH Consulting Services: > consulting@freeswitch.org > http://www.freeswitchsolutions.com > > Official FreeSWITCH Sites > http://www.freeswitch.org > http://confluence.freeswitch.org > http://www.cluecon.com > > 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 >
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
I read provided doc link. Working scheme: 1) create separate sip_profile for twilio. As example use internal profile. Also you may set port to 5090 in new profile; 2) configure ACL with twilio IP in new profile; 3) set required context in new profile; 4) set correct port in trunk originatin settings on twilio side. After it incoming calls must work correctly. On Tue, Oct 6, 2015, 20:32 Michael Nielsen <mic.niel84@gmail.com> wrote:
I'm only able to have Twilio route calls to a URL (such as sip: my-domain.com or sip:1000@my-domain.com:port-number). Whatever I do, I'm not able to get a gateway to register to Twilio.
Would it be a correct way to have my sip_profiles/internal.xml use context default instead of public, so I can catch it in that way? All internal should require authentication.
Here is some info about Twilio and their trunk setup: https://www.twilio.com/docs/sip-trunking/getting-started
My idea of perfect setup would of course to be able to have a sip_profiles/external/twilio.xml which automatically had all incoming calls routed/transfer directly to default context - so my directory-users could receive calls in that manner.
On Tue, Oct 6, 2015 at 3:43 PM, Sergey Safarov <s.safarov@gmail.com> wrote:
It say that twillio is not use your inbound gaeway. It may be deleted. If you want route call via inbound gateway, then configure call routing on twilio side.
In your case incoming call is processed in context configured in sip_profile '<param name="context" value="public"/>'
Alternative it can be setted in directory via '<variable name="user_context" value="targed_context"/>'
On Tue, Oct 6, 2015 at 4:07 PM, Michael Nielsen <mic.niel84@gmail.com> wrote:
I did have Twilio IP's in ACL - as their guide told me to. Removing them gives me the following error: "Rejected by acl "domains". Falling back to Digest auth."
I do have a twilio.xml in my /sip_profiles/external/ directory and this does work for outbound calls.
On Tue, Oct 6, 2015 at 12:57 PM, Sergey Safarov <s.safarov@gmail.com> wrote:
I has two FS serves "client" and provider. On client configired gateway. On server user in directory.
On servers I take command "originate user/fs2@gateways.rcsnet.ru &park()" Below two string from FS log
10:31:55.818435 [NOTICE] switch_channel.c:1055 New Channel sofia/external/0000000000@gateways.rcsnet.ru [6bc096cb-b903-4b47-9a9b-3fba54c10d6a] [INFO] mod_dialplan_xml.c:635 Processing <0000000000>->fs2 in context target_context
"target_context" is value of '<param name="context" value="target_context"/>' in gateway config file.
Tested on 7add4b2 commit
Think you has disable authorization or configure twilio server IP addess in ACL. Locate this changes and revert it back.
On Tue, Oct 6, 2015 at 12:05 PM, Michael Nielsen <mic.niel84@gmail.com> wrote:
I just did - change to 5080 - and nothing else happens. It still gets routed directly to the public context - without getting "catched" by the gateway-config.
I've tried to use the extension parameter in the gateway and route calls from Twilio directly to 1000@my-domain.com:5080, still nothing else happens.
On Tue, Oct 6, 2015 at 9:59 AM, Stanislav Sinyagin < ssinyagin@gmail.com> wrote:
Well, if your URL points to 5060, then yes, you need to change it to 5080 :-))
On Tue, Oct 6, 2015 at 9:47 AM, Michael Nielsen <mic.niel84@gmail.com > wrote:
> I can only give Twilio an url. But I am able to change the default > Twilio uses, as an example to 5080. Would that trigger the external gateway > perhaps? > > > On Tuesday, October 6, 2015, Stanislav Sinyagin <ssinyagin@gmail.com> > wrote: > >> but what exactly is configured on twilio side? I guess it should be >> configurable where it should send calls >> >> On Tue, Oct 6, 2015 at 9:27 AM, Michael Nielsen < >> mic.niel84@gmail.com> wrote: >> >>> If I disable registration on my twilio-inbound, it does not fail - >>> however - incoming calls are still not "catched" by my twilio-inbound >>> gateway profile. It still lands in the public context without any variables >>> set. >>> >>> On Tue, Oct 6, 2015 at 5:57 AM, Sergey Safarov < >>> s.safarov@gmail.com> wrote: >>> >>>> If disable registration on inbound gateway, then is possible >>>> receive inbound call? >>>> >>>> On Mon, Oct 5, 2015, 22:45 Michael Nielsen <mic.niel84@gmail.com> >>>> wrote: >>>> >>>>> Twilio is just taking a sip address as termination address. In >>>>> this case my domain which FS runs on. >>>>> Apparently, Twilio is sending calls to the standard 5060 port - >>>>> which then lands in my public context. >>>>> >>>>> On Monday, October 5, 2015, Stanislav Sinyagin < >>>>> ssinyagin@gmail.com> wrote: >>>>> >>>>>> in your pastebin, you seem to receive the call on your internal >>>>>> profile (port 5060): >>>>>> 11:18:58.277709 [DEBUG] sofia.c:9229 sofia/internal/+ >>>>>> 4432445867@sip.ie1.twilio.com receiving invite from >>>>>> 54.171.127.192:5060 >>>>>> >>>>>> >>>>>> so, what exactly is configured on both sides? The external >>>>>> profile is usually on the port 5080. >>>>>> >>>>>> >>>>>> >>>>>> On Mon, Oct 5, 2015 at 6:26 PM, Michael Nielsen < >>>>>> mic.niel84@gmail.com> wrote: >>>>>> >>>>>>> Here's as log from an incoming call from Twilio: >>>>>>> http://pastebin.com/n0de7jhv >>>>>>> >>>>>>> My guess is the problem is with line 33: "Processing >>>>>>> +4432445867 <+4432445867>->+44213395867 in context public" >>>>>>> and it fails on line 40: "Regex (FAIL) [gateway_inbound] >>>>>>> ${target_context}() =~ /^[a-z]/ break=on-false" >>>>>>> due to the fact that there aren't set any ${target_context} >>>>>>> variable. >>>>>>> >>>>>>> I've added the Twilio inbound gateway as described in the >>>>>>> Twilio guide, but adding it, removing it etc. doesn't change anything at >>>>>>> all. >>>>>>> To the Twilio-Inbound gateway I've added the variable >>>>>>> ${target_context} according to this guide: >>>>>>> https://github.com/voxserv/freeswitch_conf_minimal/blob/master/docs/tutorial... >>>>>>> >>>>>>> So my guess is that the Twilio-Inbound gateway aren't being >>>>>>> used - however - calls are routed to my FS. >>>>>>> >>>>>>> On Sun, Oct 4, 2015 at 10:15 PM, Michael Nielsen < >>>>>>> mic.niel84@gmail.com> wrote: >>>>>>> >>>>>>>> I'll create some logs tomorrow. >>>>>>>> >>>>>>>> Just to clarify: >>>>>>>> - Calls are routes from Twilio to my FS >>>>>>>> - My FS is a clean installation, 1.6.2 >>>>>>>> - I've used Twilio's guide for setting up gateways, inbound >>>>>>>> and outbound >>>>>>>> - Outbound calls are routed correctly >>>>>>>> - Inbound calls are as mentioned routes to my FS, but my >>>>>>>> Twilio-inbound doesn't seem to have anything to do with it, therefor, I'm >>>>>>>> not able to set any variables in incoming calls from Twilio so I can detect >>>>>>>> them in my public context and transfer them to my default context. >>>>>>>> >>>>>>>> I don't want to route all calls in my public context to my >>>>>>>> default context, this would open a security issue. Only Twilio calls should >>>>>>>> be handled in such a manner. >>>>>>>> That's my challenge. >>>>>>>> >>>>>>>> >>>>>>>> On Sunday, October 4, 2015, Sergey Safarov < >>>>>>>> s.safarov@gmail.com> wrote: >>>>>>>> >>>>>>>>> Inbound call can be received >>>>>>>>> 1) if twillio guys configure gateway to route incomes calls >>>>>>>>> to you >>>>>>>>> 2) or if FS provide information how to route call for you >>>>>>>>> >>>>>>>>> After reading gateway config files, I has found that used >>>>>>>>> second case "FS provides information how to route calls via registration >>>>>>>>> mechanism". >>>>>>>>> >>>>>>>>> Please: >>>>>>>>> - configure clean FS host as described in twilio manuals; >>>>>>>>> - enable siptrace; >>>>>>>>> - enable debug log; >>>>>>>>> - make incoming call; >>>>>>>>> - attach debug log in respond to this message. >>>>>>>>> >>>>>>>>> I try help you >>>>>>>>> >>>>>>>>> >>>>>>>>> On Sun, Oct 4, 2015 at 2:37 PM, Michael Nielsen < >>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>> >>>>>>>>>> Still no luck. >>>>>>>>>> Any other ideas on how to "catch" the calls from the public >>>>>>>>>> context in FS? >>>>>>>>>> My goal is to transfer all calls from Twilio to my default >>>>>>>>>> context. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Saturday, October 3, 2015, Michael Nielsen < >>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>> >>>>>>>>>>> Looking at their guide for secure setup: >>>>>>>>>>> https://www.twilio.com/resources/images/docs/Twilio-Freeswitch.pdf >>>>>>>>>>> they've added <param name="register" value="false"/> >>>>>>>>>>> When I do this, registering doesn't fail (obviously), but >>>>>>>>>>> inbound calls are still not registered as coming from twilio... They still >>>>>>>>>>> land directly in the public context without the variables set correctly. >>>>>>>>>>> >>>>>>>>>>> On Sat, Oct 3, 2015 at 11:58 AM, Michael Nielsen < >>>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>>> >>>>>>>>>>>> When adding the extension, I get the following - even >>>>>>>>>>>> though my username and password etc. are correct as they work for the >>>>>>>>>>>> outbound gateway...: >>>>>>>>>>>> >>>>>>>>>>>> twilio-inbound Failed Registration [908] >>>>>>>>>>>> >>>>>>>>>>>> On Sat, Oct 3, 2015 at 11:57 AM, Michael Nielsen < >>>>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> I see. >>>>>>>>>>>>> Does it matter that I don't have an extension called >>>>>>>>>>>>> 1000 in my FS, nor in my Twilio account? >>>>>>>>>>>>> >>>>>>>>>>>>> On Fri, Oct 2, 2015 at 11:34 PM, Ahmed Habiba < >>>>>>>>>>>>> ahabiba@gmail.com> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> if you have a deep look at inbound gateway it is for >>>>>>>>>>>>>> receiving calls from Twilio as you can see below, this line informing >>>>>>>>>>>>>> freeswitch where to route inkling call. >>>>>>>>>>>>>> >>>>>>>>>>>>>> <param name="extension" value="1000"/> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> *From: *Michael Nielsen <mic.niel84@gmail.com> >>>>>>>>>>>>>> *Date: *October 2, 2015 at 11:24:51 PM GMT+3 >>>>>>>>>>>>>> *To: *FreeSWITCH Users Help < >>>>>>>>>>>>>> freeswitch-users@lists.freeswitch.org> >>>>>>>>>>>>>> *Subject: **Re: [Freeswitch-users] Freeswitch and >>>>>>>>>>>>>> twilio* >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> Outbound works fine. >>>>>>>>>>>>>> >>>>>>>>>>>>>> Without having the inbound gateway calls are still >>>>>>>>>>>>>> routed to my FS to my public context from Twilio. >>>>>>>>>>>>>> Adding the twilio-inbound doesn't seem to change >>>>>>>>>>>>>> anything...? >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Friday, October 2, 2015, Brian West < >>>>>>>>>>>>>> brian@freeswitch.org> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> Well you'd send outbound calls out the outbound and >>>>>>>>>>>>>>> the inbound one is just to register with twilio so they know where to send >>>>>>>>>>>>>>> your inbound calls. Nothing more. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Fri, Oct 2, 2015 at 1:46 PM, Michael Nielsen < >>>>>>>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> I'm trying to setup twilio as gateway following this >>>>>>>>>>>>>>>> guide: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> https://www.twilio.com/docs/sip-trunking/sample-configuration#freeswitch >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> In their example of twiliotrunk.xml they have >>>>>>>>>>>>>>>> twilio-inbound and twilio-outbound. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> What is the difference between the two gateways? I >>>>>>>>>>>>>>>> know their names indicate inbound and outbound calling, but how can >>>>>>>>>>>>>>>> Freeswitch tell the difference between them. Especially how can Freeswitch >>>>>>>>>>>>>>>> now to use twilio-inbound for incoming calls from twilio and not just >>>>>>>>>>>>>>>> twilit-outbound as the only difference is register-proxy and expire-seconds >>>>>>>>>>>>>>>> between the two? >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Make sense? >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> _________________________________________________________________________ >>>>>>>>>>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>>>>>>>>>> consulting@freeswitch.org >>>>>>>>>>>>>>>> http://www.freeswitchsolutions.com >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Official FreeSWITCH Sites >>>>>>>>>>>>>>>> http://www.freeswitch.org >>>>>>>>>>>>>>>> http://confluence.freeswitch.org >>>>>>>>>>>>>>>> http://www.cluecon.com >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> *Brian West* >>>>>>>>>>>>>>> brian@freeswitch.org >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> *Twitter: @FreeSWITCH , @briankwest* >>>>>>>>>>>>>>> http://www.freeswitchbook.com >>>>>>>>>>>>>>> http://www.freeswitchcookbook.com >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Got Bugs? Report them here >>>>>>>>>>>>>>> <https://freeswitch.org/jira>! | Reddit: /r/freeswitch >>>>>>>>>>>>>>> <https://www.reddit.com/r/freeswitch> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> *T:*+19184209001 | *F:*+19184209002 | *M:*+1918424WEST >>>>>>>>>>>>>>> (9378) >>>>>>>>>>>>>>> *iNUM:*+883 5100 1420 9001 | *ISN:*410*543 | *Skype:* >>>>>>>>>>>>>>> briankwest >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>> 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 >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> _________________________________________________________________________ >>>>>>>>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>>>>>>>> consulting@freeswitch.org >>>>>>>>>>>>>> http://www.freeswitchsolutions.com >>>>>>>>>>>>>> >>>>>>>>>>>>>> Official FreeSWITCH Sites >>>>>>>>>>>>>> http://www.freeswitch.org >>>>>>>>>>>>>> http://confluence.freeswitch.org >>>>>>>>>>>>>> http://www.cluecon.com >>>>>>>>>>>>>> >>>>>>>>>>>>>> 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 >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> _________________________________________________________________________ >>>>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>>>> consulting@freeswitch.org >>>>>>>>>> http://www.freeswitchsolutions.com >>>>>>>>>> >>>>>>>>>> Official FreeSWITCH Sites >>>>>>>>>> http://www.freeswitch.org >>>>>>>>>> http://confluence.freeswitch.org >>>>>>>>>> http://www.cluecon.com >>>>>>>>>> >>>>>>>>>> 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 >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>> >>>>>>> >>>>>>> _________________________________________________________________________ >>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>> consulting@freeswitch.org >>>>>>> http://www.freeswitchsolutions.com >>>>>>> >>>>>>> Official FreeSWITCH Sites >>>>>>> http://www.freeswitch.org >>>>>>> http://confluence.freeswitch.org >>>>>>> http://www.cluecon.com >>>>>>> >>>>>>> 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 >>>>>>> >>>>>> >>>>>> >>>>> _________________________________________________________________________ >>>>> Professional FreeSWITCH Consulting Services: >>>>> consulting@freeswitch.org >>>>> http://www.freeswitchsolutions.com >>>>> >>>>> Official FreeSWITCH Sites >>>>> http://www.freeswitch.org >>>>> http://confluence.freeswitch.org >>>>> http://www.cluecon.com >>>>> >>>>> 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 >>>> >>>> >>>> >>>> _________________________________________________________________________ >>>> Professional FreeSWITCH Consulting Services: >>>> consulting@freeswitch.org >>>> http://www.freeswitchsolutions.com >>>> >>>> Official FreeSWITCH Sites >>>> http://www.freeswitch.org >>>> http://confluence.freeswitch.org >>>> http://www.cluecon.com >>>> >>>> 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 >>>> >>> >>> >>> >>> _________________________________________________________________________ >>> Professional FreeSWITCH Consulting Services: >>> consulting@freeswitch.org >>> http://www.freeswitchsolutions.com >>> >>> Official FreeSWITCH Sites >>> http://www.freeswitch.org >>> http://confluence.freeswitch.org >>> http://www.cluecon.com >>> >>> 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 >>> >> >> > > _________________________________________________________________________ > Professional FreeSWITCH Consulting Services: > consulting@freeswitch.org > http://www.freeswitchsolutions.com > > Official FreeSWITCH Sites > http://www.freeswitch.org > http://confluence.freeswitch.org > http://www.cluecon.com > > 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 >
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
Hello Sergey, This is what I've done. 1) Twilio is set up to route calls to sip:my-domain:5080. I've validated that calls are entering my server on port 5080 and sofia/external/ captures it. 2) Twilio IP's are added to my ACL and validated that incoming calls are accepted. 3) I've created a sip_profile/gateway/twilio.xml which contains: <gateway name="twilio-outbound"> <param name="username" value="MY-USERNAME"/> <param name="password" value="MY-PASSWORD"/> <param name="proxy" value="MY-BUSINESS-NAME.pstn.twilio.com"/> <param name="register" value="false"/> </gateway> <gateway name="twilio-inbound"> <param name="username" value="MY-USERNAME"/> <param name="password" value="MY-PASSWORD"/> <param name="proxy" value="MY-BUSINESS-NAME.pstn.twilio.com"/> <param name="register" value="false"/> <param name="context" value="default"/> </gateway> Twilio-outbound does work. Twilio-inbound does not place incoming calls in the default context. If I make a dialplan in /dialplan/public/gateway_incoming.xml which checks if the user exists and then transfer calls, then it works. But I would prefer to have a gateway (or sip_profile) setup correctly for placing calls in default context from Twilio. On Wed, Oct 7, 2015 at 8:27 AM, Sergey Safarov <s.safarov@gmail.com> wrote:
I read provided doc link. Working scheme: 1) create separate sip_profile for twilio. As example use internal profile. Also you may set port to 5090 in new profile; 2) configure ACL with twilio IP in new profile; 3) set required context in new profile; 4) set correct port in trunk originatin settings on twilio side.
After it incoming calls must work correctly.
On Tue, Oct 6, 2015, 20:32 Michael Nielsen <mic.niel84@gmail.com> wrote:
I'm only able to have Twilio route calls to a URL (such as sip: my-domain.com or sip:1000@my-domain.com:port-number). Whatever I do, I'm not able to get a gateway to register to Twilio.
Would it be a correct way to have my sip_profiles/internal.xml use context default instead of public, so I can catch it in that way? All internal should require authentication.
Here is some info about Twilio and their trunk setup: https://www.twilio.com/docs/sip-trunking/getting-started
My idea of perfect setup would of course to be able to have a sip_profiles/external/twilio.xml which automatically had all incoming calls routed/transfer directly to default context - so my directory-users could receive calls in that manner.
On Tue, Oct 6, 2015 at 3:43 PM, Sergey Safarov <s.safarov@gmail.com> wrote:
It say that twillio is not use your inbound gaeway. It may be deleted. If you want route call via inbound gateway, then configure call routing on twilio side.
In your case incoming call is processed in context configured in sip_profile '<param name="context" value="public"/>'
Alternative it can be setted in directory via '<variable name="user_context" value="targed_context"/>'
On Tue, Oct 6, 2015 at 4:07 PM, Michael Nielsen <mic.niel84@gmail.com> wrote:
I did have Twilio IP's in ACL - as their guide told me to. Removing them gives me the following error: "Rejected by acl "domains". Falling back to Digest auth."
I do have a twilio.xml in my /sip_profiles/external/ directory and this does work for outbound calls.
On Tue, Oct 6, 2015 at 12:57 PM, Sergey Safarov <s.safarov@gmail.com> wrote:
I has two FS serves "client" and provider. On client configired gateway. On server user in directory.
On servers I take command "originate user/fs2@gateways.rcsnet.ru &park()" Below two string from FS log
10:31:55.818435 [NOTICE] switch_channel.c:1055 New Channel sofia/external/0000000000@gateways.rcsnet.ru [6bc096cb-b903-4b47-9a9b-3fba54c10d6a] [INFO] mod_dialplan_xml.c:635 Processing <0000000000>->fs2 in context target_context
"target_context" is value of '<param name="context" value="target_context"/>' in gateway config file.
Tested on 7add4b2 commit
Think you has disable authorization or configure twilio server IP addess in ACL. Locate this changes and revert it back.
On Tue, Oct 6, 2015 at 12:05 PM, Michael Nielsen <mic.niel84@gmail.com
wrote:
I just did - change to 5080 - and nothing else happens. It still gets routed directly to the public context - without getting "catched" by the gateway-config.
I've tried to use the extension parameter in the gateway and route calls from Twilio directly to 1000@my-domain.com:5080, still nothing else happens.
On Tue, Oct 6, 2015 at 9:59 AM, Stanislav Sinyagin < ssinyagin@gmail.com> wrote:
> Well, if your URL points to 5060, then yes, you need to change it to > 5080 :-)) > > > > On Tue, Oct 6, 2015 at 9:47 AM, Michael Nielsen < > mic.niel84@gmail.com> wrote: > >> I can only give Twilio an url. But I am able to change the default >> Twilio uses, as an example to 5080. Would that trigger the external gateway >> perhaps? >> >> >> On Tuesday, October 6, 2015, Stanislav Sinyagin < >> ssinyagin@gmail.com> wrote: >> >>> but what exactly is configured on twilio side? I guess it should >>> be configurable where it should send calls >>> >>> On Tue, Oct 6, 2015 at 9:27 AM, Michael Nielsen < >>> mic.niel84@gmail.com> wrote: >>> >>>> If I disable registration on my twilio-inbound, it does not fail >>>> - however - incoming calls are still not "catched" by my twilio-inbound >>>> gateway profile. It still lands in the public context without any variables >>>> set. >>>> >>>> On Tue, Oct 6, 2015 at 5:57 AM, Sergey Safarov < >>>> s.safarov@gmail.com> wrote: >>>> >>>>> If disable registration on inbound gateway, then is possible >>>>> receive inbound call? >>>>> >>>>> On Mon, Oct 5, 2015, 22:45 Michael Nielsen <mic.niel84@gmail.com> >>>>> wrote: >>>>> >>>>>> Twilio is just taking a sip address as termination address. In >>>>>> this case my domain which FS runs on. >>>>>> Apparently, Twilio is sending calls to the standard 5060 port - >>>>>> which then lands in my public context. >>>>>> >>>>>> On Monday, October 5, 2015, Stanislav Sinyagin < >>>>>> ssinyagin@gmail.com> wrote: >>>>>> >>>>>>> in your pastebin, you seem to receive the call on your >>>>>>> internal profile (port 5060): >>>>>>> 11:18:58.277709 [DEBUG] sofia.c:9229 sofia/internal/+ >>>>>>> 4432445867@sip.ie1.twilio.com receiving invite from >>>>>>> 54.171.127.192:5060 >>>>>>> >>>>>>> >>>>>>> so, what exactly is configured on both sides? The external >>>>>>> profile is usually on the port 5080. >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Mon, Oct 5, 2015 at 6:26 PM, Michael Nielsen < >>>>>>> mic.niel84@gmail.com> wrote: >>>>>>> >>>>>>>> Here's as log from an incoming call from Twilio: >>>>>>>> http://pastebin.com/n0de7jhv >>>>>>>> >>>>>>>> My guess is the problem is with line 33: "Processing >>>>>>>> +4432445867 <+4432445867>->+44213395867 in context public" >>>>>>>> and it fails on line 40: "Regex (FAIL) [gateway_inbound] >>>>>>>> ${target_context}() =~ /^[a-z]/ break=on-false" >>>>>>>> due to the fact that there aren't set any ${target_context} >>>>>>>> variable. >>>>>>>> >>>>>>>> I've added the Twilio inbound gateway as described in the >>>>>>>> Twilio guide, but adding it, removing it etc. doesn't change anything at >>>>>>>> all. >>>>>>>> To the Twilio-Inbound gateway I've added the variable >>>>>>>> ${target_context} according to this guide: >>>>>>>> https://github.com/voxserv/freeswitch_conf_minimal/blob/master/docs/tutorial... >>>>>>>> >>>>>>>> So my guess is that the Twilio-Inbound gateway aren't being >>>>>>>> used - however - calls are routed to my FS. >>>>>>>> >>>>>>>> On Sun, Oct 4, 2015 at 10:15 PM, Michael Nielsen < >>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>> >>>>>>>>> I'll create some logs tomorrow. >>>>>>>>> >>>>>>>>> Just to clarify: >>>>>>>>> - Calls are routes from Twilio to my FS >>>>>>>>> - My FS is a clean installation, 1.6.2 >>>>>>>>> - I've used Twilio's guide for setting up gateways, inbound >>>>>>>>> and outbound >>>>>>>>> - Outbound calls are routed correctly >>>>>>>>> - Inbound calls are as mentioned routes to my FS, but my >>>>>>>>> Twilio-inbound doesn't seem to have anything to do with it, therefor, I'm >>>>>>>>> not able to set any variables in incoming calls from Twilio so I can detect >>>>>>>>> them in my public context and transfer them to my default context. >>>>>>>>> >>>>>>>>> I don't want to route all calls in my public context to my >>>>>>>>> default context, this would open a security issue. Only Twilio calls should >>>>>>>>> be handled in such a manner. >>>>>>>>> That's my challenge. >>>>>>>>> >>>>>>>>> >>>>>>>>> On Sunday, October 4, 2015, Sergey Safarov < >>>>>>>>> s.safarov@gmail.com> wrote: >>>>>>>>> >>>>>>>>>> Inbound call can be received >>>>>>>>>> 1) if twillio guys configure gateway to route incomes calls >>>>>>>>>> to you >>>>>>>>>> 2) or if FS provide information how to route call for you >>>>>>>>>> >>>>>>>>>> After reading gateway config files, I has found that used >>>>>>>>>> second case "FS provides information how to route calls via registration >>>>>>>>>> mechanism". >>>>>>>>>> >>>>>>>>>> Please: >>>>>>>>>> - configure clean FS host as described in twilio manuals; >>>>>>>>>> - enable siptrace; >>>>>>>>>> - enable debug log; >>>>>>>>>> - make incoming call; >>>>>>>>>> - attach debug log in respond to this message. >>>>>>>>>> >>>>>>>>>> I try help you >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Sun, Oct 4, 2015 at 2:37 PM, Michael Nielsen < >>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>> >>>>>>>>>>> Still no luck. >>>>>>>>>>> Any other ideas on how to "catch" the calls from the >>>>>>>>>>> public context in FS? >>>>>>>>>>> My goal is to transfer all calls from Twilio to my default >>>>>>>>>>> context. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Saturday, October 3, 2015, Michael Nielsen < >>>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>>> >>>>>>>>>>>> Looking at their guide for secure setup: >>>>>>>>>>>> https://www.twilio.com/resources/images/docs/Twilio-Freeswitch.pdf >>>>>>>>>>>> they've added <param name="register" value="false"/> >>>>>>>>>>>> When I do this, registering doesn't fail (obviously), but >>>>>>>>>>>> inbound calls are still not registered as coming from twilio... They still >>>>>>>>>>>> land directly in the public context without the variables set correctly. >>>>>>>>>>>> >>>>>>>>>>>> On Sat, Oct 3, 2015 at 11:58 AM, Michael Nielsen < >>>>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> When adding the extension, I get the following - even >>>>>>>>>>>>> though my username and password etc. are correct as they work for the >>>>>>>>>>>>> outbound gateway...: >>>>>>>>>>>>> >>>>>>>>>>>>> twilio-inbound Failed Registration [908] >>>>>>>>>>>>> >>>>>>>>>>>>> On Sat, Oct 3, 2015 at 11:57 AM, Michael Nielsen < >>>>>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> I see. >>>>>>>>>>>>>> Does it matter that I don't have an extension called >>>>>>>>>>>>>> 1000 in my FS, nor in my Twilio account? >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Fri, Oct 2, 2015 at 11:34 PM, Ahmed Habiba < >>>>>>>>>>>>>> ahabiba@gmail.com> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> if you have a deep look at inbound gateway it is for >>>>>>>>>>>>>>> receiving calls from Twilio as you can see below, this line informing >>>>>>>>>>>>>>> freeswitch where to route inkling call. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> <param name="extension" value="1000"/> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> *From: *Michael Nielsen <mic.niel84@gmail.com> >>>>>>>>>>>>>>> *Date: *October 2, 2015 at 11:24:51 PM GMT+3 >>>>>>>>>>>>>>> *To: *FreeSWITCH Users Help < >>>>>>>>>>>>>>> freeswitch-users@lists.freeswitch.org> >>>>>>>>>>>>>>> *Subject: **Re: [Freeswitch-users] Freeswitch and >>>>>>>>>>>>>>> twilio* >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Outbound works fine. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Without having the inbound gateway calls are still >>>>>>>>>>>>>>> routed to my FS to my public context from Twilio. >>>>>>>>>>>>>>> Adding the twilio-inbound doesn't seem to change >>>>>>>>>>>>>>> anything...? >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Friday, October 2, 2015, Brian West < >>>>>>>>>>>>>>> brian@freeswitch.org> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Well you'd send outbound calls out the outbound and >>>>>>>>>>>>>>>> the inbound one is just to register with twilio so they know where to send >>>>>>>>>>>>>>>> your inbound calls. Nothing more. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Fri, Oct 2, 2015 at 1:46 PM, Michael Nielsen < >>>>>>>>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> I'm trying to setup twilio as gateway following this >>>>>>>>>>>>>>>>> guide: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> https://www.twilio.com/docs/sip-trunking/sample-configuration#freeswitch >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> In their example of twiliotrunk.xml they have >>>>>>>>>>>>>>>>> twilio-inbound and twilio-outbound. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> What is the difference between the two gateways? I >>>>>>>>>>>>>>>>> know their names indicate inbound and outbound calling, but how can >>>>>>>>>>>>>>>>> Freeswitch tell the difference between them. Especially how can Freeswitch >>>>>>>>>>>>>>>>> now to use twilio-inbound for incoming calls from twilio and not just >>>>>>>>>>>>>>>>> twilit-outbound as the only difference is register-proxy and expire-seconds >>>>>>>>>>>>>>>>> between the two? >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Make sense? >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> _________________________________________________________________________ >>>>>>>>>>>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>>>>>>>>>>> consulting@freeswitch.org >>>>>>>>>>>>>>>>> http://www.freeswitchsolutions.com >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Official FreeSWITCH Sites >>>>>>>>>>>>>>>>> http://www.freeswitch.org >>>>>>>>>>>>>>>>> http://confluence.freeswitch.org >>>>>>>>>>>>>>>>> http://www.cluecon.com >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> *Brian West* >>>>>>>>>>>>>>>> brian@freeswitch.org >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> *Twitter: @FreeSWITCH , @briankwest* >>>>>>>>>>>>>>>> http://www.freeswitchbook.com >>>>>>>>>>>>>>>> http://www.freeswitchcookbook.com >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Got Bugs? Report them here >>>>>>>>>>>>>>>> <https://freeswitch.org/jira>! | Reddit: >>>>>>>>>>>>>>>> /r/freeswitch <https://www.reddit.com/r/freeswitch> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> *T:*+19184209001 | *F:*+19184209002 | *M:*+1918424WEST >>>>>>>>>>>>>>>> (9378) >>>>>>>>>>>>>>>> *iNUM:*+883 5100 1420 9001 | *ISN:*410*543 | *Skype:* >>>>>>>>>>>>>>>> briankwest >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> _________________________________________________________________________ >>>>>>>>>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>>>>>>>>> consulting@freeswitch.org >>>>>>>>>>>>>>> http://www.freeswitchsolutions.com >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Official FreeSWITCH Sites >>>>>>>>>>>>>>> http://www.freeswitch.org >>>>>>>>>>>>>>> http://confluence.freeswitch.org >>>>>>>>>>>>>>> http://www.cluecon.com >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> _________________________________________________________________________ >>>>>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>>>>> consulting@freeswitch.org >>>>>>>>>>> http://www.freeswitchsolutions.com >>>>>>>>>>> >>>>>>>>>>> Official FreeSWITCH Sites >>>>>>>>>>> http://www.freeswitch.org >>>>>>>>>>> http://confluence.freeswitch.org >>>>>>>>>>> http://www.cluecon.com >>>>>>>>>>> >>>>>>>>>>> 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 >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> _________________________________________________________________________ >>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>> consulting@freeswitch.org >>>>>>>> http://www.freeswitchsolutions.com >>>>>>>> >>>>>>>> Official FreeSWITCH Sites >>>>>>>> http://www.freeswitch.org >>>>>>>> http://confluence.freeswitch.org >>>>>>>> http://www.cluecon.com >>>>>>>> >>>>>>>> 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 >>>>>>>> >>>>>>> >>>>>>> >>>>>> _________________________________________________________________________ >>>>>> Professional FreeSWITCH Consulting Services: >>>>>> consulting@freeswitch.org >>>>>> http://www.freeswitchsolutions.com >>>>>> >>>>>> Official FreeSWITCH Sites >>>>>> http://www.freeswitch.org >>>>>> http://confluence.freeswitch.org >>>>>> http://www.cluecon.com >>>>>> >>>>>> 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 >>>>> >>>>> >>>>> >>>>> _________________________________________________________________________ >>>>> Professional FreeSWITCH Consulting Services: >>>>> consulting@freeswitch.org >>>>> http://www.freeswitchsolutions.com >>>>> >>>>> Official FreeSWITCH Sites >>>>> http://www.freeswitch.org >>>>> http://confluence.freeswitch.org >>>>> http://www.cluecon.com >>>>> >>>>> 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 >>>>> >>>> >>>> >>>> >>>> _________________________________________________________________________ >>>> Professional FreeSWITCH Consulting Services: >>>> consulting@freeswitch.org >>>> http://www.freeswitchsolutions.com >>>> >>>> Official FreeSWITCH Sites >>>> http://www.freeswitch.org >>>> http://confluence.freeswitch.org >>>> http://www.cluecon.com >>>> >>>> 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 >>>> >>> >>> >> >> _________________________________________________________________________ >> Professional FreeSWITCH Consulting Services: >> consulting@freeswitch.org >> http://www.freeswitchsolutions.com >> >> Official FreeSWITCH Sites >> http://www.freeswitch.org >> http://confluence.freeswitch.org >> http://www.cluecon.com >> >> 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 >> > > > > _________________________________________________________________________ > Professional FreeSWITCH Consulting Services: > consulting@freeswitch.org > http://www.freeswitchsolutions.com > > Official FreeSWITCH Sites > http://www.freeswitch.org > http://confluence.freeswitch.org > http://www.cluecon.com > > 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 >
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
make as i write in prevesion message. 1) 5080 - port is used external profile 2) remove inbound gateway On Wed, Oct 7, 2015 at 12:02 PM, Michael Nielsen <mic.niel84@gmail.com> wrote:
Hello Sergey,
This is what I've done. 1) Twilio is set up to route calls to sip:my-domain:5080. I've validated that calls are entering my server on port 5080 and sofia/external/ captures it. 2) Twilio IP's are added to my ACL and validated that incoming calls are accepted. 3) I've created a sip_profile/gateway/twilio.xml which contains:
<gateway name="twilio-outbound"> <param name="username" value="MY-USERNAME"/> <param name="password" value="MY-PASSWORD"/> <param name="proxy" value="MY-BUSINESS-NAME.pstn.twilio.com"/> <param name="register" value="false"/> </gateway>
<gateway name="twilio-inbound"> <param name="username" value="MY-USERNAME"/> <param name="password" value="MY-PASSWORD"/> <param name="proxy" value="MY-BUSINESS-NAME.pstn.twilio.com"/> <param name="register" value="false"/> <param name="context" value="default"/> </gateway> Twilio-outbound does work. Twilio-inbound does not place incoming calls in the default context.
If I make a dialplan in /dialplan/public/gateway_incoming.xml which checks if the user exists and then transfer calls, then it works. But I would prefer to have a gateway (or sip_profile) setup correctly for placing calls in default context from Twilio.
On Wed, Oct 7, 2015 at 8:27 AM, Sergey Safarov <s.safarov@gmail.com> wrote:
I read provided doc link. Working scheme: 1) create separate sip_profile for twilio. As example use internal profile. Also you may set port to 5090 in new profile; 2) configure ACL with twilio IP in new profile; 3) set required context in new profile; 4) set correct port in trunk originatin settings on twilio side.
After it incoming calls must work correctly.
On Tue, Oct 6, 2015, 20:32 Michael Nielsen <mic.niel84@gmail.com> wrote:
I'm only able to have Twilio route calls to a URL (such as sip: my-domain.com or sip:1000@my-domain.com:port-number). Whatever I do, I'm not able to get a gateway to register to Twilio.
Would it be a correct way to have my sip_profiles/internal.xml use context default instead of public, so I can catch it in that way? All internal should require authentication.
Here is some info about Twilio and their trunk setup: https://www.twilio.com/docs/sip-trunking/getting-started
My idea of perfect setup would of course to be able to have a sip_profiles/external/twilio.xml which automatically had all incoming calls routed/transfer directly to default context - so my directory-users could receive calls in that manner.
On Tue, Oct 6, 2015 at 3:43 PM, Sergey Safarov <s.safarov@gmail.com> wrote:
It say that twillio is not use your inbound gaeway. It may be deleted. If you want route call via inbound gateway, then configure call routing on twilio side.
In your case incoming call is processed in context configured in sip_profile '<param name="context" value="public"/>'
Alternative it can be setted in directory via '<variable name="user_context" value="targed_context"/>'
On Tue, Oct 6, 2015 at 4:07 PM, Michael Nielsen <mic.niel84@gmail.com> wrote:
I did have Twilio IP's in ACL - as their guide told me to. Removing them gives me the following error: "Rejected by acl "domains". Falling back to Digest auth."
I do have a twilio.xml in my /sip_profiles/external/ directory and this does work for outbound calls.
On Tue, Oct 6, 2015 at 12:57 PM, Sergey Safarov <s.safarov@gmail.com> wrote:
I has two FS serves "client" and provider. On client configired gateway. On server user in directory.
On servers I take command "originate user/fs2@gateways.rcsnet.ru &park()" Below two string from FS log
10:31:55.818435 [NOTICE] switch_channel.c:1055 New Channel sofia/external/0000000000@gateways.rcsnet.ru [6bc096cb-b903-4b47-9a9b-3fba54c10d6a] [INFO] mod_dialplan_xml.c:635 Processing <0000000000>->fs2 in context target_context
"target_context" is value of '<param name="context" value="target_context"/>' in gateway config file.
Tested on 7add4b2 commit
Think you has disable authorization or configure twilio server IP addess in ACL. Locate this changes and revert it back.
On Tue, Oct 6, 2015 at 12:05 PM, Michael Nielsen < mic.niel84@gmail.com> wrote:
> I just did - change to 5080 - and nothing else happens. > It still gets routed directly to the public context - without > getting "catched" by the gateway-config. > > I've tried to use the extension parameter in the gateway and route > calls from Twilio directly to 1000@my-domain.com:5080, still > nothing else happens. > > > On Tue, Oct 6, 2015 at 9:59 AM, Stanislav Sinyagin < > ssinyagin@gmail.com> wrote: > >> Well, if your URL points to 5060, then yes, you need to change it >> to 5080 :-)) >> >> >> >> On Tue, Oct 6, 2015 at 9:47 AM, Michael Nielsen < >> mic.niel84@gmail.com> wrote: >> >>> I can only give Twilio an url. But I am able to change the default >>> Twilio uses, as an example to 5080. Would that trigger the external gateway >>> perhaps? >>> >>> >>> On Tuesday, October 6, 2015, Stanislav Sinyagin < >>> ssinyagin@gmail.com> wrote: >>> >>>> but what exactly is configured on twilio side? I guess it should >>>> be configurable where it should send calls >>>> >>>> On Tue, Oct 6, 2015 at 9:27 AM, Michael Nielsen < >>>> mic.niel84@gmail.com> wrote: >>>> >>>>> If I disable registration on my twilio-inbound, it does not fail >>>>> - however - incoming calls are still not "catched" by my twilio-inbound >>>>> gateway profile. It still lands in the public context without any variables >>>>> set. >>>>> >>>>> On Tue, Oct 6, 2015 at 5:57 AM, Sergey Safarov < >>>>> s.safarov@gmail.com> wrote: >>>>> >>>>>> If disable registration on inbound gateway, then is possible >>>>>> receive inbound call? >>>>>> >>>>>> On Mon, Oct 5, 2015, 22:45 Michael Nielsen < >>>>>> mic.niel84@gmail.com> wrote: >>>>>> >>>>>>> Twilio is just taking a sip address as termination address. In >>>>>>> this case my domain which FS runs on. >>>>>>> Apparently, Twilio is sending calls to the standard 5060 port >>>>>>> - which then lands in my public context. >>>>>>> >>>>>>> On Monday, October 5, 2015, Stanislav Sinyagin < >>>>>>> ssinyagin@gmail.com> wrote: >>>>>>> >>>>>>>> in your pastebin, you seem to receive the call on your >>>>>>>> internal profile (port 5060): >>>>>>>> 11:18:58.277709 [DEBUG] sofia.c:9229 sofia/internal/+ >>>>>>>> 4432445867@sip.ie1.twilio.com receiving invite from >>>>>>>> 54.171.127.192:5060 >>>>>>>> >>>>>>>> >>>>>>>> so, what exactly is configured on both sides? The external >>>>>>>> profile is usually on the port 5080. >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Mon, Oct 5, 2015 at 6:26 PM, Michael Nielsen < >>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>> >>>>>>>>> Here's as log from an incoming call from Twilio: >>>>>>>>> http://pastebin.com/n0de7jhv >>>>>>>>> >>>>>>>>> My guess is the problem is with line 33: "Processing >>>>>>>>> +4432445867 <+4432445867>->+44213395867 in context public" >>>>>>>>> and it fails on line 40: "Regex (FAIL) [gateway_inbound] >>>>>>>>> ${target_context}() =~ /^[a-z]/ break=on-false" >>>>>>>>> due to the fact that there aren't set any ${target_context} >>>>>>>>> variable. >>>>>>>>> >>>>>>>>> I've added the Twilio inbound gateway as described in the >>>>>>>>> Twilio guide, but adding it, removing it etc. doesn't change anything at >>>>>>>>> all. >>>>>>>>> To the Twilio-Inbound gateway I've added the variable >>>>>>>>> ${target_context} according to this guide: >>>>>>>>> https://github.com/voxserv/freeswitch_conf_minimal/blob/master/docs/tutorial... >>>>>>>>> >>>>>>>>> So my guess is that the Twilio-Inbound gateway aren't being >>>>>>>>> used - however - calls are routed to my FS. >>>>>>>>> >>>>>>>>> On Sun, Oct 4, 2015 at 10:15 PM, Michael Nielsen < >>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>> >>>>>>>>>> I'll create some logs tomorrow. >>>>>>>>>> >>>>>>>>>> Just to clarify: >>>>>>>>>> - Calls are routes from Twilio to my FS >>>>>>>>>> - My FS is a clean installation, 1.6.2 >>>>>>>>>> - I've used Twilio's guide for setting up gateways, inbound >>>>>>>>>> and outbound >>>>>>>>>> - Outbound calls are routed correctly >>>>>>>>>> - Inbound calls are as mentioned routes to my FS, but my >>>>>>>>>> Twilio-inbound doesn't seem to have anything to do with it, therefor, I'm >>>>>>>>>> not able to set any variables in incoming calls from Twilio so I can detect >>>>>>>>>> them in my public context and transfer them to my default context. >>>>>>>>>> >>>>>>>>>> I don't want to route all calls in my public context to my >>>>>>>>>> default context, this would open a security issue. Only Twilio calls should >>>>>>>>>> be handled in such a manner. >>>>>>>>>> That's my challenge. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Sunday, October 4, 2015, Sergey Safarov < >>>>>>>>>> s.safarov@gmail.com> wrote: >>>>>>>>>> >>>>>>>>>>> Inbound call can be received >>>>>>>>>>> 1) if twillio guys configure gateway to route incomes >>>>>>>>>>> calls to you >>>>>>>>>>> 2) or if FS provide information how to route call for you >>>>>>>>>>> >>>>>>>>>>> After reading gateway config files, I has found that used >>>>>>>>>>> second case "FS provides information how to route calls via registration >>>>>>>>>>> mechanism". >>>>>>>>>>> >>>>>>>>>>> Please: >>>>>>>>>>> - configure clean FS host as described in twilio manuals; >>>>>>>>>>> - enable siptrace; >>>>>>>>>>> - enable debug log; >>>>>>>>>>> - make incoming call; >>>>>>>>>>> - attach debug log in respond to this message. >>>>>>>>>>> >>>>>>>>>>> I try help you >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Sun, Oct 4, 2015 at 2:37 PM, Michael Nielsen < >>>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>>> >>>>>>>>>>>> Still no luck. >>>>>>>>>>>> Any other ideas on how to "catch" the calls from the >>>>>>>>>>>> public context in FS? >>>>>>>>>>>> My goal is to transfer all calls from Twilio to my >>>>>>>>>>>> default context. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Saturday, October 3, 2015, Michael Nielsen < >>>>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Looking at their guide for secure setup: >>>>>>>>>>>>> https://www.twilio.com/resources/images/docs/Twilio-Freeswitch.pdf >>>>>>>>>>>>> they've added <param name="register" value="false"/> >>>>>>>>>>>>> When I do this, registering doesn't fail (obviously), >>>>>>>>>>>>> but inbound calls are still not registered as coming from twilio... They >>>>>>>>>>>>> still land directly in the public context without the variables set >>>>>>>>>>>>> correctly. >>>>>>>>>>>>> >>>>>>>>>>>>> On Sat, Oct 3, 2015 at 11:58 AM, Michael Nielsen < >>>>>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> When adding the extension, I get the following - even >>>>>>>>>>>>>> though my username and password etc. are correct as they work for the >>>>>>>>>>>>>> outbound gateway...: >>>>>>>>>>>>>> >>>>>>>>>>>>>> twilio-inbound Failed Registration [908] >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Sat, Oct 3, 2015 at 11:57 AM, Michael Nielsen < >>>>>>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> I see. >>>>>>>>>>>>>>> Does it matter that I don't have an extension called >>>>>>>>>>>>>>> 1000 in my FS, nor in my Twilio account? >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Fri, Oct 2, 2015 at 11:34 PM, Ahmed Habiba < >>>>>>>>>>>>>>> ahabiba@gmail.com> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> if you have a deep look at inbound gateway it is for >>>>>>>>>>>>>>>> receiving calls from Twilio as you can see below, this line informing >>>>>>>>>>>>>>>> freeswitch where to route inkling call. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> <param name="extension" value="1000"/> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> *From: *Michael Nielsen <mic.niel84@gmail.com> >>>>>>>>>>>>>>>> *Date: *October 2, 2015 at 11:24:51 PM GMT+3 >>>>>>>>>>>>>>>> *To: *FreeSWITCH Users Help < >>>>>>>>>>>>>>>> freeswitch-users@lists.freeswitch.org> >>>>>>>>>>>>>>>> *Subject: **Re: [Freeswitch-users] Freeswitch and >>>>>>>>>>>>>>>> twilio* >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Outbound works fine. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Without having the inbound gateway calls are still >>>>>>>>>>>>>>>> routed to my FS to my public context from Twilio. >>>>>>>>>>>>>>>> Adding the twilio-inbound doesn't seem to change >>>>>>>>>>>>>>>> anything...? >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Friday, October 2, 2015, Brian West < >>>>>>>>>>>>>>>> brian@freeswitch.org> wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Well you'd send outbound calls out the outbound and >>>>>>>>>>>>>>>>> the inbound one is just to register with twilio so they know where to send >>>>>>>>>>>>>>>>> your inbound calls. Nothing more. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> On Fri, Oct 2, 2015 at 1:46 PM, Michael Nielsen < >>>>>>>>>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> I'm trying to setup twilio as gateway following >>>>>>>>>>>>>>>>>> this guide: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> https://www.twilio.com/docs/sip-trunking/sample-configuration#freeswitch >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> In their example of twiliotrunk.xml they have >>>>>>>>>>>>>>>>>> twilio-inbound and twilio-outbound. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> What is the difference between the two gateways? I >>>>>>>>>>>>>>>>>> know their names indicate inbound and outbound calling, but how can >>>>>>>>>>>>>>>>>> Freeswitch tell the difference between them. Especially how can Freeswitch >>>>>>>>>>>>>>>>>> now to use twilio-inbound for incoming calls from twilio and not just >>>>>>>>>>>>>>>>>> twilit-outbound as the only difference is register-proxy and expire-seconds >>>>>>>>>>>>>>>>>> between the two? >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Make sense? >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> _________________________________________________________________________ >>>>>>>>>>>>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>>>>>>>>>>>> consulting@freeswitch.org >>>>>>>>>>>>>>>>>> http://www.freeswitchsolutions.com >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Official FreeSWITCH Sites >>>>>>>>>>>>>>>>>> http://www.freeswitch.org >>>>>>>>>>>>>>>>>> http://confluence.freeswitch.org >>>>>>>>>>>>>>>>>> http://www.cluecon.com >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> *Brian West* >>>>>>>>>>>>>>>>> brian@freeswitch.org >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> *Twitter: @FreeSWITCH , @briankwest* >>>>>>>>>>>>>>>>> http://www.freeswitchbook.com >>>>>>>>>>>>>>>>> http://www.freeswitchcookbook.com >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Got Bugs? Report them here >>>>>>>>>>>>>>>>> <https://freeswitch.org/jira>! | Reddit: >>>>>>>>>>>>>>>>> /r/freeswitch <https://www.reddit.com/r/freeswitch> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> *T:*+19184209001 | *F:*+19184209002 | *M:*+1918424WEST >>>>>>>>>>>>>>>>> (9378) >>>>>>>>>>>>>>>>> *iNUM:*+883 5100 1420 9001 | *ISN:*410*543 | >>>>>>>>>>>>>>>>> *Skype:*briankwest >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> _________________________________________________________________________ >>>>>>>>>>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>>>>>>>>>> consulting@freeswitch.org >>>>>>>>>>>>>>>> http://www.freeswitchsolutions.com >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Official FreeSWITCH Sites >>>>>>>>>>>>>>>> http://www.freeswitch.org >>>>>>>>>>>>>>>> http://confluence.freeswitch.org >>>>>>>>>>>>>>>> http://www.cluecon.com >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> _________________________________________________________________________ >>>>>>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>>>>>> consulting@freeswitch.org >>>>>>>>>>>> http://www.freeswitchsolutions.com >>>>>>>>>>>> >>>>>>>>>>>> Official FreeSWITCH Sites >>>>>>>>>>>> http://www.freeswitch.org >>>>>>>>>>>> http://confluence.freeswitch.org >>>>>>>>>>>> http://www.cluecon.com >>>>>>>>>>>> >>>>>>>>>>>> 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 >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> _________________________________________________________________________ >>>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>>> consulting@freeswitch.org >>>>>>>>> http://www.freeswitchsolutions.com >>>>>>>>> >>>>>>>>> Official FreeSWITCH Sites >>>>>>>>> http://www.freeswitch.org >>>>>>>>> http://confluence.freeswitch.org >>>>>>>>> http://www.cluecon.com >>>>>>>>> >>>>>>>>> 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 >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> _________________________________________________________________________ >>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>> consulting@freeswitch.org >>>>>>> http://www.freeswitchsolutions.com >>>>>>> >>>>>>> Official FreeSWITCH Sites >>>>>>> http://www.freeswitch.org >>>>>>> http://confluence.freeswitch.org >>>>>>> http://www.cluecon.com >>>>>>> >>>>>>> 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 >>>>>> >>>>>> >>>>>> >>>>>> _________________________________________________________________________ >>>>>> Professional FreeSWITCH Consulting Services: >>>>>> consulting@freeswitch.org >>>>>> http://www.freeswitchsolutions.com >>>>>> >>>>>> Official FreeSWITCH Sites >>>>>> http://www.freeswitch.org >>>>>> http://confluence.freeswitch.org >>>>>> http://www.cluecon.com >>>>>> >>>>>> 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 >>>>>> >>>>> >>>>> >>>>> >>>>> _________________________________________________________________________ >>>>> Professional FreeSWITCH Consulting Services: >>>>> consulting@freeswitch.org >>>>> http://www.freeswitchsolutions.com >>>>> >>>>> Official FreeSWITCH Sites >>>>> http://www.freeswitch.org >>>>> http://confluence.freeswitch.org >>>>> http://www.cluecon.com >>>>> >>>>> 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 >>>>> >>>> >>>> >>> >>> _________________________________________________________________________ >>> Professional FreeSWITCH Consulting Services: >>> consulting@freeswitch.org >>> http://www.freeswitchsolutions.com >>> >>> Official FreeSWITCH Sites >>> http://www.freeswitch.org >>> http://confluence.freeswitch.org >>> http://www.cluecon.com >>> >>> 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 >>> >> >> >> >> _________________________________________________________________________ >> Professional FreeSWITCH Consulting Services: >> consulting@freeswitch.org >> http://www.freeswitchsolutions.com >> >> Official FreeSWITCH Sites >> http://www.freeswitch.org >> http://confluence.freeswitch.org >> http://www.cluecon.com >> >> 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 >> > > > > _________________________________________________________________________ > Professional FreeSWITCH Consulting Services: > consulting@freeswitch.org > http://www.freeswitchsolutions.com > > Official FreeSWITCH Sites > http://www.freeswitch.org > http://confluence.freeswitch.org > http://www.cluecon.com > > 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 >
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
Ok, so internal user like /directory/default/twilio.xml and then use the destination number in the HEADER for routing calls? The Twilio guide uses an external gateway and not an internal - but I guess that's wrong... On Wed, Oct 7, 2015 at 12:19 PM, Sergey Safarov <s.safarov@gmail.com> wrote:
make as i write in prevesion message. 1) 5080 - port is used external profile 2) remove inbound gateway
On Wed, Oct 7, 2015 at 12:02 PM, Michael Nielsen <mic.niel84@gmail.com> wrote:
Hello Sergey,
This is what I've done. 1) Twilio is set up to route calls to sip:my-domain:5080. I've validated that calls are entering my server on port 5080 and sofia/external/ captures it. 2) Twilio IP's are added to my ACL and validated that incoming calls are accepted. 3) I've created a sip_profile/gateway/twilio.xml which contains:
<gateway name="twilio-outbound"> <param name="username" value="MY-USERNAME"/> <param name="password" value="MY-PASSWORD"/> <param name="proxy" value="MY-BUSINESS-NAME.pstn.twilio.com"/> <param name="register" value="false"/> </gateway>
<gateway name="twilio-inbound"> <param name="username" value="MY-USERNAME"/> <param name="password" value="MY-PASSWORD"/> <param name="proxy" value="MY-BUSINESS-NAME.pstn.twilio.com"/> <param name="register" value="false"/> <param name="context" value="default"/> </gateway> Twilio-outbound does work. Twilio-inbound does not place incoming calls in the default context.
If I make a dialplan in /dialplan/public/gateway_incoming.xml which checks if the user exists and then transfer calls, then it works. But I would prefer to have a gateway (or sip_profile) setup correctly for placing calls in default context from Twilio.
On Wed, Oct 7, 2015 at 8:27 AM, Sergey Safarov <s.safarov@gmail.com> wrote:
I read provided doc link. Working scheme: 1) create separate sip_profile for twilio. As example use internal profile. Also you may set port to 5090 in new profile; 2) configure ACL with twilio IP in new profile; 3) set required context in new profile; 4) set correct port in trunk originatin settings on twilio side.
After it incoming calls must work correctly.
On Tue, Oct 6, 2015, 20:32 Michael Nielsen <mic.niel84@gmail.com> wrote:
I'm only able to have Twilio route calls to a URL (such as sip: my-domain.com or sip:1000@my-domain.com:port-number). Whatever I do, I'm not able to get a gateway to register to Twilio.
Would it be a correct way to have my sip_profiles/internal.xml use context default instead of public, so I can catch it in that way? All internal should require authentication.
Here is some info about Twilio and their trunk setup: https://www.twilio.com/docs/sip-trunking/getting-started
My idea of perfect setup would of course to be able to have a sip_profiles/external/twilio.xml which automatically had all incoming calls routed/transfer directly to default context - so my directory-users could receive calls in that manner.
On Tue, Oct 6, 2015 at 3:43 PM, Sergey Safarov <s.safarov@gmail.com> wrote:
It say that twillio is not use your inbound gaeway. It may be deleted. If you want route call via inbound gateway, then configure call routing on twilio side.
In your case incoming call is processed in context configured in sip_profile '<param name="context" value="public"/>'
Alternative it can be setted in directory via '<variable name="user_context" value="targed_context"/>'
On Tue, Oct 6, 2015 at 4:07 PM, Michael Nielsen <mic.niel84@gmail.com> wrote:
I did have Twilio IP's in ACL - as their guide told me to. Removing them gives me the following error: "Rejected by acl "domains". Falling back to Digest auth."
I do have a twilio.xml in my /sip_profiles/external/ directory and this does work for outbound calls.
On Tue, Oct 6, 2015 at 12:57 PM, Sergey Safarov <s.safarov@gmail.com> wrote:
> I has two FS serves "client" and provider. > On client configired gateway. > On server user in directory. > > On servers I take command "originate user/fs2@gateways.rcsnet.ru > &park()" > Below two string from FS log > > 10:31:55.818435 [NOTICE] switch_channel.c:1055 New Channel > sofia/external/0000000000@gateways.rcsnet.ru > [6bc096cb-b903-4b47-9a9b-3fba54c10d6a] > [INFO] mod_dialplan_xml.c:635 Processing <0000000000>->fs2 in > context target_context > > "target_context" is value of '<param name="context" > value="target_context"/>' in gateway config file. > > Tested on 7add4b2 commit > > > Think you has disable authorization or configure twilio server IP > addess in ACL. Locate this changes and revert it back. > > > On Tue, Oct 6, 2015 at 12:05 PM, Michael Nielsen < > mic.niel84@gmail.com> wrote: > >> I just did - change to 5080 - and nothing else happens. >> It still gets routed directly to the public context - without >> getting "catched" by the gateway-config. >> >> I've tried to use the extension parameter in the gateway and route >> calls from Twilio directly to 1000@my-domain.com:5080, still >> nothing else happens. >> >> >> On Tue, Oct 6, 2015 at 9:59 AM, Stanislav Sinyagin < >> ssinyagin@gmail.com> wrote: >> >>> Well, if your URL points to 5060, then yes, you need to change it >>> to 5080 :-)) >>> >>> >>> >>> On Tue, Oct 6, 2015 at 9:47 AM, Michael Nielsen < >>> mic.niel84@gmail.com> wrote: >>> >>>> I can only give Twilio an url. But I am able to change the >>>> default Twilio uses, as an example to 5080. Would that trigger the external >>>> gateway perhaps? >>>> >>>> >>>> On Tuesday, October 6, 2015, Stanislav Sinyagin < >>>> ssinyagin@gmail.com> wrote: >>>> >>>>> but what exactly is configured on twilio side? I guess it should >>>>> be configurable where it should send calls >>>>> >>>>> On Tue, Oct 6, 2015 at 9:27 AM, Michael Nielsen < >>>>> mic.niel84@gmail.com> wrote: >>>>> >>>>>> If I disable registration on my twilio-inbound, it does not >>>>>> fail - however - incoming calls are still not "catched" by my >>>>>> twilio-inbound gateway profile. It still lands in the public context >>>>>> without any variables set. >>>>>> >>>>>> On Tue, Oct 6, 2015 at 5:57 AM, Sergey Safarov < >>>>>> s.safarov@gmail.com> wrote: >>>>>> >>>>>>> If disable registration on inbound gateway, then is possible >>>>>>> receive inbound call? >>>>>>> >>>>>>> On Mon, Oct 5, 2015, 22:45 Michael Nielsen < >>>>>>> mic.niel84@gmail.com> wrote: >>>>>>> >>>>>>>> Twilio is just taking a sip address as termination address. >>>>>>>> In this case my domain which FS runs on. >>>>>>>> Apparently, Twilio is sending calls to the standard 5060 port >>>>>>>> - which then lands in my public context. >>>>>>>> >>>>>>>> On Monday, October 5, 2015, Stanislav Sinyagin < >>>>>>>> ssinyagin@gmail.com> wrote: >>>>>>>> >>>>>>>>> in your pastebin, you seem to receive the call on your >>>>>>>>> internal profile (port 5060): >>>>>>>>> 11:18:58.277709 [DEBUG] sofia.c:9229 sofia/internal/+ >>>>>>>>> 4432445867@sip.ie1.twilio.com receiving invite from >>>>>>>>> 54.171.127.192:5060 >>>>>>>>> >>>>>>>>> >>>>>>>>> so, what exactly is configured on both sides? The external >>>>>>>>> profile is usually on the port 5080. >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On Mon, Oct 5, 2015 at 6:26 PM, Michael Nielsen < >>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>> >>>>>>>>>> Here's as log from an incoming call from Twilio: >>>>>>>>>> http://pastebin.com/n0de7jhv >>>>>>>>>> >>>>>>>>>> My guess is the problem is with line 33: "Processing >>>>>>>>>> +4432445867 <+4432445867>->+44213395867 in context public" >>>>>>>>>> and it fails on line 40: "Regex (FAIL) [gateway_inbound] >>>>>>>>>> ${target_context}() =~ /^[a-z]/ break=on-false" >>>>>>>>>> due to the fact that there aren't set any ${target_context} >>>>>>>>>> variable. >>>>>>>>>> >>>>>>>>>> I've added the Twilio inbound gateway as described in the >>>>>>>>>> Twilio guide, but adding it, removing it etc. doesn't change anything at >>>>>>>>>> all. >>>>>>>>>> To the Twilio-Inbound gateway I've added the variable >>>>>>>>>> ${target_context} according to this guide: >>>>>>>>>> https://github.com/voxserv/freeswitch_conf_minimal/blob/master/docs/tutorial... >>>>>>>>>> >>>>>>>>>> So my guess is that the Twilio-Inbound gateway aren't being >>>>>>>>>> used - however - calls are routed to my FS. >>>>>>>>>> >>>>>>>>>> On Sun, Oct 4, 2015 at 10:15 PM, Michael Nielsen < >>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>> >>>>>>>>>>> I'll create some logs tomorrow. >>>>>>>>>>> >>>>>>>>>>> Just to clarify: >>>>>>>>>>> - Calls are routes from Twilio to my FS >>>>>>>>>>> - My FS is a clean installation, 1.6.2 >>>>>>>>>>> - I've used Twilio's guide for setting up gateways, >>>>>>>>>>> inbound and outbound >>>>>>>>>>> - Outbound calls are routed correctly >>>>>>>>>>> - Inbound calls are as mentioned routes to my FS, but my >>>>>>>>>>> Twilio-inbound doesn't seem to have anything to do with it, therefor, I'm >>>>>>>>>>> not able to set any variables in incoming calls from Twilio so I can detect >>>>>>>>>>> them in my public context and transfer them to my default context. >>>>>>>>>>> >>>>>>>>>>> I don't want to route all calls in my public context to my >>>>>>>>>>> default context, this would open a security issue. Only Twilio calls should >>>>>>>>>>> be handled in such a manner. >>>>>>>>>>> That's my challenge. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Sunday, October 4, 2015, Sergey Safarov < >>>>>>>>>>> s.safarov@gmail.com> wrote: >>>>>>>>>>> >>>>>>>>>>>> Inbound call can be received >>>>>>>>>>>> 1) if twillio guys configure gateway to route incomes >>>>>>>>>>>> calls to you >>>>>>>>>>>> 2) or if FS provide information how to route call for you >>>>>>>>>>>> >>>>>>>>>>>> After reading gateway config files, I has found that used >>>>>>>>>>>> second case "FS provides information how to route calls via registration >>>>>>>>>>>> mechanism". >>>>>>>>>>>> >>>>>>>>>>>> Please: >>>>>>>>>>>> - configure clean FS host as described in twilio manuals; >>>>>>>>>>>> - enable siptrace; >>>>>>>>>>>> - enable debug log; >>>>>>>>>>>> - make incoming call; >>>>>>>>>>>> - attach debug log in respond to this message. >>>>>>>>>>>> >>>>>>>>>>>> I try help you >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Sun, Oct 4, 2015 at 2:37 PM, Michael Nielsen < >>>>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Still no luck. >>>>>>>>>>>>> Any other ideas on how to "catch" the calls from the >>>>>>>>>>>>> public context in FS? >>>>>>>>>>>>> My goal is to transfer all calls from Twilio to my >>>>>>>>>>>>> default context. >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> On Saturday, October 3, 2015, Michael Nielsen < >>>>>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> Looking at their guide for secure setup: >>>>>>>>>>>>>> https://www.twilio.com/resources/images/docs/Twilio-Freeswitch.pdf >>>>>>>>>>>>>> they've added <param name="register" value="false"/ >>>>>>>>>>>>>> > >>>>>>>>>>>>>> When I do this, registering doesn't fail (obviously), >>>>>>>>>>>>>> but inbound calls are still not registered as coming from twilio... They >>>>>>>>>>>>>> still land directly in the public context without the variables set >>>>>>>>>>>>>> correctly. >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Sat, Oct 3, 2015 at 11:58 AM, Michael Nielsen < >>>>>>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> When adding the extension, I get the following - even >>>>>>>>>>>>>>> though my username and password etc. are correct as they work for the >>>>>>>>>>>>>>> outbound gateway...: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> twilio-inbound Failed Registration [908] >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Sat, Oct 3, 2015 at 11:57 AM, Michael Nielsen < >>>>>>>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> I see. >>>>>>>>>>>>>>>> Does it matter that I don't have an extension called >>>>>>>>>>>>>>>> 1000 in my FS, nor in my Twilio account? >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Fri, Oct 2, 2015 at 11:34 PM, Ahmed Habiba < >>>>>>>>>>>>>>>> ahabiba@gmail.com> wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> if you have a deep look at inbound gateway it is >>>>>>>>>>>>>>>>> for receiving calls from Twilio as you can see below, this line informing >>>>>>>>>>>>>>>>> freeswitch where to route inkling call. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> <param name="extension" value="1000"/> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> *From: *Michael Nielsen <mic.niel84@gmail.com> >>>>>>>>>>>>>>>>> *Date: *October 2, 2015 at 11:24:51 PM GMT+3 >>>>>>>>>>>>>>>>> *To: *FreeSWITCH Users Help < >>>>>>>>>>>>>>>>> freeswitch-users@lists.freeswitch.org> >>>>>>>>>>>>>>>>> *Subject: **Re: [Freeswitch-users] Freeswitch and >>>>>>>>>>>>>>>>> twilio* >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Outbound works fine. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Without having the inbound gateway calls are still >>>>>>>>>>>>>>>>> routed to my FS to my public context from Twilio. >>>>>>>>>>>>>>>>> Adding the twilio-inbound doesn't seem to change >>>>>>>>>>>>>>>>> anything...? >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> On Friday, October 2, 2015, Brian West < >>>>>>>>>>>>>>>>> brian@freeswitch.org> wrote: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Well you'd send outbound calls out the outbound >>>>>>>>>>>>>>>>>> and the inbound one is just to register with twilio so they know where to >>>>>>>>>>>>>>>>>> send your inbound calls. Nothing more. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> On Fri, Oct 2, 2015 at 1:46 PM, Michael Nielsen < >>>>>>>>>>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> I'm trying to setup twilio as gateway following >>>>>>>>>>>>>>>>>>> this guide: >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> https://www.twilio.com/docs/sip-trunking/sample-configuration#freeswitch >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> In their example of twiliotrunk.xml they have >>>>>>>>>>>>>>>>>>> twilio-inbound and twilio-outbound. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> What is the difference between the two gateways? I >>>>>>>>>>>>>>>>>>> know their names indicate inbound and outbound calling, but how can >>>>>>>>>>>>>>>>>>> Freeswitch tell the difference between them. Especially how can Freeswitch >>>>>>>>>>>>>>>>>>> now to use twilio-inbound for incoming calls from twilio and not just >>>>>>>>>>>>>>>>>>> twilit-outbound as the only difference is register-proxy and expire-seconds >>>>>>>>>>>>>>>>>>> between the two? >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Make sense? >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> _________________________________________________________________________ >>>>>>>>>>>>>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>>>>>>>>>>>>> consulting@freeswitch.org >>>>>>>>>>>>>>>>>>> http://www.freeswitchsolutions.com >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Official FreeSWITCH Sites >>>>>>>>>>>>>>>>>>> http://www.freeswitch.org >>>>>>>>>>>>>>>>>>> http://confluence.freeswitch.org >>>>>>>>>>>>>>>>>>> http://www.cluecon.com >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> *Brian West* >>>>>>>>>>>>>>>>>> brian@freeswitch.org >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> *Twitter: @FreeSWITCH , @briankwest* >>>>>>>>>>>>>>>>>> http://www.freeswitchbook.com >>>>>>>>>>>>>>>>>> http://www.freeswitchcookbook.com >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Got Bugs? Report them here >>>>>>>>>>>>>>>>>> <https://freeswitch.org/jira>! | Reddit: >>>>>>>>>>>>>>>>>> /r/freeswitch <https://www.reddit.com/r/freeswitch> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> *T:*+19184209001 | *F:*+19184209002 | *M:*+1918424WEST >>>>>>>>>>>>>>>>>> (9378) >>>>>>>>>>>>>>>>>> *iNUM:*+883 5100 1420 9001 | *ISN:*410*543 | >>>>>>>>>>>>>>>>>> *Skype:*briankwest >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> _________________________________________________________________________ >>>>>>>>>>>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>>>>>>>>>>> consulting@freeswitch.org >>>>>>>>>>>>>>>>> http://www.freeswitchsolutions.com >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Official FreeSWITCH Sites >>>>>>>>>>>>>>>>> http://www.freeswitch.org >>>>>>>>>>>>>>>>> http://confluence.freeswitch.org >>>>>>>>>>>>>>>>> http://www.cluecon.com >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> _________________________________________________________________________ >>>>>>>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>>>>>>> consulting@freeswitch.org >>>>>>>>>>>>> http://www.freeswitchsolutions.com >>>>>>>>>>>>> >>>>>>>>>>>>> Official FreeSWITCH Sites >>>>>>>>>>>>> http://www.freeswitch.org >>>>>>>>>>>>> http://confluence.freeswitch.org >>>>>>>>>>>>> http://www.cluecon.com >>>>>>>>>>>>> >>>>>>>>>>>>> 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 >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> _________________________________________________________________________ >>>>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>>>> consulting@freeswitch.org >>>>>>>>>> http://www.freeswitchsolutions.com >>>>>>>>>> >>>>>>>>>> Official FreeSWITCH Sites >>>>>>>>>> http://www.freeswitch.org >>>>>>>>>> http://confluence.freeswitch.org >>>>>>>>>> http://www.cluecon.com >>>>>>>>>> >>>>>>>>>> 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 >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> _________________________________________________________________________ >>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>> consulting@freeswitch.org >>>>>>>> http://www.freeswitchsolutions.com >>>>>>>> >>>>>>>> Official FreeSWITCH Sites >>>>>>>> http://www.freeswitch.org >>>>>>>> http://confluence.freeswitch.org >>>>>>>> http://www.cluecon.com >>>>>>>> >>>>>>>> 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 >>>>>>> >>>>>>> >>>>>>> >>>>>>> _________________________________________________________________________ >>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>> consulting@freeswitch.org >>>>>>> http://www.freeswitchsolutions.com >>>>>>> >>>>>>> Official FreeSWITCH Sites >>>>>>> http://www.freeswitch.org >>>>>>> http://confluence.freeswitch.org >>>>>>> http://www.cluecon.com >>>>>>> >>>>>>> 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 >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> _________________________________________________________________________ >>>>>> Professional FreeSWITCH Consulting Services: >>>>>> consulting@freeswitch.org >>>>>> http://www.freeswitchsolutions.com >>>>>> >>>>>> Official FreeSWITCH Sites >>>>>> http://www.freeswitch.org >>>>>> http://confluence.freeswitch.org >>>>>> http://www.cluecon.com >>>>>> >>>>>> 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 >>>>>> >>>>> >>>>> >>>> >>>> _________________________________________________________________________ >>>> Professional FreeSWITCH Consulting Services: >>>> consulting@freeswitch.org >>>> http://www.freeswitchsolutions.com >>>> >>>> Official FreeSWITCH Sites >>>> http://www.freeswitch.org >>>> http://confluence.freeswitch.org >>>> http://www.cluecon.com >>>> >>>> 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 >>>> >>> >>> >>> >>> _________________________________________________________________________ >>> Professional FreeSWITCH Consulting Services: >>> consulting@freeswitch.org >>> http://www.freeswitchsolutions.com >>> >>> Official FreeSWITCH Sites >>> http://www.freeswitch.org >>> http://confluence.freeswitch.org >>> http://www.cluecon.com >>> >>> 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 >>> >> >> >> >> _________________________________________________________________________ >> Professional FreeSWITCH Consulting Services: >> consulting@freeswitch.org >> http://www.freeswitchsolutions.com >> >> Official FreeSWITCH Sites >> http://www.freeswitch.org >> http://confluence.freeswitch.org >> http://www.cluecon.com >> >> 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 >> > > > > _________________________________________________________________________ > Professional FreeSWITCH Consulting Services: > consulting@freeswitch.org > http://www.freeswitchsolutions.com > > Official FreeSWITCH Sites > http://www.freeswitch.org > http://confluence.freeswitch.org > http://www.cluecon.com > > 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 >
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
Michael, A few points to clarify: (TL;DR) - Twilio do not support SIP Registration - When Twilio send a call to your IP PBX it will send it based in the origination URI you configured in Twilio page which is documented here: *PLEASE READ THE FOLLOWING DOCS* https://www.twilio.com/blog/2015/07/sip-trunking-load-balancing-and-failover... https://www.twilio.com/blog/2014/12/getting-started-placing-outbound-calls-w... https://www.twilio.com/docs/sip-trunking/getting-started Example: sip:1.1.1.1 (Here we send as Dialed number your Twilio phone number sip:+1661748024@1.1.1.1) sip:2000@1.1.1.1 (Here we send as Dialed number 2000) Twilio outbound profile is used for Outgoing calls from Freeswitch to Twilio. Twilio inbound profile in the documentation is not used at all. For incoming calls you can configure your public.xml to send calls to the context you prefer: <param name="dialplan" value="XML"/> <param name="context" value="public"/> I think at this point your question is can I assign the context via Gateways? I sent an email with this to the mailer. Please monitor that one. (Freeswitch inbound logic match) In my case Im using US IP addresses for Twilio, you may need to change it to your UK (EU datacenter) Let me know if you have other questions related to Twilio. Thanks -Gonzalo On Wed, Oct 7, 2015 at 4:21 AM, Michael Nielsen <mic.niel84@gmail.com> wrote:
Ok, so internal user like /directory/default/twilio.xml and then use the destination number in the HEADER for routing calls? The Twilio guide uses an external gateway and not an internal - but I guess that's wrong...
On Wed, Oct 7, 2015 at 12:19 PM, Sergey Safarov <s.safarov@gmail.com> wrote:
make as i write in prevesion message. 1) 5080 - port is used external profile 2) remove inbound gateway
On Wed, Oct 7, 2015 at 12:02 PM, Michael Nielsen <mic.niel84@gmail.com> wrote:
Hello Sergey,
This is what I've done. 1) Twilio is set up to route calls to sip:my-domain:5080. I've validated that calls are entering my server on port 5080 and sofia/external/ captures it. 2) Twilio IP's are added to my ACL and validated that incoming calls are accepted. 3) I've created a sip_profile/gateway/twilio.xml which contains:
<gateway name="twilio-outbound"> <param name="username" value="MY-USERNAME"/> <param name="password" value="MY-PASSWORD"/> <param name="proxy" value="MY-BUSINESS-NAME.pstn.twilio.com"/> <param name="register" value="false"/> </gateway>
<gateway name="twilio-inbound"> <param name="username" value="MY-USERNAME"/> <param name="password" value="MY-PASSWORD"/> <param name="proxy" value="MY-BUSINESS-NAME.pstn.twilio.com"/> <param name="register" value="false"/> <param name="context" value="default"/> </gateway> Twilio-outbound does work. Twilio-inbound does not place incoming calls in the default context.
If I make a dialplan in /dialplan/public/gateway_incoming.xml which checks if the user exists and then transfer calls, then it works. But I would prefer to have a gateway (or sip_profile) setup correctly for placing calls in default context from Twilio.
On Wed, Oct 7, 2015 at 8:27 AM, Sergey Safarov <s.safarov@gmail.com> wrote:
I read provided doc link. Working scheme: 1) create separate sip_profile for twilio. As example use internal profile. Also you may set port to 5090 in new profile; 2) configure ACL with twilio IP in new profile; 3) set required context in new profile; 4) set correct port in trunk originatin settings on twilio side.
After it incoming calls must work correctly.
On Tue, Oct 6, 2015, 20:32 Michael Nielsen <mic.niel84@gmail.com> wrote:
I'm only able to have Twilio route calls to a URL (such as sip: my-domain.com or sip:1000@my-domain.com:port-number). Whatever I do, I'm not able to get a gateway to register to Twilio.
Would it be a correct way to have my sip_profiles/internal.xml use context default instead of public, so I can catch it in that way? All internal should require authentication.
Here is some info about Twilio and their trunk setup: https://www.twilio.com/docs/sip-trunking/getting-started
My idea of perfect setup would of course to be able to have a sip_profiles/external/twilio.xml which automatically had all incoming calls routed/transfer directly to default context - so my directory-users could receive calls in that manner.
On Tue, Oct 6, 2015 at 3:43 PM, Sergey Safarov <s.safarov@gmail.com> wrote:
It say that twillio is not use your inbound gaeway. It may be deleted. If you want route call via inbound gateway, then configure call routing on twilio side.
In your case incoming call is processed in context configured in sip_profile '<param name="context" value="public"/>'
Alternative it can be setted in directory via '<variable name="user_context" value="targed_context"/>'
On Tue, Oct 6, 2015 at 4:07 PM, Michael Nielsen <mic.niel84@gmail.com > wrote:
> I did have Twilio IP's in ACL - as their guide told me to. > Removing them gives me the following error: > "Rejected by acl "domains". Falling back to Digest auth." > > I do have a twilio.xml in my /sip_profiles/external/ directory and > this does work for outbound calls. > > On Tue, Oct 6, 2015 at 12:57 PM, Sergey Safarov <s.safarov@gmail.com > > wrote: > >> I has two FS serves "client" and provider. >> On client configired gateway. >> On server user in directory. >> >> On servers I take command "originate user/fs2@gateways.rcsnet.ru >> &park()" >> Below two string from FS log >> >> 10:31:55.818435 [NOTICE] switch_channel.c:1055 New Channel >> sofia/external/0000000000@gateways.rcsnet.ru >> [6bc096cb-b903-4b47-9a9b-3fba54c10d6a] >> [INFO] mod_dialplan_xml.c:635 Processing <0000000000>->fs2 in >> context target_context >> >> "target_context" is value of '<param name="context" >> value="target_context"/>' in gateway config file. >> >> Tested on 7add4b2 commit >> >> >> Think you has disable authorization or configure twilio server IP >> addess in ACL. Locate this changes and revert it back. >> >> >> On Tue, Oct 6, 2015 at 12:05 PM, Michael Nielsen < >> mic.niel84@gmail.com> wrote: >> >>> I just did - change to 5080 - and nothing else happens. >>> It still gets routed directly to the public context - without >>> getting "catched" by the gateway-config. >>> >>> I've tried to use the extension parameter in the gateway and route >>> calls from Twilio directly to 1000@my-domain.com:5080, still >>> nothing else happens. >>> >>> >>> On Tue, Oct 6, 2015 at 9:59 AM, Stanislav Sinyagin < >>> ssinyagin@gmail.com> wrote: >>> >>>> Well, if your URL points to 5060, then yes, you need to change it >>>> to 5080 :-)) >>>> >>>> >>>> >>>> On Tue, Oct 6, 2015 at 9:47 AM, Michael Nielsen < >>>> mic.niel84@gmail.com> wrote: >>>> >>>>> I can only give Twilio an url. But I am able to change the >>>>> default Twilio uses, as an example to 5080. Would that trigger the external >>>>> gateway perhaps? >>>>> >>>>> >>>>> On Tuesday, October 6, 2015, Stanislav Sinyagin < >>>>> ssinyagin@gmail.com> wrote: >>>>> >>>>>> but what exactly is configured on twilio side? I guess it >>>>>> should be configurable where it should send calls >>>>>> >>>>>> On Tue, Oct 6, 2015 at 9:27 AM, Michael Nielsen < >>>>>> mic.niel84@gmail.com> wrote: >>>>>> >>>>>>> If I disable registration on my twilio-inbound, it does not >>>>>>> fail - however - incoming calls are still not "catched" by my >>>>>>> twilio-inbound gateway profile. It still lands in the public context >>>>>>> without any variables set. >>>>>>> >>>>>>> On Tue, Oct 6, 2015 at 5:57 AM, Sergey Safarov < >>>>>>> s.safarov@gmail.com> wrote: >>>>>>> >>>>>>>> If disable registration on inbound gateway, then is possible >>>>>>>> receive inbound call? >>>>>>>> >>>>>>>> On Mon, Oct 5, 2015, 22:45 Michael Nielsen < >>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>> >>>>>>>>> Twilio is just taking a sip address as termination address. >>>>>>>>> In this case my domain which FS runs on. >>>>>>>>> Apparently, Twilio is sending calls to the standard 5060 >>>>>>>>> port - which then lands in my public context. >>>>>>>>> >>>>>>>>> On Monday, October 5, 2015, Stanislav Sinyagin < >>>>>>>>> ssinyagin@gmail.com> wrote: >>>>>>>>> >>>>>>>>>> in your pastebin, you seem to receive the call on your >>>>>>>>>> internal profile (port 5060): >>>>>>>>>> 11:18:58.277709 [DEBUG] sofia.c:9229 sofia/internal/+ >>>>>>>>>> 4432445867@sip.ie1.twilio.com receiving invite from >>>>>>>>>> 54.171.127.192:5060 >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> so, what exactly is configured on both sides? The external >>>>>>>>>> profile is usually on the port 5080. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Mon, Oct 5, 2015 at 6:26 PM, Michael Nielsen < >>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>> >>>>>>>>>>> Here's as log from an incoming call from Twilio: >>>>>>>>>>> http://pastebin.com/n0de7jhv >>>>>>>>>>> >>>>>>>>>>> My guess is the problem is with line 33: "Processing >>>>>>>>>>> +4432445867 <+4432445867>->+44213395867 in context public" >>>>>>>>>>> and it fails on line 40: "Regex (FAIL) [gateway_inbound] >>>>>>>>>>> ${target_context}() =~ /^[a-z]/ break=on-false" >>>>>>>>>>> due to the fact that there aren't set any >>>>>>>>>>> ${target_context} variable. >>>>>>>>>>> >>>>>>>>>>> I've added the Twilio inbound gateway as described in the >>>>>>>>>>> Twilio guide, but adding it, removing it etc. doesn't change anything at >>>>>>>>>>> all. >>>>>>>>>>> To the Twilio-Inbound gateway I've added the variable >>>>>>>>>>> ${target_context} according to this guide: >>>>>>>>>>> https://github.com/voxserv/freeswitch_conf_minimal/blob/master/docs/tutorial... >>>>>>>>>>> >>>>>>>>>>> So my guess is that the Twilio-Inbound gateway aren't >>>>>>>>>>> being used - however - calls are routed to my FS. >>>>>>>>>>> >>>>>>>>>>> On Sun, Oct 4, 2015 at 10:15 PM, Michael Nielsen < >>>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>>> >>>>>>>>>>>> I'll create some logs tomorrow. >>>>>>>>>>>> >>>>>>>>>>>> Just to clarify: >>>>>>>>>>>> - Calls are routes from Twilio to my FS >>>>>>>>>>>> - My FS is a clean installation, 1.6.2 >>>>>>>>>>>> - I've used Twilio's guide for setting up gateways, >>>>>>>>>>>> inbound and outbound >>>>>>>>>>>> - Outbound calls are routed correctly >>>>>>>>>>>> - Inbound calls are as mentioned routes to my FS, but my >>>>>>>>>>>> Twilio-inbound doesn't seem to have anything to do with it, therefor, I'm >>>>>>>>>>>> not able to set any variables in incoming calls from Twilio so I can detect >>>>>>>>>>>> them in my public context and transfer them to my default context. >>>>>>>>>>>> >>>>>>>>>>>> I don't want to route all calls in my public context to >>>>>>>>>>>> my default context, this would open a security issue. Only Twilio calls >>>>>>>>>>>> should be handled in such a manner. >>>>>>>>>>>> That's my challenge. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Sunday, October 4, 2015, Sergey Safarov < >>>>>>>>>>>> s.safarov@gmail.com> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Inbound call can be received >>>>>>>>>>>>> 1) if twillio guys configure gateway to route incomes >>>>>>>>>>>>> calls to you >>>>>>>>>>>>> 2) or if FS provide information how to route call for you >>>>>>>>>>>>> >>>>>>>>>>>>> After reading gateway config files, I has found that >>>>>>>>>>>>> used second case "FS provides information how to route calls via >>>>>>>>>>>>> registration mechanism". >>>>>>>>>>>>> >>>>>>>>>>>>> Please: >>>>>>>>>>>>> - configure clean FS host as described in twilio manuals; >>>>>>>>>>>>> - enable siptrace; >>>>>>>>>>>>> - enable debug log; >>>>>>>>>>>>> - make incoming call; >>>>>>>>>>>>> - attach debug log in respond to this message. >>>>>>>>>>>>> >>>>>>>>>>>>> I try help you >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> On Sun, Oct 4, 2015 at 2:37 PM, Michael Nielsen < >>>>>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> Still no luck. >>>>>>>>>>>>>> Any other ideas on how to "catch" the calls from the >>>>>>>>>>>>>> public context in FS? >>>>>>>>>>>>>> My goal is to transfer all calls from Twilio to my >>>>>>>>>>>>>> default context. >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Saturday, October 3, 2015, Michael Nielsen < >>>>>>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> Looking at their guide for secure setup: >>>>>>>>>>>>>>> https://www.twilio.com/resources/images/docs/Twilio-Freeswitch.pdf >>>>>>>>>>>>>>> they've added <param name="register" >>>>>>>>>>>>>>> value="false"/> >>>>>>>>>>>>>>> When I do this, registering doesn't fail (obviously), >>>>>>>>>>>>>>> but inbound calls are still not registered as coming from twilio... They >>>>>>>>>>>>>>> still land directly in the public context without the variables set >>>>>>>>>>>>>>> correctly. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Sat, Oct 3, 2015 at 11:58 AM, Michael Nielsen < >>>>>>>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> When adding the extension, I get the following - even >>>>>>>>>>>>>>>> though my username and password etc. are correct as they work for the >>>>>>>>>>>>>>>> outbound gateway...: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> twilio-inbound Failed Registration [908] >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Sat, Oct 3, 2015 at 11:57 AM, Michael Nielsen < >>>>>>>>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> I see. >>>>>>>>>>>>>>>>> Does it matter that I don't have an extension called >>>>>>>>>>>>>>>>> 1000 in my FS, nor in my Twilio account? >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> On Fri, Oct 2, 2015 at 11:34 PM, Ahmed Habiba < >>>>>>>>>>>>>>>>> ahabiba@gmail.com> wrote: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> if you have a deep look at inbound gateway it is >>>>>>>>>>>>>>>>>> for receiving calls from Twilio as you can see below, this line informing >>>>>>>>>>>>>>>>>> freeswitch where to route inkling call. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> <param name="extension" value="1000"/> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> *From: *Michael Nielsen <mic.niel84@gmail.com> >>>>>>>>>>>>>>>>>> *Date: *October 2, 2015 at 11:24:51 PM GMT+3 >>>>>>>>>>>>>>>>>> *To: *FreeSWITCH Users Help < >>>>>>>>>>>>>>>>>> freeswitch-users@lists.freeswitch.org> >>>>>>>>>>>>>>>>>> *Subject: **Re: [Freeswitch-users] Freeswitch and >>>>>>>>>>>>>>>>>> twilio* >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Outbound works fine. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Without having the inbound gateway calls are still >>>>>>>>>>>>>>>>>> routed to my FS to my public context from Twilio. >>>>>>>>>>>>>>>>>> Adding the twilio-inbound doesn't seem to change >>>>>>>>>>>>>>>>>> anything...? >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> On Friday, October 2, 2015, Brian West < >>>>>>>>>>>>>>>>>> brian@freeswitch.org> wrote: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Well you'd send outbound calls out the outbound >>>>>>>>>>>>>>>>>>> and the inbound one is just to register with twilio so they know where to >>>>>>>>>>>>>>>>>>> send your inbound calls. Nothing more. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> On Fri, Oct 2, 2015 at 1:46 PM, Michael Nielsen < >>>>>>>>>>>>>>>>>>> mic.niel84@gmail.com> wrote: >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> I'm trying to setup twilio as gateway following >>>>>>>>>>>>>>>>>>>> this guide: >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> https://www.twilio.com/docs/sip-trunking/sample-configuration#freeswitch >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> In their example of twiliotrunk.xml they have >>>>>>>>>>>>>>>>>>>> twilio-inbound and twilio-outbound. >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> What is the difference between the two gateways? >>>>>>>>>>>>>>>>>>>> I know their names indicate inbound and outbound calling, but how can >>>>>>>>>>>>>>>>>>>> Freeswitch tell the difference between them. Especially how can Freeswitch >>>>>>>>>>>>>>>>>>>> now to use twilio-inbound for incoming calls from twilio and not just >>>>>>>>>>>>>>>>>>>> twilit-outbound as the only difference is register-proxy and expire-seconds >>>>>>>>>>>>>>>>>>>> between the two? >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Make sense? >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> _________________________________________________________________________ >>>>>>>>>>>>>>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>>>>>>>>>>>>>> consulting@freeswitch.org >>>>>>>>>>>>>>>>>>>> http://www.freeswitchsolutions.com >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Official FreeSWITCH Sites >>>>>>>>>>>>>>>>>>>> http://www.freeswitch.org >>>>>>>>>>>>>>>>>>>> http://confluence.freeswitch.org >>>>>>>>>>>>>>>>>>>> http://www.cluecon.com >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> *Brian West* >>>>>>>>>>>>>>>>>>> brian@freeswitch.org >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> *Twitter: @FreeSWITCH , @briankwest* >>>>>>>>>>>>>>>>>>> http://www.freeswitchbook.com >>>>>>>>>>>>>>>>>>> http://www.freeswitchcookbook.com >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Got Bugs? Report them here >>>>>>>>>>>>>>>>>>> <https://freeswitch.org/jira>! | Reddit: >>>>>>>>>>>>>>>>>>> /r/freeswitch >>>>>>>>>>>>>>>>>>> <https://www.reddit.com/r/freeswitch> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> *T:*+19184209001 | *F:*+19184209002 | *M:*+1918424WEST >>>>>>>>>>>>>>>>>>> (9378) >>>>>>>>>>>>>>>>>>> *iNUM:*+883 5100 1420 9001 | *ISN:*410*543 | >>>>>>>>>>>>>>>>>>> *Skype:*briankwest >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> _________________________________________________________________________ >>>>>>>>>>>>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>>>>>>>>>>>> consulting@freeswitch.org >>>>>>>>>>>>>>>>>> http://www.freeswitchsolutions.com >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Official FreeSWITCH Sites >>>>>>>>>>>>>>>>>> http://www.freeswitch.org >>>>>>>>>>>>>>>>>> http://confluence.freeswitch.org >>>>>>>>>>>>>>>>>> http://www.cluecon.com >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> 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 >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> _________________________________________________________________________ >>>>>>>>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>>>>>>>> consulting@freeswitch.org >>>>>>>>>>>>>> http://www.freeswitchsolutions.com >>>>>>>>>>>>>> >>>>>>>>>>>>>> Official FreeSWITCH Sites >>>>>>>>>>>>>> http://www.freeswitch.org >>>>>>>>>>>>>> http://confluence.freeswitch.org >>>>>>>>>>>>>> http://www.cluecon.com >>>>>>>>>>>>>> >>>>>>>>>>>>>> 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 >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> _________________________________________________________________________ >>>>>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>>>>> consulting@freeswitch.org >>>>>>>>>>> http://www.freeswitchsolutions.com >>>>>>>>>>> >>>>>>>>>>> Official FreeSWITCH Sites >>>>>>>>>>> http://www.freeswitch.org >>>>>>>>>>> http://confluence.freeswitch.org >>>>>>>>>>> http://www.cluecon.com >>>>>>>>>>> >>>>>>>>>>> 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 >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>> _________________________________________________________________________ >>>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>>> consulting@freeswitch.org >>>>>>>>> http://www.freeswitchsolutions.com >>>>>>>>> >>>>>>>>> Official FreeSWITCH Sites >>>>>>>>> http://www.freeswitch.org >>>>>>>>> http://confluence.freeswitch.org >>>>>>>>> http://www.cluecon.com >>>>>>>>> >>>>>>>>> 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 >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> _________________________________________________________________________ >>>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>>> consulting@freeswitch.org >>>>>>>> http://www.freeswitchsolutions.com >>>>>>>> >>>>>>>> Official FreeSWITCH Sites >>>>>>>> http://www.freeswitch.org >>>>>>>> http://confluence.freeswitch.org >>>>>>>> http://www.cluecon.com >>>>>>>> >>>>>>>> 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 >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> _________________________________________________________________________ >>>>>>> Professional FreeSWITCH Consulting Services: >>>>>>> consulting@freeswitch.org >>>>>>> http://www.freeswitchsolutions.com >>>>>>> >>>>>>> Official FreeSWITCH Sites >>>>>>> http://www.freeswitch.org >>>>>>> http://confluence.freeswitch.org >>>>>>> http://www.cluecon.com >>>>>>> >>>>>>> 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 >>>>>>> >>>>>> >>>>>> >>>>> >>>>> _________________________________________________________________________ >>>>> Professional FreeSWITCH Consulting Services: >>>>> consulting@freeswitch.org >>>>> http://www.freeswitchsolutions.com >>>>> >>>>> Official FreeSWITCH Sites >>>>> http://www.freeswitch.org >>>>> http://confluence.freeswitch.org >>>>> http://www.cluecon.com >>>>> >>>>> 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 >>>>> >>>> >>>> >>>> >>>> _________________________________________________________________________ >>>> Professional FreeSWITCH Consulting Services: >>>> consulting@freeswitch.org >>>> http://www.freeswitchsolutions.com >>>> >>>> Official FreeSWITCH Sites >>>> http://www.freeswitch.org >>>> http://confluence.freeswitch.org >>>> http://www.cluecon.com >>>> >>>> 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 >>>> >>> >>> >>> >>> _________________________________________________________________________ >>> Professional FreeSWITCH Consulting Services: >>> consulting@freeswitch.org >>> http://www.freeswitchsolutions.com >>> >>> Official FreeSWITCH Sites >>> http://www.freeswitch.org >>> http://confluence.freeswitch.org >>> http://www.cluecon.com >>> >>> 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 >>> >> >> >> >> _________________________________________________________________________ >> Professional FreeSWITCH Consulting Services: >> consulting@freeswitch.org >> http://www.freeswitchsolutions.com >> >> Official FreeSWITCH Sites >> http://www.freeswitch.org >> http://confluence.freeswitch.org >> http://www.cluecon.com >> >> 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 >> > > > > _________________________________________________________________________ > Professional FreeSWITCH Consulting Services: > consulting@freeswitch.org > http://www.freeswitchsolutions.com > > Official FreeSWITCH Sites > http://www.freeswitch.org > http://confluence.freeswitch.org > http://www.cluecon.com > > 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 >
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
Hi Michael, This is Gonzalo w/ Twilio, I will take a look at the current guides and update them, recently we have been improving the Integration guides with the release of our Secure SIP Trunking. In the TLS/SRTP integration we also have mentioned Inbound GW which may not be necessary. Today we dont support SIP registration. -Gonzalo On Mon, Oct 5, 2015 at 9:26 AM, Michael Nielsen <mic.niel84@gmail.com> wrote:
Here's as log from an incoming call from Twilio: http://pastebin.com/n0de7jhv
My guess is the problem is with line 33: "Processing +4432445867 <+4432445867>->+44213395867 in context public" and it fails on line 40: "Regex (FAIL) [gateway_inbound] ${target_context}() =~ /^[a-z]/ break=on-false" due to the fact that there aren't set any ${target_context} variable.
I've added the Twilio inbound gateway as described in the Twilio guide, but adding it, removing it etc. doesn't change anything at all. To the Twilio-Inbound gateway I've added the variable ${target_context} according to this guide: https://github.com/voxserv/freeswitch_conf_minimal/blob/master/docs/tutorial...
So my guess is that the Twilio-Inbound gateway aren't being used - however - calls are routed to my FS.
On Sun, Oct 4, 2015 at 10:15 PM, Michael Nielsen <mic.niel84@gmail.com> wrote:
I'll create some logs tomorrow.
Just to clarify: - Calls are routes from Twilio to my FS - My FS is a clean installation, 1.6.2 - I've used Twilio's guide for setting up gateways, inbound and outbound - Outbound calls are routed correctly - Inbound calls are as mentioned routes to my FS, but my Twilio-inbound doesn't seem to have anything to do with it, therefor, I'm not able to set any variables in incoming calls from Twilio so I can detect them in my public context and transfer them to my default context.
I don't want to route all calls in my public context to my default context, this would open a security issue. Only Twilio calls should be handled in such a manner. That's my challenge.
On Sunday, October 4, 2015, Sergey Safarov <s.safarov@gmail.com> wrote:
Inbound call can be received 1) if twillio guys configure gateway to route incomes calls to you 2) or if FS provide information how to route call for you
After reading gateway config files, I has found that used second case "FS provides information how to route calls via registration mechanism".
Please: - configure clean FS host as described in twilio manuals; - enable siptrace; - enable debug log; - make incoming call; - attach debug log in respond to this message.
I try help you
On Sun, Oct 4, 2015 at 2:37 PM, Michael Nielsen <mic.niel84@gmail.com> wrote:
Still no luck. Any other ideas on how to "catch" the calls from the public context in FS? My goal is to transfer all calls from Twilio to my default context.
On Saturday, October 3, 2015, Michael Nielsen <mic.niel84@gmail.com> wrote:
Looking at their guide for secure setup: https://www.twilio.com/resources/images/docs/Twilio-Freeswitch.pdf they've added <param name="register" value="false"/> When I do this, registering doesn't fail (obviously), but inbound calls are still not registered as coming from twilio... They still land directly in the public context without the variables set correctly.
On Sat, Oct 3, 2015 at 11:58 AM, Michael Nielsen <mic.niel84@gmail.com
wrote:
When adding the extension, I get the following - even though my username and password etc. are correct as they work for the outbound gateway...:
twilio-inbound Failed Registration [908]
On Sat, Oct 3, 2015 at 11:57 AM, Michael Nielsen < mic.niel84@gmail.com> wrote:
> I see. > Does it matter that I don't have an extension called 1000 in my FS, > nor in my Twilio account? > > On Fri, Oct 2, 2015 at 11:34 PM, Ahmed Habiba <ahabiba@gmail.com> > wrote: > >> if you have a deep look at inbound gateway it is for receiving >> calls from Twilio as you can see below, this line informing freeswitch >> where to route inkling call. >> >> <param name="extension" value="1000"/> >> >> >> >> *From: *Michael Nielsen <mic.niel84@gmail.com> >> *Date: *October 2, 2015 at 11:24:51 PM GMT+3 >> *To: *FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org> >> *Subject: **Re: [Freeswitch-users] Freeswitch and twilio* >> >> >> Outbound works fine. >> >> Without having the inbound gateway calls are still routed to my FS >> to my public context from Twilio. >> Adding the twilio-inbound doesn't seem to change anything...? >> >> >> >> On Friday, October 2, 2015, Brian West <brian@freeswitch.org> >> wrote: >> >>> Well you'd send outbound calls out the outbound and the inbound >>> one is just to register with twilio so they know where to send your inbound >>> calls. Nothing more. >>> >>> On Fri, Oct 2, 2015 at 1:46 PM, Michael Nielsen < >>> mic.niel84@gmail.com> wrote: >>> >>>> I'm trying to setup twilio as gateway following this guide: >>>> >>>> https://www.twilio.com/docs/sip-trunking/sample-configuration#freeswitch >>>> >>>> In their example of twiliotrunk.xml they have twilio-inbound and >>>> twilio-outbound. >>>> >>>> What is the difference between the two gateways? I know their >>>> names indicate inbound and outbound calling, but how can Freeswitch tell >>>> the difference between them. Especially how can Freeswitch now to use >>>> twilio-inbound for incoming calls from twilio and not just twilit-outbound >>>> as the only difference is register-proxy and expire-seconds between the two? >>>> >>>> Make sense? >>>> >>>> >>>> _________________________________________________________________________ >>>> Professional FreeSWITCH Consulting Services: >>>> consulting@freeswitch.org >>>> http://www.freeswitchsolutions.com >>>> >>>> Official FreeSWITCH Sites >>>> http://www.freeswitch.org >>>> http://confluence.freeswitch.org >>>> http://www.cluecon.com >>>> >>>> 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 >>>> >>> >>> >>> >>> -- >>> >>> *Brian West* >>> brian@freeswitch.org >>> >>> >>> *Twitter: @FreeSWITCH , @briankwest* >>> http://www.freeswitchbook.com >>> http://www.freeswitchcookbook.com >>> >>> Got Bugs? Report them here <https://freeswitch.org/jira>! | >>> Reddit: /r/freeswitch <https://www.reddit.com/r/freeswitch> >>> >>> *T:*+19184209001 | *F:*+19184209002 | *M:*+1918424WEST (9378) >>> *iNUM:*+883 5100 1420 9001 | *ISN:*410*543 | *Skype:*briankwest >>> >> >> >> _______________________________________________ >> 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 >> >> >> >> >> _________________________________________________________________________ >> Professional FreeSWITCH Consulting Services: >> consulting@freeswitch.org >> http://www.freeswitchsolutions.com >> >> Official FreeSWITCH Sites >> http://www.freeswitch.org >> http://confluence.freeswitch.org >> http://www.cluecon.com >> >> 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 >> > >
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
I think you should get this book. https://www.packtpub.com/networking-and-servers/freeswitch-12 It is still quite relevant and a good introduction. On Sun, Oct 4, 2015 at 7:37 AM, Michael Nielsen <mic.niel84@gmail.com> wrote:
Still no luck. Any other ideas on how to "catch" the calls from the public context in FS? My goal is to transfer all calls from Twilio to my default context.
On Saturday, October 3, 2015, Michael Nielsen <mic.niel84@gmail.com> wrote:
Looking at their guide for secure setup: https://www.twilio.com/resources/images/docs/Twilio-Freeswitch.pdf they've added <param name="register" value="false"/> When I do this, registering doesn't fail (obviously), but inbound calls are still not registered as coming from twilio... They still land directly in the public context without the variables set correctly.
On Sat, Oct 3, 2015 at 11:58 AM, Michael Nielsen <mic.niel84@gmail.com> wrote:
When adding the extension, I get the following - even though my username and password etc. are correct as they work for the outbound gateway...:
twilio-inbound Failed Registration [908]
On Sat, Oct 3, 2015 at 11:57 AM, Michael Nielsen <mic.niel84@gmail.com> wrote:
I see. Does it matter that I don't have an extension called 1000 in my FS, nor in my Twilio account?
On Fri, Oct 2, 2015 at 11:34 PM, Ahmed Habiba <ahabiba@gmail.com> wrote:
if you have a deep look at inbound gateway it is for receiving calls from Twilio as you can see below, this line informing freeswitch where to route inkling call.
<param name="extension" value="1000"/>
*From: *Michael Nielsen <mic.niel84@gmail.com> *Date: *October 2, 2015 at 11:24:51 PM GMT+3 *To: *FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org> *Subject: **Re: [Freeswitch-users] Freeswitch and twilio*
Outbound works fine.
Without having the inbound gateway calls are still routed to my FS to my public context from Twilio. Adding the twilio-inbound doesn't seem to change anything...?
On Friday, October 2, 2015, Brian West <brian@freeswitch.org> wrote:
Well you'd send outbound calls out the outbound and the inbound one is just to register with twilio so they know where to send your inbound calls. Nothing more.
On Fri, Oct 2, 2015 at 1:46 PM, Michael Nielsen <mic.niel84@gmail.com > wrote:
> I'm trying to setup twilio as gateway following this guide: > > https://www.twilio.com/docs/sip-trunking/sample-configuration#freeswitch > > In their example of twiliotrunk.xml they have twilio-inbound and > twilio-outbound. > > What is the difference between the two gateways? I know their names > indicate inbound and outbound calling, but how can Freeswitch tell the > difference between them. Especially how can Freeswitch now to use > twilio-inbound for incoming calls from twilio and not just twilit-outbound > as the only difference is register-proxy and expire-seconds between the two? > > Make sense? > > > _________________________________________________________________________ > Professional FreeSWITCH Consulting Services: > consulting@freeswitch.org > http://www.freeswitchsolutions.com > > Official FreeSWITCH Sites > http://www.freeswitch.org > http://confluence.freeswitch.org > http://www.cluecon.com > > 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 >
--
*Brian West* brian@freeswitch.org
*Twitter: @FreeSWITCH , @briankwest* http://www.freeswitchbook.com http://www.freeswitchcookbook.com
Got Bugs? Report them here <https://freeswitch.org/jira>! | Reddit: /r/freeswitch <https://www.reddit.com/r/freeswitch>
*T:*+19184209001 | *F:*+19184209002 | *M:*+1918424WEST (9378) *iNUM:*+883 5100 1420 9001 | *ISN:*410*543 | *Skype:*briankwest
_______________________________________________ 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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
maybe it makes sense to order a training? Although the book is usually sufficient to grasp all aspects of the software. On Sun, Oct 4, 2015 at 1:37 PM, Michael Nielsen <mic.niel84@gmail.com> wrote:
Still no luck. Any other ideas on how to "catch" the calls from the public context in FS? My goal is to transfer all calls from Twilio to my default context.
On Saturday, October 3, 2015, Michael Nielsen <mic.niel84@gmail.com> wrote:
Looking at their guide for secure setup: https://www.twilio.com/resources/images/docs/Twilio-Freeswitch.pdf they've added <param name="register" value="false"/> When I do this, registering doesn't fail (obviously), but inbound calls are still not registered as coming from twilio... They still land directly in the public context without the variables set correctly.
On Sat, Oct 3, 2015 at 11:58 AM, Michael Nielsen <mic.niel84@gmail.com> wrote:
When adding the extension, I get the following - even though my username and password etc. are correct as they work for the outbound gateway...:
twilio-inbound Failed Registration [908]
On Sat, Oct 3, 2015 at 11:57 AM, Michael Nielsen <mic.niel84@gmail.com> wrote:
I see. Does it matter that I don't have an extension called 1000 in my FS, nor in my Twilio account?
On Fri, Oct 2, 2015 at 11:34 PM, Ahmed Habiba <ahabiba@gmail.com> wrote:
if you have a deep look at inbound gateway it is for receiving calls from Twilio as you can see below, this line informing freeswitch where to route inkling call.
<param name="extension" value="1000"/>
*From: *Michael Nielsen <mic.niel84@gmail.com> *Date: *October 2, 2015 at 11:24:51 PM GMT+3 *To: *FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org> *Subject: **Re: [Freeswitch-users] Freeswitch and twilio*
Outbound works fine.
Without having the inbound gateway calls are still routed to my FS to my public context from Twilio. Adding the twilio-inbound doesn't seem to change anything...?
On Friday, October 2, 2015, Brian West <brian@freeswitch.org> wrote:
Well you'd send outbound calls out the outbound and the inbound one is just to register with twilio so they know where to send your inbound calls. Nothing more.
On Fri, Oct 2, 2015 at 1:46 PM, Michael Nielsen <mic.niel84@gmail.com > wrote:
> I'm trying to setup twilio as gateway following this guide: > > https://www.twilio.com/docs/sip-trunking/sample-configuration#freeswitch > > In their example of twiliotrunk.xml they have twilio-inbound and > twilio-outbound. > > What is the difference between the two gateways? I know their names > indicate inbound and outbound calling, but how can Freeswitch tell the > difference between them. Especially how can Freeswitch now to use > twilio-inbound for incoming calls from twilio and not just twilit-outbound > as the only difference is register-proxy and expire-seconds between the two? > > Make sense? > > > _________________________________________________________________________ > Professional FreeSWITCH Consulting Services: > consulting@freeswitch.org > http://www.freeswitchsolutions.com > > Official FreeSWITCH Sites > http://www.freeswitch.org > http://confluence.freeswitch.org > http://www.cluecon.com > > 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 >
--
*Brian West* brian@freeswitch.org
*Twitter: @FreeSWITCH , @briankwest* http://www.freeswitchbook.com http://www.freeswitchcookbook.com
Got Bugs? Report them here <https://freeswitch.org/jira>! | Reddit: /r/freeswitch <https://www.reddit.com/r/freeswitch>
*T:*+19184209001 | *F:*+19184209002 | *M:*+1918424WEST (9378) *iNUM:*+883 5100 1420 9001 | *ISN:*410*543 | *Skype:*briankwest
_______________________________________________ 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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com
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 (7)
-
Ahmed Habiba
-
Gonzalo Gasca Meza
-
jungle Boogie
-
Michael Nielsen
-
Russell Treleaven
-
Sergey Safarov
-
Stanislav Sinyagin