sr-users June 2012

sr-users@lists.kamailio.org

78 participants
108 discussions

by Alex Balashov

It sends an actual REFER. -- Alex -- Alex Balashov - Principal Evariste Systems LLC 235 E Ponce de Leon Ave Suite 106 Decatur, GA 30030 Tel: +1-678-954-0670 Web: http://www.evaristesys.com/Uri Shacked <ushacked(a)gmail.com> wrote:Hi, before trying dlg_refer, does anyone know, does it send REFER to the caller/callee? or doeas it do reinvite? i ask this because my class 4 softswitch does not support REFER.... thanks, Uri

12 years, 4 months

dlg_refer

by Uri Shacked

Hi, before trying dlg_refer, does anyone know, does it send REFER to the caller/callee? or doeas it do reinvite? i ask this because my class 4 softswitch does not support REFER.... thanks, Uri

12 years, 4 months

Subscription-State: terminated;reason=terminated?

by Min Wang

HI when I removed 102 from 101's contact list (using jitsi nightly 1.1 build), kamailio 3.3 send out NOTIFY to 102 like this: NOTIFY sip:102@192.168.122.147:5060;transport=udp;registering_acc=192_168_122_32 SIP/2.0. Via: SIP/2.0/UDP 192.168.122.32;branch=z9hG4bK1bfb.afbf0a85.0. To: sip:102@192.168.122.32;tag=f6a40771. From: sip:101@192.168.122.32;tag=a6a1c5f60faecf035a1ae5b6e96e979a-5724. CSeq: 4 NOTIFY. Call-ID: c7c52dd058268596ec84dd3c645a2f17(a)0.0.0.0. Content-Length: 0. User-Agent: kamailio (3.3.0-rc0 (x86_64/linux)). Max-Forwards: 70. Event: presence. Contact: <sip:192.168.122.32:5060;transport=udp>. Subscription-State: terminated;reason=terminated. <----------------- Note the reason code is:terminated. From rfc3265, The defined reason codes are: deactivated/ probation/rejected/ timeout/giveup/noresource What is the reason to send: reason=terminated instead one of the well-defined reason codes? There was a discussion regarding at: http://sip-router.org/tracker/index.php?do=details&task_id=133 <http://sip-router.org/tracker/index.php?do=details&task_id=133> but I did not see the explaination of reason=terminated. Thanks min

12 years, 4 months

default kamailio configuration

by Vitaliy Aleksandrov

Hi All, After reading default kamailio configuration i can't understand why does kamailio remove preloaded route headers from the incoming initial INVITE before calling record_route(). remove_hf("Route"); if (is_method("INVITE|SUBSCRIBE")) record_route(); What will happen if an INVITE comes from another SIP proxy which wants to stay in the middle of the dialogue ? For example, during Re-INVITE UA from our local site will construct in-dialog INVITE with R-URI taken from the remote contact and send it to our local proxy according to RR. Local proxy will process it in route[WITHNDLG] where loose_route() function will remove top most RR header because it points to us and since there is no more RR records forward the request to a destination from the R-URI. As i understand in that case remote proxy will not receive any in-dialog requests from us.

12 years, 4 months

kamailio.org server maintenance - estimated 1 hour downtime, 26/27 June

by Daniel-Constantin Mierla

Hello, during the night of 26/27th of June, Central European Standard Time (GMT+1, with daylight saving time on), the server hosting kamailio.org and lists.sip-router.org will be down for approx 1 hour. This is a planned maintenance work to upgrade the server to a new infrastructure. Hopefully everything goes smooth and gets back online quickly, the work should start about 2:00am on the 27th of June, but don't get nervous if takes longer or happens at different time. Among the most important affected services: - the mailing lists (all mailed in this message) - main website and kamailio's wiki systems - download folders - documentations (for modules and other html tutorials) The sip-router.org server will NOT be affected, so next services will be available: - sip-router.org web site and its wiki - GIT repository - issue tracker system If things are not going as expected, tomorrow we will post news about on this server, at http://sip-router.org This is a good opportunity to thank again to voztele.com for sponsoring the server and taking care of the maintenance work. Cheers, Daniel -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio Advanced Training, Seattle, USA, Sep 23-26, 2012 - http://asipto.com/u/katu Kamailio Practical Workshop, Netherlands, Sep 10-12, 2012 - http://asipto.com/u/kpw

12 years, 4 months

Re: [SR-Users] Alias possible for presence...

by Daniel-Constantin Mierla

