I want to distingguish 200 OK is for INVITE or reINVITE。
so I do this:
request_route {
if (is_method("INVITE") && !has_totag()) {
$dlg_var(is_init_invite) = "1";
}
}
onreply_route {
xlog("L_INFO","[$rs-$rr][is_init_invite:$dlg_var(is_init_invite)]");
if (is_method("INVITE") && t_check_status("200") &&
$dlg_var(is_init_invite) == "1") {
# do somting
$dlg_var(is_init_invite) = "0";
}
xlog("L_INFO","[$rs-$rr][is_init_invite:$dlg_var(is_init_invite)]");
}
What I confuse is：
When I recive 100 Trying LOG is
[100 - Trying][is_init_invite:0]
[100 - Trying][is_init_invite:1]
why is_init_invite is 0?
Hello there,
I'm designing and implementing a kamailio solution for sip routing between
several softswitch based on prefixes.
IIn this setup i will need an b2bua in order to do topology hiding and also
to make transparent the call transfer between phones registered in kamailio
and softswitches(that doesn't support very well REFER messages).
I was searching what solution should I use and I found 3 opensource
solutions that for me seems to be acceptable:
Sems.
Freeswitch.
Opensips with module b2bua.
Based on your experience and contemplating the stability, performance and
support, what is the solution that you advice me ?
Thank you for you time.
Anthony
Hi
Is the function 't_reply_with_body' currently available in Kamailio. I am using 4.3.5
I get the error0(7176) ERROR: <core> [cfg.y:3295]: yyparse(): cfg. parser: failed to find command t_reply_with_body (params 3)
thanks
Hi,
a suggestion for Kamailio 5.0 is to get rid of the cryptic, case
sensitive pseudo-variable names.
Instead we replace them with descriptive names like the ones already
provided by the TLS module.
The current pseudo variables are a constant nuisance unless you deal
with Kamailio every day and know them all by heart. They are an
unnecessary barrier for new users learning Kamailio and force you to
refer to the documentation more often than necessary.
Ideally there would be a script to replace old variable names in
configuration files with the new ones to make the transition less painful.
-Sven
Hi All,
I am trying to get attributes from the Proxy-Authenticate WWW-Authenticate
and Authorization headers, namely username, realm, uri, nonce, and
response,
I can see some of these are already presented as psuedo-variables, however
nonce and response are not.
What's the most efficient way to obtain these headers? I'm currently using
a regex, but there must be a more efficient method.
Thanks for your help,
Matthew
Halo, my name dadang setiawan
sample case
VOIP Server A
IP Address : 192.168.10.57
voip number Jon 100
Voip server B
IP Address : 192.168.15.30
voip number Brian 200
i am using linphone video for comunication jon & brian
the question is
How to solution comunication jon with brian
withhout 200(a)192.168.15.30
but direct 200 without using @
KAMAILIO Installation Problem
Fred: re confusion. A few more details.
Site 1 is a development site. The project in question is VoIP, using ANTISIP. A Windows server application is monitoring activities and carrying out local functions via IPhones. It has a LAN with static IPs for:
· Windows 10 PC used for development
· Windows 10 laptop, used for testing
· MACBOOK, used for IPhone development
· ‘Other PC’, recently converted to Linux + KAMailIO, using the binaries installation route rather than the source code route.
It has a Comcast Modem/Router, Cisco DPC3941B
Site 2 is a business site, which demonstrates the application using its own Windows PC and IPhones. It does not have any static IPs.
Each site uses IPhones as the user interface of this application, via cell or WIFI.
Both sites can communicate via SIP.ANTISIP.COM
Site 1 can communicate with site 1 KAMAILIO but site 2 cannot: timeouts occur.
I just installed what seems like a standard package:
· Debian 32 or 64 bit graphical
· Apt-get install git gcc make flex bison mysql-server kamailio-mysql-modules kamailio-tls-modules kamailio
Should be OK so far apart from the .COM name of the Linux box. I then updated files as described earlier and the problems start. Apart from changing a few constants, I have not altered any script, I am just using the standard one shipped in the package above. I’ve had to guess how to tell KAMailIO about the static IP.
I have a local area network with:
· A Windows PC with a VOIP application
· A Linux PC with KAMailIO
There is also a remote Windows PC with the same VOIP application.
There is also an IPhone VOIP application that communicates with the Windows PC application.
All communications use the same KAMailIO system.
The IPhone application communicates with the PC on the local network. It times out trying to communicate.
I have tried a URL and a static IP address for SIP_DOMAIN, neither succeeds.
Here are some extracts from the log (ignore timestamp gap, several calls were attempted). I think the problem is that the reply to the PC is being sent to 192.168.1.12 instead of 92.13.147.87.
Mar 4 00:28:51 SIS-Server kamailio[18136]: DEBUG: <core> [ip_addr.c:243]: print_ip(): tcpconn_new: new tcp connection: 92.13.147.87
Mar 4 00:28:52 SIS-Server kamailio[18130]: DEBUG: tls [tls_server.c:354]: tls_accept(): TLS accept successful
Mar 4 00:28:52 SIS-Server kamailio[18130]: DEBUG: tls [tls_server.c:361]: tls_accept(): tls_accept: new connection from 92.13.147.87:49302 using TLSv1/SSLv3 AES256-SHA 256
Mar 4 00:28:52 SIS-Server kamailio[18130]: DEBUG: tls [tls_server.c:364]: tls_accept(): tls_accept: local socket: 96.81.57.12:5061
Mar 4 00:28:52 SIS-Server kamailio[18130]: DEBUG: auth [api.c:86]: pre_auth(): auth:pre_auth: Credentials with realm '96.81.57.12' not found
Mar 4 00:28:55 SIS-Server kamailio[18130]: DEBUG: registrar [reply.c:374]: build_contact(): created Contact HF: Contact: <sip:hvs_uk_pc@192.168.1.12:49302;transport=TLS;line=b3d07204a26e36e>;expires=120
Mar 4 00:37:09 SIS-Server kamailio[18135]: DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: 11==9 && [96.81.57.12] == [127.0.0.1]
Mar 4 00:37:09 SIS-Server kamailio[18135]: DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 5060 (advertise 0) matches port 5060
Mar 4 00:37:09 SIS-Server kamailio[18135]: DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: 11==13 && [96.81.57.12] == [192.168.1.181]
Mar 4 00:37:09 SIS-Server kamailio[18135]: DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 5060 (advertise 0) matches port 5060
Mar 4 00:37:09 SIS-Server kamailio[18135]: DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: 11==11 && [96.81.57.12] == [96.81.57.12]
Mar 4 00:37:09 SIS-Server kamailio[18135]: DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 5060 (advertise 0) matches port 5060
Mar 4 00:37:09 SIS-Server kamailio[18135]: DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: 11==9 && [96.81.57.12] == [127.0.0.1]
Mar 4 00:37:09 SIS-Server kamailio[18135]: DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 5060 (advertise 0) matches port 5060
Mar 4 00:37:09 SIS-Server kamailio[18135]: DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: 11==13 && [96.81.57.12] == [192.168.1.181]
Mar 4 00:37:09 SIS-Server kamailio[18135]: DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 5060 (advertise 0) matches port 5060
Mar 4 00:37:09 SIS-Server kamailio[18135]: DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: 11==11 && [96.81.57.12] == [96.81.57.12]
Mar 4 00:37:09 SIS-Server kamailio[18135]: DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 5060 (advertise 0) matches port 5060Mar 4 00:37:12 SIS-Server kamailio[18136]: ERROR: <core> [tcp_main.c:4159]: handle_tcpconn_ev(): connect 192.168.1.12:49302 failed
Changes to KAMCTLRC are:
SIP_DOMAIN=ed-todd-randd.com
DBENGINE=MYSQL
DBNAME=kamailio
DBRWUSER="kamailio"
DBRWPW="kamailiorw"
Changes to KAMAILIO.CFG are:
#!define WITH_MYSQL
#!define WITH_AUTH
#!define WITH_USRLOCDB
#!define WITH_TLS
Plus I set debug=4 for logging.
Whatsmyip.org shows the right IP address (static) and hostname www.ed-todd-randd.com
So, any clues?
I have a local area network with:
· A Windows PC with a VOIP application
· A Linux PC with KAMailIO
There is also a remote Windows PC with the same VOIP application.
There is also an IPhone VOIP application that communicates with the Windows PC application.
All communications use the same KAMailIO system.
The IPhone application communicates with the PC on the local network. It times out trying to communicate.
The application works fine with either PC on another server (sip.antisip.com)
I have tried a URL and a static IP address for SIP_DOMAIN, neither succeeds.
Here are some extracts from the log (ignore timestamp gap, several calls were attempted). I think the problem is that the reply to the PC is being sent to 192.168.1.12 instead of 92.13.147.87.
Mar 4 00:28:51 SIS-Server kamailio[18136]: DEBUG: <core> [ip_addr.c:243]: print_ip(): tcpconn_new: new tcp connection: 92.13.147.87
Mar 4 00:28:52 SIS-Server kamailio[18130]: DEBUG: tls [tls_server.c:354]: tls_accept(): TLS accept successful
Mar 4 00:28:52 SIS-Server kamailio[18130]: DEBUG: tls [tls_server.c:361]: tls_accept(): tls_accept: new connection from 92.13.147.87:49302 using TLSv1/SSLv3 AES256-SHA 256
Mar 4 00:28:52 SIS-Server kamailio[18130]: DEBUG: tls [tls_server.c:364]: tls_accept(): tls_accept: local socket: 96.81.57.12:5061
Mar 4 00:28:52 SIS-Server kamailio[18130]: DEBUG: auth [api.c:86]: pre_auth(): auth:pre_auth: Credentials with realm '96.81.57.12' not found
Mar 4 00:28:55 SIS-Server kamailio[18130]: DEBUG: registrar [reply.c:374]: build_contact(): created Contact HF: Contact: <sip:hvs_uk_pc@192.168.1.12:49302;transport=TLS;line=b3d07204a26e36e>;expires=120
Mar 4 00:37:09 SIS-Server kamailio[18135]: DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: 11==9 && [96.81.57.12] == [127.0.0.1]
Mar 4 00:37:09 SIS-Server kamailio[18135]: DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 5060 (advertise 0) matches port 5060
Mar 4 00:37:09 SIS-Server kamailio[18135]: DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: 11==13 && [96.81.57.12] == [192.168.1.181]
Mar 4 00:37:09 SIS-Server kamailio[18135]: DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 5060 (advertise 0) matches port 5060
Mar 4 00:37:09 SIS-Server kamailio[18135]: DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: 11==11 && [96.81.57.12] == [96.81.57.12]
Mar 4 00:37:09 SIS-Server kamailio[18135]: DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 5060 (advertise 0) matches port 5060
Mar 4 00:37:09 SIS-Server kamailio[18135]: DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: 11==9 && [96.81.57.12] == [127.0.0.1]
Mar 4 00:37:09 SIS-Server kamailio[18135]: DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 5060 (advertise 0) matches port 5060
Mar 4 00:37:09 SIS-Server kamailio[18135]: DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: 11==13 && [96.81.57.12] == [192.168.1.181]
Mar 4 00:37:09 SIS-Server kamailio[18135]: DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 5060 (advertise 0) matches port 5060
Mar 4 00:37:09 SIS-Server kamailio[18135]: DEBUG: <core> [socket_info.c:583]: grep_sock_info(): grep_sock_info - checking if host==us: 11==11 && [96.81.57.12] == [96.81.57.12]
Mar 4 00:37:09 SIS-Server kamailio[18135]: DEBUG: <core> [socket_info.c:587]: grep_sock_info(): grep_sock_info - checking if port 5060 (advertise 0) matches port 5060Mar 4 00:37:12 SIS-Server kamailio[18136]: ERROR: <core> [tcp_main.c:4159]: handle_tcpconn_ev(): connect 192.168.1.12:49302 failed
Changes to KAMCTLRC are:
SIP_DOMAIN=ed-todd-randd.com
DBENGINE=MYSQL
DBNAME=kamailio
DBRWUSER="kamailio"
DBRWPW="kamailiorw"
Changes to KAMAILIO.CFG are:
#!define WITH_MYSQL
#!define WITH_AUTH
#!define WITH_USRLOCDB
#!define WITH_TLS
Plus I set debug=4 for logging.
Whatsmyip.org shows the right IP address (static) and hostname www.ed-todd-randd.com
So, any clues?
Hi,
If I understand the DMQ documentation correctly, when a SIP request is
distributed to other Kamailio instances via dmq_t_replicate(), it is not
merely sent as a payload in a novel way, but actually "rehydrated" by
the receiver into a mock request on the other end and processed as
through it were a "real" message that came into the request_route[] in
the natural way.
Is this an accurate assumption?
-- Alex
--
Alex Balashov | Principal | Evariste Systems LLC
303 Perimeter Center North, Suite 300
Atlanta, GA 30346
United States
Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
