[SR-Users] force_send_socket in event route tm:local-request

[Kristian F. Høgh]

Hi,

Our kamailio 4.0.6 proxy uses pua/pua_dialoginfo and an external presence server.
The PUBLISH requests generated by pua* appear in tm:local-request event route.

Before sending, we call set_advertised_address and force_send_socket.
Still the requests have the IP address from the first "listen=" as source and Via address.
The requests are send out using the correct interface and no errors are logged.

When forwarding SUBSCRIBE requests received from clients, force_send_socket before t_relay_to_udp do work as expected.

mhomed=1 solves the issue, but I prefer force_send_socket.

Regards,
Kristian Høgh
Uni-tel

[Daniel-Constantin Mierla]

Hello,

I think the ougoing request is already created in that event route, the
set advertise address being used too late from that perspective --
however, there is no hook before to set it.

Open an enhancement issue on the tracker not to forget about it and I
will check to see if there is a possibility to add this feature.

Cheers,
Daniel

Post by Kristian F. Høgh
Hi,
Our kamailio 4.0.6 proxy uses pua/pua_dialoginfo and an external presence server.
The PUBLISH requests generated by pua* appear in tm:local-request event route.
Before sending, we call set_advertised_address and force_send_socket.
Still the requests have the IP address from the first "listen=" as source and Via address.
The requests are send out using the correct interface and no errors are logged.
When forwarding SUBSCRIBE requests received from clients, force_send_socket before t_relay_to_udp do work as expected.
mhomed=1 solves the issue, but I prefer force_send_socket.
Regards,
Kristian Høgh
Uni-tel
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

[Kristian Frederik Høgh]

Hi Daniel,

FS#462 created
http://sip-router.org/tracker/index.php?do=details&task_id=462

/Kristian.

________________________________________
Fra: sr-users-bounces-cR8azDVoa3IcDhw6gZKtMWD2FQJk+8+***@public.gmane.org <sr-users-bounces-***@public.gmane.orger.org> på vegne af Daniel-Constantin Mierla <miconda-***@public.gmane.org>
Sendt: 21. august 2014 17:11
Til: Kamailio (SER) - Users Mailing List
Emne: Re: [SR-Users] force_send_socket in event route tm:local-request

Hello,

I think the ougoing request is already created in that event route, the
set advertise address being used too late from that perspective --
however, there is no hook before to set it.

Open an enhancement issue on the tracker not to forget about it and I
will check to see if there is a possibility to add this feature.

Cheers,
Daniel

Post by Kristian F. Høgh
Hi,
Our kamailio 4.0.6 proxy uses pua/pua_dialoginfo and an external presence server.
The PUBLISH requests generated by pua* appear in tm:local-request event route.
Before sending, we call set_advertised_address and force_send_socket.
Still the requests have the IP address from the first "listen=" as source and Via address.
The requests are send out using the correct interface and no errors are logged.
When forwarding SUBSCRIBE requests received from clients, force_send_socket before t_relay_to_udp do work as expected.
mhomed=1 solves the issue, but I prefer force_send_socket.
Regards,
Kristian Høgh
Uni-tel
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Next Kamailio Advanced Trainings 2014 - http://www.asipto.com
Sep 22-25, Berlin, Germany ::: Oct 15-17, San Francisco, USA