Hello, On 6/20/12 9:19 AM, Gertjan Wolzak wrote: > > Well, the account name is not public, but I would like to have the > possibility to have a "private" account for registering and a > "public"account to publish. > > The goal is to have others to be able to send messages to your > "public" id, while you log in with your "private" id. > most of user agent have two fields, one to be used as SIP id and another one for authentication id. > I know, think the next step is to get an communicator that has that > possibility..... > > So I want to be able to publish the "public" account and not the > "private" one. > > For example: > > I register to the presence server with uid gertjan and my password, > but I want to be known to others as newbie. > > So my friend can send an invitation/message to newbie as well as to > gertjan . > > Just like the db_alias which is used in the kamalio for linking sip > accounts to aliases. > For presence, people have to subscribe to a SIP id, in this case it your public ID known by everybody. The easiest will be that the user agent will publish in behalf of the public id. But ultimately, you can replace the values in headers and xml body (see textops/xmlops functions), then do presence handling, after applying the changes to the message (see textopsx module). Cheers, Daniel > Rgds, > > Gertjan > > *From:*Daniel-Constantin Mierla [mailto:miconda@gmail.com] > *Sent:* dinsdag 19 juni 2012 10:27 > *To:* SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - > Users Mailing List > *Cc:* Gertjan Wolzak > *Subject:* Re: [SR-Users] Alias possible for presence... > > Hello, > > On 6/14/12 10:28 AM, Gertjan Wolzak wrote: > > Hello All, > > I have the following challenge. > > We are using kamailio 3.2 and have enabled presence. Which works fine. > > But we would like to be able to work with aliases, so that the > account name and "presentation" name can be different. > > Any Ideas... Or did I miss the documentation on that? > > the account name is public or not? If it is some internal id, > eventually is used for authentication, but for presence the contacts > should know the public id. > > Or maybe you can give some example to understand how you use aliases > in the context of presence... > > Cheers, > Daniel > > > > -- > Daniel-Constantin Mierla -http://www.asipto.com > http://twitter.com/#!/miconda <http://twitter.com/#%21/miconda> -http://www.linkedin.com/in/miconda > Kamailio Advanced Training, Seattle, USA, Sep 23-26, 2012 -http://asipto.com/u/katu > Kamailio Practical Workshop, Netherlands, Sep 10-12, 2012 -http://asipto.com/u/kpw > > > -- > This message was scanned by Foize and is believed to be clean. > Click here to report this message as spam. > <http://filter.foize.com/cgi-bin/learn-msg.cgi?id=> > > > > _______________________________________________ > 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 -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio Advanced Training, Seattle, USA, Sep 23-26, 2012 - http://asipto.com/u/katu Kamailio Practical Workshop, Netherlands, Sep 10-12, 2012 - http://asipto.com/u/kpw

12 years, 4 months

Kamailio : Listening on multiple ports behind NAT

by Reda Aouad

Hello, I am trying to implement the following configuration : - Kamailio as a SIP proxy/registrar behind a one-to-one NAT (port number is not modified) listening on ports 5060 and 53 (and more ports in the future) - aliases correctly configured : alias= udp: public_ip:53 alias= udp: public_ip:5060 alias= udp: hostname:53 alias= udp: hostname:5060 - listen directive correctly on private ip address and both ports : listen=udp:private_ip:53 listen=udp:private_ip:5060 - advertised_address=public_ip - record_route_preset("public_ip") is used to announce the public IP address in the RR header - user A : registered on port 5060 - user B : registered on port 53 Suppose user A tries to call user B. The Record-Route header in the INVITE forwarded from Kamailio to user B should contain the port number on which user B is connected (53), to force user B to send future requests to that port number. But I have no method to know which port user B is connected to, and that problem is aggravated when user B has multiple registrations on different port numbers and parralel forking is done. Declaring advertised_port doesn't solve the problem. I cannot force port number 53 in record_route_preset("public_ip:53") since it wouldn't work when user B calls user A. Using the record_route( ) function, Kamailio doesn't use the advertised_address to construct the RR header. Another problem is that the record_route_preset function clears the DID cookie set by the dialog module, which makes Kamailio fallback to SIP elements to match the request to an existing dialog, thus dialog matching becomes slower, and performance is an issue for me. Any suggestions? I know that one solution would be to run Kamailio with a public IP address and no NAT, but unfortunately it's not possible. I suggest that the function record_route( ) takes a public IP address as a parameter, still doing what it does (correct record routing and cookie addition did=xxx and loose route lr=on), but only replacing the private IP address on which Kamailio listens with a public IP address. Or that the record_route( ) function uses the advertised_address to construct the RR header. Thank you RA

12 years, 4 months

Kamailio v3.3.0 packages

by Daniel-Constantin Mierla

Hello, I'm summarizing the status of packages for latest release v3.3.0. Debian/Ubuntu packages are ready in the usual APT repository, including nightly builds of the GIT branch 3.3, details at: * http://www.kamailio.org/wiki/packages/debs RPMs for CentOS/RedHat, Fedora, openSuse (various versions for each OS) are now available on opensuse build factory repository, details at: * http://www.kamailio.org/wiki/packages/rpms There you find the note about Peter Dunkley's repository, which has also builds for Raspberry Pi. Cheers, Daniel -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio Advanced Training, Seattle, USA, Sep 23-26, 2012 - http://asipto.com/u/katu Kamailio Practical Workshop, Netherlands, Sep 10-12, 2012 - http://asipto.com/u/kpw

12 years, 5 months

Over 100% of CPU usage on kamailio

by Konstantin M.

