Hi Samuel,
We will have a DR tutorial in place next week (after the release).
Now, reading your scenario, I see you have 2 ops here : (1) mapping the
DID to your subscriber (what about using aliases here ?) and (2) doing
call fwd on no-answer for your subscriber (serial forking)
Of course you can combine all this in CR / DR tool, or you can simply
script everything (using aliases and AVPs with serial forking for fallback).
With DR, you need to set in dr_rules the DIDs and to point into
dr_gateways (as IP of the proxy). Now, as attribute of the gateway you
can define the mobile number -> if the call to GW failed, you can use
the attribute and get the mobile number.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 01/18/2013 07:27 PM, Samuel Muller wrote:
Hello Bogdan,
it should be nice to get some tutorials, of course.
but I tried today to understand a bit more the drouting module, and it
does not do what I need, as the carriermodule.
to explain briefly :
an incoming call from PSTN to one of my subscriber DID I've to take in
charge.
the carrierroute module find as prefix the R-URI username and tries to
route the call to one of my other proxy.
but, I get a 408 Time Out and I need to route in fallback to, i.e.,
the PSTN mobile phone of my subscriber.
So, I've to rewrite to R-URI username and send the new request to my
PSTN gateway.
In the drouting module or in the carrierroute, I've no way to find
this new username to rewrite.
I think that I need to add a new column in the carrierfailureroute (or
something equal in the drouting module) that contains the fallback
r-uri username ...
If you have better idea, I take it !
*Samuel MULLER*
[email protected] <mailto:[email protected]>
On Wed, Jan 16, 2013 at 5:49 PM, Bogdan-Andrei Iancu
<[email protected] <mailto:[email protected]>> wrote:
Hi Samuel,
What is the kind of "complexity" you got stuck with DR ? You can
use it both in a simple or a complex way - maybe I can help with it.
Anyhow we plan to publish a tutorial for Dynamic Routing after the
1.9.0 release.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 01/16/2013 03:03 PM, Samuel Muller wrote:
Hey Bogdan,
I already tried the drouting module, I found that it was too
complex for my needs - and I was not agree in some way to take in
charge the routing (source routing is so weird in my case, regex
are not working, and so on) - so I turned back myself to the old
LCR module I used once upon a time which was really sufficient -
to finally use carrierroute - that I thought it was maintained yet.
I'll try again the drouting but I'm not really confident with
this one ...
Thanks a lot,
*Samuel MULLER*
[email protected] <mailto:[email protected]>
On Wed, Jan 16, 2013 at 1:51 PM, Bogdan-Andrei Iancu
<[email protected] <mailto:[email protected]>> wrote:
Hi Samuel,
I would suggest rather using the drouting module instead of
carrierroute (this module is not maintained). With drouting
module you have attributes per rules, per gateways and per
carriers, and you use these attributes for whatever purposes
(and they are available in script).
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 01/16/2013 02:40 PM, Samuel Muller wrote:
Hello,
I've a single question about carrierroute module.
I would like to use the failure route to rewrite the user +
domain to a new one as fallback (i.e. when 4xx catched after
the main carrier route, redirect to another pstn number).
Is there an easy way to do it - as adding a new column in
the carrierfailureroute table ?
I would like to save the db requests ...
thanks a lot,
*Samuel MULLER*
[email protected] <mailto:[email protected]>
_______________________________________________
Users mailing list
[email protected] <mailto:[email protected]>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
