There are multiple ways to do so: first try sip:ipaddr:port?headername=value This is a common way to add headers to SIP URI according to rfc3261 If that won't work for you (which should work), you may also go ds_select_domain ( which replaces R-URI), but add Route by yourself via: with https://www.kamailio.org/docs/modules/6.0.x/modules/dispatcher.html#dispatcher.p.xavp_dst https://www.kamailio.org/docs/modules/6.0.x/modules/dispatcher.html#dispatcher.p.xavp_dst_mode as 1 which executes attrs. You can add your own attribute (like du or route ) and use it as Route header value, then for each chosen destination:
$xavp(_dsdst_=>attrs)) чт, 18 сент. 2025 г. в 15:05, Benoit Panizzon via sr-users < [email protected]>: > Hi all > > Kamailio <=> SBC <=> Interconnection > > 10.1.1.1 <=> i: 10.1.1.2 SBC e: 10.99.1.77 <=> IC: 10.88.88.1 > |> i: 10.1.1.3 SBC e: 10.99.1.77 <=> IC: 10.88.88.2 > > At the moment I have the issue that our commercial SBC can only handle > n to 1 static ingress to egress mappings. > > So basically I can tell the SBC: Do route everything you get from > Kamailio 10.1.1.1 received in 10.1.1.2 to IC peer: 10.88.88.1 and vice > versa. > So I need one internal SBC IP per ic peer. > > But we want redundancy and load balancing. So IC peer (like the largest > telco in Switzerland) increased their redundancy and are reachable on 4 > ip addresses via two independent exchanges. > > Let's use 10.88.88.1 to 10.88.88.4 > > I discovered that our SBC would support Route header. > > At the moment my dispatcher.lst looks like this: > > 1100 sip:10.1.1.2:5060 0 0 name="IC-A" > 1100 sip:10.1.1.3:5060 0 0 name="IC-A" > > But! Is there a possibility to set a route on the dispatcher list? > > Like: > > 1100 sip:10.88.88.1:5060 Route:10.1.1.2:5060 0 0 name="IC-A" > 1100 sip:10.88.88.2:5060 Route:10.1.1.2:5060 0 0 name="IC-A" > 1100 sip:10.88.88.3:5060 Route:10.1.1.2:5060 0 0 name="IC-A" > 1100 sip:10.88.88.4:5060 Route:10.1.1.2:5060 0 0 name="IC-A" > > So I could use only one ip address on the internal SBC interface. > > And I could extend this to further interconnections using only one IP > and have the SBC route according the route header received: > > 1100 sip:10.88.88.1:5060 Route:10.1.1.2:5060 0 0 name="IC-A" > 1100 sip:10.88.88.2:5060 Route:10.1.1.2:5060 0 0 name="IC-A" > 1100 sip:10.88.88.3:5060 Route:10.1.1.2:5060 0 0 name="IC-A" > 1100 sip:10.88.88.4:5060 Route:10.1.1.2:5060 0 0 name="IC-A" > > 1200 sip:10.5.5.10:5060 Route:10.1.1.2:5060 0 0 name="IC-B" > 1200 sip:10.5.5.10:5060 Route:10.1.1.2:5060 0 0 name="IC-B" > > 2000 sip:10.1.1.10:5060 0 0 name="Kamailio-Registrar-A" > 2001 sip:10.1.1.11:5060 0 0 name="Kamailio-Registrar-B" > > 3000 sip:10.1.1.20:5060 0 0 name="Voicemail-A" > 3000 sip:10.1.1.21:5060 0 0 name="Voicemail-B" > > and so on to send call to the various IC via the same SBC ip with pre-set > route? > > The obproxy attribute is only for pings, right? > > Mit freundlichen Grüssen > > -Benoît Panizzon- > -- > I m p r o W a r e A G - Leiter Commerce Kunden > ______________________________________________________ > > Zurlindenstrasse 29 Tel +41 61 826 93 00 > CH-4133 Pratteln Fax +41 61 826 93 01 > Schweiz Web http://www.imp.ch > ______________________________________________________ > __________________________________________________________ > Kamailio - Users Mailing List - Non Commercial Discussions -- > [email protected] > To unsubscribe send an email to [email protected] > Important: keep the mailing list in the recipients, do not reply only to > the sender! >
__________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions -- [email protected] To unsubscribe send an email to [email protected] Important: keep the mailing list in the recipients, do not reply only to the sender!
