sr-users November 2007

sr-users@lists.kamailio.org

138 participants
248 discussions

[OpenSER-Users] X-lite (for Linux) and BYE Scenario

by Daniel Grotti

Hi All, I've noticed that using X-lite (for Linux) there are some problems with BYE method. When X-lite generates BYE, it puts in the Route Header field the address known through the record-route added by proxy. As "SER - Gettin Started" shown, an address like : IP_proxy:5060;nat=yes: " /.... .... if(method=="INVITE" && client_nat_test("7")) { record_route_preset ("proxy_ip_address :5060;nat=yes"); .... } /" 1. When we have a BYE message sended by X-lite (user A), it is like this: "/Request-Line: BYE sip: B@proxy_ip_address : 5060 SIP/2.0 Via: SIP/2.0/UDP A_address:5061; rport;branch=xyz From: <sip: A@proxy_ip_address:5061>;tag=123 To: <sip: B@proxy_ip_address:5060>;tag=456 Contact:<sip:A@A_address:5061> * Route: <sip: proxy_ip_address:5060; nat=yes; ftag=9098789; lr=on>* .... ..... .... "/ 2. Now the message BYE is parsed by the Proxy, and it uses the loose_route(): /if(loose_route())/ { forward the message }; but Proxy doesn't recognizes its address and then rewrites the R-URI with the address in Route header field and sends the BYE message.....to itself! then Proxy parses the new BYE (sended by itself) with the URI :/* <sip: proxy_ip_address:5060; nat=yes; ftag=9098789; lr=on>,*/ the the answer to user A is : 404 Destination not found! Why doesn't OpenSER, in the loose_route() function, recognize its address in Route header field? This is what should it do. And then, delete the route header field and then forward the message using R-URI. I think there is something wrong.... Regards, Daniel -- --------------------------------------------------- Daniel Grotti DEIS - University of Bologna Via Venezia, 52 - 47023 Cesena (FC) - ITALY Contacts e-mail : daniel.grotti(a)unibo.it Skype name : Daniel Grotti ---------------------------------------------------

17 years

[Serusers] What are the possible HFNAME values in hf selects in ser rel_2_0_0?

by Tomasz Zieleniewski

Hi, What are the possible HFNAME values in hf selects in ser rel_2_0_0? When I try to add my own header and then use the a select for it the select is empty. I do it for P-Asserted-Identity header I did the following selects and no results: xlog("L_INFO", " route[AUTHENTICATION]: P-ASS: %(a)hf_value.p-asserted-identity \n"); xlog("L_INFO", " route[AUTHENTICATION]: P-ASS: %(a)hf_value.P_Asserted_Identity \n"); xlog("L_INFO", " route[AUTHENTICATION]: P-ASS: %(a)hf_value.p_asserted_identity \n"); xlog("L_INFO", " route[AUTHENTICATION]: P-ASS: %(a)hf_value2.p-asserted-identity \n"); xlog("L_INFO", " route[AUTHENTICATION]: P-ASS: %(a)hf_value2.P_Asserted_Identity \n"); xlog("L_INFO", " route[AUTHENTICATION]: P-ASS: %(a)hf_value2.p_asserted_identity \n"); Please point me what do I miss. Regards Tomasz

17 years

[Serusers] (no subject)

by Shad Mortazavi

Shad Mortazavi UK Managing Director Nexus Management (EMEA) Ltd -------------------- T: +44 (0)844 484 2574 M: +44 (0)781 721 0758 Sent from Windows Mobile.

17 years

Re: [OpenSER-Users] CPL "Location" and "Proxy" behavior

by Bogdan-Andrei Iancu

Hi Daniel, Hmmm....I see - you say (for outgoing scenario) that the location set is initialized with the A destination instead of B destination, right? If so, please open a bug report on the tracker. regards, Bogdan Daniel Grotti wrote: > Hi bogdan, > If it's my cpl outgoing script configuration, from USER A > ****************************************************** > <cpl> > <outgoing> > <address-switch field="destination" subfield="user"> > <address is="B"> > <proxy /> > </address> > </address-switch> > </outgoing> > <cpl> > ******************************************************* > When I make a call from A to B, then the script has called, but in > debug I can see that CPL rewrites R-URI with source address > (A@A_ip_address) instead of destination address (B@B_ip_address). So > the message goes back to user A. > > regards, > Daniel > > Bogdan-Andrei Iancu wrote: >> Hi Daniel, >> >> there are no differences - the implementation follows the RFC. For >> incoming calls, the location set is empty, but it can be populated by >> the CPL script during execution. So, when you do "proxy", you may >> have multiple entries in the location set. >> >> The comment in the cpl_sig.c file refers to some implementation >> details - how to process the available location set, depeding if it >> is the first time doing proxy (for the call) or a second time. >> >> regards, >> bogdan >> >> daniel grotti wrote: >>> Hi all, >>> this is what CPL_SIG.c says about forwarding a given message to the >>> given location set: >>> >>> " forwards the msg to the given location set; if flags has set the >>> CPL_PROXY_DONE, all locations will be added as branches, >>> otherwise, the first one will set as RURI (this is ha case when >>> this is the first proxy of the message) >>> The given list of location will be freed, returning 0 instead. >>> Returns: 0 - OK " >>> >>> >>> My question is : which and what is "the first one" location ? Can >>> you explain it better? >>> Because RFC 3880 say that : "For the incoming top-level call >>> processing action, the location set is initialized to the empty set. >>> For the outgoing action, it is initialized to the destination >>> address of the call." >>> >>> So RFC is very clear. I think there are considerable differences >>> between RFC and the behavior of CPL interpreter. >>> >>> Thanks. >>> Daniel >>>

