[SR-Users] #!define and #!subst problem

Hi! I tried #!subst /IPADDRESS_VIRTUAL/83.136.32.161/ listen=udp:IPADDRESS_VIRTUAL:5060 and #!define IPADDRESS_VIRTUAL 83.136.32.161 listen=udp:IPADDRESS_VIRTUAL:5060 Both do not work - am I doing something wrong or is this a known limitation with listen statements? Thanks Klaus

[SR-Users] Question about LCR

Hello, I have a question about LCR which I have been unable to solve. I have 4 upstream carrier gateways owned by 2 carriers. Each carrier provides a primary and secondary gateway for load balancing purposes. On a 5XX error I am trying to send the same call to the other carrier. If both

Re: [SR-Users] #!define and #!subst problem

Hello, subst is replacing inside the sintring values, those being in between quotes, like: #subst /404/408/ sl_send_reply(404, Timeout) The define is replacing ID tokes, which are alpha-numeric tokens stand alone. In your case, you try to replace inside a composite value, and the ip address

Re: [SR-Users] Question about LCR

Hello, I am not an extensive user of lcr module, but probably next_gw() adds a branch each time is called in failure route. If yes (when true you should see some parallel forking, depending o how the addresses are selected), you can mark the bad branches with a branch flag and drop them in a

Re: [SR-Users] #!define and #!subst problem

Daniel-Constantin Mierla wrote: Hello, subst is replacing inside the sintring values, those being in between quotes, like: #subst /404/408/ sl_send_reply(404, Timeout) The define is replacing ID tokes, which are alpha-numeric tokens stand alone. In your case, you try to replace inside a

Re: [SR-Users] Question about LCR

Daniel-Constantin Mierla writes: The issue I am running into is that in a scenario where both my carriers respond with a 5XX, I end up presenting the same call to all 4 gateways. I would like to present the call to one gateway on each carrier and not try the same carriers second gateway