Robert Dyck wrote: > Question, is $Ri ( the source IP ) writable and if so would this arbitrary > information be available to add_rcv_param?
Hi Robert! No, it is not readable. It would have to be added to Contact URI parameter as well, e.g. "sip:.....;socket=ip.add.re.ss:port" Looks like there is always some source code editing necessary - for adding the socket parameter. Forcing the sendsocket during INVITE routing could be done by extending the force_sendsocket to accept PV too (if it does not yet) or as a workaround by using dp_apply_policy() from domainpolicy module and setting the send_socket_avp manually. regards klaus > On Monday 21 April 2008, Klaus Darilion wrote: >> Hi all! >> >> FYI: I just found this old thread: >> http://www.openser.org/pipermail/devel/2006-March/002188.html >> >> I think this could work too. The openser is stateless and encodes the >> routing information into Contact URI param: >> http://openser.org/docs/modules/1.3.x/nathelper.html#AEN376 >> >> >> Further, if save() is used too (not for routing!!!!), then the openser >> can be used for NAT pinging too. >> >> regards >> Klaus >> >> Robert McNaught schrieb: >>> Hi, >>> >>> Has anyone replaced the functionality of a kagoor voiceflow session >>> border controller with openser? and is it possible? >>> >>> TIA >>> >>> Robert >>> >>> _______________________________________________ >>> Users mailing list >>> [email protected] >>> http://lists.openser.org/cgi-bin/mailman/listinfo/users >> _______________________________________________ >> Users mailing list >> [email protected] >> http://lists.openser.org/cgi-bin/mailman/listinfo/users > > _______________________________________________ Users mailing list [email protected] http://lists.openser.org/cgi-bin/mailman/listinfo/users
