sr-users

sr-users@lists.kamailio.org

18 participants
37571 discussions

[Kamailio-Users] Kamailio 3.0.0 RC1
by Daniel-Constantin Mierla 30 Oct '09

30 Oct '09

Hello, I created a tarball with sources of Kamailio 3.0.0 RC1 in order to easy the usage and testing: http://www.kamailio.org/pub/kamailio/3.0.0-rc1/src/kamailio-3.0.0-rc1_src.t… There is also now a tutorial to guide the installation of kamailio 3.0 branch from GIT repository: http://www.kamailio.org/dokuwiki/doku.php/install:kamailio-3.0.x-from-git Two wiki pages were created to collect what is new in Kamailio 3.0 and how to migrate to this version: http://www.kamailio.org/dokuwiki/doku.php/features:new-in-3.0.x http://www.kamailio.org/dokuwiki/doku.php/install:1.5.x-to-3.0.0 Both documents need a lot of care since many new features are missing or are not detailed, and definitely update guidelines do not cover all changes. Help is very much appreciated there. As we keep hunting and fixing issues, improve documentation, I hope to get to full release Kamailio 3.0.0 very soon. Enjoy RC1 meanwhile and report any issue you find to sr-dev(a)lists.sip-router.org. Thanks, Daniel

1 0

[Kamailio-Users] Route header problem
by Alex Rendour 30 Oct '09

30 Oct '09

Hello, We have a problem with route on header. I receive an ack from X.X.X.X (asterisk) on Y.Y.Y.Y (kamailio 1.5.3). Y.Y.Y.Y relay ACK to Z.Z.Z.Z Y.Y.Y.Y this route from X.X.X.X: <sip:Y.Y.Y.Y;lr=on;ftag=as7e58db45>,<sip:11dc0d7918b56374@Z.Z.Z.Z;lr> And forward as the same to Z.Z.Z.Z. The route header must be : <sip:11dc0d7918b56374@Z.Z.Z.Z;lr> I think my kamailio must delete the first part of the route header, like this explaination: http://www.tech-invite.com/Ti-sip-dialog.html#inv-ack Could you help me? Regards, -- alex

2 4

[Kamailio-Users] kam 1.5 syslog on solaris 10
by Robert McGilvray 29 Oct '09

29 Oct '09

I'm having some issues getting kam to log correctly to syslog after it daemonizes. I get all the initialization entries in the proper logfile but nothing after that - I have xlog statements throughout the config which only show up in syslog if fork=no. I've tested my syslog config with the system logger which works correctly executed as the kamailio user. If I run syslog in debug I don't see it receiving anything from kam after initialization. Any ideas? log_stderror=no log_facility=LOG_LOCAL1 debug=7 fork=yes children=4 /etc/syslog.conf (with tabs) local1.debug /var/log/globeop/kamailio.log This is the correct format of syslog in solaris. It only uses wildcard (*) in facility not levels. Specifying debug will include everything at higher levels. From the man page: For a given facility and level, syslogd matches all messages for that level and all higher levels. For example, an entry that specifies a level of crit also logs messages at the alert and emerg levels. This config is working correctly on sol 10 with openser 1.3. ykt1sipprd2# tail -f /var/log/globeop/kamailio.log Oct 27 09:50:46 ykt1sipprd2 kamailio[3813]: [ID 951507 local1.debug] DBG:core:grep_aliases: comparing host [2:loghost:5060] with us [1:loghost:5060] Oct 27 09:50:46 ykt1sipprd2 kamailio[3813]: [ID 951507 local1.debug] DBG:core:grep_aliases: comparing host [2:loghost:5060] with us [1:ykt1sipprd2:5060] Oct 27 09:50:46 ykt1sipprd2 kamailio[3813]: [ID 793175 local1.debug] DBG:core:grep_aliases: no match for: [2:loghost:5060] Oct 27 09:50:46 ykt1sipprd2 kamailio[3813]: [ID 634971 local1.debug] DBG:core:socket2str: <tcp:172.20.151.148:5060> Oct 27 09:50:46 ykt1sipprd2 kamailio[3813]: [ID 797031 local1.debug] DBG:core:fm_malloc_init: F_OPTIMIZE=16384, /ROUNDTO=2048 Oct 27 09:50:46 ykt1sipprd2 kamailio[3813]: [ID 596959 local1.debug] DBG:core:fm_malloc_init: F_HASH_SIZE=2067, fm_block size=16560 Oct 27 09:50:46 ykt1sipprd2 kamailio[3813]: [ID 362601 local1.debug] DBG:core:fm_malloc_init: params (fc400000, 33554432), start=fc400000 Oct 27 09:50:46 ykt1sipprd2 kamailio[3813]: [ID 551434 local1.debug] DBG:core:shm_mem_init_mallocs: success Oct 27 09:50:46 ykt1sipprd2 kamailio[3813]: [ID 123545 local1.info] INFO:core:init_tcp: using /dev/poll as the TCP io watch method (auto detected) Oct 27 09:50:46 ykt1sipprd2 kamailio[3815]: [ID 721503 local1.warning] WARNING:core:daemonize: pid file contains old pid, replacing pid -------------------------------------------------------------------------- This email with all information contained herein or attached hereto may contain confidential and/or privileged information intended for the addressee(s) only. If you have received this email in error, please contact the sender and immediately delete this email in its entirety and any attachments thereto.

