Hi,
since we integrated IPv6 into our existing routing logic, in some cases
"fix_nated_sdp" gets called for IPv6 calls, too. (Actually, this just
happens because of the mistakenly detected NAT.) But that ends up with a an
error in the log.
ERROR: nathelper [nathelper.c:1685]: replace_sdp_ip(): not an IPv4 address
in 'c=' SDP
So I'm looking for a way to exempt IPv6 calls from that. But I can't find a
pseudovariable which carries the SDP contact IP. I guess I could take some
function from the sdpops module, but is there a more convenient way to get
just the contact IP?
Best Regards,
Sebastian
Registrar module save() function stores "received" field in wrong format like
sip:2601:3:8805:107:41E6:C7A1:7724:CF01:5062
When lookup() config function is executed for ipv6 client, kamailio log shows
error
Feb 3 12:07:34 east /usr/local/sbin/kamailio[16069]: ERROR: tm [ut.h:254]:
uri2dst2(): ERROR: uri2dst: bad_uri: sip:2601:3:8
805:107:41E6:C7A1:7724:CF01:5062
Feb 3 12:07:34 east /usr/local/sbin/kamailio[16069]: ERROR: tm
[t_fwd.c:1709]: t_forward_nonack(): ERROR: t_forward_nonack:
failure to add branches
Is it kamailio bug or a problem with my config?
Hey community,
I'm trying to understand t_relay () when a forward times out.
This is an abbreviated version of what i have:
Request_route {
...
Route(do1)
}
Route [do1] {
...
T_on_reply (1reply)
T_on_failure (1fail)
T_relay ()
}
Reply_route[1reply] {
...
If (t_check_status (302)) {
Route (do2)
}
}
Failure_route [1fail] {
Xlog (dafail1)
}
Route [do2]{
...
T_on_reply (2reply)
T_on_failure (2fail)
T_relay ()
}
Reply_route [2reply]{
Xlog (twerked)
}
Failure_route [2fail]{
Xlog (failured)
}
The case im currently interested in is when the first relay (do1) returns a
302 and then the second (do2) times out.
What happens on the second when it times out, it hits the 1fail
failure_route. This messes with my logic as i would've expected (and want
to find out how to make it) hit the 2nd failure_route.
I also noticed that if i loop and try the do2 again after the first failure
it will then hit the 2fail route.
Any clarification on this subject would be greatly appreciated,
Ryan
Hello,
I am counting the number o dialogs using this:
# kamctl fifo dlg_list |grep dialog:: |wc -l
126
However when I use 'get_statistics dialog:' I get this:
# kamctl fifo get_statistics dialog:
dialog:active_dialogs = 67
dialog:early_dialogs = 3
dialog:expired_dialogs = 253
dialog:failed_dialogs = 29529
dialog:processed_dialogs = 338783
The number of dialogs don't match (i tested this several times).
What could be causing this? (I am using kamailio 4.1).
Regards,
Takeshi
Hello All,
I currently am running Kamailio in a WSS configuration with sipML5. I use
rtpengine to convert a RTP/SAVPF packet to a RTP/AVP packet as the
destination server only supports AVP or SAVP.
RTPEngine has no issues rewriting the packet going out, the SIP session
comes up and handshakes correctly to start the session. Then the remote
server sends the RTP stream back and I'm having issues getting Kamailio or
RTPEngine or something to take the RTP stream, process it back to SAVPF and
send it back out the WSS port. I see no RTP data come from Kam/RTPengine
going towards the remote server.
On the server side, I do see STUN being called and the sipML5 bind
successfully but that's it.
Both the destination and server sit without firewalls in the way so the
problem has to be what I'm doing in Kamailio.
My config is located here:
http://pastebin.com/dWLdUz5j
Packet dumps available upon request.
Thanks for any assistance!
Hi,
I am currently experiencing an intermittent one way audio issue, when using RTPEngine and proxying between srtp and rtp. There is no apparent pattern, I have managed to repeat the on the 7th, 23rd, and 63rd calls to a test number, where upon connection only audio in the RTP => SRTP direction was working. All other test calls worked as normal. Digging through the RTPEngine log file the only abnormalities I can see are: Discarded invalid SRTP packet: authentication failed entries on the calls that had the one way audio issue.
What could be causing this?
Thanks
Tim.
Hello,
I'm very disappointed because of the following behaviour:
if ($tu=~"^sip:0[1-9]{9}") {
[.]
In that case, Kamailio returns TRUE because the instructions in
the block are executed.
}
if ($rU=~"^33" || $rU=~"^0033" || $rU=~"^0[1-9]{9}" || $rU=~"^\+33" ||
$tu=~"^sip:33" || $tu=~"^sip:0033" || $tu=~"^sip:0[1-9]{9}" ||
$tu=~"^sip:\+33" ) {
[.]
In that case, Kamailio should return FALSE because the instructions in the
block are not executed.
}
Am I missed something regarding 'OR' ?
Regards,
Igor.
Hello. We use 2 kamailio server 4.3 master brancher for load balansing
cluster. We have some problems with this deplooiment
fist of all we have REgstering issue: Witth one server all works fine (we
have some endpoints with same creditians) all endpoints reinging well. But
at 2 servers we hawe problem with this- call ringing only at one endpoint.
We use Database for USRLOC module
modparam("usrloc", "db_url", DBURL)
modparam("usrloc", "db_mode", 3)
modparam("usrloc", "use_domain", MULTIDOMAIN)
As i think it mean al connections to servers ives at database. We have one
database for 2 servers and this is means it only one table LOCATION for its.
The second problen id that when loadbalanser sends bye to kamailio from the
outside- bye is not recieves to endpoint. It say that no transaction with
this CallID. I think it is because transaction goues through another
kamailio and kamiaio that recieves BYE does not know about it transaction.
So my first qestion- Does anybody have some information about loafd
balansiong between kamailios?
And second question - how to resolve issue with LOCATION table?
Thanks
