You can do it however you like, but a common way this is handled is to map the
DID to a registrar AOR using alias_db, then to revert the user part of the
request URI to the DID (having stored it in a variable prior to the alias_db
lookup).
However, not all registrants can accept an invite to a different RURI than the
Contact binding they registered. Some want exactly that one and none other
than. But if you're sure your registrant can, that would be the way to do it.
"Daniel W. Graham" <d...@cmsinter.net> wrote:
>Wondering how others handle DID routing?
>
>I have seen some former posts that talk about using alaias_db, however
>the request URI gets changed to the users SIP URI and the receiving
>device (asterisk) cant distinguish the DID as a result.
>
>Any thoughts are appreciated.
>
>-dan
>
>
>------------------------------------------------------------------------
>
>_______________________________________________
>SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
>sr-users@lists.sip-router.org
>http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Sent from my mobile, and thus lacking in the refinement one might expect from a
fully fledged keyboard.
Alex Balashov - Principal
Evariste Systems LLC
235 E Ponce de Leon Ave
Suite 106
Decatur, GA 30030
United States
Tel: +1-678-954-0670
Web: http://www.evaristesys.com/, http://www.alexbalashov.com
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
