Hello, what do you mean with:
"Both SIP trunks are IP registration only" Does it mean that you do not know the IPs upfront (they are not static values, they can change)? So the trunk sends REGISTER requests in order to let the proxy know where to send traffic to it? If you know the IP addresses upfront, then dispatcher should help (like the others recommended). Use ds_select_domain() to pick up round-robin sip-server2x, then use script operations to add the number in front of domain $rd and then to update the user part $rU If it is the case with registrations, then let us know and we can provide hints how to solve that one as well. Cheers, Daniel On 23.05.20 23:33, christian (cx labs) wrote: > Hi, > > I'm trying to set up a Kamailio server as a proxy to forward SIP > messages between two trunks, where I manipulate only the INVITE in the > following manner: > > incoming call: > INVITE +4969123456@server1 > > outgoing call: > round robin to > INVITE user@4969123456-sip-server2a > INVITE user@4969123456-sip-server2b > INVITE user@4969123456-sip-server2c > > Can anyone point me in the right direction? Both SIP trunks are IP > registration only. Also, I am aware how strange this is, but the > upstream service has decided to interpret SIP in a novel way. > > Cheers, > Chris > > _______________________________________________ > Kamailio (SER) - Users Mailing List > [email protected] > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Funding: https://www.paypal.me/dcmierla
_______________________________________________ Kamailio (SER) - Users Mailing List [email protected] https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
