Hi,
Downloaded Kamailio-4.2.1.tar.gz file from Kamailio.org site and compiled it on RHEL 6.2 server. Configured as per setup instruction given in attached document. While start pcscf, getting the following errors:
Jan 20 01:25:17 localhost pcscf: INFO: <core> [ppcfg.c:80]: pp_subst_add(): ### added subst expression: /PORT/4060/
Jan 20 01:25:17 localhost pcscf: INFO: <core> [ppcfg.c:80]: pp_subst_add(): ### added subst expression: /NETWORKNAME/open-ims.test/
Jan 20 01:25:17 localhost pcscf: INFO: <core> [ppcfg.c:80]: pp_subst_add(): ### added subst expression: /HOSTNAME/pcscf.open-ims.test/
Jan 20 01:25:17 localhost ./pcscf[4201]: INFO: rr [../outbound/api.h:54]: ob_load_api(): Failed to import bind_ob
Jan 20 01:25:17 localhost ./pcscf[4201]: INFO: rr [rr_mod.c:160]: mod_init(): outbound module not available
Jan 20 01:25:17 localhost ./pcscf[4201]: INFO: ims_usrloc_pcscf [hslot.c:62]: ul_init_locks(): locks array size 512
Jan 20 01:25:17 localhost ./pcscf[4201]: INFO: path [../outbound/api.h:54]: ob_load_api(): Failed to import bind_ob
Jan 20 01:25:17 localhost ./pcscf[4201]: INFO: path [path_mod.c:147]: mod_init(): outbound module not available
Jan 20 01:25:17 localhost ./pcscf[4201]: ERROR: registrar [reg_mod.c:352]: mod_init(): can't bind usrloc
Jan 20 01:25:17 localhost ./pcscf[4201]: ERROR: <core> [sr_module.c:968]: init_mod(): Error while initializing module registrar (/usr/local/lib64/kamailio/modules/registrar.so)
Please help us to resolve above issue.
Thanks,
Sravan.
============================================================================================================================
Disclaimer: This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at http://www.techmahindra.com/Disclaimer.html externally http://tim.techmahindra.com/tim/disclaimer.html internally within TechMahindra.
============================================================================================================================
Hi all!
Seems to be an old topic but still unclean is it possible or not, please
correct me if I'm wrong.
There are some old threads like
http://lists.sip-router.org/pipermail/users/2007-May/011278.html
I use Kamailio 4.2.1 trying to create intercepting registrar proxy, which
handles NAT (rewrites contact), forwards REGISTER to backend and then
stores REGISTER in its internal location on 200 OK from backend, so I call
save() from reply route in noreply mode.
The problem is, it stores IP source of reply as 'received' and modified
contact which i sent out to backend server as 'contact', so it loses
original information from initial REGISTER.
Is there a way to make save() use original request fields like T_req($ct),
or some way to call save() with full set of custom params?
Of course, I can save() all REGISTERs in request_route and then delete on
backend fail, but it seems to be waste of resources, especially when
REGISTER traffic is high :(
I'd be glad to hear any advice.
Hi all!
Seems to be an old topic but still unclean is it possible or not, please
correct me if I'm wrong.
There are some old threads like
http://lists.sip-router.org/pipermail/users/2007-May/011278.html
I use Kamailio 4.2.1 trying to create intercepting registrar proxy, which
handles NAT (rewrites contact), forwards REGISTER to backend and then
stores REGISTER in its internal location on 200 OK from backend, so I call
save() from reply route in noreply mode.
The problem is, it stores IP source of reply as 'received' and modified
contact which i sent out to backend server as 'contact', so it loses
original information from initial REGISTER.
Is there a way to make save() use original request fields like T_req($ct),
or some way to call save() with full set of custom params?
Of course, I can save() all REGISTERs in request_route and then delete on
backend fail, but it seems to be waste of resources, especially when
REGISTER traffic is high :(
I'd be glad to hear any advice.
--
Best regards,
Dmitry Sytchev,
IT Engineer
Dear sr-users!
We are facing serious problem.
We built openIMS based on Kamailio. Moreover, we have RCS users registered, but some users are automatically unregistered on the openIMS core:
1) We don't know what a piece of log on S-CSCF means:
/usr/sbin/kamailio[17392]: ERROR: --- EXPLOIT --- We need to do an UNREG server SAR assignemnt
2) In log files there is "404 Not Found: Unknown destination" or "404 user offline".
Probably there is some diameter problem.
Has anyone of you already faced such problem?
Many thanks for your answers.
Piotr Kowalski
Starszy Architekt Techniczny
Tel. +48 22 699 50 93
Kom. +48 519 123 289
Orange
Orange Polska
Hurt
Badania i Rozwój Sieci i Platform Usługowych
Wydział Usług Konwergentnych
Obrzeżna 7 /p. 309, 02-691 Warszawa
Fax. +48 22 857 99 86
www.hurt-orange.pl<http://www.hurt-orange.pl/>
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Czy musisz drukować tę wiadomość? Pomyśl o środowisku. Korzystaj z e-faktury.
Treść tej wiadomości jest własnością Orange Polska i zawiera informacje stanowiące tajemnicę przedsiębiorstwa Orange Polska. Jeżeli nie jesteście Państwo jej adresatem, bądź otrzymaliście ją przez pomyłkę, prosimy o powiadomienie o tym nadawcy oraz trwałe jej usunięcie. Orange Polska Spółka Akcyjna z siedzibą i adresem w Warszawie (02-326) przy Al. Jerozolimskich 160, wpisana do Rejestru Przedsiębiorców prowadzonego przez Sąd Rejonowy dla m.st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego pod numerem 0000010681; REGON 012100784, NIP 526-02-50-995; z pokrytym w całości kapitałem zakładowym wynoszącym 3.937.072.437 złotych.
Hi,
I find a problem when I try to search the header "Expires" with value 0.
At my kamailio.cfg the configuration is:
if ( search_hf("Expires", ":0@", "a") )
{
xlog("L_INFO", "Encontrado expires 0 ($rm)");
}
This way find nothing.
I test with 0 (no wildcards regular expression), but this make matches in
any Register with header Expires content 0. Example:
...
if ( search_hf("Expires", "0", "a") )
....
I saw some people control expires=0 at contact header, but not my case.
Example:
if (search("expires=0"))
{
xlog("L_INFO", "Encontrado expires 0 ($rm)");
}
Regards,
--
Emilio Soler
emiliosoler(a)gmail.com
Hi,
I use Kamailio as a stateless proxy with UDP + TCP.
When TCP is used, I get the following TCP errors:
WARNING: <core> [receive.c:265]: receive_msg(): error while trying onreply
script
ERROR: <core> [tcp_main.c:4338]: tcpconn_main_timeout(): connect xxxxxxxxx
failed (timeout)
WARNING: <core> [receive.c:265]: receive_msg(): error while trying onreply
script
ERROR: <core> [tcp_main.c:4338]: tcpconn_main_timeout(): connect xxxxxxxxxx
failed (timeout)
The TCP config in my script:
tcp_connection_lifetime=3605
I get this issue when I receive replies to INVITE from the UAS.
I can see the replies using ngrep but Kamailio doesn't seem to be able to
process them correctly.
I precise that the UAS is behind NAT and NAT configuration is correct (the
INVITE does reach the UAS).
I also precise that the UAS sends keepalive every 5 sec (I can see the
ping-pong using ngrep). I set it to 5 sec to eliminate the possibility that
the NAT closes the connection.
Thanks,
Mickael
Hi,
I want to experiment with the following setup and was wondering which
module(s) you all recommend.
I have a working simple kamailio 4.2 setup where registered users can only
call each other on the same domain (ie no outbound calling to PSTN or other
domains).
Now I want to explore the possibility of limiting call times for certain
users but allowing unlimited call times for others (ie user 5000's calls
are limited to 2 minutes while user 6000 has unlimited calling time).
There are some tutorials available on the internet but they seem to be
quite outdated.
Given my simple scenario, should I be looking into using the callcontrol
module and install the CDR tool from here
http://callcontrol.ag-projects.com/ (I don't really need any complex
billing scheme with various rates but rather a simple scheme were user x is
either time limited or not).
Before I dig in any further, I'd appreciate it of someone could tell me if
this is the way to go or is there's a simpler solution. Are there any
recent tutorials that I should be looking at?
Cheers,
Peter
hi!
Frankly, I don't really know the difference between the uid* modules and the "regular" modules. I know the history, but would like to understand and maybe some text I can add to the README files of these modules to explain to other users what the difference is.
/O
Hi,
I'm trying to use one Kamailio instance as load balancer for multiple
Kamailio instances. The load balancer only performs NAT handling and
dispatching of messages. The other instances handle registrations, routing,
RTP proxy, authentication, etc.
When a REGISTER request is received by the load balancer, a Path header is
added to the request which is then forwarded to one of the registrars. The
registration request is successfully handled and the Path header is saved in
database. All subscribers register through the load balancer.
When an INVITE is received from one subscriber by the load balancer, a
Record-Route header is added by the load balancer which then forwards the
INVITE to one of the other instances. The selected instance authenticates
the subscriber, looks for the callee using the REGISTRAR module, adds a
Record-Route header, adds a Route header according to the Path header
associated with the callee, and forwards the INVITE to the load balancer.
The load balancer performs loose routing (removing the Route header), adds
another Record-Route header, and forwards the INVITE to the callee using the
right transport address (indicated by the received parameter present in the
Route header). The flow is right for the INVITE and its replies. However,
when the caller sends the ACK, the route set is: load balancer, proxy, load
balancer - without any information about how to reach the callee. Therefore,
when the ACK reaches the "second" load balancer, the latter forwards it
according to the RURI which is the Contact URI present in the 200 OK (which
is not routable because of the NAT). I expected Kamailio to reuse the
information that was present in the Path header to route the ACK correctly.
What am I doing wrong?
Thanks,
Mickael
