Greetings,

Sorry about the confusion, the Routing works perfectly with multiple
addresses in one header. I think i have a better scenario now.

So, i have this SBC with 2 IPs (212.13.40.205 and 212.13.40.209) where in
INVITES i use uac_replace_from() and uac_replace_to(). Kamailio UAC’s
module is set for “AUTO” restore.

In this scenario, the original call arrives at Kamailio like this
(Restore.pcap) :

From: 351211450093

To : 351258064574

The call is routed to my client and the packet leaves Kamailio like this
(Restore.pcap) :

From: +351211450093

To : +351258064574

The info is stored in the “vst” and “vsf” parameters in Record-Route header
( Note : Kamailio has 2 IPs) (Restore.pcap):

Later, i receive a BYE request from the client with To and From like this
(Restore.pcap) :

The To Header has “I2116446I_500” as user part which i think it’s still RFC
compliant. Regarding this i couldn’t find anything proving that wrong.

Here is where the problem starts. If the auto restore is activated, the To
header end result is malformed (Restore.pcap) :

If i deactivate the restore and a similar test, the headers are unchanged
(NotRestore.pcap):

I have a couple questions about this :

Are the vsf and vst alone enough to do a proper restore ?
If not, what inputs does it take ?

Does the “AUTO” restore works if the client sends me a
different user than i sent him ?

Please find the captures mentioned in annex.

Thanks a lot for your help.

Best Regards,

[image: g9telecom]

*Duarte Rocha*
Desenvolvimento de software
T.: 351 211 450 050
F.: 351 221 450 059
www.g9telecom.pt

[Download vCard] <http://public.g9telecom.pt/vCards/tec45er-duarte.vcf>

[image: certif]

Esta mensagem (incluindo anexos) pode conter informação confidencial para
uso exclusivo do destinatário. Se não for o destinatário pretendido não
deverá usar, distribuir ou copiar este e-mail, devendo eliminá-lo e
informar o emissor imediatamente. Obrigado.

This message (including any attachments) may contain confidential
information for the exclusive use of the recipient. If you are not the
intended recipient, you should not use, distribute or copy this email, and
you must delete it and inform the issuer immediately. Thank you.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.