Eric Dean wrote:

...

I have a SER Proxy that is routing calls to a SIP Redirector which then informs SER as to which gateway to send calls to.

GW1 GW2 | | SERProxy------->SIP Redirector | IP Phone

Just a thought, I havent experimented it though. You can have a work-around for this. Contact would still reflect SERProxy and will have gateway prefix like 001 for GW1 002 for GW2 ( Contact: <sip:001<number in orig uri>@SERProxy). This way IP Phone will call the new number on SERProxy and Proxy will send that to appropriate gateway based on prefix.

Hi Eric,

It's just a matter of SER configuration. The service provider may decide on whatever criteria he likes (upstream entity, downstream UA, ACLs, etc) which redirect replies are filtered and processed on server and which ones are forwarded to the UAC.

Best regards, Marian

Eric Dean wrote:

ok..I hesitate to ask...so as not to insult the development community. But do you know of a SIP Proxy that can respond to redirects on behalf od the client?

Marian Dumitru wrote:

...

Hi Eric,

AFAIK, for the moment there is no way to configure this behavior in SER. We are considering extending the UAC module to perform client redirection, but these are only future plans for the moment.

Best regards, Marian

Eric Dean wrote:

...

I have a SER Proxy that is routing calls to a SIP Redirector which then informs SER as to which gateway to send calls to.

GW1 GW2 | | SERProxy------->SIP Redirector | IP Phone

SER is currently sending the redirect to the IP Phone.. .which is unauthorized to send SIP messages to the gateway.

I would like for SER to take a 302 redirect and then proxy the call to the gateway per the redirect..

How do I configure SER to actually proxy the call per the redirect on behalf of the IP Phone?

---

Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers

Hi Erin

So, your problem sounds like: you have these 155,000 NPA/NXX prefixes and for each of them a GW or set of GWs to route through. Right?

If so, there are 2 solution:

1) use the SIP redirector which will generate a SIP redirect to the GW(s) to be used. In this case, from SER script, mark the INVITE before sending it to the Redirector and when the redirect comes (looking to the mark you will know for sure who generated the redirect and it's not coming from another SIP entity) use the future SER UAC redirection feature and send the INVITE the GW mentioned in contact.

2) integrate the redirection logic into SER (to avoid this redirect mechanism) - not sure what kind of logic the Redirector implements, but if it's about prefixes translating into GW address(es), you can use something similar to PDT or LCR modules.

I hope I brought some light on to the problem.

Best regards, Marian

Eric Dean wrote:

Ok..let me be a bit more clear.

We have a SIP redirector...which is just a database bolted onto libsip. This database has an entire LERG per client...which means 155,000 NPA/NXX combinations.... There is no way to manage this in ser.cfg routing...therefore we created it.

However, I simply need a proxy that can query our database and route the call on behalf of the UA to the corresponding gateway/interface.

Marian Dumitru wrote:

...

Hi Eric,

It's just a matter of SER configuration. The service provider may decide on whatever criteria he likes (upstream entity, downstream UA, ACLs, etc) which redirect replies are filtered and processed on server and which ones are forwarded to the UAC.

Best regards, Marian