3 9

[Kamailio-Users] How to take MAC address
by Chandrakant Solanki 29 Oct '09

29 Oct '09

Hi I want to know the MAC address of registered client on kamailio... suppose i have 3 Client registered with 192.168.1.2, 192.168.1.3 and 192.168.1.4 from these 3 Client, i am registered successfully with 101, 102, 103(a)test.com But for additional authentication ... i also need MAC address for this Client. Is there any module, method, function or variable to take MAC address or is there any alternative for the above case. Waiting for favorable reply... -- Regards, Chandrakant Solanki

4 3

[Kamailio-Users] Pass calls from/to another realm to gateway
by Alexander 29 Oct '09

29 Oct '09

I've encountered one problem I can not solve :( The situation is following: we've got Kamailio working together with our own SIP platform. Our platform is about various call processing business logic and billing. All calls from SIP users should pass through our platform. For now we successfully can make and receive calls inside our domain - NAT is handled fine in most cases, instant messages are handled and so on. It looks like that: - Kamailio receives a call from caller - Call is redirected to our platform - Platform redirects call back to Kamailio and it looks for callee. I've tried to implement that logic. It seems to work in some cases, but I encounter one problem. Sometimes Kamailio can not forward a call to the platform via rewritehostport(). It tries to forward SIP request, but nothing happens - only retransmission handler is called. I mean, after call to t_relay(), I see this: Oct 27 12:12:35 [16751] DBG:tm:retransmission_handler: retransmission_handler : request resending (t=0xb618de58, INVITE sip:200213@62.117.120.101:5061 SIP/2.0... Oct 27 12:12:35 [16751] DBG:tm:retransmission_handler: retransmission_handler : request resending (t=0xb618de58, INVITE sip:200213@62.117.120.101:5061 SIP/2.0... Oct 27 12:12:35 [16751] DBG:tm:retransmission_handler: retransmission_handler : request resending (t=0xb618de58, INVITE sip:200213@62.117.120.101:5061 SIP/2.0... SIP requests seem to be correct, and configuration file works ok from time to time. The problem I've described happens when Kamailio receives a call from another domain (for example, from sipbroker). Inside our domain everything works fine and INVITE passes to our platform correctly. I've attached configuration file and debug output. Files were written for and by Opensips, but with Kamailio I encounter the same problem. Is this a problem with configuration file or something else?

2 2

[Kamailio-Users] roadmap to kamailio 3.0.0
by Daniel-Constantin Mierla 29 Oct '09

29 Oct '09

Hello, I am thinking of planning to release Kamailio 3.0.0 next Wednesday or day after (October 28 or 29). With some delays, testing is going fine in my side, still some bits to be done, here is what I collected: - taking in consideration $du updates in branch route - import fixes from sr_3.0 branch - complete core statistics and handling of drop reply I believe is feasible, in the worse case we can package it at respective date and allow a bit more time for testing, but we unfreeze code and can go for new development. I encourage people to start writing migration documents. Let's see other opinions as well. Cheers, Daniel

4 6

Re: [Kamailio-Users] How to take MAC address
by Zahid Mehmood 28 Oct '09

28 Oct '09

I know that the Polycom phones can be configured to add the MAC address in one of the headers (probably the user agent hdr). -- Zahid ----- Original Message ----- From: users-bounces(a)lists.kamailio.org <users-bounces(a)lists.kamailio.org> To: users(a)lists.kamailio.org <users(a)lists.kamailio.org> Sent: Wed Oct 28 02:58:05 2009 Subject: Re: [Kamailio-Users] How to take MAC address On Wednesday 28 October 2009 06:35:28 Chandrakant Solanki wrote: > Hi > > I want to know the MAC address of registered client on kamailio... > > suppose i have 3 Client registered with 192.168.1.2, 192.168.1.3 and > 192.168.1.4 > > from these 3 Client, i am registered successfully with 101, 102, > 103(a)test.com > > But for additional authentication ... i also need MAC address for this > Client. > > Is there any module, method, function or variable to take MAC address or is > there any alternative for the above case. > > > Waiting for favorable reply... You will not have luck outsite "your proxy network" ... I mean ... that if your proxy is on 192.168.0.10/24 and your clients on any other network, you will always get's the same MAC, the mac of the 192.168.0.10/24 gateway. Your only hope is that SOME SIP devices add their MAC as part of some subscribe or register petition. I don't see any security increase on this, because MAC's could be easily spoofed. -- Raúl Alexis Betancor Santana Dimensión Virtual _______________________________________________ Kamailio (OpenSER) - Users mailing list Users(a)lists.kamailio.org http://lists.kamailio.org/cgi-bin/mailman/listinfo/users http://lists.openser-project.org/cgi-bin/mailman/listinfo/users

