On Saturday 17 August 2013 06:50:25 Daniel W. Graham wrote:
> I didn't think of pulling from to header, but in my case the to changes so
> I think storing in avp may be my only option.
As Alex mentioned, the to header might be filled with something else. In my
use case people fooling around with
I didn't think of pulling from to header, but in my case the to changes so I
think storing in avp may be my only option. Since the call will be sent to an
asterisk farm, I think I'll have to prepend rU with did after alias db lookup
so while in 'asterisk land', the did and associated user is ret
Yes, but there is absolutely no requirement, arising from the standards, that
the To URI have any relationship to the RURI. The To header is, from a semantic
point of view, a purely cosmetic commentary on the intended logical destination
of the call. Most endpoints will put the dialed digits in
On Thursday 15 August 2013 20:55:27 Alex Balashov wrote:
> 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 loo
Yeah that was what I was thinking but wasn't confident it was the most
efficient or 'right' way of handling it. Sounds like it is my best option. I do
have registrants that can't accept the behavior so I will probably add a column
to the subscriber table or add a usr_preference to distinguish th
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
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
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
___