17 years

[OpenSER-Users] CPL "Location" and "Proxy" behavior

by daniel grotti

Hi all, this is what CPL_SIG.c says about forwarding a given message to the given location set: " forwards the msg to the given location set; if flags has set the CPL_PROXY_DONE, all locations will be added as branches, otherwise, the first one will set as RURI (this is ha case when this is the first proxy of the message) The given list of location will be freed, returning 0 instead. Returns: 0 - OK " My question is : which and what is "the first one" location ? Can you explain it better? Because RFC 3880 say that : "For the incoming top-level call processing action, the location set is initialized to the empty set. For the outgoing action, it is initialized to the destination address of the call." So RFC is very clear. I think there are considerable differences between RFC and the behavior of CPL interpreter. Thanks. Daniel ----------------------------- Daniel Grotti DEIS - Universita' di Bologna ----------------------------- Via Venezia, 52 47023 Cesena (FC) - ITALY ----------------------------- email:daniel.grotti@unibo.it -----------------------------

17 years

[Serusers] Openser bridging

by Max Lock

Hi Folks, I'm still 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

17 years

[Serusers] Integrate LCS & SER Server

by elilkumaran s

Sir/Madam I'm a System administrator of Institute. I use MS LCS 2005 SP1 Enterprise edition & Office Communicator in my work place. I have linux SER Server & CISCO ATA 186 Telephone adapter. I have to run to Messenger client X-Lite for SER Server and Office Communicator for LCS. Because I place TP in Guard Office they can call Staff through SER server / X-Lite. But can't call Office Communicator! CISCO ATA 186 can't registering in LCS, I thing it not possible directly. ( Because LCS use Active Directory Account through Kerbas & NTLM authentication). So I want integrate LCS & SER Server to facilitate TP call to Office Communicator & Office Communicator call TP. I use a pool in LCS as normal TCP (not TLS). SER Server also use normal (with out DB -Any one can registrar with any name) Could you kindly tell the process for integrate LCS & SER Server? Thank You Your truly Elil

17 years

[OpenSER-Users] Core dumped when deploying presence module

by Sergio Gutierrez

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

17 years

Re: [Serusers] Integrate LCS & SER Server

by Jiri Kuthan

At 18:17 05/11/2007, elilkumaran s wrote: >Sir/Madam > >I'm a System administrator of Institute. > >I use MS LCS 2005 SP1 Enterprise edition & Office Communicator in my work place. >I have linux SER Server & CISCO ATA 186 Telephone adapter. > >I have to run to Messenger client X-Lite for SER Server and Office Communicator for LCS. > >Because I place TP in Guard Office they can call Staff through SER server / X-Lite. >But can't call Office Communicator! Consider this "howto": - log in as administrator in the Windows machine on which LCS is running - start debian installation CD - when asked "replace existing partitions", answer yes - when finished, install SER debian packages, along with mysql - continue testing your SIP end-devices ;-) >CISCO ATA 186 can't registering in LCS, I thing it not possible directly. ( Because LCS use Active Directory Account through Kerbas & NTLM authentication). >So I want integrate LCS & SER Server to facilitate TP call to Office Communicator & Office Communicator call TP. >I use a pool in LCS as normal TCP (not TLS). SER Server also use normal (with out DB -Any one can registrar with any name) > >Could you kindly tell the process for integrate LCS & SER Server? Seriously -- why would you like to have two servers when you can have one, whichever you prefer better? -jiri >Thank You >Your truly >Elil > > > >_______________________________________________ >Serusers mailing list >Serusers(a)lists.iptel.org >http://lists.iptel.org/mailman/listinfo/serusers -- Jiri Kuthan http://iptel.org/~jiri/

17 years

[OpenSER-Users] mi_fifo leaves little openser_receiver_* fifos on the floor

by Chris Heiser

I have a cronjob that periodically runs openserctl to gather stats out of openser. I've noticed that in my fifo directory, there are anywhere from 1.5 ~ 3k openser_receiver files laying around. Is there something screwy with mi_fifo in v1.2.2-tls that's preventing it from cleaning up after itself? --Chris

17 years

← Newer
1
...
18
19
20
21
22
23
24
25
Older →

Jump to page:

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