Dears,
I started my lab on VMware (debian lenny) where I installed Kamailio 3.2 and
started drouting configuration.
I'm using 2 PCs each having an x-lite softphone and the Kamailio on the
vmware all connected locally. My primary test is to make a call from x-lite
on PC (192.168.111.11) to x-lite on PC (192.168.111.226) through Kamailio\
drouting modules (192.168.111.139).
What is happening is that when I call 9611558800, for example, am getting
'Calling' message on PC x-lite followed by 'Call Failed: Request Timeout'
after a certain time.
Attached is my routing logic script, and ngrep for the call that is failing.
And my dr_tables data is :
dr_rules: 4, '0', '9611', '', 0, '', '#3', 'Lebanon Fix'
dr_gw_lists: 3, '5', 'Test Call'
dr_groups: 3, '.*', '.*', 0, 'Everyone'
dr_gateways: 5, 1, '192.168.111.226', 0, '', '', 2, 'PC1'
I tried adding port number to the gateways, remove '#' and add 5 in the
dr_rules, remove the "0" from do_routing in the script, but with no success.
Reading some related documents and books, I found that all scenarios using
drouting have gateways as media servers (Asterisks) . So my question: is
this a must, to have a media proxy even using my above primary enviroment?
If not, can you please help me finding my mistake that prohibit the call's
success(ringing)?
Thanks in advance.
F.Chahrour
Our PSTN provider has three servers. Two of them are located in our town,
and we prefer them, and the last one much further away. We can use them
interchangeably.
>From our dispatcher file:
# 10: PSTN
10 sip:preferred1.example.com:7476 0 5
10 sip:preferred2.example.com:7476 0 5
10 sip:third.example.com:7476 0 4
In our dispatch router we use 'ds_select_dst("10","4")'. Then the
round-robin algorithm evenly distributes the load on all three of them,
instead of round robin on the ones with priority 5 and fallbacking to
priority 4. Is the unconditional round robin as excepted?
When changing the selection algorithm to "8", «use first destination», the
dispatcher module correctly uses first "preferred2", then "preferred1" and
then lastly "third".
Why «first destination» is not the first one listed in the dispatcher file
has always puzzled me..
# kamailio -V
version: kamailio 3.2.1 (i386/linux) 31c991
flags: STATS: Off, USE_IPV6, USE_TCP, USE_TLS, TLS_HOOKS, USE_RAW_SOCKS,
DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC,
DBG_QM_MALLOC, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE,
USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16,
MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 4MB
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
id: 31c991
compiled on 08:08:06 Dec 6 2011 with gcc 4.1.2
--
Øyvind Kolbu
Hello,
I am running a presence server. I am searching for a problem with my
presence, and I have traced it down to this query :
delete from active_watchers where
presentity_uri='sip:test109@domain.tld' AND event='dialog' AND
to_tag='f0253efb8005057b3cc0ab8fa35ff1d9-c961'
This query is being sent to the database a few seconds after the initial
subscribe is received. So the subscription only lasts in the database
for a few seconds.
I tried running level 3 error reporting ( hundreds of DEBUG ). I did not
see any justification for query.
Where is this query coming from ( source code/ config file )? Why is
this subscription being deleted almost immediatly after it is setup ?
Thanks,
David
Here is a sample request ( not the same as the one above, I did not
capture the SIP at the same time as the SQL ) :
U PROXYIP:5060 -> PRESENCEIP:5060
SUBSCRIBE sip:test109@domain.tld SIP/2.0.
Record-Route: <sip:PROXYIP;lr=on;ftag=db911ce615f1598c>.
Record-Route: <sip:TCPPROXYIP;r2=on;lr=on>.
Record-Route: <sip:TCPPROXYIP;transport=tcp;r2=on;lr=on>.
Via: SIP/2.0/UDP PROXYIP;branch=z9hG4bK9543.f0668033.0.
Via: SIP/2.0/UDP TCPPROXYIP;branch=z9hG4bK9543.d2e18073.0;i=0a3.
Via: SIP/2.0/TCP USERIP:61334;branch=z9hG4bK-6ee64c28;rport=61334.
To: sip:test109@domain.tld.
From: "103 Zone T" <sip:test103@domain.tld>;tag=db911ce615f1598c.
Call-ID: 3f55db6e-b2ec6ca4(a)192.168.219.109.
CSeq: 53944 SUBSCRIBE.
Max-Forwards: 68.
Contact: "103 Zone T" <sip:test103@USERIP:8280;transport=tcp>.
Accept: application/dialog-info+xml.
Expires: 1800.
Event: dialog.
User-Agent: Cisco/SPA504G-7.4.9c.
Content-Length: 0.
.
#
U PRESENCEIP:5060 -> PROXYIP:5060
SIP/2.0 202 OK.
Record-Route: <sip:PROXYIP;lr=on;ftag=db911ce615f1598c>.
Record-Route: <sip:TCPPROXYIP;r2=on;lr=on>.
Record-Route: <sip:TCPPROXYIP;transport=tcp;r2=on;lr=on>.
Via: SIP/2.0/UDP PROXYIP;branch=z9hG4bK9543.f0668033.0.
Via: SIP/2.0/UDP TCPPROXYIP;branch=z9hG4bK9543.d2e18073.0;i=0a3.
Via: SIP/2.0/TCP USERIP:61334;branch=z9hG4bK-6ee64c28;rport=61334.
To: sip:test109@domain.tld;tag=f0253efb8005057b3cc0ab8fa35ff1d9-8c10.
From: "103 Zone T" <sip:test103@domain.tld>;tag=db911ce615f1598c.
Call-ID: 3f55db6e-b2ec6ca4(a)192.168.219.109.
CSeq: 53944 SUBSCRIBE.
Expires: 1800.
Contact: <sip:PRESENCEIP:5060>.
Server: kamailio (3.1.5 (x86_64/linux)).
Content-Length: 0.
Hi Pavel,
Many thanks for your reaction.
Good to know about the issues, saved me some important time with
troubleshooting. Will try to find alternatives in this case since I
already found some other limitations which stop me in having an
enterprise solution.
Have a good one!
DanB
>
> Hi Dan,
>
> student of mine (Martin) realized that, but it was using Jabberd2 not
> opernfire XMPP server, because the Openfire did not register domain from the
> XMPP component correctly and did some other strange things.
> Here are parts of Martin communication
>
> http://comments.gmane.org/gmane.comp.voip.openser.user/31713
>
>
> palo73
>
>> -----Original Message-----
>> From: sr-users-bounces(a)lists.sip-router.org [mailto:sr-users-
>> bounces(a)lists.sip-router.org] On Behalf Of Dan-Cristian Bogos
>> Sent: Friday, March 02, 2012 11:22 AM
>> To: sr-users(a)lists.sip-router.org
>> Subject: [SR-Users] XMPP module not passing subscribes coming from xmpp
>> side
>>
>> Hey Guys,
>>
>> I was wondering if anyone having experience with using xmpp module as
>> presence gateway between SIP and XMPP. I started evaluating it and till
>> now got some weird results, not sure if it is just my setup which does
>> not match the one widely used or the module is incomplete.
>>
>> Regarding my setup, I use OpenFIRE 3.7.1 on one side and Kamailio 3.2.0
>> out of debian packages on the other.
>>
>> The issue I got right now is that the subscribe coming from XMPP side
>> produces no action/reply on SIP side. Bellow you can see the packet
>> coming from OpenFIRE:
>> #
>> T 2012/03/02 09:49:57.743750 127.0.0.1:5275 -> 127.0.0.1:49965 [AP]
>> <presence id="4h8F6-19" to="dan4(a)gw.mydomain.com" type="subscribe"
>> from="dan(a)mydomain.com"><c xmlns="http://jabber.org/protocol/caps"
>> ext="voice-v1 video-v1 camera-v1 " hash="sha-1"
>> node="http://jitsi.org"
>> ver="ohjz8WKq0ZQRiNWRNcapX4BBHLk="/></presence>
>> """
>>
>> Anyone here got this working somehow?
>>
>> Ta,
>> DanB
>>
>> _______________________________________________
>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
>> sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-
>> bin/mailman/listinfo/sr-users
>
>
>
>
> ------------------------------
>
> Message: 5
> Date: Fri, 2 Mar 2012 11:44:12 +0100
> From: Reda Aouad <reda.aouad(a)gmail.com>
> Subject: [SR-Users] Registration Limits
> To: "SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) -
> Users Mailing List" <sr-users(a)lists.sip-router.org>
> Message-ID:
> <CAA30pc7pkPcBSfMSdRpvCSHNm0kiSw9r13huUe4jikiEPdcr1Q(a)mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi,
>
> Is there a way to ensure single-registration per user-agent for a user,
> which overwrites previous registration ?
> Or is there a way to limit the number of registrations per user, but
> overwriting the earliest registration for each new one ?
>
> Thanks,
> Reda
>
Dears,
I started my lab on VMware (debian lenny) where I installed Kamailio 3.2 and
started drouting configuration.
I'm using 2 PCs each having an x-lite softphone and the Kamailio on the
vmware all connected locally. My primary test is to make a call from x-lite
on PC (192.168.111.11) to x-lite on PC (192.168.111.226) through Kamailio\
drouting modules (192.168.111.139).
What is happening is that when I call 9611558800, for example, am getting
'Calling' message on PC x-lite followed by 'Call Failed: Request Timeout'
after a certain time.
Attached is my routing logic script, and ngrep for the call that is failing.
And my dr_tables data is :
dr_rules: 4, '0', '9611', '', 0, '', '#3', 'Lebanon Fix'
dr_gw_lists: 3, '5', 'Test Call'
dr_groups: 3, '.*', '.*', 0, 'Everyone'
dr_gateways: 5, 1, '192.168.111.226', 0, '', '', 2, 'PC1'
I tried adding port number to the gateways, remove '#' and add 5 in the
dr_rules, remove the "0" from do_routing in the script, but with no success.
Reading some related documents and books, I found that all scenarios using
drouting have gateways as media servers (Asterisks) . So my question: is
this a must, to have a media proxy even using my above primary enviroment?
If not, can you please help me finding my mistake that prohibit the call's
success(ringing)?
Thanks in advance.
F.Chahrour
Hi,
I am using msilo module to store offline message. I am sending back "202
pending" when the message is stored (m_store)
However, when I message delivered (m_dump), how do I inform the sender that
the message is successfully
delivered? Also, how do I handle if the sender if offline when I try to
inform about the delivery of the message. I think I need
offline notify store to handle this condition. Instead of removing the
message from the silo table upon receipt of 200 OK
from the receiver, I am thinking keep the message there until the NOTIFY is
successfully delivered to the sender. In effect,
the silo table in the database function as offline message and notify
store.
I reviewed module_k/msilo source code, and the functionality that I need
seems missing. I am thinking of two
approaches.
1) Extend the msilo module to implement the feature, if more people need
it, then I can submit the changes.
2) Write sqlops + lua script to address the missing function.
In either case, I am thinking of storing the callid of the original message
(possibly in silo table?) in the database
and sending the NOTIFY with the callid to the sender.
I would like to extend the silo table with two columns:
1. the callid of the message
2. flags to indicate status of the delivery of the message.
Appreciate your comments, suggestions and alternatives.
Thanks
Krish Kura
Dear Daniel,
Thanks for your reply..
I'd like to ask you too if my script in my first post that am using in the
routing area is correct?
I found file named core in the '/' location as you mentioned.
When I open it using #cat core, the opened file go crazy and writes strange
characters and it ending with the below:
/usr/local/sbin/kamailio-P/var/run/kamailio.pid-f/usr/local/etc/kamailio//ka
mailio.cfgSSH_AGENT_PID=3234GPG_AGENT_INFO=/tmp/seahorse-jKaZEU/S.gpg-agent:
3246:1TERM=xtermDESKTOP_STARTUP_ID=SHELL=/bin/bashGTK_RC_FILES=/etc/gtk/gtkr
c:/home/vanrise/.gtkrc-1.2-gnome2WINDOWID=33580848USER=rootGNOME_KEYRING_SOC
KET=/tmp/keyring-ZKxFck/socketSSH_AUTH_SOCK=/tmp/keyring-ZKxFck/sshUSERNAME=
vanriseSESSION_MANAGER=local/debian:/tmp/.ICE-unix/3188MAIL=/var/mail/rootPA
TH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/DESKTOP_SES
SION=defaultGDM_XSERVER_LOCATION=localPWD=/usr/local/etc/kamailioLANG=en_US.
UTF-8GDM_LANG=en_US.UTF-8GDMSESSION=defaultSHLVL=4HOME=/rootGNOME_DESKTOP_SE
SSION_ID=DefaultLOGNAME=rootDBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus
-sH8atcWdX4,guid=f0dcba443f8fd1d5267161364f4dd99dXDG_DATA_DIRS=/usr/local/sh
are/:/usr/share/:/usrdebian:/# 62;9;c62;9
Sorry, I've just realized an info that I should mention and would be
helpful, am running this Kamailio on a debian Lenny VMware as a trial before
migrating it to its server.
Thank you,
F.Chahrour
From: Daniel-Constantin Mierla [mailto:miconda@gmail.com]
Sent: Thursday, March 01, 2012 10:15 AM
To: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - Users
Mailing List
Cc: Fatima Chahrour~Vanrise Support; sr-users-bounces(a)lists.sip-router.org
Subject: Re: [SR-Users] DRouting cause Kamailio 3.2 to stop
Hello,
have you found the core file in /var/log/? It is a strange location unless
you started with -w /var/log. The core file is named usually 'core' or
core.pid (replace pid with same number, like, 'core.1234'). The default
location in in '/' unless there is a different location set via -w or
enforced by operating system (e.g., mac os x puts it in '/corefiles').
Hope it helps to locate the core file and send the backtrace.
Cheers,
Daniel
On 3/1/12 9:05 AM, Fatima Chahrour~Vanrise Support wrote:
I also tried : #gdb /usr/local/sbin/kamailio /var/log/core.file
(gdb) bt
And got No Stack..
BR,
F.Chahrour