sr-users November 2007

sr-users@lists.kamailio.org

138 participants
249 discussions

[OpenSER-Users] Loose route problem with ;nat=yes
by Daniel 12 Nov '07

12 Nov '07

Hi all, there is a little problem in loose_route () function. Loose_route() function is not able to recognize the address of the proxy server (in the ROUTE header field) if ROUTE header field has the ";nat=yes" tag. So, addresses like " Route: 192.168.2.1;nat=yes;lr=on;ftag=123455 " are read by loose_route as foreign address. Meanwhile "Route: 192.168.2.1;lr=on;ftag=123455" are recognized correctly. where 192.168.2.1 = proxy server address Regerds, Daniel -- Daniel Grotti ________________________ e-mail : d.grotti(a)gmail.com

2 1

[OpenSER-Users] Reg. conditional processing of invite
by Padmaja 12 Nov '07

12 Nov '07

Hi all, I have an issue, where the sip user dials 911 number and hangs up. The 911 operator then calls back to the user using the call back command provided earlier say 8911 (there is a b2bua that interprets the call back number and routes the call to the specific user). This number is to be routed via the openser proxy to the b2bua. However, when the 911 calls back, proxy treats this number as a username and since there are no registrations to this 8911 number (though this entry is present at the proxy, no device has registered with this number), it sends back "404 Not found". How can this be circumvented? Thanks, Padmaja ----- Original Message ----- From: <users-request(a)lists.openser.org> To: <users(a)lists.openser.org> Sent: Saturday, November 03, 2007 3:46 AM Subject: Users Digest, Vol 30, Issue 6 > Send Users mailing list submissions to > users(a)lists.openser.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.openser.org/cgi-bin/mailman/listinfo/users > or, via email, send a message with subject or body 'help' to > users-request(a)lists.openser.org > > You can reach the person managing the list at > users-owner(a)lists.openser.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Users digest..." > > > Today's Topics: > > 1. Core dumped when deploying presence module (Sergio Gutierrez) > 2. Re: MediaProxy 1.9.0 - Radius (Brian Heath) > 3. Re: Forking Madness (Chris Heiser) > 4. Re: MediaProxy 1.9.0 - Radius (Mike O'Connor) > 5. Re: MediaProxy 1.9.0 - Radius (Ovidiu Sas) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 2 Nov 2007 15:59:56 -0500 > From: "Sergio Gutierrez" <saguti(a)gmail.com> > Subject: [OpenSER-Users] Core dumped when deploying presence module > To: users(a)lists.openser.org, users(a)openser.org > Message-ID: > <8a4af3e20711021359p3327c719t4ae680de4ac3e155(a)mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > Hello to all members. > > Currently we are trying to deploy presence module in the following > environment: > > 1. Openser 1.2.1 > 2. Solaris 10 on Sparc System > 3. libxml 2.6.30 > > Openser starts up fine, but when happens any event as a Status change of a > user agent, Openser crashes. > Below I send an extract from the logfile, and the backtrace of the core. > Thanks in advance for your attention. > > Sergio Guti?rrez > EPM Telecomunicaciones > Medellin - Colombia > > **************************************************** >>From Openser logfile. > > 0(5493) Nuevo Requerimiento - M=SUBSCRIBE > RURI=sip:5192901@200.13.225.250F= > sip:5192902@200.13.225.250 T=sip:5192901@200.13.225.250 > IP=200.116.28.88ID=YmE2MGVhMGQzMTI3ZmU0YTkzMDJjNjIxODNmMGIwOWE. > 0(5493) comp_scriptvar: str 20 : 5192901 > 0(5493) DEBUG:maxfwd:is_maxfwd_present: value = 70 > 0(5493) parse_headers: flags=ffffffffffffffff > 0(5493) get_hdr_field: cseq <CSeq>: <1> <SUBSCRIBE> > 0(5493) DEBUG: get_hdr_body : content_length=0 > 0(5493) found end of header > 0(5493) PRESENCE: handle_subscribe: 'expires' found > 0(5493) PRESENCE: handle_subscribe: lexpire= 3600 > 0(5493) PRESENCE: handle_subscribe: 'To' header ALREADY PARSED: < > sip:5192901@200.13.225.250> > 0(5493) PRESENCE:handle_subscribe: generating to_tag > 0(5493) > [p_user]= 5192901 [p_domain]= 200.13.225.250 > [w_user]= 5192902 [w_domain]= 200.13.225.250 > 0(5493) [event]= presence > [staus]= pending > [expires]= 3600 > 0(5493) [to_tag]= 10.5493.1194034490.40 > [from_tag]= 1f783845 > 0(5493) PRESENCE: update_subscription ... > 0(5493) > [p_user]= 5192901 [p_domain]= 200.13.225.250 > [w_user]= 5192902 [w_domain]= 200.13.225.250 > 0(5493) [event]= presence > [staus]= pending > [expires]= 3600 > 0(5493) [to_tag]= 10.5493.1194034490.40 > [from_tag]= 1f783845 > 0(5493) expires: 3600 > 0(5493) PRESENCE:update_subscription:Inserting into database: > n_query_cols:14 > 0(5493) [0] = to_user 5192901 > 0(5493) [1] = to_domain 200.13.225.250 > 0(5493) [2] = from_user 5192902 > 0(5493) [3] = from_domain 200.13.225.250 > 0(5493) [4] = event presence > 0(5493) [5] = event_id > 0(5493) [6] = callid YmE2MGVhMGQzMTI3ZmU0YTkzMDJjNjIxODNmMGIwOWE. > 0(5493) [7] = to_tag 10.5493.1194034490.40 > 0(5493) [8] = from_tag 1f783845 > 0(5493) [9] = contact sip:5192902@200.116.28.88:47166 > 0(5493) [10] = status pending > 0(5493) [11] = cseq 1 > 0(5493) [12] = expires 1194038090 > 0(5493) [13] = version 0 > 0(5493) parse_headers: flags=ffffffffffffffff > 0(5493) check_via_address(200.116.28.88, 192.168.0.13, 0) > 0(5493) DBG:sl:run_sl_callbacks: callback id 0 entered > 0(5493) trace_sl_onreply_out: trace off... > 0(5493) PRESENCE: get_subs_dialog:n= 1 > 0(5493) PRESENCE:notify:dialog informations: > 0(5493) > [p_user]= 5192901 [p_domain]= 200.13.225.250 > [w_user]= 5192901 [w_domain]= 200.13.225.250 > 0(5493) [event]= presence.winfo > [staus]= active > [expires]= 3518 > 0(5493) [to_tag]= 10.5493.1194034408.34 > [from_tag]= 39320458 > 0(5493) presence:uandd_to_uri: uri=sip:5192901@200.13.225.250 > 0(5493) presence:uandd_to_uri: uri=sip:5192902@200.13.225.250 > 0(5493) presence:uandd_to_uri: uri=sip:5192901@200.13.225.250 > 0(5493) PRESENCE: notify: build notify to user= 5192901 domain= > 200.13.225.250 for event= presence.winfo > 0(5493) > [p_user]= 5192901 [p_domain]= 200.13.225.250 > [w_user]= 5192901 [w_domain]= 200.13.225.250 > 0(5493) [event]= presence.winfo > [staus]= active > [expires]= 3518 > 0(5493) [to_tag]= 10.5493.1194034408.34 > [from_tag]= 39320458 > 0(5493) PRESENCE:build_str_hdr: expires = 3518 > 0(5493) PRESENCE:build_str_hdr: subs_expires : 3518 > 0(5493) PRESENCE: build_str_hdr: headers: > Event: presence.winfo > Contact: <sip:200.13.225.250:5060> > Subscription-State: active;expires=3518 > Content-Type: application/watcherinfo+xml > > 0(5493) PRESENCE:notify: headers:Event: presence.winfo > Contact: <sip:200.13.225.250:5060> > Subscription-State: active;expires=3518 > Content-Type: application/watcherinfo+xml > > 0(5493) CONTACT = sip:5192901@200.13.254.180:17116 > 0(5493) presence:uandd_to_uri: uri=sip:5192901@200.13.225.250 > 0(5493) parse_rr_body(): No body for record-route > 0(5493) PRESENCE: notify:Send notify for presence on callback 1(5494) > DEBUG: timer routine:4,tl=fc5c9a80 next=0, timeout=353600000 > 1(5494) DEBUG: retransmission_handler : request resending (t=fc5c9910, > NOTIFY si ... ) > 1(5494) DEBUG:tm:set_timer: relative timeout is 1000000 > 1(5494) DEBUG: add_to_tail_of_timer[5]: fc5c9a80 (354600000) > 1(5494) DEBUG: retransmission_handler : done > 1(5494) DEBUG: timer routine:5,tl=fc5c9a80 next=0, timeout=354600000 > 1(5494) DEBUG: retransmission_handler : request resending (t=fc5c9910, > NOTIFY si ... ) > 1(5494) DEBUG:tm:set_timer: relative timeout is 2000000 > 1(5494) DEBUG: add_to_tail_of_timer[6]: fc5c9a80 (356600000) > 1(5494) DEBUG: retransmission_handler : done > 1(5494) DEBUG: timer routine:6,tl=fc5c9a80 next=0, timeout=356600000 > 1(5494) DEBUG: retransmission_handler : request resending (t=fc5c9910, > NOTIFY si ... ) > 1(5494) DEBUG:tm:set_timer: relative timeout is 4000000 > 1(5494) DEBUG: add_to_tail_of_timer[7]: fc5c9a80 (360600000) > 1(5494) DEBUG: retransmission_handler : done > > > ******************************************************************************** > Backtrace of the core: > > #0 0xfe7f77bc in shm_dup_subs (subs=0xffbff1b0, to_tag=Cannot access > memory > at address 0x96 > ) at notify.c:1819 > 1819 cb_param->wi_subs->to_user.s = (char*)cb_param + size; > (gdb) bt > #0 0xfe7f77bc in shm_dup_subs (subs=0xffbff1b0, to_tag=Cannot access > memory > at address 0x96 > ) at notify.c:1819 > #1 0xfe7f8238 in notify (subs=0x1779c8, watcher_subs=0x15, n_body=0x0, > force_null_body=1024) at notify.c:1562 > #2 0xfe7f8f18 in query_db_notify (p_user=0x234, p_domain=0xdff08, > event=0xfe809a28 "presence.winfo", watcher_subs=0xffbff1b0, etag=0x0) > at notify.c:957 > #3 0xfe8028a8 in update_subscription (msg=0x175fd8, subs=0xffbff1b0, > rtag=0xffbff228, to_tag_gen=1) at subscribe.c:476 > #4 0xfe805080 in handle_subscribe (msg=0x175fd8, str1=0xffbff0e0 "", > str2=0x800 <Address 0x800 out of bounds>) at subscribe.c:1252 > #5 0x00018378 in do_action (a=0x145270, msg=0x175fd8) at action.c:883 > #6 0x00019bb8 in run_action_list (a=0x145270, msg=0x175fd8) at > action.c:131 > #7 0x000192bc in do_action () > #8 0x00019bb8 in run_action_list (a=0x1452c8, msg=0x175fd8) at > action.c:131 > #9 0x00019df8 in run_top_route (a=0x143e10, msg=0x175fd8) at action.c:111 > #10 0x00043b60 in receive_msg (buf=0x12dc00 "", len=1024, > rcv_info=0xe0400) > at receive.c:156 > #11 0x0006f294 in udp_rcv_loop () at udp_server.c:465 > #12 0x000338bc in main_loop () at main.c:834 > #13 0x00035c44 in main (argc=9, argv=0xe7800) at main.c:1399 > (gdb) quit >

