Re: [Freeswitch-users] Confusing handling of incoming calls
0. Probably, gonna have to go get them on the phone.1. No, but the information I need to process is stored in separate databases by gateway. There is no single table that has all of the DIDs and which gateway they belong to. I could create/maintain that table, but if I can determine the gateway before beginning my logic, I can avoid that. Original Message Subject: Re: [Freeswitch-users] Confusing handling of incoming calls From: Rupa Schomaker Date: Wed, July 22, 2009 6:04 am To: freeswitch-users@lists.freeswitch.org On Wed, Jul 22, 2009 at 5:11 AM, Pete Mueller <p...@privateconnect.com> wrote: 0) Rupa, you are absolutely right, I forgot that. ports was never an issue because previous gateways all REGISTERed. I will have to swap my ports around as bandwidth is not flexible. You can't tell bandwidth.com to use port 5080? 1) I thought of this, but I have hundreds of DID, (around 600 at the moment) and maintaining that mapping in the dialplan would be a mess. AFTER I know what gateway the call arrived on, I have a database for each gateway that helps me process from there. You have cases where the same DID maps differently for one gateway or another? If not, why is the gateway part of the database query? 2) Yes, separate profiles would work, but does sound gross. I'm going to swap my ports around and see if that clears things up... -pete Original Message ---- Subject: Re: [Freeswitch-users] Confusing handling of incoming calls From: Rupa Schomaker <r...@rupa.com> Date: Wed, July 22, 2009 2:12 am To: freeswitch-users@lists.freeswitch.org On Tue, Jul 21, 2009 at 11:35 PM, Pete Mueller <p...@privateconnect.com> wrote: My goal is:0) figure out why the bandwidth gateway is being processed as "internal" (this is more of a security thing) they are probably terminating traffic on port 5060 rather than 5080. 5060 is internal, 5080 is external. 1) have both gateways enter at the same point in the dialplan (this seems to be the purpose of the "Extension" param) I'd drop the extension param and instead match on the destination_number (the DID used to reach you). 2) be able to identify which gateway the call came in on. I was hoping to set a param in the gateway configuration that would be passed through onto the channel, but have not found one. Worst case, I could have each gateway enter at a different extension in the dialplan, however, that doesn't seem to be working if the channel comes in the "internal" profile. Not sure here... gateways are an outbound thing. Inbound calls just hit your dialplan and you process from there. A sledgehammer approach would be to have a different sip_profile for each gateway. But that is just silly. Flowroute at least puts their name in the sdp Thanks for your help. I've provided INFO dumps from both gateways if they help...-pete-- -Rupa ___ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org ___ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org -- -Rupa ___ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org ___ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
Re: [Freeswitch-users] Confusing handling of incoming calls
On Jul 22, 2009, at 8:04 AM, Rupa Schomaker wrote: On Wed, Jul 22, 2009 at 5:11 AM, Pete Mueller wrote: 0) Rupa, you are absolutely right, I forgot that. ports was never an issue because previous gateways all REGISTERed. I will have to swap my ports around as bandwidth is not flexible. You can't tell bandwidth.com to use port 5080? Yes you can... I do it all the time. 1) I thought of this, but I have hundreds of DID, (around 600 at the moment) and maintaining that mapping in the dialplan would be a mess. AFTER I know what gateway the call arrived on, I have a database for each gateway that helps me process from there. You have cases where the same DID maps differently for one gateway or another? If not, why is the gateway part of the database query? 2) Yes, separate profiles would work, but does sound gross. I'm going to swap my ports around and see if that clears things up... -pete ___ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
Re: [Freeswitch-users] Confusing handling of incoming calls
On Wed, Jul 22, 2009 at 5:11 AM, Pete Mueller wrote: > 0) Rupa, you are absolutely right, I forgot that. ports was never an issue > because previous gateways all REGISTERed. I will have to swap my ports > around as bandwidth is not flexible. > You can't tell bandwidth.com to use port 5080? > > 1) I thought of this, but I have hundreds of DID, (around 600 at the > moment) and maintaining that mapping in the dialplan would be a mess. AFTER > I know what gateway the call arrived on, I have a database for each gateway > that helps me process from there. > You have cases where the same DID maps differently for one gateway or another? If not, why is the gateway part of the database query? > > 2) Yes, separate profiles would work, but does sound gross. I'm going to > swap my ports around and see if that clears things up... > > -pete > > ---- Original Message ---- > Subject: Re: [Freeswitch-users] Confusing handling of incoming calls > From: Rupa Schomaker > Date: Wed, July 22, 2009 2:12 am > To: freeswitch-users@lists.freeswitch.org > > > > On Tue, Jul 21, 2009 at 11:35 PM, Pete Mueller wrote: > >> My goal is: >> 0) figure out why the bandwidth gateway is being processed as "internal" >> (this is more of a security thing) >> > > they are probably terminating traffic on port 5060 rather than 5080. 5060 > is internal, 5080 is external. > > >> >> 1) have both gateways enter at the same point in the dialplan (this seems >> to be the purpose of the "Extension" param) >> > > I'd drop the extension param and instead match on the destination_number > (the DID used to reach you). > > >> 2) be able to identify which gateway the call came in on. I was hoping to >> set a param in the gateway configuration that would be passed through onto >> the channel, but have not found one. Worst case, I could have each gateway >> enter at a different extension in the dialplan, however, that doesn't seem >> to be working if the channel comes in the "internal" profile. >> > > Not sure here... gateways are an outbound thing. Inbound calls just hit > your dialplan and you process from there. A sledgehammer approach would be > to have a different sip_profile for each gateway. But that is just silly. > Flowroute at least puts their name in the sdp > > >> Thanks for your help. I've provided INFO dumps from both gateways if they >> help... >> -pete >> > > > -- > -Rupa > -- > ___ > FreeSWITCH-users mailing list > FreeSWITCH-users@lists.freeswitch.org > http://lists.freeswitch.org/mailman/listinfo/freeswitch-users > UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users > http://www.freeswitch.org > > > ___ > FreeSWITCH-users mailing list > FreeSWITCH-users@lists.freeswitch.org > http://lists.freeswitch.org/mailman/listinfo/freeswitch-users > UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users > http://www.freeswitch.org > > -- -Rupa ___ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
Re: [Freeswitch-users] Confusing handling of incoming calls
On Jul 22, 2009, at 5:11 AM, Pete Mueller wrote: 0) Rupa, you are absolutely right, I forgot that. ports was never an issue because previous gateways all REGISTERed. I will have to swap my ports around as bandwidth is not flexible. What do you mean here? 1) I thought of this, but I have hundreds of DID, (around 600 at the moment) and maintaining that mapping in the dialplan would be a mess. AFTER I know what gateway the call arrived on, I have a database for each gateway that helps me process from there. XML_CURL? 2) Yes, separate profiles would work, but does sound gross. I'm going to swap my ports around and see if that clears things up... -pete ___ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
Re: [Freeswitch-users] Confusing handling of incoming calls
0) Rupa, you are absolutely right, I forgot that. ports was never an issue because previous gateways all REGISTERed. I will have to swap my ports around as bandwidth is not flexible.1) I thought of this, but I have hundreds of DID, (around 600 at the moment) and maintaining that mapping in the dialplan would be a mess. AFTER I know what gateway the call arrived on, I have a database for each gateway that helps me process from there.2) Yes, separate profiles would work, but does sound gross. I'm going to swap my ports around and see if that clears things up... -pete Original Message Subject: Re: [Freeswitch-users] Confusing handling of incoming calls From: Rupa Schomaker Date: Wed, July 22, 2009 2:12 am To: freeswitch-users@lists.freeswitch.org On Tue, Jul 21, 2009 at 11:35 PM, Pete Mueller <p...@privateconnect.com> wrote: My goal is:0) figure out why the bandwidth gateway is being processed as "internal" (this is more of a security thing) they are probably terminating traffic on port 5060 rather than 5080. 5060 is internal, 5080 is external. 1) have both gateways enter at the same point in the dialplan (this seems to be the purpose of the "Extension" param) I'd drop the extension param and instead match on the destination_number (the DID used to reach you). 2) be able to identify which gateway the call came in on. I was hoping to set a param in the gateway configuration that would be passed through onto the channel, but have not found one. Worst case, I could have each gateway enter at a different extension in the dialplan, however, that doesn't seem to be working if the channel comes in the "internal" profile. Not sure here... gateways are an outbound thing. Inbound calls just hit your dialplan and you process from there. A sledgehammer approach would be to have a different sip_profile for each gateway. But that is just silly. Flowroute at least puts their name in the sdp Thanks for your help. I've provided INFO dumps from both gateways if they help...-pete-- -Rupa ___ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org ___ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
Re: [Freeswitch-users] Confusing handling of incoming calls
On Tue, Jul 21, 2009 at 11:35 PM, Pete Mueller wrote: > My goal is: > 0) figure out why the bandwidth gateway is being processed as "internal" > (this is more of a security thing) > they are probably terminating traffic on port 5060 rather than 5080. 5060 is internal, 5080 is external. > > 1) have both gateways enter at the same point in the dialplan (this seems > to be the purpose of the "Extension" param) > I'd drop the extension param and instead match on the destination_number (the DID used to reach you). > 2) be able to identify which gateway the call came in on. I was hoping to > set a param in the gateway configuration that would be passed through onto > the channel, but have not found one. Worst case, I could have each gateway > enter at a different extension in the dialplan, however, that doesn't seem > to be working if the channel comes in the "internal" profile. > Not sure here... gateways are an outbound thing. Inbound calls just hit your dialplan and you process from there. A sledgehammer approach would be to have a different sip_profile for each gateway. But that is just silly. Flowroute at least puts their name in the sdp > Thanks for your help. I've provided INFO dumps from both gateways if they > help... > -pete > -- -Rupa ___ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
[Freeswitch-users] Confusing handling of incoming calls
I have two different gateways setup on my server. One with FlowRoute (which uses SIP REGISTER) and one with bandwidth.com (which does not). I can send and receive from both gateways, but the dialplan processing seems to be confused. Calls from bandwidth do not respect the "Extension" param in the gateway configuration and have the Destination-Number = the inbound caller ID, whereas calls coming from flowroute do respect the param, and have a Destination-Number of "PrivateConnect". Setting "From-user" and "from-domain" on the bandwidth gateway does not seems to affect anything either, though these may be for outbound calls only.One thing I noticed, calls from the FlowRout gateway have a channel of the form of "sofia/external/@" where bandwidth.com channels have the form of "sofia/internal/@". The "Internal" profile is what's confusing me. as both calls are coming from external gateways (defined in the "sip_profiles/external" directory.I also noticed that bandwidth uses "internal" non-routeable IP addresses as part of the SIP URI. I thought might be confusing the system. My goal is:0) figure out why the bandwidth gateway is being processed as "internal" (this is more of a security thing)1) have both gateways enter at the same point in the dialplan (this seems to be the purpose of the "Extension" param)2) be able to identify which gateway the call came in on. I was hoping to set a param in the gateway configuration that would be passed through onto the channel, but have not found one. Worst case, I could have each gateway enter at a different extension in the dialplan, however, that doesn't seem to be working if the channel comes in the "internal" profile.Thanks for your help. I've provided INFO dumps from both gateways if they help...-peteHere is the INFO from a bandwidth.com call:EXECUTE sofia/internal/+1480...@192.168.47.68 info()2009-07-21 21:13:47.479471 [INFO] mod_dptools.c:946 CHANNEL_DATA:Channel-State: [CS_EXECUTE]Channel-State-Number: [4]Channel-Name: [sofia/internal/+1480...@192.168.47.68]Unique-ID: [0da43b5a-7676-11de-aa26-1dfbbe056c65]Call-Direction: [inbound]Presence-Call-Direction: [inbound]Answer-State: [ringing]Channel-Read-Codec-Name: [PCMU]Channel-Read-Codec-Rate: [8000]Channel-Write-Codec-Name: [PCMU]Channel-Write-Codec-Rate: [8000]Caller-Username: [+1480xxx]Caller-Dialplan: [XML]Caller-Caller-ID-Name: [+1480xxx]Caller-Caller-ID-Number: [+1480xxx]Caller-Network-Addr: [216.82.224.202]Caller-Destination-Number: [+14082561963]Caller-Unique-ID: [0da43b5a-7676-11de-aa26-1dfbbe056c65]Caller-Source: [mod_sofia]Caller-Context: [public]Caller-Channel-Name: [sofia/internal/+1480...@192.168.47.68]Caller-Profile-Index: [1]Caller-Profile-Created-Time: [1248236027477846]Caller-Channel-Created-Time: [1248236027477846]Caller-Channel-Answered-Time: [0]Caller-Channel-Progress-Time: [0]Caller-Channel-Progress-Media-Time: [0]Caller-Channel-Hangup-Time: [0]Caller-Channel-Transfer-Time: [0]Caller-Screen-Bit: [true]Caller-Privacy-Hide-Name: [false]Caller-Privacy-Hide-Number: [false]variable_sip_received_ip: [216.82.224.202]variable_sip_received_port: [5060]variable_sip_via_protocol: [udp]variable_sip_authorized: [true]variable_sip_from_user: [+1480xxx]variable_sip_from_uri: [+1480...@192.168.47.68]variable_sip_from_host: [192.168.47.68]variable_sip_from_user_stripped: [1480xxx]variable_sip_from_tag: [gK0b629aa9]variable_sofia_profile_name: [internal]variable_sip_req_params: [transport=udp]variable_sip_req_user: [+14082561963]variable_sip_req_port: [5060]variable_sip_req_uri: [+14082561...@70.99.197.36:5060]variable_sip_req_host: [70.99.197.36]variable_sip_to_user: [+14082561963]variable_sip_to_uri: [+14082561...@192.168.4.90]variable_sip_to_host: [192.168.4.90]variable_sip_contact_user: [+1480xxx]variable_sip_contact_port: [5060]variable_sip_contact_uri: [+1480...@192.168.47.68:5060]variable_sip_contact_host: [192.168.47.68]variable_channel_name: [sofia/internal/+1480...@192.168.47.68]variable_sip_call_id: [1376511423_73037...@192.168.47.68]variable_sip_via_host: [216.82.224.202]variable_max_forwards: [32]variable_presence_id: [+1480...@192.168.47.68]variable_sip_nat_detected: [true]variable_switch_r_sdp: [v=0o=Sonus_UAC 23552 274 IN IP4 192.168.47.68s=SIP Media Capabilitiesc=IN IP4 67.231.4.98t=0 0m=audio 25748 RTP/AVP 0 18 101a=rtpmap:0 PCMU/8000a=rtpmap:18 G729/8000a=fmtp:18 annexb=noa=rtpmap:101 telephone-event/8000a=fmtp:101 0-15a=maxptime:20]variable_remote_media_ip: [67.231.4.98]variable_remote_media_port: [25748]variable_read_codec: [PCMU]variable_read_rate: [8000]variable_write_codec: [PCMU]variable_write_rate: [8000]variable_endpoint_disposition: [RECEIVED]variable_outside_call: [true]variable_current_application: [info]Here is the flowroute INFO:EXECUTE sofia/external/+1480...@66.53.188.187 info()2009-07-21 21:17:49.5616 [INFO] mod_dptools.c:946 CHANNEL_DATA:Channel-State: [CS_EXECUTE]Channel-State-Number: [4]Channel-Name: [sofia/externa
