Here is the output from "event_route[evapi:message-received]"
Aug 30 13:18:49 everest /usr/local/kamailio/sbin/kamailio[3897]: INFO:
<script>: Message received in evapi:
{"Event":"CGR_AUTH_REPLY","TransactionIndex":39453,"TransactionLabel":1341515504,"MaxSessionTime":60,"Suppliers":"","Error":""}
Aug 30 13:18:49 everest /usr/local/kamailio/sbin/kamailio[3897]: INFO:
<script>: Event received in evapi: "CGR_AUTH_REPLY"
Aug 30 13:19:00 everest /usr/local/kamailio/sbin/kamailio[3891]: ERROR:
tmx [t_var.c:521]: pv_get_tm_reply_code(): unsupported route_type 64
Thanks.
Hello,
wondering if people here can shed some light on few github things:
1) is possible to have a multi-line project description (the text at the
top of https://github.com/kamailio/kamailio)? Maybe a special format (I
tried to add \n or <br />, but they were displayed as is, not interpreted).
I would like to add a short note and a link to a page with commit
guidelines (http://www.kamailio.org/wiki/devel/github-contributions), so
new contributors make proper formatted commits. Displying it at the top
will make it easy to spot, as opposity to adding to readme, which is
shown at the bottom.
2) is there any specific content/marker to add to README to have it
interpreted as markdown (without adding .md extensions)? Something like
a special first or last line, ... It will be displayed nicer, but
renaming will result in changing lot of other places (makefiles, deb/rpm
specs, etc...) and somehow README is the traditional approach for the
kind of this file name for Linux/Unix apps.
Cheers,
Daniel
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.com
I'm trying to use a PSTN gateway with Kamailio for outbound - and incoming
- calls.
Everything seems to be routed correctly, except the PSTN gateway denies the
call due to missing authentication.
How do I add credentials for my PSTN gateway in a secure way?
Best regards,
Michael
My PBX registered in bulk to Kamailio successfully.PBX --> Register --> kamailioPBX <-- 401 with nonce value <-- kamailioPBX --> Register with nonce and md5 response values --> kamailioBOX <-- 200ok <-- kamailioHowever, when one of the PBX client sends an invite out, kamailio AUTH module does not authorize this client:client (813-111-1111) --> Invite --> kamailio
What would be the right way to authorize a 10-digit client to send a call out when a bulk registration and not 10-digit registration is performed.
Your assistance in this matter is greatly appreciatedThanks,Al
Hello!
I'm having problems with Kamailio configuration with TLS. Or, maybe, that's
my misunderstanding about how it should work.
So, the issue - inbound TLS works just great, I can call everyone in my
domain. I have PositiveSSL certificate, so I have such files:
calist.crt AddTrustExternalCARoot.crt + COMODORSAAddTrustCA.crt +
COMODORSADomainValidationSecureServerCA.crt divided by \n
server.key - key
server.crt - cert
The configuration of tls.cfg
[server:default]
method = SSLv23
verify_certificate = no
require_certificate = no
private_key = /etc/ssl/sectel.io.ssl/sip/server.key
certificate = /etc/ssl/sectel.io.ssl/sip/server.crt
ca_list = /etc/ssl/sectel.io.ssl/sip/calist.crt
#crl = /etc/kamailio/crl.pem
(however with or without ca_list nothing changes)
[client:default]
verify_certificate = yes
require_certificate = yes
And with that configuration when I'm trying to call to ostel.co (public SIP
service supporting TLS) from my server I get such error:
ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS write:error:14090086:SSL
routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
Putting that in tls.cfg:
[client:default]
verify_certificate = no
require_certificate = no
Make everything work.
Cross-domain calling is essential and I'm just trying to figure out -
what's the problem? Is that my certificate, is that ostel.co certificate or
it is just the way it should be?
Thanks!
--
Alexandru Covalschi
ABRISS-Solutions
VoIP engineer and system administrator
phone: +37367398493
web: http://abs-telecom.com/
||Hello,
we use Kamailio 4.2 with Presence_DIALOGINFO module for BLF
notifications (blinking lamps on phone panel).
Since version 4.1 Kamailio has a new module parametr "
modparam("presence_dialoginfo", "force_dummy_dialog", 1)" - this option
generate first NOTIFY to Subscribed phone (without PUBLISH message) and
it's lamps became GREEN ( <state>terminated</state>).
Without this module parametr the first NOTIFY won't be sent to phone and
lamps will stay turned off until first PUBLISH will be handled by
presence server.
The first NOTIFY sip message with xml body look like this:
NOTIFY sip:1005@22.22.22.22:1120 SIP/2.0.
To: <sip:1005@11.11.11.11>;tag=867246696.
From: <sip:9095@11.11.11.11>;tag=495949c4c25d687c77ca707bd10a0818-5171.
CSeq: 2 NOTIFY.
Call-ID: 662126467-5060-6(a)BJC.BGI.E.CDD.
Route: <sip:10.60.1.3;r2=on;lr=on>, <sip:11.11.11.11;r2=on;lr=on>.
Content-Length: 272.
User-Agent: kamailio (4.2.3 (x86_64/linux)).
Max-Forwards: 70.
Event: dialog.
Subscription-State: active;expires=600.
Content-Type: application/dialog-info+xml.
.
<?xml version="1.0"?>
<dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="1" ух
state="full" entity="sip:9095@10.60.1.3">
<dialog direction="recipient">
<state>terminated</state>
</dialog>
</dialog-info>
Especially pay attention on XML body.
But for some SIP phones this xml body with state = terminated is not
enough to turn the BLF lamp on. (for example Grandstream phones).
It requires one more or two more fields: "dialog id", "call-id".
<?xml version="1.0"?>
<dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info"
version="28" state="full" entity="sip:9093@10.60.1.3">
<dialog id="830b4fd4-c75d-1233-ca9f-0050569560f4"
call-id="830b4fd4-c75d-1233-ca9f-0050569560f4" direction="recipient">
<state>terminated</state>
</dialog>
</dialog-info>
The question is how to modify this first NOTIFY XML body message to add
"dialog id" and "call-id" to </dialog>.
For example latest Kamailio Kazoo fixed that already. :)
Kind Regards
Ewgeny
Hi,
I am running Kamailio (4.4.0-dev2 (x86_64/linux)) with cgrates
real-time billing application. At the end of a basic call (prepaid to
postpaid), I receive the following error:
ERROR:tmx [t_var.c:521]:pv_get_tm_reply_code():unsupported route_type 64
8(6740) DEBUG:tmx [t_var.c:526]:pv_get_tm_reply_code():reply code is <0>
What does route_type 64 mean? I checked the archive posts (FS#456) and
seemed to be fixed in branch 4.1 (part of 4.1.5).
Thanks.
Hi All,
I have a strange issue occuring, when I enable the siptrace
functionality within the routing logic, I begin to get a bunch of parser
error as show below. Is this normal behaviour or, more than likely, am I
doing something wrong?
I enable siptrace as follows:
request_route {
route("InitialMessageChecks");
sip_trace();
setflag(22);
...
}
event_route[tm:local-request] {
sip_trace();
...
}
When I enable this functions in the routing logic, I begin to see alot
of the following messages in the log file:
ERROR: <core> [parser/parse_fline.c:257]: parse_first_line():
parse_first_line: bad message (offset: 39)
ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg:
message=<#002#020#002#021® #023ÄÔ#002 ÊÂÕ#035mùLàU{#002>
INFO: <core> [parser/parse_fline.c:144]: parse_first_line():
ERROR:parse_first_line: method not followed by SP
ERROR: <core> [parser/parse_fline.c:257]: parse_first_line():
parse_first_line: bad message (offset: 0)
ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg:
message=<#002#020#002#021#023Ä#023Ä#012#007>
ERROR: <core> [parser/parse_fline.c:257]: parse_first_line():
parse_first_line: bad message (offset: 39)
ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg:
message=<#002#020#002#021® #023ÄÔ#002 ÊÂÕ#035mùLàUÞž#002>
ERROR: <core> [parser/parse_fline.c:257]: parse_first_line():
parse_first_line: bad message (offset: 35)
ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg:
message=<#002#020#002#021® #023ÄÔ#002 ÊÂÕ#035mùLàU #011#003>
INFO: <core> [parser/parse_fline.c:144]: parse_first_line():
ERROR:parse_first_line: method not followed by SP
ERROR: <core> [parser/parse_fline.c:257]: parse_first_line():
parse_first_line: bad message (offset: 0)
ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg:
message=<#002#020#002#021#023Ä#023Ä#012#007>
INFO: <core> [parser/parse_fline.c:144]: parse_first_line():
ERROR:parse_first_line: method not followed by SP
ERROR: <core> [parser/parse_fline.c:257]: parse_first_line():
parse_first_line: bad message (offset: 0)
ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg:
message=<#002#020#002#021#023Ä#023Ä#012#007>
INFO: <core> [parser/parse_fline.c:144]: parse_first_line():
ERROR:parse_first_line: method not followed by SP
ERROR: <core> [parser/parse_fline.c:257]: parse_first_line():
parse_first_line: bad message (offset: 0)
ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg:
message=<#002#020#002#021#023Ä#023Ä#012#007>
INFO: <core> [parser/parse_fline.c:144]: parse_first_line():
ERROR:parse_first_line: method not followed by SP
ERROR: <core> [parser/parse_fline.c:257]: parse_first_line():
parse_first_line: bad message (offset: 0)
ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR:
parse_msg: message=<#002#020#002#006y|#023ÄN˜#036ÂÕ#035múLàUű#012>
INFO: <core> [parser/parse_fline.c:144]: parse_first_line():
ERROR:parse_first_line: method not followed by SP
ERROR: <core> [parser/parse_fline.c:257]: parse_first_line():
parse_first_line: bad message (offset: 0)
ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg:
message=<#002#020#002#021#023Ä#023Ä#012#007>
INFO: <core> [parser/parse_fline.c:144]: parse_first_line():
ERROR:parse_first_line: method not followed by SP
ERROR: <core> [parser/parse_fline.c:257]: parse_first_line():
parse_first_line: bad message (offset: 0)
ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg:
message=<#002#020#002#021#023Ä#023Ä#012#007>
INFO: <core> [parser/parse_fline.c:144]: parse_first_line():
ERROR:parse_first_line: method not followed by SP
ERROR: <core> [parser/parse_fline.c:257]: parse_first_line():
parse_first_line: bad message (offset: 0)
ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg:
message=<#002#020#002#021#023Ä#023Ä#012#007>
INFO: <core> [parser/parse_fline.c:144]: parse_first_line():
ERROR:parse_first_line: method not followed by SP
ERROR: <core> [parser/parse_fline.c:257]: parse_first_line():
parse_first_line: bad message (offset: 0)
ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg:
message=<#002#020#002#021#023Ä#023Ä#012#007>
INFO: <core> [parser/parse_fline.c:144]: parse_first_line():
ERROR:parse_first_line: method not followed by SP
ERROR: <core> [parser/parse_fline.c:257]: parse_first_line():
parse_first_line: bad message (offset: 0)
ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg:
message=<#002#020#002#021#023Ä#023Ä#012#007>
INFO: <core> [parser/parse_fline.c:144]: parse_first_line():
ERROR:parse_first_line: method not followed by SP
ERROR: <core> [parser/parse_fline.c:257]: parse_first_line():
parse_first_line: bad message (offset: 0)
ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg:
message=<#002#020#002#021#023Ä#023Ä#012#007>
INFO: <core> [parser/parse_fline.c:144]: parse_first_line():
ERROR:parse_first_line: method not followed by SP
ERROR: <core> [parser/parse_fline.c:257]: parse_first_line():
parse_first_line: bad message (offset: 0)
ERROR: <core> [parser/msg_parser.c:688]: parse_msg(): ERROR: parse_msg:
message=<#002#020#002#021#023Ä#023Ä#012#007>
Is there any way I can disable seeing these messages? What are these
messages?
Any thoughts are appreciated.
Thanks
After updating kamailio I get:
ERROR: Error opening Kamailio's FIFO /var/run/kamailio/kamailio_fifo
ERROR: Make sure you have the line 'modparam("mi_fifo", "fifo_name",
"/var/run/kamailio/kamailio_fifo")' in your config
ERROR: and also have loaded the mi_fifo module.
Any solution?
Best regards
Sven
