Hi,
I have another update.
The problem that I had is fixed now and it is fixed in an unexpected way!
The fix seems to be in changing the SIPp default client scenario. In
specific, once I change the UAC.xml in SIPp trunk to generate the "BYE"
message's "To" field like this:
To: sut
>
inst
Shedding some more light on the situation, here are some further facts I
could figure out:
1) I did the same test without the proxy in between (UAC <--> UAS) purely
in SIPp, everything was fine, no dead call error
2) With the Kamailio proxy in between, I can see that there is a problem in
call te
Thanks very much Daniel,
This is solving a part of my issue for now.
Here is the routing section of my configuration file (it may be good to
share it once complete as a minimally working proxy):
route{
> if (!mf_process_maxfwd_header("10")) {
> sl_reply("483","Too Many Ho
Hello,
listen is to specify local ip address or network interface on which
kamailio should listen for sip traffic.
To send to an ip address there are couple of variants, in config file:
$ru = "sip:" + $rU + "@__NEXT_PROXY_IP__";
t_relay();
exit;
Or, if you don't want to change the r-uri, the
Dear Kamailio users,
I am trying to set up a simple scenario as follows:
UAC --> Proxy_1 --> Proxy_2 --> Proxy_3 --> UAC
I am new to Kamailio and had the following basic questions that came to my
mind after reading the documentation an the default kamilio.cfg config
script:
1) Is there any good