2 1

Re: [Kamailio-Users] Asterisk to Kamailio Call forwarding error
by Daniel-Constantin Mierla 28 Oct '09

28 Oct '09

On 28.10.2009 11:23 Uhr, Chandrakant Solanki wrote: > > > On Wed, Oct 28, 2009 at 3:50 PM, Daniel-Constantin Mierla > <miconda(a)gmail.com <mailto:miconda@gmail.com>> wrote: > > > > On 28.10.2009 11:14 Uhr, Chandrakant Solanki wrote: > > > > On Wed, Oct 28, 2009 at 3:18 PM, Daniel-Constantin Mierla > <miconda(a)gmail.com <mailto:miconda@gmail.com> > <mailto:miconda@gmail.com <mailto:miconda@gmail.com>>> wrote: > > > > On 28.10.2009 10:37 Uhr, Chandrakant Solanki wrote: > > Hi > > Call Sequence is ... > > Client A/B register on Kamailio and both are registered > successfully.. > Firewall is stopped. > > Now... Client A call to Client B.. > > Client A => Kamailio => Asterisk => Kamailio => Client B > > Above is call sequence, when call goes from Asterisk to > Kamailio ... then found below error.... > > ERROR:tm:t_forward_nonack: no branch for forwarding > Oct 28 02:14:07 openser1 /sbin/kamailio[2915]: > ERROR:tm:w_t_relay: t_forward_nonack failed > Oct 28 02:14:07 openser1 /sbin/kamailio[2915]: ***** > OUT route[8] > > what processing are you doing in kamailio for this case? Do > you do > same failure routing to another destination if B does not > answer? > Such error occurs when r-uri is changed in failure route but no > append_branch() was executed. > > Cheers, > Daniel > > > > hi > > where could i put this thing.... > > Here is my config file for kamailio... > > http://pastebin.com/m34e07510 > > Please help me out ... > > > your config is big to troubleshoot it quick and easy. Definitely > you have call forwarding, what version of kamailio are you using? > the header of file says openser 1.2. > > I suggest you use ngrep/wireshark to watch the sip traffic and put > xlog() messages in the config to correlate and get hints about > what happesn. > > Cheers, > Daniel > > PS. Keep cc-ing to mailing list, there are people that can help > better or faster inc ase they use the sip wizard config. > > -- > Daniel-Constantin Mierla > * Kamailio SIP Masterclass, Nov 9-13, 2009, Berlin > * http://www.asipto.com/index.php/sip-router-masterclass/ > > > hi > > i m using kamailio-1.5.2-tls... > if you don't keep mailing list in the discussion thread, your messages will be ignored... Daniel

1 0

Re: [Kamailio-Users] Asterisk to Kamailio Call forwarding error
by Daniel-Constantin Mierla 28 Oct '09

28 Oct '09

On 28.10.2009 11:14 Uhr, Chandrakant Solanki wrote: > > > On Wed, Oct 28, 2009 at 3:18 PM, Daniel-Constantin Mierla > <miconda(a)gmail.com <mailto:miconda@gmail.com>> wrote: > > > > On 28.10.2009 10:37 Uhr, Chandrakant Solanki wrote: > > Hi > > Call Sequence is ... > > Client A/B register on Kamailio and both are registered > successfully.. > Firewall is stopped. > > Now... Client A call to Client B.. > > Client A => Kamailio => Asterisk => Kamailio => Client B > > Above is call sequence, when call goes from Asterisk to > Kamailio ... then found below error.... > > ERROR:tm:t_forward_nonack: no branch for forwarding > Oct 28 02:14:07 openser1 /sbin/kamailio[2915]: > ERROR:tm:w_t_relay: t_forward_nonack failed > Oct 28 02:14:07 openser1 /sbin/kamailio[2915]: ***** OUT route[8] > > what processing are you doing in kamailio for this case? Do you do > same failure routing to another destination if B does not answer? > Such error occurs when r-uri is changed in failure route but no > append_branch() was executed. > > Cheers, > Daniel > > > > hi > > where could i put this thing.... > > Here is my config file for kamailio... > > http://pastebin.com/m34e07510 > > Please help me out ... > your config is big to troubleshoot it quick and easy. Definitely you have call forwarding, what version of kamailio are you using? the header of file says openser 1.2. I suggest you use ngrep/wireshark to watch the sip traffic and put xlog() messages in the config to correlate and get hints about what happesn. Cheers, Daniel PS. Keep cc-ing to mailing list, there are people that can help better or faster inc ase they use the sip wizard config. -- Daniel-Constantin Mierla * Kamailio SIP Masterclass, Nov 9-13, 2009, Berlin * http://www.asipto.com/index.php/sip-router-masterclass/

1 0

[Kamailio-Users] kamctl online
by Chandrakant Solanki 28 Oct '09

28 Oct '09

hello I would like to print user@domainname while i execute kamctl online command... Any Idea -- Regards, Chandrakant Solanki

5 5

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users