2 3

Re: [Serusers] Voicemail setup on SER v0.9.6
by roayu 12 Nov '07

12 Nov '07

Hi Eneref, Thanks for your reply. So, do u mean that I'm gonna have the follwing applications in the SAME box? - 2 SER servers ( 1 existing SER + 1 new SER for SEMS ) with different port - 1 SEMS Thanks. Roa Yu -----Original Message----- From: Eneref [mailto:eneref@arcdiv.com] Sent: Friday, November 09, 2007 4:14 PM To: roayu Subject: Re: [Serusers] Voicemail setup on SER v0.9.6 Yes. You need either SEMS or Asterisk or some such. Meshing SEMS with SER, though it LOOKS complex, is really not that bad. The easiest thing to do is to run another SER server to handle voicemail (on a different port from the first SER if it's on the same box) and forward messages to it if voicemail is required (on time outs, or whatever conditions you set). There are some good instructions on how to do that in the SEMS docs. This also makes it quite easy to swap out with Asterisk or any other sort of voicemail-capable server should the need arise in future. N. roayu wrote: > > Hi there! > > > > Could anyone let me know how to setup Voicemail on SER v.0.9.6 ? Do I > need to install SEMS as well? > > > > Thanks > > > > > > Regards, > > Roa Yu > > ------------------------------------------------------------------------ > > _______________________________________________ > Serusers mailing list > Serusers(a)lists.iptel.org > http://lists.iptel.org/mailman/listinfo/serusers >

