Hi Toyima,
I would suggest something like aliases for that (alias from SIP user to
ISDN number) (the alias_db module with a separate dedicated table for this)
Regards,
Bogdan
Toyima Dias wrote:
Hi Bogdan,
Just to let you know why i have to change destiny...
I have gateways RTB, R2, ISDN, QGIS, etc...
If A in PROXY_A wants to call B (B@PROXY_B <mailto:B@PROXY_B>) on
PROXY_B, PROXY_A will have many routes to reachto usear B, like the
following:
directly from PROXY_A to PROXY_B, if it fails for some reason then:
from PROXY_A to ISDN_GW ---> ISDN_B_GW...
.
.
.
In the last case i have to change the R-URI "B@PROXY_B
<mailto:B@PROXY_B>" to ISDN_NUMBER_ASSIGNED_TO_B@ISDN_GW
<mailto:ISDN_NUMBER_ASSIGNED_TO_B@ISDN_GW> so it can reach the isdn GW
and then converts this to isdn signaling to communicate with ISDN_B_GW
Does the dialplan module can do this? i mean, assign on-the-flight
variables to change the user-id of the R-URI depending on the
destination selected?
Best Regards!
2011/3/1 Bogdan-Andrei Iancu <[email protected]
<mailto:[email protected]>>
Hi Toyima,
you have 2 things here:
- domain routing - this is automatically done via DNS based
forwarding
- username routing - not sure why you want to change the dialed
username, but if there is not mapping logic for (B->12345 ,
C->47896, etc) you can use aliases or dialplan module for
translating these usernames.
Regards,
Bogdan
Toyima Dias wrote:
Hello,
I'm having doubts with the following architecture:
A---PROXY_A---PROXY_B---B
A calls B with the R-URI: B@PROXY_B <mailto:B@PROXY_B
<mailto:B@PROXY_B>>
This will reach at PROXY_A; but here i need to make some
dinamic changes...
if the destiny is B@PROXY_B <mailto:B@PROXY_B
<mailto:B@PROXY_B>> i must set the R-URI with a number:
12345@PROXY_B <mailto:12345@PROXY_B <mailto:12345@PROXY_B>>
If the destiny is C@PROXY_B <mailto:C@PROXY_B
<mailto:C@PROXY_B>> i must set the R-URI like this:
47896@PROXY_B <mailto:47896@PROXY_B <mailto:47896@PROXY_B>>
Setting different routes on the script is not the best way,
bacause i won't define routes for every destination at the
same domain. Dinamyc routing should help and also avps i
guess, am i right? what should i check to accomplish this?
Using Remote-Party-ID or/and P-Asserted-Identity will also help?
Any clarification will be much appreciated!
------------------------------------------------------------------------
_______________________________________________
Users mailing list
[email protected] <mailto:[email protected]>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
--
Bogdan-Andrei Iancu
OpenSIPS eBootcamp - 28th February 2011
OpenSIPS solutions and "know-how"
_______________________________________________
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
--
Bogdan-Andrei Iancu
OpenSIPS eBootcamp - 28th February 2011
OpenSIPS solutions and "know-how"
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