Hello, Is there any reason to consume over 135% of CPU usage on kamailio ? (sreenshot: http://i48.tinypic.com/2u72hr8.png). Any ideas ? Thanks!

12 years, 5 months

Fwd: Can Kamailio be used to redirect media between a client that switches from wifi to 3g/gsm

by Shaun Clark

Forgot to post the response to the list as well. Date: Fri, Jun 22, 2012 at 6:57 AM Subject: Re: [SR-Users] Can Kamailio be used to redirect media between a client that switches from wifi to 3g/gsm To: Klaus Darilion <klaus.mailinglists(a)pernau.at> Thanks for the response! I see a series of what I believe are re-REGISTER statements: Message sent: (to dest=75.101.244.XXX:5060) REGISTER sip:75.101.244.XXX SIP/2.0 Via: SIP/2.0/UDP 10.165.27.161:2407;rport;branch=z9hG4bK1839704852 From: <sip:990XX@75.101.244.XXX>;tag=1689684502 To: <sip:990XX@75.101.244.XXX> Call-ID: 1867622191 CSeq: 1 REGISTER Contact: <sip:990XX@10.165.27.161:2407;line=daeb0d9351eff22> Max-Forwards: 70 User-Agent: Linphone/3.4.0 (eXosip2/unknown) Expires: 3600 Content-Length: 0 Received message: SIP/2.0 401 Unauthorized Via: SIP/2.0/UDP 10.165.27.161:2407;received=32.158.143.61 ;rport=2407;branch=z9hG4bK1839704852 From: <sip:990XX@75.101.244.XXX>;tag=1689684502 To: <sip:990XX@75.101.244.XXX>;tag=c97b4d1cb1f3d0da549e06a8d482ef63.e10d Call-ID: 1867622191 CSeq: 1 REGISTER WWW-Authenticate: Digest realm="75.101.244.XXX", nonce="4fe476e500000e00aa8700d49b8c668f4c6f1e6a367f2XXX" Server: Kamailio Content-Length: 0 REGISTER sip:75.101.244.XXX SIP/2.0 Via: SIP/2.0/UDP 10.165.27.161:2407;rport;branch=z9hG4bK123406454 From: <sip:990XX@75.101.244.XXX>;tag=1689684502 To: <sip:990XX@75.101.244.XXX> Call-ID: 1867622191 CSeq: 2 REGISTER Contact: <sip:990XX@10.165.27.161:2407;line=daeb0d9351eff22> Authorization: Digest username="990XX", realm="75.101.244.XXX", nonce="4fe476e500000e00aa8700d49b8c668f4c6f1e6a367f2XXX", uri="sip:75.101.244.XXX", response="1e1d558894f2c05c322c76efbb2f9XXX", algorithm=MD5 Max-Forwards: 70 User-Agent: Linphone/3.4.0 (eXosip2/unknown) Expires: 3600 Content-Length: 0 Received message: SIP/2.0 200 OK Via: SIP/2.0/UDP 10.165.27.161:2407;received=32.158.143.61 ;rport=2407;branch=z9hG4bK123406454 From: <sip:990XX@75.101.244.XXX>;tag=1689684502 To: <sip:990XX@75.101.244.XXX>;tag=c97b4d1cb1f3d0da549e06a8d482ef63.8b5a Call-ID: 1867622191 CSeq: 2 REGISTER Contact: <sip:990XX@10.165.27.161:2407;line=daeb0d9351eff22>;expires=120, <sip:990XX@50.43.101.83:51879;line=59ecc207f06f4e9>;expires=81 Server: Kamailio Content-Length: 0 But after this I would expect to see an INVITE but one is never sent, but if I switch back to the original IP on that device the call is reconnected, so it proves we're missing an INVITE I believe. What do I need to do on the server side to force a re-INVITE to be sent after this registration occurs? Thanks! On Fri, Jun 22, 2012 at 1:14 AM, Klaus Darilion < klaus.mailinglists(a)pernau.at> wrote: > Hi Shaun! > > Your problem description is too short to give you any good help. > > Use tcpdump (or other tools) to capture the scenario with Asterisk and > Kamailio. Then compare them to find out why it doesn't work. > > Is media sent directly to Asterisk then it ca not be the problem of > Kamailio. > > I hope the mobile client is smart enough to also send a reINVITE when > getting the new IP address (of the mobile connection) with proper Contact > header - otherwise it can not receive SIP requests from Asterisk. > > regards > Klaus > > > On 20.06.2012 18:07, Shaun Clark wrote: > >> The use case is that I have a SIP client registered to Kamailio talking >> to an Asterisk box connected to the PSTN. The client is a mobile phone >> and the user is connected to wifi. The user then steps out of wifi range >> and the phone drops the connection and picks up the 3g data connection. >> I want the media stream to reconnect to the client and the call to >> resume without having to redial. This works now if the client is >> directly connected to the Asterisk machine, but not when I am routing >> through my Kamailio server. How do I go about this, examples are always >> appreciated, thanks! >> >> >> ______________________________**_________________ >> 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<http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users> >> >> > > --

12 years, 5 months

← Newer
1
2
3
4
5
6
7
...
11
Older →

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 June 2012