1 0

[OpenSER-Users] MediaProxy 1.9.0 - Radius
by Mike O'Connor 11 Nov '07

11 Nov '07

Hi Guys I really think there is something wrong with MediaProxy, I can not get the radius or the mysql accounting to report any details, as best as I can see there is never any attempt to even try. There is nothing in the logs about there being anything wrong at all. I had added print statement thought out the code and I can see that the code for both mysql update and the code for sending radius updates never gets call. I have not been able to find the connection between the radius or mysql thread and the rtphandler but the print statement a in the actual calls to the mysql or radius and the print messages are never seen in the logs. Other prints added by me do get logged. Has any one actual tried the current code and got do the stop updates ? Mike

4 7

[OpenSER-Users] Openser bridging
by Max Lock 11 Nov '07

11 Nov '07

Hi Folks, I'm struggling with bridging openser between a public and a private network. The private 10.10.12.0/24 network connects openser and an asterisk server that plays a file and hangs up. I've got 2 sip clients connected to the public and private sides of the openser server. When I make calls via openser to the asterisk box, I only get audio on the private networks sip client, and neither client gets hung up correctly at the end of the call. I've put the SIP debug from the external client here: http://pastebin.com/m388a707d My openser and rtpproxy configs are here: http://pastebin.com/m3ed309d3 Can anyone give me any pointers? I've been staring at this for days :( -Cheers Max

2 3

[OpenSER-Users] Regarding the LCR module and AVPs...
by Kyle Stone 09 Nov '07

09 Nov '07

I'm using 1.2.X and the LCR module... following syntax fails at start up... $avp(i:20) = 1; if(!load_gw( $avp(i:20) ) ) { with an invalid arg to load_gw... anyone have a suggestion?

3 3

Re: [OpenSER-Users] lack of notify, subscribe problem
by Anca Vamanu 09 Nov '07

09 Nov '07

Stanisław Pitucha wrote: > ----- "Anca Vamanu" <anca(a)voice-system.ro> wrote: > >> I am not sure if snom 190 supports server presence. I've searched a >> bit >> but did not find sufficient info. >> Does the phone send other Subscribe messages apart from the ones with >> >> event: dialog? Does it send any Publish message? >> > > It has "Publish Presence" option turned on. It has also line monitoring with lights. I've found this site with example notify packets: > http://www.abptech.com/support/faqs/faq_snomphone_LED_explained.html > I have both support broken registrar on and filtering off, whatever that means for snom phone. That means it supports something. > Still - it subscribes for dialog properly (as far as I can tell from rfc4235), so I don't understand the bad event response... Or maybe openser just doesn't support 'dialog' events? > Yes, as I have mentioned before, OpenSer does not support 'dialog' event. It has support only for dialog with sla parameter (Event: dialog;sla) , used for BLA implementation (draft draft-anil-sipping-bla-03.txt). Please send a ngrep capture with a Subscribe message with Event: presence , its reply and the Notify that follows. Anca

1 0

[Serusers] proxy_authorize and radius_proxy_authorize doesn't work for ACK
by Tomasz Zieleniewski 09 Nov '07

09 Nov '07

Hi, When I invoke proxy_authorize and radius_proxy_authorize for an ACK message the is no uid avp present. All other messages which are authorized work fine. Why is that so?? Is it the right behaviour?? Bests regards Tomasz

4 4

Re: [Serusers] proxy_authorize and radius_proxy_authorize doesn't work for ACK
by Jiri Kuthan 09 Nov '07

09 Nov '07

At 17:49 08/11/2007, Tomasz Zieleniewski wrote: >Hi Piotr:) > >RFC only implies that proxy should not challenge the ACK message and >moreover it says that client sending ACK should duplicate >Authorization and Proxy-Authorization headers. This it what my client >does. But according to the description of the proxy_authorize function >it only verifies that credentials are valid. This function doesn't >cause the challenge response to be sent to the client. This is >performed with the usage of proxy_challenge function. >"The function verifies credentials according to RFC2617. If the >credentials are verified successfully then the function will succeed >and mark the credentials as authorized (marked credentials can be >later used by some other functions). If the function was unable to >verify the credentials for some reason then it will fail and the >script should call proxy_challenge which will challenge the user >again." >In my opinion, that is why proxy_authorize function should generate >the uid avp for ACK request if verification of credential gives >positive result. Well -- it should be stored somewhere in transaction state and someway I guess you should be able to get access to it (not sure if with or without some hack) ... but do you relaly need that? ACK has a transport function and as such, I don't see the use value for doing more processing with it than abosrbing/forwarding... -jiri -- Jiri Kuthan http://iptel.org/~jiri/

1 0

Re: [Serusers] proxy_authorize and radius_proxy_authorize doesn't work for ACK
by Jiri Kuthan 09 Nov '07

09 Nov '07

At 15:53 08/11/2007, Tomasz Zieleniewski wrote: >Hi, > >When I invoke proxy_authorize and radius_proxy_authorize for an ACK >message the is no uid avp present. >All other messages which are authorized work fine. >Why is that so?? >Is it the right behaviour?? yes. ACk has only a transport function and does not really impact SIP processing. -jiri >Bests regards >Tomasz >_______________________________________________ >Serusers mailing list >Serusers(a)lists.iptel.org >http://lists.iptel.org/mailman/listinfo/serusers -- Jiri Kuthan http://iptel.org/~jiri/

1 0

← Newer
1
...
15
16
17
18
19
20
21
...
25
Older →

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 November 2007