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 <r...@rupa.com>
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

Reply via email to