sr-users August 2007

sr-users@lists.kamailio.org

169 participants
286 discussions

[OpenSER-Users] Problem in XMPP module - Open SER xmpp gateway

by Aditya Chaturvedi

I have openser and jabberd running on the same server. After doing configurations described in documentation of XMPP module (http://www.openser.org/docs/modules/1.2.x/xmpp.html ) I am able to send message from SIP client to XMPP client but not able to send it backwards address of XMPP client : username*xmpp_host@gateway_domain address of SIP client : sip_user_name*openser_domain@xmpp_domain I have seen in log and it seems that message is coming to xmpp module(when sending from xmpp client) but it is unable to send to SIP client. Please have a look at attached log and please help : LOG dump ----------------------------------------------- Aug 31 10:47:26 catch22 /usr/sbin/openser[17071]: xmpp: server read [<message xmlns='jabber:client' type='chat' xml:lang='en' id='sd10' to='aditya*192.168.2.14(a)sipxmpp.catch22' from='nitin(a)xmpp.catch22/Pandion'><body>3333333333333333333333333333333</body><html xmlns='http://jabber.org/protocol/xhtml-im'><body xmlns=' http://www.w3.org/1999/xhtml'><span style='font-weight: normal; font-size: 9pt; color: #004200; font-style: normal; font-family: arial'>3333333333333333333333333333333</span></body></html><x xmlns='jisp:x:jep-0038'><name>shinyicons</name></x><active xmlns=' http://jabber.org/protocol/chatstates'/></message>] Aug 31 10:47:26 catch22 /usr/sbin/openser[17071]: xmpp: stream callback: 1: message Aug 31 10:47:26 catch22 /usr/sbin/openser[17071]: DEBUG:tm:t_uac: next_hop=< sip:aditya@192.168.2.14> Aug 31 10:47:26 catch22 /usr/sbin/openser[17071]: DEBUG: mk_proxy: doing DNS lookup... Aug 31 10:47:26 catch22 /usr/sbin/openser[17071]: DEBUG:destroy_avp_list: destroying list (nil) Aug 31 10:47:26 catch22 /usr/sbin/openser[17071]: DEBUG: dlg2hash: 35729 Aug 31 10:47:26 catch22 /usr/sbin/openser[17071]: print_request_uri: sip:aditya@192.168.2.14 Aug 31 10:47:26 catch22 /usr/sbin/openser[17071]: DEBUG:tm:set_timer: relative timeout is 500000 Aug 31 10:47:26 catch22 /usr/sbin/openser[17071]: DEBUG: add_to_tail_of_timer[4]: 0xb612897c (66815700000) Aug 31 10:47:26 catch22 /usr/sbin/openser[17071]: DEBUG:tm:set_timer: relative timeout is 30 Aug 31 10:47:26 catch22 /usr/sbin/openser[17071]: DEBUG: add_to_tail_of_timer[0]: 0xb6128998 (66845) Aug 31 10:47:26 catch22 /usr/sbin/openser[17056]: SIP Request: Aug 31 10:47:26 catch22 /usr/sbin/openser[17056]: method: <MESSAGE> Aug 31 10:47:26 catch22 /usr/sbin/openser[17056]: uri: < sip:aditya@192.168.2.14> Aug 31 10:47:26 catch22 /usr/sbin/openser[17056]: version: <SIP/2.0> Aug 31 10:47:26 catch22 /usr/sbin/openser[17056]: parse_headers: flags=2 Aug 31 10:47:26 catch22 /usr/sbin/openser[17056]: Found param type 232, <branch> = <z9hG4bK19b8.405ac901.0>; state=16 Aug 31 10:47:26 catch22 /usr/sbin/openser[17056]: end of header reached, state=5 Aug 31 10:47:26 catch22 /usr/sbin/openser[17056]: parse_headers: Via found, flags=2 Aug 31 10:47:26 catch22 /usr/sbin/openser[17056]: parse_headers: this is the first via Aug 31 10:47:26 catch22 /usr/sbin/openser[17056]: After parse_msg... Aug 31 10:47:26 catch22 /usr/sbin/openser[17056]: preparing to run routing scripts... Aug 31 10:47:26 catch22 /usr/sbin/openser[17056]: parse_headers: flags=100 Aug 31 10:47:26 catch22 /usr/sbin/openser[17056]: DEBUG:parse_to:end of header reached, state=9 Aug 31 10:47:26 catch22 /usr/sbin/openser[17056]: DBUG:parse_to: display={}, ruri={sip:aditya@192.168.2.14} Aug 31 10:47:26 catch22 /usr/sbin/openser[17056]: DEBUG: get_hdr_field: <To> [25]; uri=[sip:aditya@192.168.2.14] Aug 31 10:47:26 catch22 /usr/sbin/openser[17056]: DEBUG: to body [ sip:aditya@192.168.2.14^M ] Aug 31 10:47:26 catch22 /usr/sbin/openser[17056]: get_hdr_field: cseq <CSeq>: <10> <MESSAGE> Aug 31 10:47:26 catch22 /usr/sbin/openser[17056]: DEBUG: get_hdr_body : content_length=31 Aug 31 10:47:26 catch22 /usr/sbin/openser[17056]: found end of header Aug 31 10:47:26 catch22 /usr/sbin/openser[17056]: DEBUG: is_maxfwd_present: max_forwards header not found! Aug 31 10:47:26 catch22 /usr/sbin/openser[17056]: DEBUG: add_param: tag=d536f7aa2bf73a9942d6233ad6d8ee06-0364 Aug 31 10:47:26 catch22 /usr/sbin/openser[17056]: DEBUG:parse_to:end of header reached, state=29 Aug 31 10:47:26 catch22 /usr/sbin/openser[17056]: DBUG:parse_to: display={}, ruri={sip:nitin*xmpp.catch22@sipxmpp.catch22} Aug 31 10:47:26 catch22 /usr/sbin/openser[17056]: parse_headers: flags=200 Aug 31 10:47:26 catch22 /usr/sbin/openser[17056]: find_first_route: No Route headers found Aug 31 10:47:26 catch22 /usr/sbin/openser[17056]: loose_route: There is no Route HF Aug 31 10:47:26 catch22 /usr/sbin/openser[17056]: grep_sock_info - checking if host==us: 12==12 && [192.168.2.14] == [192.168.2.14] Aug 31 10:47:26 catch22 /usr/sbin/openser[17056]: grep_sock_info - checking if port 5060 matches port 5060 Aug 31 10:47:26 catch22 /usr/sbin/openser[17056]: grep_sock_info - checking if host==us: 12==12 && [192.168.2.14] == [192.168.2.14] Aug 31 10:47:26 catch22 /usr/sbin/openser[17056]: grep_sock_info - checking if port 5060 matches port 5060 Aug 31 10:47:26 catch22 /usr/sbin/openser[17056]: DEBUG:avpops:check_avp: check <192.168.2.14> against <sipxmpp.catch22> as str /1 Aug 31 10:47:26 catch22 /usr/sbin/openser[17056]: DEBUG:avpops:check_avp: no match Aug 31 10:47:26 catch22 /usr/sbin/openser[17056]: lookup(): 'aditya' Not found in usrloc Aug 31 10:47:26 catch22 /usr/sbin/openser[17056]: grep_sock_info - checking if host==us: 12==12 && [192.168.2.14] == [192.168.2.14] Aug 31 10:47:26 catch22 /usr/sbin/openser[17056]: grep_sock_info - checking if port 5060 matches port 5060 Aug 31 10:47:26 catch22 /usr/sbin/openser[17056]: DEBUG: t_newtran: T on entrance=0xffffffff Aug 31 10:47:26 catch22 /usr/sbin/openser[17056]: parse_headers: flags=ffffffffffffffff Aug 31 10:47:26 catch22 /usr/sbin/openser[17056]: parse_headers: flags=78 Aug 31 10:47:26 catch22 /usr/sbin/openser[17056]: t_lookup_request: start searching: hash=35729, isACK=0 Aug 31 10:47:26 catch22 /usr/sbin/openser[17056]: DEBUG: RFC3261 transaction matching failed Aug 31 10:47:26 catch22 /usr/sbin/openser[17056]: DEBUG: t_lookup_request: no transaction found Aug 31 10:47:26 catch22 /usr/sbin/openser[17056]: DEBUG: mk_proxy: doing DNS lookup... Aug 31 10:47:26 catch22 /usr/sbin/openser[17056]: check_via_address( 192.168.2.14, 192.168.2.14, 0) Aug 31 10:47:26 catch22 /usr/sbin/openser[17056]: DBG:check_against_rule_list: using list dns Aug 31 10:47:26 catch22 /usr/sbin/openser[17056]: DEBUG:tm:set_timer: relative timeout is 500000 Aug 31 10:47:26 catch22 /usr/sbin/openser[17056]: DEBUG: add_to_tail_of_timer[4]: 0xb613508c (66815700000) Aug 31 10:47:26 catch22 /usr/sbin/openser[17056]: DEBUG:tm:set_timer: relative timeout is 30 Aug 31 10:47:26 catch22 /usr/sbin/openser[17056]: DEBUG: add_to_tail_of_timer[0]: 0xb61350a8 (66845) Aug 31 10:47:26 catch22 /usr/sbin/openser[17056]: DEBUG:tm:t_relay_to: new transaction fwd'ed Aug 31 10:47:26 catch22 /usr/sbin/openser[17056]: DEBUG:tm:UNREF_UNSAFE: after is 0 Aug 31 10:47:26 catch22 /usr/sbin/openser[17056]: DEBUG:destroy_avp_list: destroying list (nil) Aug 31 10:47:26 catch22 /usr/sbin/openser[17056]: receive_msg: cleaning up Thanks in advance ~Aditya

16 years, 7 months

[OpenSER-Users] PDT Module - R-URI translation

by Noel R. Morais

Hi all, I am trying to use PDT module to translate an URI user@domain to user@IP. But it doesn't accept regex for the domain and prefix. Does somebody know a workaround or another module that works for this purpose? What I am trying to do is something like that: source domain | prefix | destination domain --------------------------------------------------------------------------------- example.com voicemail XXX.XXX.XXX.XXX example.com * YYY.YYY.YYY.YYY example2.com 5511[2-9]{4}[0-9]{4} XXX.XXX.XXX.XXX * voicemail XXX.XXX.XXX.XXX * * YYY.YYY.YYY.YYY thanks, Noel

16 years, 7 months

[OpenSER-Users] Openser 1.3 with Asterisk 1.4 as mediaserver - any experience on call park/pickup and music on hold

by FRITTELLA FABIO

Hello, can anyone has esperience on configure asterisk 1.4 with openser 1.3 to allow call park/pickup and MOH ? Thanks. Fabio Frittella

16 years, 7 months

[OpenSER-Users] can a branch route block be called from another branch route block?

by jh＠tutpro.com

lets say that two branch route blocks have a common piece of code. can duplicating of this code be avoided by including the common code in a third branch route block, which is then called from the other two branch route blocks or is there some other means to avoid the duplication? i tried to find this out from the core cookbook, but the issue was not discussed. -- juha

16 years, 7 months

[OpenSER-Users] Problem with Media for the proxies making calls

by Kaeman Chris

Hello, I am having problem with Media - for one scenario; This scenario works for signaling and media both; softphone --> openser --> proprietory softswitch Caller Via Called Status Duration Codec Type Traffic -------------------------------------------------------------------------------------------- -------- softphoneIP:port - openserIP:port - softswitchIP:port active 0'08" g711 Audio 0/0/0 Total traffic: 0bps/0bps/0bps (in1/in2/out) Session count: 1 Proxy version: 1.9.0 This scenario give PROBLEMS with MEDIA whereas signaling works OK: softphone --> proprietory softswitch --> openser --> proprietory softswitch Below is the output of /usr/local/mediaproxy/sessions.py which shows the called media ip is not seen by openser which results into no audio.. Caller Via Called Status Duration Codec Type Traffic -------------------------------------------------------------------------------------------- -------- spftswitchIP:11920 - openserIP:60008 - ?.?.?.? inactive 0'05" Unknown Audio 0/0/0 Total traffic: 0bps/0bps/0bps (in1/in2/out) Session count: 1 Proxy version: 1.9.0 Here the above called party media shows ? which is the problem. Where i should look as the problem? Please help me. thanks! Kchris --------------------------------- Once upon a time there was 1 GB storage in your inbox. Click here for happy ending.

16 years, 7 months

[OpenSER-Users] openser 1.2.2 segmentation fault

by Marco

Hi all, I'm trying to run openser 1.2.2 on Linux, but I obtain alway a segfault while loading module. The gdb shows: Program terminated with signal 11, Segmentation fault. #0 pg_free_row (_row=0x785bc8) at db_res.c:575 575 switch (VAL_TYPE(_val)) { I've a complex configuration, but the problem arise early so I don't think it's a configuration issue. The last messages I got in the log are: openser[31824]: PG[free_query]: PQclear(0x863a70) result set openser[31824]: PG[free_columns]: Freeing RES_NAMES(0x785b20)[0] -> free(0x785b90) 'table_version' openser[31824]: PG[free_columns]: 0x785b90=pkg_free() RES_NAMES[0] openser[31824]: PG[free_columns]: 0x785b60=pkg_free() RES_NAMES openser[31824]: PG[free_columns]: 0x785b78=pkg_free() RES_TYPES openser[31824]: PG[free_rows]: Freeing 1 rows openser[31824]: PG[free_rows]: Row[0]=0x785bc8 The last query I could see in the database is "select table_version from version where table_name='domain'" (it returns 1) I use postgres 8.2.4 on Linux 2.6.18 with xen, and gcc 4.1.3. Could someone suggest how I can investigate further? TIA, -- "Work and play are words used to describe the same thing under differing conditions." Mark Twain http://people.equars.com/blogs/marco

16 years, 7 months

RE: [OpenSER-Users] nat pinging question

by Papadopoulos Georgios

you are right, thanks a lot! > -----Original Message----- > From: Klaus Darilion [mailto:klaus.mailinglists@pernau.at] > Sent: Thursday, August 30, 2007 2:53 PM > To: Papadopoulos Georgios > Cc: users(a)openser.org > Subject: Re: [OpenSER-Users] nat pinging question > > maybe you are loading mediaproxy module too which also sends > keep alives? > > regards > klaus > > Papadopoulos Georgios schrieb: > > Hello all, > > > > In nathelper the documentation mentions two pinging types > (upd 4 byte > > packets and stateless SIP request). Is there a way to > choose between > > one or the other or are they both activated by default? > > I have configured nathelped to ping with OPTIONS every 15 seconds. > > modparam("nathelper", "natping_interval", 15) modparam("nathelper", > > "sipping_method", "OPTIONS") In addition to the OPTIONS > packets that > > are sent every 15 seconds, there is a 4 byte packet that is > sent every > > minute. Why does this happen and is there a way to turn it off? > > > > This is what the ping packet sequence looks like: > > time ping > > 0 ---> 4 byte pkt > > 0 ---> OPTIONS > > 15 ---> OPTIONS > > 30 ---> OPTIONS > > 45 ---> OPTIONS > > 60 ---> 4 byte pkt > > 60 ---> OPTIONS > > > > thank you > > > > George > > > > > > > > > > > > Disclaimer > > > > The information in this e-mail and any attachments is > confidential. It > > is intended solely for the attention and use of the named > addressee(s). > > If you are not the intended recipient, or person responsible for > > delivering this information to the intended recipient, > please notify > > the sender immediately. Unless you are the intended recipient or > > his/her representative you are not authorized to, and must > not, read, > > copy, distribute, use or retain this message or any part of > it. E-mail > > transmission cannot be guaranteed to be secure or error-free as > > information could be intercepted, corrupted, lost, > destroyed, arrive > > late or incomplete, or contain viruses. > > > > > > > ---------------------------------------------------------------------- > > -- > > > > _______________________________________________ > > Users mailing list > > Users(a)openser.org > > http://openser.org/cgi-bin/mailman/listinfo/users >

16 years, 7 months

[OpenSER-Users] nat pinging question

by Papadopoulos Georgios

Hello all, In nathelper the documentation mentions two pinging types (upd 4 byte packets and stateless SIP request). Is there a way to choose between one or the other or are they both activated by default? I have configured nathelped to ping with OPTIONS every 15 seconds. modparam("nathelper", "natping_interval", 15) modparam("nathelper", "sipping_method", "OPTIONS") In addition to the OPTIONS packets that are sent every 15 seconds, there is a 4 byte packet that is sent every minute. Why does this happen and is there a way to turn it off? This is what the ping packet sequence looks like: time ping 0 ---> 4 byte pkt 0 ---> OPTIONS 15 ---> OPTIONS 30 ---> OPTIONS 45 ---> OPTIONS 60 ---> 4 byte pkt 60 ---> OPTIONS thank you George Disclaimer The information in this e-mail and any attachments is confidential. It is intended solely for the attention and use of the named addressee(s). If you are not the intended recipient, or person responsible for delivering this information to the intended recipient, please notify the sender immediately. Unless you are the intended recipient or his/her representative you are not authorized to, and must not, read, copy, distribute, use or retain this message or any part of it. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses.

16 years, 7 months

[OpenSER-Users] New module - carrierroute - in OpenSER

by Henning Westerholt

Hello everybody, i'm happy to announce the addition of a new module for OpenSER called "carrierroute". This module provides routing, balancing and blacklisting capabilities, from a config file or a database source. It can uses one routing tree, or if needed for every user a different routing tree for number prefix based routing. It supports several route tree levels, e.g. for failback routes. This modules scales up to more than a million users, and is able to handle more than 10k routing table entries. It should be able to handle more, but this is untested at the moment. Routing tables can be reloaded and edited (in config file mode) with the MI interface, the config file is updated according the changes. This is not implemented for the db interface, because its easier to do the changes directly on the db. But the reload and dump functions works of course here too. Basically the module could be used as an replacement for the lcr and the dispatcher module, if you have certain performance, flexibility and/or integration requirements that these modules don't handle properly. But for small installations it probably make more sense to use the lcr and dispatcher modules. Please refer to the documentation at http://www.openser.org/docs/modules/devel/carrierroute.html for further informations, the source code of the modules is available in the svn trunk. Best regards, Henning Westerholt -- Henning Westerholt - Unix system development 1&1 Internet AG, Ernst-Frey-Str. 9, 76135 Karlsruhe, Germany

16 years, 7 months

[OpenSER-Users] proxy1(client)-->Openser-->proxy2(supplier)

by Kaeman Chris

Hello, I have a problem while handling media with openser when the call arrives from a proxy as shown in the following scenario; proxy1(client) --> Openser (No Audio on the call)--> proxy2(supplier) Where as the same scenario with the call originating from the user from the local domain/realm works perfect with this scenario. user@openserdomain --> openser --> proxy2(supplier) After spending the whole day with googling the stuff on the openser sites and others, i am in a vision that Openser with the mediaproxy module can handle only user on the local domain for media. Please help me to understand is the first scenario possible to have audio? thanks!! Hope to hear soon.Thanks!! Regards, KChris --------------------------------- Download prohibited? No problem. CHAT from any browser, without download.

16 years, 7 months

← Newer
1
2
3
4
5
6
7
...
29
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 August 2007