Hi,
They are different. RURI is the part in request's first line, while the
DURI is a an outbound proxy used just to finding the destination at
network level (it will not be present in the SIP request).
by using the set functions you do not create a new branch, you are just
changing the RURI and DURI from the default branch. To create a new
branch you have to use append_branch().
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 22.06.2016 17:13, Ramachandran, Agalya (Contractor) wrote:
Hi Bogdan,
Request URI and destination URI are one and the same right?
Basically what I understand from the below mail is , we can use both
seturi and setdsturi to set a new branch.
Am I right?
Regards,
Agalya
*From:*Bogdan-Andrei Iancu [mailto:[email protected]]
*Sent:* Wednesday, June 22, 2016 3:15 AM
*To:* Ramachandran, Agalya (Contractor) <[email protected]>
*Cc:* OpenSIPS users mailling list <[email protected]>
*Subject:* Re: [OpenSIPS-Users] DNS-SRV query in opensips
Hi Agalya,
seturi() and setdsturi() set the RURI / DestinationURI for the current
message / branch.
When you do an append_branch() a new branch is stored for
serial/parallel forking (note that the current branch does not changes
- this is branch number 1).
So, append_branch() will make a copy of the current branch (RURI,
DURI, PATH, Forced Socket, etc) and store a new branch for later forking.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 21.06.2016 21:08, Ramachandran, Agalya (Contractor) wrote:
Hi Bogdan,
I have a question regarding /seturi/and /setdsturi///function calls.
As far as my understanding, when append_branch() is called, seturi
() is called to set the URI where to fork the call.
I tried by calling only /seturi ()/function call, after
append_branch it was working same behavior as when I used
/setdsturi()/as well.
My question is do we really need /setdsturi /or when is the case
when /setdsturi()/is used.?
Regards,
Agalya
*From:*Bogdan-Andrei Iancu [mailto:[email protected]]
*Sent:* Tuesday, June 21, 2016 3:41 AM
*To:* OpenSIPS users mailling list <[email protected]
<mailto:[email protected]>>; Ramachandran, Agalya
(Contractor) <[email protected]
<mailto:[email protected]>>; Ramachandran, Agalya
(Contractor) <[email protected]
<mailto:[email protected]>>
*Subject:* Re: [OpenSIPS-Users] DNS-SRV query in opensips
Hi Agalya,
OpenSIPS does full flavor DNS lookup (with NATPR and SRV), but
this is internal, and not accessible from script. OpenSIPS
implements auto DNS-based failover :
http://www.opensips.org/html/docs/modules/2.2.x/tm.html#id293694
My understanding is you want the DNS resolving to be done at
script level and to have access to the results ?
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 20.06.2016 20:35, Ramachandran, Agalya (Contractor) wrote:
Hi team,
We are using opensips for our project requirements.
I have a scenario where we need DNS-SRV query and the result
of this should be placed as the desturi to send request
out.(In case of forking call)
As far as I went through opensips documentation, there are
some core parameters for dns related config such as
“dns_retr_time
<https://www.opensips.org/Documentation/Script-CoreParameters-1-11#toc44>”
,”dns_retr_time
<https://www.opensips.org/Documentation/Script-CoreParameters-1-11#toc44>”
,”dns_servers_no
<https://www.opensips.org/Documentation/Script-CoreParameters-1-11#toc46>”
etc…
According to my understanding these config variables can be
declared and used in the opensips.config file to control the
settings of DNS query.
Is there any available function where I can use and pass the
DNS server domain name, so that it fetches the IP address of
the host ?
Please let us know what is the best way to achieve this?
Regards,
Agalya
_______________________________________________
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
