Hi,
thanks very much for your reply. That's also what i thought, first it
was just a siptrace where opensips sends to the second gw but the invite
got no Record-route header.
But later on, I was able to reproduce the problem and when adding
another record_route() the second invite is indeed fixed (contains a
record-route header)? Maybe there is some other reason for this behavior
i am not seeing yet?
Best Regards
Max M.
On 03/14/2013 05:35 PM, Muhammad Shahzad wrote:
No, I think the serial forked invite contains same RR and in general
all changes you did to original invite just before creating the
transaction (by calling t_newtrans or t_relay or any t_* function that
creates transaction).
Thank you.
On Thu, Mar 14, 2013 at 5:15 PM, Max Mühlbronner <[email protected]
<mailto:[email protected]>> wrote:
Hi,
I am not sure about record-routing in combination with failover of
drouting. Maybe someone knows for sure :)
If i got a configuration where i am record_routing on inital
invite, but later there is a failover (use_next_gw() returns true)
and the call is sent to the next gateway. But the serial forked
call (second INVITE) is missing the Record-route header?
Does this mean i just have to explicitly call record routing again
on failover? But to me it seems like this can't be right, or is
this correct/expected behaviour?
|
if (use_next_gw()) {
...
record_route();
|}
Best Regards
--
Max Mühlbronner
42com Telecommunication GmbH
Straße der Pariser Kommune 12-16
10243 Berlin
E-Mail:[email protected] <mailto:[email protected]>
Web:www.42com.com <http://www.42com.com>
Firmenangaben/Company information:
Handelsregister/Commercial register: Amtsgericht Berlin HRB 99071 B
Umsatzsteuer-ID/VAT-ID: DE223812306
Geschäftsführer/CEO: Thomas Reinig, Alexander Reinig
Diese E-Mail enthält Informationen von 42com Telecommunication GmbH. Diese
sind möglicherweise vertraulich und ausschließlich für den Adressaten bestimmt.
Sollten Sie diese elektronische Nachricht irrtümlicherweise erhalten haben, so
informieren Sie uns bitte unverzüglich telefonisch oder per E-Mail.
This message is intended only for the use of the individual or entity to
which it is addressed. If you have received this message by mistake, please
notify us immediately.
_______________________________________________
Users mailing list
[email protected] <mailto:[email protected]>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
--
Mit freundlichen Grüßen
Muhammad Shahzad
-----------------------------------
CISCO Rich Media Communication Specialist (CRMCS)
CISCO Certified Network Associate (CCNA)
Cell: +49 176 99 83 10 85
MSN: [email protected] <mailto:[email protected]>
Email: [email protected] <mailto:[email protected]>
_______________________________________________
Users mailing list
[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
