On 4/30/15 9:28 AM, Alex Balashov wrote:
No, that's not correct. The provider needs to send DNIS in the RURI in these
cases, and providers should have a setting to enable this. It does require
overriding the Contact binding of the registrant (if applicable), which is not
RFC-compliant, but tha
No, that's not correct. The provider needs to send DNIS in the RURI in these
cases, and providers should have a setting to enable this. It does require
overriding the Contact binding of the registrant (if applicable), which is not
RFC-compliant, but that's okay.
--
Alex Balashov | Principal | E
On 4/30/15 7:35 AM, Alex Balashov wrote:
On 04/30/2015 07:31 AM, Andres wrote:
I am inclined to believe this is perfectly normal and compliant but let
me know what you think.
Yep, it's normal. Moreover, only the RURI value should be used for
routing purposes or for anything else that's conse
On 04/30/2015 07:31 AM, Andres wrote:
I am inclined to believe this is perfectly normal and compliant but let
me know what you think.
Yep, it's normal. Moreover, only the RURI value should be used for
routing purposes or for anything else that's consequential in relation
to the destination;
I have a general question maybe somebody can help me out with. We have
a new SIP Trunk setup with a provider. The SIP Trunk has a username of
'jane' and it handles 400 DIDs. When the incoming INVITE from the
provider comes in, the URI in the Invite is the username of the trunk
while the To h
