Hi !
I have the following simple scenario
A <---> Kamailio <---> Asterisk <---> B
now i'm trying to handle Timeout reply when B is unavailable. First i suspend transaction and wait for B available.
i use uac_reg_send() to reINVITE B .The problem is when B available, it receive INVITE but A doesn't receive ACK therefore the call is incomplete
I guess the reason is source IP in reINVITE is Kamailio's not A's IP, so ACK can't reach A.
How can i set this source IP to A's IP ?
Any idea is appreciated
Thank you !
Hi all,
Thanks for your hard working on Kamailio!
I was just trying to install kamailio 4.2.X on a RedHat 7 machine but I got
checksum mismatch:
I took the yum configuration from:
http://rpm.kamailio.org/
[kamailio]
name=RPMs for Kamailio on RHEL 7
type=rpm-md
baseurl=http://rpm.kamailio.org/stable/RHEL_7/
gpgcheck=1
gpgkey=http://rpm.kamailio.org/stable/RHEL_7/repodata/repomd.xml.key
enabled=1
Than started yum update
$ sudo yum update
Loaded plugins: amazon-id, rhui-lb
kamailio
| 1.2 kB 00:00:00
kamailio/primary FAILED
] 0.0 B/s | 0 B --:--:-- ETA
http://rpm.kamailio.org/stable/RHEL_7/repodata/primary.xml.gz: [Errno -1]
Metadata file does not match checksum] 0.0 B/s | 0 B --:--:-- ETA
Trying other mirror.
kamailio/primary
| 7.4 kB 00:00:00
http://rpm.kamailio.org/stable/RHEL_7/repodata/primary.xml.gz: [Errno -1]
Metadata file does not match checksum
Trying other mirror.
Indeed http://rpm.kamailio.org/stable/RHEL_7/repodata/repomd.xml says:
<data type="primary">
<checksum type="sha">4cc322a95d4a978e383903feaf8fbbe8ccc2ff9e</checksum>
<open-checksum
type="sha">9fd04e59185a8e844133b834a662cae3cc0837b7</open-checksum>
<location href="repodata/primary.xml.gz"/>
<timestamp>1413465311</timestamp>
<size>7344</size>
<open-size>70829</open-size>
</data>
while http://rpm.kamailio.org/stable/RHEL_7/repodata/primary.xml.gz I can
download is:
$ ls -l primary.xml.gz
-rw-rw-r-- 1 alberto alberto 7562 gen 22 10:58 primary.xml.gz
$ shasum primary.xml.gz
e8e052970984feb0cdb16b98f05aefc516295aba primary.xml.gz
Do I have to switch to other repository?
Thank you,
Best Regards
--
Alberto Panizzo
CTO - Co-Founder
Amarula Solutions BV
Cruquiuskade 47
Amsterdam 1018 AM NL
T. +31(0)851119171
F. +31(0)204106211
www.amarulasolutions.com
Hello all.
I've been testing presence module for a while and I do notice that
presentity table grows endlessly over time.
Each time a call is made a new record is added in presentity with a
different etag.
In documentation, namely developers guide we can read this:
int etag_not_new;
/*
* 0 - the standard mechanism (allocating new etag
for each Publish)
* 1 - allocating an etag only
for an initial Publish
*/
How can I tell the presence module in kamailio config to work using the
second form of the above?
Looking forward to hear from you.
BR,
--
*Nuno Miguel Reis* | *Unified Communication** Systems*
M. +351 913907481 | nreis(a)wavecom.pt
WAVECOM-Soluções Rádio, S.A.
Cacia Park | Rua do Progresso, Lote 15
3800-639 AVEIRO | Portugal
T. +351 309 700 225 | F. +351 234 919 191
*GPS
<http://maps.google.com/maps/ms?msa=0&msid=202333747613191340808.0004b4b227a…>
| www.wavecom.pt <http://www.wavecom.pt/>** <http://www.wavecom.pt/>*
[image: Description: Description: WavecomSignature]
<http://www.wavecom.pt/pt/wavecom/premios.php>
[image: Publicity] <http://www.wavecom.pt/pt/mail_eventos.php>
Hi,
My Kamailio box works very well for a year, in front of a Freeswitch box.
Nowadays, some of my users live problems about receiving calls. But this
problem occurs on a couple of specific users. %1 of users complain about
it. When I capture the traffic, I see that, Kamailio receives an invite
package from freeswitch but takes no action. Normally it should response
with a 100 trying message. Here is the INVITE package. 1.2.3.6 is the
Freeswitch box and 1.2.3.2 is the Kamailio box. I captured this package on
Kamailio box.
U 1.2.3.6:5060 -> 1.2.3.2:5060
INVITE sip:2000@test.example.net SIP/2.0.
Via: SIP/2.0/UDP 1.2.3.6;rport;branch=z9hG4bKZU1Z76FvDZ26r.
Route: <sip:1.2.3.2>;lr.
Max-Forwards: 65.
From: "908508850000" <sip:908508850000@test.example.net>;tag=KjcgDe0NyKN0B.
To: <sip:2000@88.235.112.33:1028>.
Call-ID: 72b344f4-1c09-1233-ad8d-0050568e9066.
CSeq: 70585075 INVITE.
Contact: <sip:mod_sofia@1.2.3.6:5060>.
User-Agent:
FreeSWITCH-mod_sofia/1.4.14+git~20141119T221113Z~ca1d990cfc~64bit.
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER,
REFER, NOTIFY, PUBLISH, SUBSCRIBE.
Supported: timer, path, replaces.
Allow-Events: talk, hold, conference, presence, as-feature-event, dialog,
line-seize, call-info, sla, include-session-description, presence.winfo,
message-summary, refer.
Content-Type: application/sdp.
Content-Disposition: session.
Content-Length: 270.
X-AUTH-IP: 159.253.40.138.
X-BF-SRC: 2.
X-FS-Support: update_display,send_info.
Remote-Party-ID: "908508850000" <sip:908508850000@test.example.net
>;party=calling;screen=yes;privacy=off.
.
v=0.
o=FreeSWITCH 1421813895 1421813896 IN IP4 1.2.3.6.
s=FreeSWITCH.
c=IN IP4 1.2.3.6.
t=0 0.
m=audio 28384 RTP/AVP 3 8 0 101 13.
a=rtpmap:3 GSM/8000.
a=rtpmap:8 PCMA/8000.
a=rtpmap:0 PCMU/8000.
a=rtpmap:101 telephone-event/8000.
a=fmtp:101 0-16.
a=ptime:20.
I use standart location lookup and relay procedure in Kamailio default
script.
Is there anything wrong with this INVITE package and how can I trace this
issue on Kamailio box?
Thank you.
/Volkan
Hello Folks:
Hope you can see this and share your ideas as to how to fix it?
Thanks and regards,
Zaka
________________________________________
From: Zaka Ul Isam
Sent: Wednesday, January 21, 2015 12:20 PM
To: Carsten Bock
Cc: miconda(a)gmail.com
Subject: RE: KAMAILIO IMS Questions
hello All:
First of all many thanks for your kind response. In fact my last few emails did not make it to the list (and nor bounced). It seems there is an error on the receiving mail server! However, I am regularly receiving list emails and can respond to threads but due to unknown reason, can not initiate a thread!
Yes, it is an install from stable version source. Inorder to bouble check, we even compiled this module from source and copied to the kamailio modules folder replacing the actual module,but without luck!
Please suggest the fix.
Thanks and regards,
Zaka
________________________________________
From: Carsten Bock [carsten(a)ng-voice.com]
Sent: Wednesday, January 21, 2015 11:56 AM
To: Zaka Ul Isam
Cc: miconda(a)gmail.com
Subject: Re: KAMAILIO IMS Questions
Hi Zaka,
please forward the request to the sr-users list, as neither me or
Daniel provide direct support.
How did you install Kamailio? Are you sure, that you have the
SIP-Trace in (/usr/local/lib64/kamailio/modules/)?
>From your log, i can see, that you did not install it from the
Debian-Packages....
Thanks,
Carsten
2015-01-21 12:17 GMT+02:00 Zaka Ul Isam <Zaka.Ul(a)albtelecom.al>:
> Hi Gentlemen:
>
> Yet another stumbling block!
> Now it is not setting module parameters or finding module <SIPTRACE>
> The module is there, I have confirmed it. Below is the error log & relevant
> code snippet:
>
> Error LOG
>
> kamailio -cf /usr/local/etc/kamailio/pcscf/kamailio.cfg
> loading modules under config path: /usr/local/lib64/kamailio/modules/
> 0(22035) ERROR: <core> [modparam.c:166]: set_mod_param_regex(): No module
> matching <siptrace> found
> 0(22035) : <core> [cfg.y:3439]: yyerror_at(): parse error in config file
> /usr/local/etc/kamailio/pcscf/kamailio.cfg, line 366, column 42: Can't set
> module parameter
> 0(22035) ERROR: <core> [modparam.c:166]: set_mod_param_regex(): No module
> matching <siptrace> found
> 0(22035) : <core> [cfg.y:3439]: yyerror_at(): parse error in config file
> /usr/local/etc/kamailio/pcscf/kamailio.cfg, line 368, column 35: Can't set
> module parameter
> 0(22035) ERROR: <core> [modparam.c:166]: set_mod_param_regex(): No module
> matching <siptrace> found
> 0(22035) : <core> [cfg.y:3439]: yyerror_at(): parse error in config file
> /usr/local/etc/kamailio/pcscf/kamailio.cfg, line 369, column 44: Can't set
> module parameter
> 0(22035) ERROR: <core> [modparam.c:166]: set_mod_param_regex(): No module
> matching <siptrace> found
> 0(22035) : <core> [cfg.y:3439]: yyerror_at(): parse error in config file
> /usr/local/etc/kamailio/pcscf/kamailio.cfg, line 370, column 37: Can't set
> module parameter
> 0(22035) ERROR: <core> [modparam.c:166]: set_mod_param_regex(): No module
> matching <siptrace> found
> 0(22035) : <core> [cfg.y:3439]: yyerror_at(): parse error in config file
> /usr/local/etc/kamailio/pcscf/kamailio.cfg, line 371, column 38: Can't set
> module parameter
> 0(22035) : <core> [cfg.y:3439]: yyerror_at(): parse error in config file
> /usr/local/etc/kamailio/pcscf/kamailio.cfg, line 372, column 1: syntax error
> 0(22035) : <core> [cfg.y:3439]: yyerror_at(): parse error in config file
> /usr/local/etc/kamailio/pcscf/kamailio.cfg, line 372, column 1:
> ERROR: bad config file (7 errors)
> 0(22035) WARNING: <core> [ppcfg.c:219]: pp_ifdef_level_check(): different
> number of preprocessor directives: N(#!IF[N]DEF) - N(#!ENDIF) = 1
> [root@IMS-dta1 pcscf]# locate modparam.c
> bash: locate: command not found
>
> Source File
>
> }
>
> regfree(&preg);
> pkg_free(reg);
> if (!mod_found) {
> LM_ERR("No module matching <%s> found\n", regex);
> return -4;
> }
> return 0;
> }
>
>
> Please advise!
>
> Kindest regards,
>
> Zaka
>
>
>
> ________________________________________
> From: Zaka Ul Isam
> Sent: Friday, January 09, 2015 4:07 PM
> To: Carsten Bock
> Subject: RE: KAMAILIO IMS Questions
>
>
> Hi Carsten:
>
> Thanks a lot for your quick response and elaboration.
>
> As regards HSS, for testbed, we plan to use FOKUS HSS, Hope it will serve
> the purpose. Please note that in addition to DIALOG_NG old DIALOG Module was
> also required!
>
>
> Thanks again & regards,
>
> Zaka
>
> ________________________________________
> From: Carsten Bock [carsten(a)ng-voice.com]
> Sent: Friday, January 09, 2015 3:05 PM
> To: Zaka Ul Isam
> Subject: Re: KAMAILIO IMS Questions
>
> Hi Zaka,
>
> Thanks :-)
>
> You questions:
> 1) you should be able to start the three components with "kamailio -f
> /path/to/kamailio.cfg".
>
> You may need to modify the following line:
> # ------------------ module loading ----------------------------------
> mpath="/usr/lib64/kamailio/modules_k/:/usr/lib64/kamailio/modules/:/usr/lib/kamailio/modules_k/:/usr/lib/kamailio/modules/"
>
> This defines, where Kamailio will find it's modules. After the
> source-code install, this is probably not correct :-)
>
> 2) The PCRF (and the pcscf.xml-Configuration) is optional (this
> functionality has to be enabled by enabling "WITH_RX" in the
> configuration, otherwise the pcscf.xml is ignored)
>
> 3) I assume, you also installed FHoSS from source instead from the
> Package? In any case, you need to edit the hibernate.properties (e.g.
> /opt/FHoSS/deploy/hibernate.properties).
>
> Regarding the errors of the Webinterface: It doesn't matter, if it's
> 32 or 64 bit. FHoSS and it's Webinterface are for showcase and
> scientific work only, so i assume, that's fine (as long as it works).
> In production environments, we use e.g. a Nokia Siemens HSS (if
> already present, e.g. for the LTE access) or our own drop in
> replacement (with a totally different interface).
>
> Kind regards,
> Carsten
>
> 2015-01-08 15:27 GMT+01:00 Zaka Ul Isam <Zaka.Ul(a)albtelecom.al>:
>> Hi, Carsten:
>>
>> Thanks for the informative posts and responses on IMS related topics. I
>> was
>> trying to configure based on your last post at:
>>
>> http://www.kamailio.org/wiki/tutorials/ims/installation-howto
>>
>> With respect to above, I have few questions:
>>
>> 1: If the Kamailio based IMS, compiled from source (not package manager
>> install) and all components in one machine. How do we start different
>> components?
>>
>> kamailio -f /PATH/TO/RESPECTIVE COMPONENTS EXECUTABLE (kamailio.cfg with
>> an
>> include file P/I/S-CSCF.CFG)
>>
>> 2: In case of P-CSCF there are three config files as well (.xml for
>> Diameter
>> interface). The latter has reference to PCRF PEER
>> Is it must? as there is no corresponding DNS entry in
>> Kamailio-IMS.DNSZONE file.
>> 3: As regards FOKUS HSS, in order to adapt the config to our scenario, do
>> we
>> also need to edit FHOSS/hibernate.properties file? Besides, we have errors
>> with HSS WEB interface on 64 bit machines. Is 32 bit architecture the
>> recommended one for HSS?
>>
>> Thanking you in anticipation,
>>
>> Zaka
>>
>>
>>
>>
>> ________________________________
>>
>> Albtelecom & Eagle Mobile invite you to protect together the Environment.
>> Please do not print the e-mail unless really necessary.
>>
>> Albtelecom & Eagle Mobile iu ftojnë të mbrojmë së bashku Mjedisin. Lutemi
>> të
>> mos e printoni këtë komunikim elektronik nëse nuk është vërtet i
>> nevojshëm.
>>
>> ________________________________
>>
>> This e-mail and any files transmitted with it are confidential and
>> intended
>> solely for the use of the addressee/s. If you are not the intended
>> recipient
>> you are hereby notified that any dissemination, forwarding, copying or use
>> of any of the information is strictly prohibited. If you receive this
>> e-mail
>> in error, please notify the sender immediately and delete it! Albtelecom
>> makes no warranty as to the accuracy or completeness of any information
>> contained in this message and hereby excludes any liability of any kind
>> for
>> the information contained therein or for the information transmission,
>> reception, storage or use of such in any way whatsoever. The opinions
>> expressed in this message may belong to sender alone and may not
>> necessarily
>> reflect the opinions of Albtelecom. Albtelecom shall bear no liability for
>> any loss or damage caused by software or e-mail viruses.
>>
>> Ky mesazh dhe çdo informacion i transmetuar në përmbajtje te këtij mesazhi
>> është konfidencial dhe është i destinuar vetëm për marrësin e destinuar.
>> Nëse nuk jeni marrësi i destinuar, Ju bëjmë me dije se çdo përhapje,
>> transmetim, kopjim apo përdorim i çdo informacioni është i ndaluar. Nëse e
>> merrni këtë mesazh gabimisht, ju lutem kontaktoni urgjentisht nisësin e
>> tij
>> dhe fshijeni atë. Albtelecom nuk jep asnjë garanci për saktësinë apo
>> plotësinë e informacionit në përmbajtje të këtij mesazhi dhe nuk mban
>> asnjë
>> përgjegjësi për informacionin e përmbajtur, transmetimin, marrjen,
>> ruajtjen
>> apo përdorimin e tij në çfarëdolloj mënyre. Mendimet e shprehura në këtë
>> mesazh mund t'i përkasin vetë nisësit dhe nuk mund të reflektojnë
>> domosdoshmërisht qëndrimet e Albtelecom. Albtelecom nuk do të mbaje asnjë
>> përgjegjësi për humbje ose dëme te shkaktuara nga programet apo viruset.
>
>
>
> --
> Carsten Bock
> CEO (Geschäftsführer)
>
> ng-voice GmbH
> Schomburgstr. 80
> D-22767 Hamburg / Germany
>
> http://www.ng-voice.com
> mailto:carsten@ng-voice.com
>
> Office +49 40 5247593-0
> Fax +49 40 5247593-99
>
> Sitz der Gesellschaft: Hamburg
> Registergericht: Amtsgericht Hamburg, HRB 120189
> Geschäftsführer: Carsten Bock
> Ust-ID: DE279344284
>
> Hier finden Sie unsere handelsrechtlichen Pflichtangaben:
> http://www.ng-voice.com/imprint/
>
> ________________________________
>
> This e-mail and any files transmitted with it are confidential and intended
> solely for the use of the addressee/s. If you are not the intended recipient
> you are hereby notified that any dissemination, forwarding, copying or use
> of any of the information is strictly prohibited. If you receive this e-mail
> in error, please notify the sender immediately and delete it! Albtelecom
> makes no warranty as to the accuracy or completeness of any information
> contained in this message and hereby excludes any liability of any kind for
> the information contained therein or for the information transmission,
> reception, storage or use of such in any way whatsoever. The opinions
> expressed in this message may belong to sender alone and may not necessarily
> reflect the opinions of Albtelecom. Albtelecom shall bear no liability for
> any loss or damage caused by software or e-mail viruses.
>
> Ky mesazh dhe çdo informacion i transmetuar në përmbajtje te këtij mesazhi
> është konfidencial dhe është i destinuar vetëm për marrësin e destinuar.
> Nëse nuk jeni marrësi i destinuar, Ju bëjmë me dije se çdo përhapje,
> transmetim, kopjim apo përdorim i çdo informacioni është i ndaluar. Nëse e
> merrni këtë mesazh gabimisht, ju lutem kontaktoni urgjentisht nisësin e tij
> dhe fshijeni atë. Albtelecom nuk jep asnjë garanci për saktësinë apo
> plotësinë e informacionit në përmbajtje të këtij mesazhi dhe nuk mban asnjë
> përgjegjësi për informacionin e përmbajtur, transmetimin, marrjen, ruajtjen
> apo përdorimin e tij në çfarëdolloj mënyre. Mendimet e shprehura në këtë
> mesazh mund t'i përkasin vetë nisësit dhe nuk mund të reflektojnë
> domosdoshmërisht qëndrimet e Albtelecom. Albtelecom nuk do të mbaje asnjë
> përgjegjësi për humbje ose dëme te shkaktuara nga programet apo viruset.
--
Carsten Bock
CEO (Geschäftsführer)
ng-voice GmbH
Schomburgstr. 80
D-22767 Hamburg / Germany
http://www.ng-voice.com
mailto:carsten@ng-voice.com
Office +49 40 5247593-0
Fax +49 40 5247593-99
Sitz der Gesellschaft: Hamburg
Registergericht: Amtsgericht Hamburg, HRB 120189
Geschäftsführer: Carsten Bock
Ust-ID: DE279344284
Hier finden Sie unsere handelsrechtlichen Pflichtangaben:
http://www.ng-voice.com/imprint/
________________________________
This e-mail and any files transmitted with it are confidential and intended solely for the use of the addressee/s. If you are not the intended recipient you are hereby notified that any dissemination, forwarding, copying or use of any of the information is strictly prohibited. If you receive this e-mail in error, please notify the sender immediately and delete it! Albtelecom makes no warranty as to the accuracy or completeness of any information contained in this message and hereby excludes any liability of any kind for the information contained therein or for the information transmission, reception, storage or use of such in any way whatsoever. The opinions expressed in this message may belong to sender alone and may not necessarily reflect the opinions of Albtelecom. Albtelecom shall bear no liability for any loss or damage caused by software or e-mail viruses.
Ky mesazh dhe çdo informacion i transmetuar në përmbajtje te këtij mesazhi është konfidencial dhe është i destinuar vetëm për marrësin e destinuar. Nëse nuk jeni marrësi i destinuar, Ju bëjmë me dije se çdo përhapje, transmetim, kopjim apo përdorim i çdo informacioni është i ndaluar. Nëse e merrni këtë mesazh gabimisht, ju lutem kontaktoni urgjentisht nisësin e tij dhe fshijeni atë. Albtelecom nuk jep asnjë garanci për saktësinë apo plotësinë e informacionit në përmbajtje të këtij mesazhi dhe nuk mban asnjë përgjegjësi për informacionin e përmbajtur, transmetimin, marrjen, ruajtjen apo përdorimin e tij në çfarëdolloj mënyre. Mendimet e shprehura në këtë mesazh mund t'i përkasin vetë nisësit dhe nuk mund të reflektojnë domosdoshmërisht qëndrimet e Albtelecom. Albtelecom nuk do të mbaje asnjë përgjegjësi për humbje ose dëme te shkaktuara nga programet apo viruset.
My Kamailio box works very well for a year, in front of a Freeswitch box.
Nowadays, some of my users live problems about receiving calls. But this
problem occurs on a couple of specific users. %1 of users complain about
it. When I capture the traffic, I see that, Kamailio receives an invite
package from freeswitch but takes no action. Normally it should response
with a 100 trying message. Here is the INVITE package. 1.2.3.6 is the
Freeswitch box and 1.2.3.2 is the Kamailio box. I captured this package on
Kamailio box.
U 1.2.3.6:5060 -> 1.2.3.2:5060
INVITE sip:2000@test.example.net SIP/2.0.
Via: SIP/2.0/UDP 1.2.3.6;rport;branch=z9hG4bKZU1Z76FvDZ26r.
Route: <sip:1.2.3.2>;lr.
Max-Forwards: 65.
From: "908508850000" <sip:908508850000@test.example.net>;tag=KjcgDe0NyKN0B.
To: <sip:2000@88.235.112.33:1028>.
Call-ID: 72b344f4-1c09-1233-ad8d-0050568e9066.
CSeq: 70585075 INVITE.
Contact: <sip:mod_sofia@1.2.3.6:5060>.
User-Agent:
FreeSWITCH-mod_sofia/1.4.14+git~20141119T221113Z~ca1d990cfc~64bit.
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER,
REFER, NOTIFY, PUBLISH, SUBSCRIBE.
Supported: timer, path, replaces.
Allow-Events: talk, hold, conference, presence, as-feature-event, dialog,
line-seize, call-info, sla, include-session-description, presence.winfo,
message-summary, refer.
Content-Type: application/sdp.
Content-Disposition: session.
Content-Length: 270.
X-AUTH-IP: 159.253.40.138.
X-BF-SRC: 2.
X-FS-Support: update_display,send_info.
Remote-Party-ID: "908508850000" <sip:908508850000@test.example.net
>;party=calling;screen=yes;privacy=off.
.
v=0.
o=FreeSWITCH 1421813895 1421813896 IN IP4 1.2.3.6.
s=FreeSWITCH.
c=IN IP4 1.2.3.6.
t=0 0.
m=audio 28384 RTP/AVP 3 8 0 101 13.
a=rtpmap:3 GSM/8000.
a=rtpmap:8 PCMA/8000.
a=rtpmap:0 PCMU/8000.
a=rtpmap:101 telephone-event/8000.
a=fmtp:101 0-16.
a=ptime:20.
I use standart location lookup and relay procedure in Kamailio default
script.
Is there anything wrong with this INVITE package and how can I trace this
issue on Kamailio box?
Thank you.
Hi,
Hello!
I'm having trouble with matching massages for some Patton equipment,
from the looks of it, Patton don't like </> in headers.
The initial INVITE from Patton is sent without </> in To and From-headers.
In the logs from Patton I can see that it matches the "100 trying" that Kamailio sends back to it, and this message has To and From-headers without </>,
but the "180 Ringing" and "200 OK" that Kamailio sends is not matched, and these two has </>.
I would like to remove < and > in my onreply_route, how can I do this?
Or does anyone have experience on how Patton matches messages?
Br
Sebastian Thörn
Hi need some help please,
kamailio v-4.2.2
asterisk 13.1
;#### sip.conf
[general]
context=incoming calls
allowguest=yes
bindport=5080
bindaddr=192.168.1.77
rtcachefriends=yes
[kamailio]
type=friend
host=192.168.1.77
port=5060
context=kamailio-trunk
canreinvite=no
insecure=port,invite
dtmfmode=rfc2833
nat=force_rport,comedia
qualify=yes
i have followed this tutorial
http://kb.asipto.com/asterisk:realtime:kamailio-4.0.x-asterisk-11.3.0-astdb
My DDI provider sending call to ip address via DDNS.
DDI à DDNS à kamailio & asterisk in one server [192.168.1.77].
kamailio passing DDI to asterisk, but its sending to wrong context.
If any of the sip users is registered, the calls were sending to
registered user context. If no sip user is online then calls has been send
to kamailio-trunk. How can I get all DDI to kamailio-trunk? How can I
solve this problem?
Many thanks
Sathees
Hello,
Are the Kamailio presence modules (presence, xcap, pua, rls, etc.) RCS 5.X and OMA Presence Simple spec compliant. I found the following bullet from this announcement - http://www.kamailio.org/w/2012/09/kamailio-at-11-years/
* SIMPLE Presence & IM extensions – embedded XCAP server, MSRP relay, RLS full OMA/RCS extensions implementation, IMS registrar records replication, a.s.o.
Does that mean that only the RLS functionality is fully OMA/RCS compliant? Thanks and I appreciate any guidance.
Regards,
Alex
Hello,
I'm using the dialog module to control the maximum number of calls allowed to be passed through.
Is it possible to share the dialogs stored in memory with multiple instances of kamailio?
So if both kamailio instances process calls, and the maximum is set to a global of 10, both combined should never let more than 10 calls through.
Regards,
Grant
