- sr-users - kamailio.org

[Users] Help wanted
by Flavio Goncalves 06 Apr '07

06 Apr '07

Dear coleagues, I need help to translate an OpenSER eBook (building a SIP provider) from portuguese to english. I'm willing paying US$75,00 (paypal) per chapter. If any of you have interest, please contact me at flavio(a)asteriskguide.com Regards, Flavio E. Goncalves

1 0

[Serusers] Can SER do it? Extract info
by Gustavo Passos Tourinho 05 Apr '07

05 Apr '07

Hi There. Can SER extract info from request uri? For example, If I have this uri: INVITE sip:123456#0159559432@my.sip.domain How can I get data before "#" (123456)? I dont want to "strip" this information, just want to get it for further utilization. Is that possible? If it can be done, can be done using variable number of digits? For example: INVITE sip:123#0159559432@my.sip.domain INVITE sip:1234567#0159559432@my.sip.domain Thanks in advanced. Regards, Gustavo

2 1

[Serusers] support to implemente multi leg call radius accounting
by Rosario Pingaro 05 Apr '07

05 Apr '07

We are looking to find support to implement multi leg call accounting in our 0.9.6 ser configuration. We use radius accounting. Any consultant interested supporting us may submit a quotation to this email. Reagrds Rosario

1 0

[Users] t_relay() has no effect !
by JP Ramoul 05 Apr '07

05 Apr '07

2 1

[Serusers] uninstall
by Tuan Nguyen 05 Apr '07

05 Apr '07

Hi everybody, I have installed ser-0.9.6 and now i want to uninstall it to new install in correctly way because it works not property. how can i complete uninstall old version. thanks in advance T.

2 1

Re: [Serusers] error by ser-2.1
by Ladislav Andel 05 Apr '07

05 Apr '07

Here is the answer: http://lists.iptel.org/pipermail/serusers/2007-April/032657.html or http://lists.iptel.org/pipermail/serusers/2007-April/032655.html You need to download stable or earlier version of SER 2.1 because of temporary broken database API. Lada Tuan Nguyen wrote: > Hi Andel, > > I do not see anywhere say that "2 posts before question". > > I am newbie by SER, I have many problem to try to run it, how can > solve this problem without question? and what is "Support for users of > the SIP Express Router" in http://lists.iptel.org/mailman/listinfo/ ? > > Please tell me what should i do to solve my problem when i don`t find > answer in archive? > thanks, > T. > On 4/5/07, *Ladislav Andel* <ladaan(a)iptel.org > <mailto:ladaan@iptel.org>> wrote: > > Hi, > Have you been reading the serusers mailing list ? > Just 2 posts before your question you will find the answer. > > It is for everybody. Read and search the list before asking. > > Peace :), > Lada > > >

1 0

[Serusers] error by ser-2.1
by Tuan Nguyen 05 Apr '07

05 Apr '07

hi everyone, when i compile new version i get follow error: make[1]: Entering directory `/net/u/ntm/Desktop/ser- 2.1.0+cvs20070404/modules/auth_db' make[1]: Leaving directory `/net/u/ntm/Desktop/ser- 2.1.0+cvs20070404/modules/auth_db' make[1]: Entering directory `/net/u/ntm/Desktop/ser- 2.1.0+cvs20070404/modules/auth_db' gcc -fPIC -DPIC -g -O9 -funroll-loops -Wcast-align -minline-all-stringops -falign-loops -ftree-vectorize -mtune=athlon64 -Wall -DNAME='"ser"' -DVERSION='"2.1.0+cvs20070404"' -DARCH='"i386"' -DOS='linux_' -DOS_QUOTED='"linux"' -DCOMPILER='"gcc 4.1.2"' -D__CPU_i386 -D__OS_linux -DSER_VER=2001000 -DCFG_DIR='"/usr/local/etc/ser/"' -DPKG_MALLOC -DSHM_MEM -DSHM_MMAP -DDNS_IP_HACK -DUSE_IPV6 -DUSE_MCAST -DUSE_TCP -DDISABLE_NAGLE -DHAVE_RESOLV_RES -DUSE_DNS_CACHE -DUSE_DNS_FAILOVER -DUSE_DST_BLACKLIST -DDBG_QM_MALLOC -DUSE_TLS -DTLS_HOOKS -DFAST_LOCK -DADAPTIVE_WAIT -DADAPTIVE_WAIT_LOOPS=1024 -DCC_GCC_LIKE_ASM -DHAVE_GETHOSTBYNAME2 -DHAVE_UNION_SEMUN -DHAVE_SCHED_YIELD -DHAVE_MSG_NOSIGNAL -DHAVE_MSGHDR_MSG_CONTROL -DHAVE_ALLOCA_H -DHAVE_TIMEGM -DHAVE_EPOLL -DHAVE_SIGIO_RT -DSIGINFO64_WORKARROUND -DHAVE_SELECT -c authdb_mod.c -o authdb_mod.o In file included from authdb_mod.c:49: authdb_mod.h:57: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'auth_dbf' authdb_mod.c:106: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'auth_dbf' authdb_mod.c: In function 'child_init': authdb_mod.c:165: error: 'auth_dbf' undeclared (first use in this function) authdb_mod.c:165: error: (Each undeclared identifier is reported only once authdb_mod.c:165: error: for each function it appears in.) authdb_mod.c: In function 'mod_init': authdb_mod.c:180: warning: implicit declaration of function 'bind_dbmod' authdb_mod.c:180: error: 'auth_dbf' undeclared (first use in this function) authdb_mod.c: In function 'destroy': authdb_mod.c:206: error: 'auth_dbf' undeclared (first use in this function) authdb_mod.c: In function 'authdb_fixup': authdb_mod.c:226: error: 'auth_dbf' undeclared (first use in this function) authdb_mod.c:231: warning: implicit declaration of function 'table_version' make[1]: *** [authdb_mod.o] Error 1 make[1]: Leaving directory `/net/u/ntm/Desktop/ser- 2.1.0+cvs20070404/modules/auth_db' make: *** [modules] Error 1 anyone know why and how correct it. thanks T.

2 1

[Users] Advanced OpenSER Programming Course, Paris, INRIA, June 4-6, 2007
by Daniel-Constantin Mierla 05 Apr '07

05 Apr '07

Hello, following some discussions started during first OpenSER Summit, we are happy to announce that first Advanced Programming Course will happen very soon. Courtesy of INRIA (many thanks to Philippe Sultan) we have the room and a good connected location. There will be three full days of deep analysis and survey of internal architecture and structures, best practices to add new features, optimizations and OpenSER's specific components (memory manager, locking system, ...). The course is dedicated to people willing to develop OpenSER extensions. It will be a class of 14 persons. The participation fee will be just to cover the logistic required for this event, estimated to be about 150-200Euro per person, for the full course (mainly is subject of how many participants will be registered). Teachers will be Bogdan-Andrei Iancu and Daniel-Constantin Mierla, from OpenSER development team, and the primary goal is to attract more developers to core components of OpenSER and build a higher development squad. Also, there will be open discussions to improve existing code and functionalities. If the interest for this event is high, the primary selection criteria will include the level of contributions so far and willingness to contribute in the future. New similar events will be scheduled if the number of people showing interest is enough for another one or more classes. For this one, we expect to have people with pretty good knowledge of SIP and OpenSER operation, to avoid long introduction lessons. If you are interested in this course, please send an email to team(a)openser.org. <mailto:team@openser.org.> News link: http://www.openser.org/mos/view/News/NewsItem/Advanced-OpenSER-Programming-… Cheers, Daniel

1 1

[Users] Presence: nothing to retransmit ???
by Eddie 05 Apr '07

05 Apr '07

Hi all, I am a new to openser. I am using openser-1.2.0-notls. I met a issue when I setup a presence server. I use a UDP testing tool to send PUBLISH message : PUBLISH sip:111@sip.comverse.com SIP/2.0 To: <sip:111@sip.comverse.com> From: <sip:111@sip.comverse.com>;tag=aa0e9e60 Via: SIP/2.0/UDP 172.19.1.190:5060;branch=z9hG4bK-d87543-4f7005092661b51b-1--d87543-;rport Call-ID: dd2288324976454c@UG9ja2V0X1BD CSeq: 4444 PUBLISH Contact: <sip:111@172.19.1.190:5060> Expires: 3600 Max-Forwards: 70 Content-Type: application/pidf+xml Event: presence Content-Length: 549 <?xml version="1.0" encoding="UTF-8" ?> <presence xmlns="urn:ietf:params:xml:ns:pidf" xmlns:rpid="urn:ietf:params:xml:ns:pidf:rpid" xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model" xmlns:op="urn:oma:params:xml:ns:pidf:oma-pres" xmlns:xsi="<A href="http://www.w3.org/2001/XMLSchema-instan">http://www.w3.org/2001/XMLSchema-instan</A><BR> <tuple id="t0001"><BR> <status><BR> <basic>open</basic><BR> </status><BR> <op:overriding-willingness><BR> <op:basic>open</op:basic><BR> </op:overriding-willingness><BR> </tuple><BR></presence></DIV> <DIV> </DIV> <DIV>but no 200 OK return back from the server. and I set debug level to 7, the log is as followed: </DIV> <DIV> </DIV> <DIV>4(5485) method: <PUBLISH><BR> 4(5485) uri: <sip:111@sip.comverse.com><BR> 4(5485) version: <SIP/2.0><BR> 4(5485) parse_headers: flags=2<BR> 4(5485) DEBUG:parse_to:end of header reached, state=10<BR> 4(5485) DBUG:parse_to: display={}, ruri={sip:111@sip.comverse.com}<BR> 4(5485) DEBUG: get_hdr_field: <To> [28]; uri=[sip:111@sip.comverse.com]<BR> 4(5485) DEBUG: to body [<sip:111@sip.comverse.com><BR><BR> 4(5485) Found param type 232, <branch> = <z9hG4bK-d87543-4f7005092661b51b-1--d87543->; state=6<BR> 4(5485) Found param type 235, <rport> = <n/a>; state=17<BR> 4(5485) end of header reached, state=5<BR> 4(5485) parse_headers: Via found, flags=2<BR> 4(5485) parse_headers: this is the first via<BR> 4(5485) After parse_msg...<BR> 4(5485) preparing to run routing scripts...<BR> 4(5485) parse_headers: flags=100<BR> 4(5485) get_hdr_field: cseq <CSeq>: <4445> <PUBLISH><BR> 4(5485) DEBUG:maxfwd:is_maxfwd_present: value = 70<BR> 4(5485) DEBUG: add_param: tag=aa0e9e60<BR> 4(5485) DEBUG:parse_to:end of header reached, state=29<BR> 4(5485) DBUG:parse_to: display={}, ruri={sip:111@sip.comverse.com}<BR> 4(5485) parse_headers: flags=200<BR> 4(5485) DEBUG: get_hdr_body : content_length=549<BR> 4(5485) found end of header<BR> 4(5485) find_first_route: No Route headers found<BR> 4(5485) loose_route: There is no Route HF<BR> 4(5485) grep_sock_info - checking if host==us: 16==12 && [sip.comverse.com] == [172.19.1.170]<BR> 4(5485) grep_sock_info - checking if port 5060 matches port 5060<BR> 4(5485) grep_sock_info - checking if host==us: 16==12 && [sip.comverse.com] == [172.19.1.170]<BR> 4(5485) grep_sock_info - checking if port 5060 matches port 5060<BR> 4(5485) DEBUG: t_newtran: T on entrance=0xffffffff<BR> 4(5485) parse_headers: flags=ffffffffffffffff<BR> 4(5485) parse_headers: flags=78<BR> 4(5485) t_lookup_request: start searching: hash=29736, isACK=0<BR> 4(5485) DEBUG: RFC3261 transaction matched, tid=-d87543-4f7005092661b51b-1--d87543-<BR> 4(5485) DEBUG:tm:REF_UNSAFE: after is 1<BR> 4(5485) DEBUG: t_lookup_request: transaction found (T=0xb6148f48)<BR> 4(5485) DEBUG:tm:t_retransmit_reply: nothing to retransmit<BR> 4(5485) DEBUG:tm:UNREF_UNSAFE: after is 0<BR> 4(5485) DEBUG:destroy_avp_list: destroying list (nil)<BR> 4(5485) receive_msg: cleaning up<BR> 5(5488) PRESENCE: msg_watchers_clean:cleaning pending subscriptions<BR> 5(5488) PRESENCE: msg_active_watchers_clean:cleaning expired watcher information<BR> 5(5488) PRESENCE:msg_presentity_clean:cleaning expired presentity information</DIV> <DIV> </DIV> <DIV>I am confused about the issue, and I am not sure whether it is caused by configuration files or mysql database.</DIV> <DIV> </DIV> <DIV>Please help me. Thanks so much !</DIV> <DIV> </DIV> <DIV> </DIV> <DIV>Brs,</DIV> <DIV> </DIV> <DIV>Eddie</DIV> <DIV> </DIV>

2 1

[Users] host identification
by Joao Pereira 05 Apr '07

05 Apr '07

Hello does openSER uses the host identificayion in any way to authenticate its costumers? Because I re-installed my server and thats the only difference from the previous instalation (its even in the same machine). Thanks regards Joao pereira

2 1

[Users] openser 1.2 avp
by laurent schweizer 05 Apr '07

05 Apr '07

Hello, with openser 1.0 I have this if ( avp_db_load("$low_c_service/username","i:/serviceLowCoastredirect")) and for openser 1.2 I try to do this if ( avp_db_load("$avp(low_c_service)/username","i:/serviceLowCoastredirect")) or if ( avp_db_load("$avp($low_c_service)/username","i:/serviceLowCoastredirect")) low_c_service is an alias avp_aliases="low_c_service=i:500" but I have always an error. 0(0) ERROR:avops:parse_avp_db:: error - bad avp flags 0(0) ERROR:avpops:fixup_db_avp: parse failed 0(0) ERROR: fix_actions: fixing failed (code=-1) at cfg line 633 0(0) ERROR: fix_expr : fix_actions error

2 1

[Users] SIP SUBSCRIBE AND MESSAGE msgs
by Abdurrahman Sahin 05 Apr '07

05 Apr '07

hi all; i installed openser now trying to setup a basic text commnuication between two clients on the same pc (one client is windows msngr and the other one is x-lite ) it seems to me SUBSCRIBE and MESSAGE sip msgs are not processed. i generated openser.cfg with the wizard at sipwise.com site here is my ngrep dump for SUBSCRIBE msg ==================== U ua_public_ip:29350 -> 192.168.200.2:5060 SUBSCRIBE sip:burak@testsrv200 SIP/2.0. Via: SIP/2.0/UDP ua_public_ip:29347. Max-Forwards: 70. From: "apo@testsrv200" <sip:apo@testsrv200>;tag=29774bb79657418eb518068a22304b7c;epid=13d631ff91. To: <sip:burak@testsrv200>. Call-ID: 15088cb5e87d4fb887cc073d0fd9df07. CSeq: 1 SUBSCRIBE. Contact: <sip:ua_public_ip:29347>. User-Agent: RTC/1.3. Event: presence. Accept: application/xpidf+xml, text/xml+msrtc.pidf, application/pidf+xml. Supported: com.microsoft.autoextend. Supported: ms-benotify. Proxy-Require: ms-benotify. Content-Length: 0. . # U 192.168.200.2:5060 -> ua_public_ip:29350 SIP/2.0 501 Method Not Supported Here. Via: SIP/2.0/UDP ua_public_ip:29347;rport=29350. From: "apo@testsrv200" <sip:apo@testsrv200>;tag=29774bb79657418eb518068a22304b7c;epid=13d631ff91. To: <sip:burak@testsrv200>;tag=329cfeaa6ded039da25ff8cbb8668bd2.ea73. Call-ID: 15088cb5e87d4fb887cc073d0fd9df07. CSeq: 1 SUBSCRIBE. Server: OpenSER (1.2.0-notls (x86_64/linux)). Content-Length: 0. MESSAGE msg (while trying to establish a text chat) =========================== U ua_public_ip:29355 -> 192.168.200.2:5060 MESSAGE sip:apo@testsrv200 SIP/2.0. Via: SIP/2.0/UDP 192.168.1.33:58348;branch=z9hG4bK-d87543-2a3b75359734fe48-1--d87543-;rport. Max-Forwards: 70. To: "apo"<sip:apo@testsrv200>. From: "burak"<sip:burak@testsrv200>;tag=fb1a9f68. Call-ID: NTNhMGZlMmYwODIxNmFlNmNmYThmYjQ0NzFhOGFjODI.. CSeq: 2 MESSAGE. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO. Content-Type: application/im-iscomposing+xml. User-Agent: X-Lite release 1006e stamp 34025. Content-Length: 259. . <?xml version='1.0' encoding='UTF-8'?> <isComposing xmlns='urn:ietf:params:xml:ns:im-iscomposing' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'> <state>active</state> <contenttype>goober</contenttype> <refresh>60</refresh> </isComposing> # U 192.168.200.2:5060 -> ua_public_ip:29355 SIP/2.0 501 Method Not Supported Here. Via: SIP/2.0/UDP 192.168.1.33:58348;branch=z9hG4bK-d87543-2a3b75359734fe48-1--d87543-;rport=29355;received=ua_public_ip. To: "apo"<sip:apo@testsrv200>;tag=329cfeaa6ded039da25ff8cbb8668bd2.402d. From: "burak"<sip:burak@testsrv200>;tag=fb1a9f68. Call-ID: NTNhMGZlMmYwODIxNmFlNmNmYThmYjQ0NzFhOGFjODI.. CSeq: 2 MESSAGE. Server: OpenSER (1.2.0-notls (x86_64/linux)). Content-Length: 0. . .

2 1

[Users] Strange behaviour on siptrace module
by Sergio Gutierrez 05 Apr '07

05 Apr '07

Hi list. I am having a problem with siptrace module. When I send the command sip_trace on through fifo, openser do not send back responses to user agents. On logfile (with debug=9), I just receive this message: sip_trace: storing info... On database do not appear any trace message. Thanks in advance for your attention. Kind regards. Sergio G.

2 1

[Users] proxy-authenticate causes phone to drop authenticate creds
by Mark Price 05 Apr '07

05 Apr '07

Hi, I am using openser 1.1.x as a front end to asterisk. Here is what happens in the dialog: 1. phone sends invite 2. openser says "Unauthorized" 3. phone sends invite + Authorization header 4. openser auths the packet and forwards to asterisk 5. asterisk says "proxy authentication required" 6. openser says "proxy authentication required" here is where it gets interesting. 7.a On some devices, the phone sends invite + Authorization header + Proxy-Authorizaiton header. 7.b On some devices, the phone sends invite + Proxy-Authorization header. How does one work around 7.b? Really, what I want to see is how to make it so that asterisk does not try to authenticate the call. However, since that doesn't seem to be possible, what is the sensible way to route these calls? Thanks, Mark Price

2 1

[Users] Authentication problem
by charl van vuuren 05 Apr '07

05 Apr '07

I'm trying to setup Openser (1.1) as registrar with mediaproxy and mysql all on the same box. I am currently using the SIP Proxy/Registrar with Mediaproxy config from sipwise. MySQL and Mediaproxy are running. Xlite registers successfully with Openser with the users I have created. The problem comes with the authentication. Both www_authorize and proxy_authorize fail. www_authorize fails at regtistration and proxy_authorize off course then fails when I try make a call. Any suggestions? Thanx

2 1

[Users] user agent in avp
by Mark Price 05 Apr '07

05 Apr '07

Hi, In openser 1.1.x, is it possible to get similar functionality to that suggested by the following: avp_check($hdr(ua[0]),"re/Some Phone UA/") thanks Mark Price

2 1

[Users] radius attributes
by Terry Robert 05 Apr '07

05 Apr '07

Hi openser, Following the tutorial on FreeRadius integration (http://www.openser.org/docs/openser-radius-1.0.x.html), I'm seeing accounting packets successfully sent to Radiusd. However, some attributes are missing, notably: UserName, CallingStationId, and CalledStationId. Radius client dictionary contains: ATTRIBUTE User-Name 1 string ATTRIBUTE Password 2 string ... ATTRIBUTE Called-Station-Id 30 string ATTRIBUTE Calling-Station-Id 31 string Output from 'radiusd -X' shows: ... Module: Instantiated detail (detail) Listening on authentication *:1812 Listening on accounting *:1813 Ready to process requests. rad_recv: Accounting-Request packet from host 10.10.90.198:32812, id=10, length=120 Acct-Status-Type = Start Service-Type = IAPP-Register Attr-102 = 0x000000c8 Error-Cause = 1 Event-Timestamp = "Apr 4 2007 15:10:27 PDT" Attr-105 = 0x3937333153495070546167303031 Attr-104 = 0x3937323853495070546167303131 Acct-Session-Id = "1-9731(a)10.10.90.51" NAS-Port = 5060 Acct-Delay-Time = 0 NAS-IP-Address = 10.10.90.198 Processing the preacct section of radiusd.conf modcall: entering group preacct for request 0 modcall[preacct]: module "preprocess" returns noop for request 0 rlm_acct_unique: WARNING: Attribute User-Name was not found in request, unique ID MAY be inconsistent ... Any tips on how to fix this? Thanks.

1 0

RE: [Serusers] Problems with ACK
by Jiri Kuthan 04 Apr '07

04 Apr '07

I think the key message for problem analysis, client's ACK, is missing. This is the setting, right:? .100/UAC -----NAT/.248----> SER outbound @ .246 -----> UAS @ .239 The ACK in your message dump is only that one sent from proxy (246) to UAS (.239). The ACK which can possibly mismatch and produce the error message you mentioned must come from upstream. To be properly formatted, it must have Via identical to that of initial INVITE ( Via: SIP/2.0/UDP 192.168.1.100:5060;rport=46127;received=100.100.100.248;branch=z9hG4bK2893084087) -jiri At 17:50 27/03/2007, Ricardo Martinez wrote: No. Time Source Destination Protocol Info > 14 6.102719 100.100.100.239 100.100.100.246 SIP Status: 487 Request Terminated >Session Initiation Protocol > Status-Line: SIP/2.0 487 Request Terminated > Status-Code: 487 > Resent Packet: False > Message Header > Via: SIP/2.0/UDP 100.100.100.246;branch=z9hG4bK895c.a98d35.0 > Via: SIP/2.0/UDP 192.168.1.100:5060;rport=46127;received=100.100.100.248;branch=z9hG4bK2893084087 >No. Time Source Destination Protocol Info > 15 6.103011 100.100.100.246 100.100.100.239 SIP Request: ACK sip:005622408196@100.100.100.239 >Session Initiation Protocol > Request-Line: ACK sip:005622408196@100.100.100.239 SIP/2.0 > Method: ACK > Resent Packet: False > Message Header > Via: SIP/2.0/UDP 100.100.100.246;branch=z9hG4bK895c.a98d35.0 > f: "cl" <sip:cl@sipvoiss.desa.redvoiss.net>;tag=1587516403 > SIP Display info: "cl" > SIP from address: sip:cl@sipvoiss.desa.redvoiss.net > SIP tag: 1587516403 > i: <mailto:e94a98aa177e8579e5242a2091c0ac5f@192.168.1.100>e94a98aa177e8579e5242a2091c0ac5f(a)192.168.1.100 > To: <sip:0299005622408196@sipvoiss.desa.redvoiss.net>;tag=9146c297a4 >Thanks > >Ricardo.- >_______________________________________________ >Serusers mailing list >Serusers(a)lists.iptel.org >http://lists.iptel.org/mailman/listinfo/serusers -- Jiri Kuthan http://iptel.org/~jiri/

3 4

[Serusers] error with CPL script( CPL module of SER)
by dillip parida 04 Apr '07

04 Apr '07

Hi all, I am trying to implement call redirection feature using cpl script. I have complied cpl module that supports the cpl script. I have uploaded the cpl script. plz help me to solve the problem.. I have written this mail regarding the error that > we are getting in testing the cpl script of Call redirection. > > We have three X-lite phones with SIP uris 2001(a)172.16.1.24, > ,2002(a)172.16.1.28 and 2003(a)172.16.1.31 and all the three soft phones > have been registered with SER proxy running on 10.2.3.123. All the > three users have added in the SER database along with mail ids. > > user mail id > 2001 2001(a)172.16.1.24 > 2002 2002(a)172.16.1.28 > 2003 2003(a)172.16.1.31 > > The call scenario is as follows.. > 1.user 2001 will make a call to user 2002. > 2. If the user 2002 is either not responding (No answer) or busy, then > the call > will be redirected to user 2003. > 3. we able to make a call to 2002,and user 2002's X-lite phone is > ringing but the call is > not getting redirected. > > The cpl script for redirection has been deployed in SER proxy. > > I am sending the call log of sip phone:2001 as an attachment along > with snapshot sip phone 2001. > > I am sending cpl script at the bottam of this mail.plz find the cpl script at the end of this mail. > As shown in the xlite screen "500 CPL script execution failed" can u > please suggest me if there is > any error in XML/CPL syntax. > > > > > > > > > > > > > > > > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------ > > <?xml version="1.0"?> > <!DOCTYPE html cpl PUBLIC "-//IETF//DTD RFCxxx CPL 1.0//EN" "cpl.dtd"> > <cpl> > <subaction id="pda"> > <location url="sip:2003@172.16.1.31 <sip:1003@172.16.1.31>"> > <proxy/> > </location> > </subaction> > <incoming> > <location url="sip:2002@172.16.1.28 <sip:1002@172.16.1.28>"> > <proxy timeout="8"> > <busy> > <sub ref="pda"/> > </busy> > <noanswer> > <sub ref="pda"/> > </noanswer> > </proxy> > </location> > </incoming> > </cpl>

1 0

Re: [Users] does openser support QoS ?
by NEILL WILKINSON 04 Apr '07

04 Apr '07

The more obvious question is: How does it know there is no more bandwidth available? As a signalling proxy, surely it has no visibility of the RTP usages or requirements. I guess if it counted all the complete INVITE-> OK dialogues and the SDP codec used it could estimate usage? But the RTP/media path could be different in each case of these so again the same question as above...... Neill...;o) ----- Original Message ---- From: Henning Westerholt <henning.westerholt(a)1und1.de> To: users(a)openser.org; yanlin <yanlin(a)fortinet.com> Sent: Tuesday, 3 April, 2007 10:41:31 AM Subject: Re: [Users] does openser support QoS ? On Tuesday 03 April 2007 11:15, yanlin wrote: > Hi, > > does openser support some kind of QoS ? > like, band width management, when there has no more usable bandwidth, then > new INVITE should be rejected. Hi Yanlin, if the bandwith is exceeded, no new INVITEs will get to the server and will timeout. :-) The "pike" module does some kind of DOS protection, but this is also no real QoS. There was a discussion two weeks ago about this topic on devel (the topic was "rand function in config file"), Klaus suggested some kind of bandwith management module there. But at the moment such a module don't exist in OpenSER. Cheers, Henning _______________________________________________ Users mailing list Users(a)openser.org http://openser.org/cgi-bin/mailman/listinfo/users

1 0

[Users] New features added to OpenSer - BLA support and XMPP presence gateway
by Anca-Maria Vamanu 04 Apr '07

04 Apr '07

Two new modules were just introduced to SVN -- both are related to presence services. 1) pua_bla - implements Bridged Line Appearances according to the specifications in draft-anil-sipping-bla-03.txt. BLA, aka Shared Call/Line Appearance, comes from old telephony, where many devices share same line. Translated to SIP, means that many SIP devices share same AoR, but only one call can be established at a time, either addressed or initiated from the line. The call can be put on hold, and the others devices are notified so that they can pick up the call (the typical example is that with the secretary answering the call and putting it on hold to be picked up by the boss). The SIP devices must have client-side support for BLA as well. In out tests we used POLYCOM SoundPoint IP 430 SIP phones. The behaviour for this specific device: when picking up the handset form one phone a red light appears at the other phones. If attempting to call from a second phone using the same line, you get the message "Resources full". If a call is established, when putting it on hold, the light starts to flicker at the other phones and it is possible to pick it up. 2) pua_xmpp - is a presence gateway between SIMPLE and XMPP. It comes to complete the IM gateway, by enabling presence state information exchange between SIP/SIMPLE and Jabber/XMPP clients. For testings we used Gaim 2.0.0beta5, Psi v0.10 for XMPP and Xlite v3.0 for SIP. Some sample config file to implement above features will be published soon on dokuwiki.

1 0

RE: [Users] Problem with dialog module
by Leonid Fainshtein 04 Apr '07

04 Apr '07

Hi Bogdan, Please check the ngrep output. I put my comments along with the trace: 1. ****** The 203(a)172.17.4.22 calls 3525(a)172.17.4.22 U 2007/03/18 12:54:09.758887 172.17.2.11:5060 -> 172.17.4.22:5060 INVITE sip:3525@172.17.4.22:5060 SIP/2.0..Via: SIP/2.0/UDP 172.17.2.11:5060 ;branch=z9hG4bK3796032784-846..Max-Forwards: 70..Allow: INVITE,OPTIONS,CANC EL,ACK,BYE,PRACK,INFO,REFER,NOTIFY..Supported: replaces..User-Agent: Claro BS3202 A454..From: <sip:203@172.17.4.22>;tag=hssUA_3795992784-846..To: <sip :3525@172.17.4.22:5060>..Call-ID: 3795992784-846..CSeq: 2 INVITE..Contact: <sip:203@172.17.2.11:5060>..Content-Type: application/sdp..Proxy-Authorizat ion: Digest username="613",realm="172.17.4.22",nonce="45fd6fdd9e385352f9c63 342cc574c454939f3ca",uri="sip:3525@172.17.4.22:5060",response="7156ea61b 864 a4ab937d17f42c7cd45a",algorithm=md5..Content-Length: 237....v=0..o=Claro 0 1 IN IP4 172.17.2.11..s=Claro..c=IN IP4 172.17.2.11..t=0 0..m=audio 30006 R TP/AVP 0 101 120..a=rtpmap:0 PCMU/8000..a=rtpmap:101 TELEPHONE-EVENT/8000.. a=fmtp:101 0-16..a=rtpmap:120 BSRTCP/8000..a=fmtp:120 ver2..a=sendrecv.. U 2007/03/18 12:54:09.766562 172.17.4.22:5060 -> 172.17.2.11:5060 SIP/2.0 100 trying -- your call is important to us..Via: SIP/2.0/UDP 172.17 .2.11:5060;branch=z9hG4bK3796032784-846..From: <sip:203@172.17.4.22>;tag=hs sUA_3795992784-846..To: <sip:3525@172.17.4.22:5060>..Call-ID: 3795992784-84 6..CSeq: 2 INVITE..Server: ClaroSIS (Openser 1.1.1 (i386/linux))..Content-L ength: 0..Warning: 392 172.17.4.22:5060 "Noisy feedback tells: pid=4003 re q_src_ip=172.17.2.11 req_src_port=5060 in_uri=sip:3525@172.17.4.22:5060 out _uri=sip:3525@172.17.2.14;user=phone via_cnt==1".... U 2007/03/18 12:54:09.766871 172.17.4.22:5060 -> 172.17.2.14:5060 INVITE sip:3525@172.17.2.14;user=phone SIP/2.0..Record-Route: <sip:172.17.4 .22;lr=on;ftag=hssUA_3795992784-846;did=55f.4491d5b2>..Via: SIP/2.0/UDP 172 .17.4.22;branch=z9hG4bKbd8b.80bd0bc3.0..Via: SIP/2.0/UDP 172.17.2.11:5060;b ranch=z9hG4bK3796032784-846..Max-Forwards: 69..Allow: INVITE,OPTIONS,CANCEL ,ACK,BYE,PRACK,INFO,REFER,NOTIFY..Supported: replaces..User-Agent: Claro BS 3202 A454..From: <sip:203@172.17.4.22>;tag=hssUA_3795992784-846..To: <sip:3 525@172.17.4.22:5060>..Call-ID: 3795992784-846..CSeq: 2 INVITE..Contact: <s ip:203@172.17.2.11:5060>..Content-Type: application/sdp..Content-Length: 23 7....v=0..o=Claro 0 1 IN IP4 172.17.2.11..s=Claro..c=IN IP4 172.17.2.11..t= 0 0..m=audio 30006 RTP/AVP 0 101 120..a=rtpmap:0 PCMU/8000..a=rtpmap:101 TE LEPHONE-EVENT/8000..a=fmtp:101 0-16..a=rtpmap:120 BSRTCP/8000..a=fmtp:120 v er2..a=sendrecv.. U 2007/03/18 12:54:09.772591 172.17.2.14:5060 -> 172.17.4.22:5060 SIP/2.0 100 Trying..Via: SIP/2.0/UDP 172.17.4.22;branch=z9hG4bKbd8b.80bd0bc 3.0..Via: SIP/2.0/UDP 172.17.2.11:5060;branch=z9hG4bK3796032784-846..From: <sip:203@172.17.4.22>;tag=hssUA_3795992784-846..To: <sip:3525@172.17.4.22:5 060>..Call-ID: 3795992784-846..CSeq: 2 INVITE..User-Agent: Grandstream BT11 0 1.0.8.16..Content-Length: 0.... U 2007/03/18 12:54:09.775043 172.17.2.14:5060 -> 172.17.4.22:5060 SIP/2.0 180 Ringing..Via: SIP/2.0/UDP 172.17.4.22;branch=z9hG4bKbd8b.80bd0b c3.0..Via: SIP/2.0/UDP 172.17.2.11:5060;branch=z9hG4bK3796032784-846..Recor d-Route: <sip:172.17.4.22;lr=on;ftag=hssUA_3795992784-846;did=55f.4491d5b2> ..From: <sip:203@172.17.4.22>;tag=hssUA_3795992784-846..To: <sip:3525@172.1 7.4.22:5060>;tag=61645575ae245b55..Call-ID: 3795992784-846..CSeq: 2 INVITE. .User-Agent: Grandstream BT110 1.0.8.16..Content-Length: 0.... U 2007/03/18 12:54:09.777250 172.17.4.22:5060 -> 172.17.2.11:5060 SIP/2.0 180 Ringing..Via: SIP/2.0/UDP 172.17.2.11:5060;branch=z9hG4bK379603 2784-846..Record-Route: <sip:172.17.4.22;lr=on;ftag=hssUA_3795992784-846;di d=55f.4491d5b2>..From: <sip:203@172.17.4.22>;tag=hssUA_3795992784-846..To: <sip:3525@172.17.4.22:5060>;tag=61645575ae245b55..Call-ID: 3795992784-846.. CSeq: 2 INVITE..User-Agent: Grandstream BT110 1.0.8.16..Content-Length: 0.. .. U 2007/03/18 12:54:13.673700 172.17.2.14:5060 -> 172.17.4.22:5060 SIP/2.0 200 OK..Via: SIP/2.0/UDP 172.17.4.22;branch=z9hG4bKbd8b.80bd0bc3.0. .Via: SIP/2.0/UDP 172.17.2.11:5060;branch=z9hG4bK3796032784-846..Record-Rou te: <sip:172.17.4.22;lr=on;ftag=hssUA_3795992784-846;did=55f.4491d5b2>..Fro m: <sip:203@172.17.4.22>;tag=hssUA_3795992784-846..To: <sip:3525@172.17.4.2 2:5060>;tag=61645575ae245b55..Call-ID: 3795992784-846..CSeq: 2 INVITE..User -Agent: Grandstream BT110 1.0.8.16..Contact: <sip:3525@172.17.2.14;user=pho ne>..Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE..Cont ent-Type: application/sdp..Supported: replaces..Content-Length: 153....v=0. .o=3525 8000 8000 IN IP4 172.17.2.14..s=SIP Call..c=IN IP4 172.17.2.14..t=0 0..m=audio 5004 RTP/AVP 0..a=sendrecv..a=rtpmap:0 PCMU/8000..a=ptime:20.. U 2007/03/18 12:54:13.676298 172.17.4.22:5060 -> 172.17.2.11:5060 SIP/2.0 200 OK..Via: SIP/2.0/UDP 172.17.2.11:5060;branch=z9hG4bK3796032784- 846..Record-Route: <sip:172.17.4.22;lr=on;ftag=hssUA_3795992784-846;did=55f .4491d5b2>..From: <sip:203@172.17.4.22>;tag=hssUA_3795992784-846..To: <sip: 3525@172.17.4.22:5060>;tag=61645575ae245b55..Call-ID: 3795992784-846..CSeq: 2 INVITE..User-Agent: Grandstream BT110 1.0.8.16..Contact: <sip:3525@172.1 7.2.14:5060;user=phone>..Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS, INFO,SUBSCRIBE..Content-Type: application/sdp..Supported: replaces..Content -Length: 153....v=0..o=3525 8000 8000 IN IP4 172.17.2.14..s=SIP Call..c=IN IP4 172.17.2.14..t=0 0..m=audio 5004 RTP/AVP 0..a=sendrecv..a=rtpmap:0 PCMU /8000..a=ptime:20.. U 2007/03/18 12:54:13.721732 172.17.2.11:5060 -> 172.17.4.22:5060 ACK sip:3525@172.17.2.14:5060;user=phone SIP/2.0..Via: SIP/2.0/UDP 172.17.2 .11:5060;branch=z9hG4bK3799992784-846..Route: <sip:172.17.4.22;lr=on;ftag=h ssUA_3795992784-846;did=55f.4491d5b2>..Max-Forwards: 70..Proxy-Authorizatio n: Digest username="613",realm="172.17.4.22",nonce="45fd6fdd9e385352f9c6334 2cc574c454939f3ca",uri="sip:3525@172.17.4.22:5060",response="7156ea61b86 4a4 ab937d17f42c7cd45a",algorithm=md5..User-Agent: Claro BS3202 A454..From: <si p:203@172.17.4.22>;tag=hssUA_3795992784-846..To: <sip:3525@172.17.4.22:5060 >;tag=61645575ae245b55..Call-ID: 3795992784-846..CSeq: 2 ACK..Contact: <sip :203@172.17.2.11:5060>..Content-Length: 0.... U 2007/03/18 12:54:13.724056 172.17.4.22:5060 -> 172.17.2.14:5060 ACK sip:3525@172.17.2.14:5060;user=phone SIP/2.0..Record-Route: <sip:172.17 .4.22;lr=on;ftag=hssUA_3795992784-846>..Via: SIP/2.0/UDP 172.17.4.22;branch =z9hG4bKbd8b.80bd0bc3.2..Via: SIP/2.0/UDP 172.17.2.11:5060;branch=z9hG4bK37 99992784-846..Max-Forwards: 69..Proxy-Authorization: Digest username="613", realm="172.17.4.22",nonce="45fd6fdd9e385352f9c63342cc574c454939f3ca",uri ="s ip:3525@172.17.4.22:5060",response="7156ea61b864a4ab937d17f42c7cd45a",al gor ithm=md5..User-Agent: Claro BS3202 A454..From: <sip:203@172.17.4.22>;tag=hs sUA_3795992784-846..To: <sip:3525@172.17.4.22:5060>;tag=61645575ae245b55..C all-ID: 3795992784-846..CSeq: 2 ACK..Contact: <sip:203@172.17.2.11:5060>..C ontent-Length: 0.... 2. ****** The call is established. The did=55f.4491d5b2. Now 3525(a)172.17.4.22 initiates call transfer. It sends re-INVITE in order to mute the call partner. The header filed Route contains did=55f.4491d5b2. U 2007/03/18 12:54:16.394546 172.17.2.14:5060 -> 172.17.4.22:5060 INVITE sip:203@172.17.2.11:5060 SIP/2.0..Via: SIP/2.0/UDP 172.17.2.14;branc h=z9hG4bKb9469def476f37f2..Route: <sip:172.17.4.22;lr=on;ftag=hssUA_3795992 784-846;did=55f.4491d5b2>..From: <sip:3525@172.17.4.22:5060>;tag=61645575ae 245b55..To: <sip:203@172.17.4.22>;tag=hssUA_3795992784-846..Contact: <sip:3 525(a)172.17.2.14;user=phone>..Supported: replaces..Call-ID: 3795992784-846.. CSeq: 321 INVITE..User-Agent: Grandstream BT110 1.0.8.16..Max-Forwards: 70. .Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE..Content- Type: application/sdp..Content-Length: 320....v=0..o=3525 8000 8001 IN IP4 172.17.2.14..s=SIP Call..c=IN IP4 0.0.0.0..t=0 0..m=audio 5004 RTP/AVP 0 8 18 4 99 2 9..a=sendonly..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpm ap:18 G729/8000..a=rtpmap:4 G723/8000..a=rtpmap:99 iLBC/8000..a=fmtp:99 mod e=20..a=rtpmap:2 G726-32/8000..a=rtpmap:9 G722/16000..a=ptime:20.. U 2007/03/18 12:54:16.396983 172.17.4.22:5060 -> 172.17.2.14:5060 SIP/2.0 100 trying -- your call is important to us..Via: SIP/2.0/UDP 172.17 .2.14;branch=z9hG4bKb9469def476f37f2..From: <sip:3525@172.17.4.22:5060>;tag =61645575ae245b55..To: <sip:203@172.17.4.22>;tag=hssUA_3795992784-846..Call -ID: 3795992784-846..CSeq: 321 INVITE..Server: ClaroSIS (Openser 1.1.1 (i38 6/linux))..Content-Length: 0..Warning: 392 172.17.4.22:5060 "Noisy feedback tells: pid=3997 req_src_ip=172.17.2.14 req_src_port=5060 in_uri=sip:203@1 72.17.2.11:5060 out_uri=sip:203@172.17.2.11:5060 via_cnt==1".... 3. ****** OpenSer sends the re-INVITE to the transferee. Please note, that "did" doesn't appear in the Record-Route. As result of that, BYE for this call will no have "did" parameter and the dialog will appear as not closed. U 2007/03/18 12:54:16.397307 172.17.4.22:5060 -> 172.17.2.11:5060 INVITE sip:203@172.17.2.11:5060 SIP/2.0..Record-Route: <sip:172.17.4.22;lr= on;ftag=61645575ae245b55>..Via: SIP/2.0/UDP 172.17.4.22;branch=z9hG4bK4751. 82bc6f96.0..Via: SIP/2.0/UDP 172.17.2.14;branch=z9hG4bKb9469def476f37f2..Fr om: <sip:3525@172.17.4.22:5060>;tag=61645575ae245b55..To: <sip:203@172.17.4 .22>;tag=hssUA_3795992784-846..Contact: <sip:3525@172.17.2.14;user=phone>.. Supported: replaces..Call-ID: 3795992784-846..CSeq: 321 INVITE..User-Agent: Grandstream BT110 1.0.8.16..Max-Forwards: 69..Allow: INVITE,ACK,CANCEL,BYE ,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE..Content-Type: application/sdp..Conten t-Length: 320....v=0..o=3525 8000 8001 IN IP4 172.17.2.14..s=SIP Call..c=IN IP4 0.0.0.0..t=0 0..m=audio 5004 RTP/AVP 0 8 18 4 99 2 9..a=sendonly..a=rt pmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:18 G729/8000..a=rtpmap:4 G 723/8000..a=rtpmap:99 iLBC/8000..a=fmtp:99 mode=20..a=rtpmap:2 G726-32/8000 ..a=rtpmap:9 G722/16000..a=ptime:20.. U 2007/03/18 12:54:16.435210 172.17.2.11:5060 -> 172.17.4.22:5060 SIP/2.0 200 OK..Via: SIP/2.0/UDP 172.17.4.22;branch=z9hG4bK4751.82bc6f96.0, SIP/2.0/UDP 172.17.2.14;branch=z9hG4bKb9469def476f37f2..Record-Route: <sip: 172.17.4.22;lr=on;ftag=61645575ae245b55>..Server: Claro BS3202 A454..From: <sip:3525@172.17.4.22:5060>;tag=61645575ae245b55..To: <sip:203@172.17.4.22> ;tag=hssUA_3795992784-846..Call-ID: 3795992784-846..CSeq: 321 INVITE..Conta ct: <sip:203@172.17.2.11:5060>..Allow: INVITE,OPTIONS,CANCEL,ACK,BYE,PRACK, INFO,REFER,NOTIFY..Content-Type: application/sdp..Content-Length: 167....v= 0..o=Claro 1174230681570 1174230681 IN IP4 172.17.2.11..s=Claro..c=IN IP4 1 72.17.2.11..t=0 0..m=audio 30006 RTP/AVP 0..a=rtpmap:0 PCMU/8000..a=ptime:2 0..a=recvonly.. U 2007/03/18 12:54:16.436772 172.17.4.22:5060 -> 172.17.2.14:5060 SIP/2.0 200 OK..Via: SIP/2.0/UDP 172.17.2.14;branch=z9hG4bKb9469def476f37f2 ..Record-Route: <sip:172.17.4.22;lr=on;ftag=61645575ae245b55>..Server: Clar o BS3202 A454..From: <sip:3525@172.17.4.22:5060>;tag=61645575ae245b55..To: <sip:203@172.17.4.22>;tag=hssUA_3795992784-846..Call-ID: 3795992784-846..CS eq: 321 INVITE..Contact: <sip:203@172.17.2.11:5060>..Allow: INVITE,OPTIONS, CANCEL,ACK,BYE,PRACK,INFO,REFER,NOTIFY..Content-Type: application/sdp..Cont ent-Length: 167....v=0..o=Claro 1174230681570 1174230681 IN IP4 172.17.2.11 ..s=Claro..c=IN IP4 172.17.2.11..t=0 0..m=audio 30006 RTP/AVP 0..a=rtpmap:0 PCMU/8000..a=ptime:20..a=recvonly.. U 2007/03/18 12:54:16.443328 172.17.2.14:5060 -> 172.17.4.22:5060 ACK sip:203@172.17.2.11:5060 SIP/2.0..Via: SIP/2.0/UDP 172.17.2.14;branch=z 9hG4bK26b04409b72e06f9..Route: <sip:172.17.4.22;lr=on;ftag=61645575ae245b55 >..From: <sip:3525@172.17.4.22:5060>;tag=61645575ae245b55..To: <sip:203@172 .17.4.22>;tag=hssUA_3795992784-846..Contact: <sip:3525@172.17.2.14;user=pho ne>..Call-ID: 3795992784-846..CSeq: 321 ACK..User-Agent: Grandstream BT110 1.0.8.16..Max-Forwards: 70..Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIO NS,INFO,SUBSCRIBE..Content-Length: 0.... U 2007/03/18 12:54:16.445463 172.17.4.22:5060 -> 172.17.2.11:5060 ACK sip:203@172.17.2.11:5060 SIP/2.0..Record-Route: <sip:172.17.4.22;lr=on; ftag=61645575ae245b55>..Via: SIP/2.0/UDP 172.17.4.22;branch=z9hG4bK4751.82b c6f96.2..Via: SIP/2.0/UDP 172.17.2.14;branch=z9hG4bK26b04409b72e06f9..From: <sip:3525@172.17.4.22:5060>;tag=61645575ae245b55..To: <sip:203@172.17.4.22 >;tag=hssUA_3795992784-846..Contact: <sip:3525@172.17.2.14;user=phone>..Cal l-ID: 3795992784-846..CSeq: 321 ACK..User-Agent: Grandstream BT110 1.0.8.16 ..Max-Forwards: 69..Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO, SUBSCRIBE..Content-Length: 0.... U 2007/03/18 12:54:20.272078 172.17.2.14:5060 -> 172.17.4.22:5060 REFER sip:203@172.17.2.11:5060 SIP/2.0..Via: SIP/2.0/UDP 172.17.2.14;branch =z9hG4bK9e02f3ad995f8245..Route: <sip:172.17.4.22;lr=on;ftag=61645575ae245b 55>..From: <sip:3525@172.17.4.22:5060>;tag=61645575ae245b55..To: <sip:203@1 72.17.4.22>;tag=hssUA_3795992784-846..Contact: <sip:3525@172.17.2.14;user=p hone>..Supported: replaces..Refer-To: <sip:5524@172.17.4.22;user=phone>..Re ferred-By: <sip:3525@172.17.4.22;user=phone>..Call-ID: 3795992784-846..CSeq : 322 REFER..User-Agent: Grandstream BT110 1.0.8.16..Max-Forwards: 70..Allo w: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE..Content-Lengt h: 0.... U 2007/03/18 12:54:20.275997 172.17.4.22:5060 -> 172.17.2.11:5060 REFER sip:203@172.17.2.11:5060 SIP/2.0..Record-Route: <sip:172.17.4.22;lr=o n;ftag=61645575ae245b55>..Via: SIP/2.0/UDP 172.17.4.22;branch=z9hG4bK1751.e 223fee7.0..Via: SIP/2.0/UDP 172.17.2.14;branch=z9hG4bK9e02f3ad995f8245..Fro m: <sip:3525@172.17.4.22:5060>;tag=61645575ae245b55..To: <sip:203@172.17.4. 22>;tag=hssUA_3795992784-846..Contact: <sip:3525@172.17.2.14;user=phone>..S upported: replaces..Refer-To: <sip:5524@172.17.4.22;user=phone>..Referred-B y: <sip:3525@172.17.4.22;user=phone>..Call-ID: 3795992784-846..CSeq: 322 RE FER..User-Agent: Grandstream BT110 1.0.8.16..Max-Forwards: 69..Allow: INVIT E,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE..Content-Length: 0.... U 2007/03/18 12:54:20.323290 172.17.2.11:5060 -> 172.17.4.22:5060 INVITE sip:5524@172.17.4.22;user=phone SIP/2.0..Via: SIP/2.0/UDP 172.17.2.1 1:5060;branch=z9hG4bK3806597784-846..Max-Forwards: 70..Allow: INVITE,OPTION S,CANCEL,ACK,BYE,PRACK,INFO,REFER,NOTIFY..Supported: replaces..From: <sip:2 03(a)172.17.4.22>;tag=hssUA_3806597784-846..To: <sip:5524@172.17.4.22;user=ph one>..Call-ID: 3806597784-846..CSeq: 1 INVITE..Contact: <sip:203@172.17.2.1 1:5060>..Referred-By: <sip:3525@172.17.4.22;user=phone>..Content-Type: appl ication/sdp..Content-Length: 237....v=0..o=Claro 0 1 IN IP4 172.17.2.11..s= Claro..c=IN IP4 172.17.2.11..t=0 0..m=audio 30006 RTP/AVP 0 101 120..a=rtpm ap:0 PCMU/8000..a=rtpmap:101 TELEPHONE-EVENT/8000..a=fmtp:101 0-16..a=rtpma p:120 BSRTCP/8000..a=fmtp:120 ver2..a=sendrecv.. U 2007/03/18 12:54:20.324935 172.17.4.22:5060 -> 172.17.2.11:5060 SIP/2.0 407 Proxy Authentication Required..Via: SIP/2.0/UDP 172.17.2.11:506 0;branch=z9hG4bK3806597784-846..From: <sip:203@172.17.4.22>;tag=hssUA_38065 97784-846..To: <sip:5524@172.17.4.22;user=phone>;tag=329cfeaa6ded039da25ff8 cbb8668bd2.dc60..Call-ID: 3806597784-846..CSeq: 1 INVITE..Proxy-Authenticat e: Digest realm="172.17.4.22", nonce="45fd6fe80721e4ce9c9b2eef4c93a66ef88b9 f2c"..Server: ClaroSIS (Openser 1.1.1 (i386/linux))..Content-Length: 0..War ning: 392 172.17.4.22:5060 "Noisy feedback tells: pid=4001 req_src_ip=172. 17.2.11 req_src_port=5060 in_uri=sip:5524@172.17.4.22;user=phone out_uri=si p:5524@172.17.4.22;user=phone via_cnt==1".... U 2007/03/18 12:54:20.328647 172.17.2.11:5060 -> 172.17.4.22:5060 SIP/2.0 202 Accepted..Via: SIP/2.0/UDP 172.17.4.22;branch=z9hG4bK1751.e223f ee7.0,SIP/2.0/UDP 172.17.2.14;branch=z9hG4bK9e02f3ad995f8245..Record-Route: <sip:172.17.4.22;lr=on;ftag=61645575ae245b55>..From: <sip:3525@172.17.4.22 :5060>;tag=61645575ae245b55..To: <sip:203@172.17.4.22>;tag=hssUA_3795992784 -846..Call-ID: 3795992784-846..CSeq: 322 REFER..Contact: <sip:203@172.17.2. 11:5060>..Content-Length: 0.... U 2007/03/18 12:54:20.330099 172.17.4.22:5060 -> 172.17.2.14:5060 SIP/2.0 202 Accepted..Via: SIP/2.0/UDP 172.17.2.14;branch=z9hG4bK9e02f3ad99 5f8245..Record-Route: <sip:172.17.4.22;lr=on;ftag=61645575ae245b55>..From: <sip:3525@172.17.4.22:5060>;tag=61645575ae245b55..To: <sip:203@172.17.4.22> ;tag=hssUA_3795992784-846..Call-ID: 3795992784-846..CSeq: 322 REFER..Contac t: <sip:203@172.17.2.11:5060>..Content-Length: 0.... U 2007/03/18 12:54:20.351529 172.17.2.11:5060 -> 172.17.4.22:5060 ACK sip:5524@172.17.4.22;user=phone SIP/2.0..Via: SIP/2.0/UDP 172.17.2.11:5 060;branch=z9hG4bK3806597784-846..Max-Forwards: 70..User-Agent: Claro BS320 2 A454..From: <sip:203@172.17.4.22>;tag=hssUA_3806597784-846..To: <sip:5524 @172.17.4.22;user=phone>;tag=329cfeaa6ded039da25ff8cbb8668bd2.dc60..Call -ID : 3806597784-846..CSeq: 1 ACK..Contact: <sip:203@172.17.2.11:5060>..Content -Length: 0.... U 2007/03/18 12:54:20.364969 172.17.2.11:5060 -> 172.17.4.22:5060 INVITE sip:5524@172.17.4.22;user=phone SIP/2.0..Via: SIP/2.0/UDP 172.17.2.1 1:5060;branch=z9hG4bK3806642784-846..Max-Forwards: 70..Allow: INVITE,OPTION S,CANCEL,ACK,BYE,PRACK,INFO,REFER,NOTIFY..Supported: replaces..User-Agent: Claro BS3202 A454..From: <sip:203@172.17.4.22>;tag=hssUA_3806597784-846..To : <sip:5524@172.17.4.22;user=phone>..Call-ID: 3806597784-846..CSeq: 2 INVIT E..Contact: <sip:203@172.17.2.11:5060>..Content-Type: application/sdp..Prox y-Authorization: Digest username="613",realm="172.17.4.22",nonce="45fd6fe80 721e4ce9c9b2eef4c93a66ef88b9f2c",uri="sip:5524@172.17.4.22",response="3f b20 f7d6e67668e07b862b99412162d",algorithm=md5..Content-Length: 237....v=0..o=C laro 0 1 IN IP4 172.17.2.11..s=Claro..c=IN IP4 172.17.2.11..t=0 0..m=audio 30006 RTP/AVP 0 101 120..a=rtpmap:0 PCMU/8000..a=rtpmap:101 TELEPHONE-EVENT /8000..a=fmtp:101 0-16..a=rtpmap:120 BSRTCP/8000..a=fmtp:120 ver2..a=sendre cv.. U 2007/03/18 12:54:20.372610 172.17.4.22:5060 -> 172.17.2.11:5060 SIP/2.0 100 trying -- your call is important to us..Via: SIP/2.0/UDP 172.17 .2.11:5060;branch=z9hG4bK3806642784-846..From: <sip:203@172.17.4.22>;tag=hs sUA_3806597784-846..To: <sip:5524@172.17.4.22;user=phone>..Call-ID: 3806597 784-846..CSeq: 2 INVITE..Server: ClaroSIS (Openser 1.1.1 (i386/linux))..Con tent-Length: 0..Warning: 392 172.17.4.22:5060 "Noisy feedback tells: pid=4 003 req_src_ip=172.17.2.11 req_src_port=5060 in_uri=sip:5524@172.17.4.22;us er=phone out_uri=sip:5524@172.17.2.168:5061 via_cnt==1".... U 2007/03/18 12:54:20.372833 172.17.4.22:5060 -> 172.17.2.168:5061 INVITE sip:5524@172.17.2.168:5061 SIP/2.0..Record-Route: <sip:172.17.4.22;l r=on;ftag=hssUA_3806597784-846;did=0e3.7c5bd92>..Via: SIP/2.0/UDP 172.17.4. 22;branch=z9hG4bK95c6.337d9f56.0..Via: SIP/2.0/UDP 172.17.2.11:5060;branch= z9hG4bK3806642784-846..Max-Forwards: 69..Allow: INVITE,OPTIONS,CANCEL,ACK,B YE,PRACK,INFO,REFER,NOTIFY..Supported: replaces..User-Agent: Claro BS3202 A 454..From: <sip:203@172.17.4.22>;tag=hssUA_3806597784-846..To: <sip:5524@17 2.17.4.22;user=phone>..Call-ID: 3806597784-846..CSeq: 2 INVITE..Contact: <s ip:203@172.17.2.11:5060>..Content-Type: application/sdp..Content-Length: 23 7....v=0..o=Claro 0 1 IN IP4 172.17.2.11..s=Claro..c=IN IP4 172.17.2.11..t= 0 0..m=audio 30006 RTP/AVP 0 101 120..a=rtpmap:0 PCMU/8000..a=rtpmap:101 TE LEPHONE-EVENT/8000..a=fmtp:101 0-16..a=rtpmap:120 BSRTCP/8000..a=fmtp:120 v er2..a=sendrecv.. U 2007/03/18 12:54:20.385872 172.17.2.168:5061 -> 172.17.4.22:5060 SIP/2.0 100 Trying..To: <sip:5524@172.17.4.22;user=phone>..From: <sip:203@1 72.17.4.22>;tag=hssUA_3806597784-846..Call-ID: 3806597784-846..CSeq: 2 INVI TE..Via: SIP/2.0/UDP 172.17.4.22;branch=z9hG4bK95c6.337d9f56.0..Via: SIP/2. 0/UDP 172.17.2.11:5060;branch=z9hG4bK3806642784-846..Record-Route: <sip:172 .17.4.22;lr=on;ftag=hssUA_3806597784-846;did=0e3.7c5bd92>..Server: Linksys/ PAP2-3.1.3(LS)..Content-Length: 0.... U 2007/03/18 12:54:20.393629 172.17.2.11:5060 -> 172.17.4.22:5060 NOTIFY sip:3525@172.17.2.14;user=phone SIP/2.0..Via: SIP/2.0/UDP 172.17.2.1 1:5060;branch=z9hG4bK3806672784-846..Route: <sip:172.17.4.22;lr=on;ftag=hss UA_3795992784-846;did=55f.4491d5b2>..Max-Forwards: 70..Proxy-Authorization: Digest username="613",realm="172.17.4.22",nonce="45fd6fdd9e385352f9c63342c c574c454939f3ca",uri="sip:3525@172.17.4.22:5060",response="7156ea61b864a 4ab 937d17f42c7cd45a",algorithm=md5..Allow: INVITE,OPTIONS,CANCEL,ACK,BYE,PRACK ,INFO,REFER,NOTIFY..Supported: replaces..From: <sip:203@172.17.4.22>;tag=hs sUA_3795992784-846..To: <sip:3525@172.17.4.22:5060>;tag=61645575ae245b55..C all-ID: 3795992784-846..CSeq: 3 NOTIFY..Contact: <sip:203@172.17.2.11:5060> ..Event: refer..Subscription-State: active;expires=60..Content-Type: messag e/sipfrag..Content-Length: 530....SIP/2.0 100 trying -- your call is import ant to us..Via: SIP/2.0/UDP 172.17.2.11:5060;received=172.17.4.22;branch=z9 hG4bK3806642784-846..From: <sip:203@172.17.4.22>;tag=hssUA_3806597784-846.. To: <sip:5524@172.17.4.22;user=phone>..Call-ID: 3806597784-846..CSeq: 2 INV ITE..Server: ClaroSIS (Openser 1.1.1 (i386/linux))..Content-Length: 0..Warn ing: 392 172.17.4.22:5060 "Noisy feedback tells: pid=4003 req_src_ip=172.1 7.2.11 req_src_port=5060 in_uri=sip:5524@172.17.4.22;user=phone out_uri=sip :5524@172.17.2.168:5061 via_cnt==1".... U 2007/03/18 12:54:20.396980 172.17.4.22:5060 -> 172.17.2.14:5060 NOTIFY sip:3525@172.17.2.14;user=phone SIP/2.0..Record-Route: <sip:172.17.4 .22;lr=on;ftag=hssUA_3795992784-846>..Via: SIP/2.0/UDP 172.17.4.22;branch=z 9hG4bKcd8b.81aaa3f3.0..Via: SIP/2.0/UDP 172.17.2.11:5060;branch=z9hG4bK3806 672784-846..Max-Forwards: 69..Proxy-Authorization: Digest username="613",re alm="172.17.4.22",nonce="45fd6fdd9e385352f9c63342cc574c454939f3ca",uri=" sip :3525@172.17.4.22:5060",response="7156ea61b864a4ab937d17f42c7cd45a",algo rit hm=md5..Allow: INVITE,OPTIONS,CANCEL,ACK,BYE,PRACK,INFO,REFER,NOTIFY..Suppo rted: replaces..From: <sip:203@172.17.4.22>;tag=hssUA_3795992784-846..To: < sip:3525@172.17.4.22:5060>;tag=61645575ae245b55..Call-ID: 3795992784-846..C Seq: 3 NOTIFY..Contact: <sip:203@172.17.2.11:5060>..Event: refer..Subscript ion-State: active;expires=60..Content-Type: message/sipfrag..Content-Length : 530....SIP/2.0 100 trying -- your call is important to us..Via: SIP/2.0/U DP 172.17.2.11:5060;received=172.17.4.22;branch=z9hG4bK3806642784-846..From : <sip:203@172.17.4.22>;tag=hssUA_3806597784-846..To: <sip:5524@172.17.4.22 ;user=phone>..Call-ID: 3806597784-846..CSeq: 2 INVITE..Server: ClaroSIS (Op enser 1.1.1 (i386/linux))..Content-Length: 0..Warning: 392 172.17.4.22:5060 "Noisy feedback tells: pid=4003 req_src_ip=172.17.2.11 req_src_port=5060 in_uri=sip:5524@172.17.4.22;user=phone out_uri=sip:5524@172.17.2.168:5061 v ia_cnt==1".... U 2007/03/18 12:54:20.401630 172.17.2.168:5061 -> 172.17.4.22:5060 SIP/2.0 180 Ringing..To: <sip:5524@172.17.4.22;user=phone>;tag=8cb5cce9fbff 0a22i1..From: <sip:203@172.17.4.22>;tag=hssUA_3806597784-846..Call-ID: 3806 597784-846..CSeq: 2 INVITE..Via: SIP/2.0/UDP 172.17.4.22;branch=z9hG4bK95c6 .337d9f56.0..Via: SIP/2.0/UDP 172.17.2.11:5060;branch=z9hG4bK3806642784-846 ..Record-Route: <sip:172.17.4.22;lr=on;ftag=hssUA_3806597784-846;did=0e3.7c 5bd92>..Server: Linksys/PAP2-3.1.3(LS)..Content-Length: 0.... U 2007/03/18 12:54:20.403183 172.17.4.22:5060 -> 172.17.2.11:5060 SIP/2.0 180 Ringing..To: <sip:5524@172.17.4.22;user=phone>;tag=8cb5cce9fbff 0a22i1..From: <sip:203@172.17.4.22>;tag=hssUA_3806597784-846..Call-ID: 3806 597784-846..CSeq: 2 INVITE..Via: SIP/2.0/UDP 172.17.2.11:5060;branch=z9hG4b K3806642784-846..Record-Route: <sip:172.17.4.22;lr=on;ftag=hssUA_3806597784 -846;did=0e3.7c5bd92>..Server: Linksys/PAP2-3.1.3(LS)..Content-Length: 0... . U 2007/03/18 12:54:20.403878 172.17.2.14:5060 -> 172.17.4.22:5060 SIP/2.0 200 OK..Via: SIP/2.0/UDP 172.17.4.22;branch=z9hG4bKcd8b.81aaa3f3.0. .Via: SIP/2.0/UDP 172.17.2.11:5060;branch=z9hG4bK3806672784-846..Record-Rou te: <sip:172.17.4.22;lr=on;ftag=hssUA_3795992784-846>..From: <sip:203@172.1 7.4.22>;tag=hssUA_3795992784-846..To: <sip:3525@172.17.4.22:5060>;tag=61645 575ae245b55..Call-ID: 3795992784-846..CSeq: 3 NOTIFY..User-Agent: Grandstre am BT110 1.0.8.16..Contact: <sip:3525@172.17.2.14;user=phone>..Allow: INVIT E,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE..Supported: replaces.. Content-Length: 0.... U 2007/03/18 12:54:20.407617 172.17.4.22:5060 -> 172.17.2.11:5060 SIP/2.0 200 OK..Via: SIP/2.0/UDP 172.17.2.11:5060;branch=z9hG4bK3806672784- 846..Record-Route: <sip:172.17.4.22;lr=on;ftag=hssUA_3795992784-846>..From: <sip:203@172.17.4.22>;tag=hssUA_3795992784-846..To: <sip:3525@172.17.4.22: 5060>;tag=61645575ae245b55..Call-ID: 3795992784-846..CSeq: 3 NOTIFY..User-A gent: Grandstream BT110 1.0.8.16..Contact: <sip:3525@172.17.2.14:5060;user= phone>..Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE..S upported: replaces..Content-Length: 0.... U 2007/03/18 12:54:20.429109 172.17.2.11:5060 -> 172.17.4.22:5060 NOTIFY sip:3525@172.17.2.14;user=phone SIP/2.0..Via: SIP/2.0/UDP 172.17.2.1 1:5060;branch=z9hG4bK3806702784-846..Route: <sip:172.17.4.22;lr=on;ftag=hss UA_3795992784-846;did=55f.4491d5b2>..Max-Forwards: 70..Proxy-Authorization: Digest username="613",realm="172.17.4.22",nonce="45fd6fdd9e385352f9c63342c c574c454939f3ca",uri="sip:3525@172.17.4.22:5060",response="7156ea61b864a 4ab 937d17f42c7cd45a",algorithm=md5..Allow: INVITE,OPTIONS,CANCEL,ACK,BYE,PRACK ,INFO,REFER,NOTIFY..Supported: replaces..From: <sip:203@172.17.4.22>;tag=hs sUA_3795992784-846..To: <sip:3525@172.17.4.22:5060>;tag=61645575ae245b55..C all-ID: 3795992784-846..CSeq: 4 NOTIFY..Contact: <sip:203@172.17.2.11:5060> ..Event: refer..Subscription-State: active;expires=60..Content-Type: messag e/sipfrag..Content-Length: 397....SIP/2.0 180 Ringing..To: <sip:5524@172.17 .4.22;user=phone>;tag=8cb5cce9fbff0a22i1..From: <sip:203@172.17.4.22>;tag=h ssUA_3806597784-846..Call-ID: 3806597784-846..CSeq: 2 INVITE..Via: SIP/2.0/ UDP 172.17.2.11:5060;received=172.17.4.22;branch=z9hG4bK3806642784-846..Rec ord-Route: <sip:172.17.4.22;lr=on;ftag=hssUA_3806597784-846;did=0e3.7c5bd92 >..Server: Linksys/PAP2-3.1.3(LS)..Content-Length: 0.... U 2007/03/18 12:54:20.431776 172.17.4.22:5060 -> 172.17.2.14:5060 NOTIFY sip:3525@172.17.2.14;user=phone SIP/2.0..Record-Route: <sip:172.17.4 .22;lr=on;ftag=hssUA_3795992784-846>..Via: SIP/2.0/UDP 172.17.4.22;branch=z 9hG4bK9d8b.47c7ce13.0..Via: SIP/2.0/UDP 172.17.2.11:5060;branch=z9hG4bK3806 702784-846..Max-Forwards: 69..Proxy-Authorization: Digest username="613",re alm="172.17.4.22",nonce="45fd6fdd9e385352f9c63342cc574c454939f3ca",uri=" sip :3525@172.17.4.22:5060",response="7156ea61b864a4ab937d17f42c7cd45a",algo rit hm=md5..Allow: INVITE,OPTIONS,CANCEL,ACK,BYE,PRACK,INFO,REFER,NOTIFY..Suppo rted: replaces..From: <sip:203@172.17.4.22>;tag=hssUA_3795992784-846..To: < sip:3525@172.17.4.22:5060>;tag=61645575ae245b55..Call-ID: 3795992784-846..C Seq: 4 NOTIFY..Contact: <sip:203@172.17.2.11:5060>..Event: refer..Subscript ion-State: active;expires=60..Content-Type: message/sipfrag..Content-Length : 397....SIP/2.0 180 Ringing..To: <sip:5524@172.17.4.22;user=phone>;tag=8cb 5cce9fbff0a22i1..From: <sip:203@172.17.4.22>;tag=hssUA_3806597784-846..Call -ID: 3806597784-846..CSeq: 2 INVITE..Via: SIP/2.0/UDP 172.17.2.11:5060;rece ived=172.17.4.22;branch=z9hG4bK3806642784-846..Record-Route: <sip:172.17.4. 22;lr=on;ftag=hssUA_3806597784-846;did=0e3.7c5bd92>..Server: Linksys/PAP2-3 .1.3(LS)..Content-Length: 0.... U 2007/03/18 12:54:20.438291 172.17.2.14:5060 -> 172.17.4.22:5060 SIP/2.0 200 OK..Via: SIP/2.0/UDP 172.17.4.22;branch=z9hG4bK9d8b.47c7ce13.0. .Via: SIP/2.0/UDP 172.17.2.11:5060;branch=z9hG4bK3806702784-846..Record-Rou te: <sip:172.17.4.22;lr=on;ftag=hssUA_3795992784-846>..From: <sip:203@172.1 7.4.22>;tag=hssUA_3795992784-846..To: <sip:3525@172.17.4.22:5060>;tag=61645 575ae245b55..Call-ID: 3795992784-846..CSeq: 4 NOTIFY..User-Agent: Grandstre am BT110 1.0.8.16..Contact: <sip:3525@172.17.2.14;user=phone>..Allow: INVIT E,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE..Supported: replaces.. Content-Length: 0.... U 2007/03/18 12:54:20.439954 172.17.4.22:5060 -> 172.17.2.11:5060 SIP/2.0 200 OK..Via: SIP/2.0/UDP 172.17.2.11:5060;branch=z9hG4bK3806702784- 846..Record-Route: <sip:172.17.4.22;lr=on;ftag=hssUA_3795992784-846>..From: <sip:203@172.17.4.22>;tag=hssUA_3795992784-846..To: <sip:3525@172.17.4.22: 5060>;tag=61645575ae245b55..Call-ID: 3795992784-846..CSeq: 4 NOTIFY..User-A gent: Grandstream BT110 1.0.8.16..Contact: <sip:3525@172.17.2.14:5060;user= phone>..Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE..S upported: replaces..Content-Length: 0.... U 2007/03/18 12:54:23.312128 172.17.2.168:5061 -> 172.17.4.22:5060 SIP/2.0 200 OK..To: <sip:5524@172.17.4.22;user=phone>;tag=8cb5cce9fbff0a22i 1..From: <sip:203@172.17.4.22>;tag=hssUA_3806597784-846..Call-ID: 380659778 4-846..CSeq: 2 INVITE..Via: SIP/2.0/UDP 172.17.4.22;branch=z9hG4bK95c6.337d 9f56.0..Via: SIP/2.0/UDP 172.17.2.11:5060;branch=z9hG4bK3806642784-846..Rec ord-Route: <sip:172.17.4.22;lr=on;ftag=hssUA_3806597784-846;did=0e3.7c5bd92 >..Contact: 5524 <sip:5524@172.17.2.168:5061>..Server: Linksys/PAP2-3.1.3(L S)..Content-Length: 210..Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPT IONS, REFER..Supported: x-sipura..Content-Type: application/sdp....v=0..o=- 23586680 23586680 IN IP4 172.17.2.168..s=-..c=IN IP4 172.17.2.168..t=0 0.. m=audio 16388 RTP/AVP 0 101..a=rtpmap:0 PCMU/8000..a=rtpmap:101 telephone-e vent/8000..a=fmtp:101 0-15..a=ptime:30..a=sendrecv.. U 2007/03/18 12:54:23.313878 172.17.4.22:5060 -> 172.17.2.11:5060 SIP/2.0 200 OK..To: <sip:5524@172.17.4.22;user=phone>;tag=8cb5cce9fbff0a22i 1..From: <sip:203@172.17.4.22>;tag=hssUA_3806597784-846..Call-ID: 380659778 4-846..CSeq: 2 INVITE..Via: SIP/2.0/UDP 172.17.2.11:5060;branch=z9hG4bK3806 642784-846..Record-Route: <sip:172.17.4.22;lr=on;ftag=hssUA_3806597784-846; did=0e3.7c5bd92>..Contact: 5524 <sip:5524@172.17.2.168:5061>..Server: Links ys/PAP2-3.1.3(LS)..Content-Length: 210..Allow: ACK, BYE, CANCEL, INFO, INVI TE, NOTIFY, OPTIONS, REFER..Supported: x-sipura..Content-Type: application/ sdp....v=0..o=- 23586680 23586680 IN IP4 172.17.2.168..s=-..c=IN IP4 172.17 .2.168..t=0 0..m=audio 16388 RTP/AVP 0 101..a=rtpmap:0 PCMU/8000..a=rtpmap: 101 telephone-event/8000..a=fmtp:101 0-15..a=ptime:30..a=sendrecv.. U 2007/03/18 12:54:23.355581 172.17.2.11:5060 -> 172.17.4.22:5060 27646@0:1480 ........NOTIFY sip:3525@172.17.2.14;user=phone SIP/2.0..Via: SIP/2.0/UDP 17 2.17.2.11:5060;branch=z9hG4bK3809632784-846..Route: <sip:172.17.4.22;lr=on; ftag=hssUA_3795992784-846;did=55f.4491d5b2>..Max-Forwards: 70..Proxy-Author ization: Digest username="613",realm="172.17.4.22",nonce="45fd6fdd9e385352f 9c63342cc574c454939f3ca",uri="sip:3525@172.17.4.22:5060",response="7156e a61 b864a4ab937d17f42c7cd45a",algorithm=md5..Allow: INVITE,OPTIONS,CANCEL,ACK,B YE,PRACK,INFO,REFER,NOTIFY..Supported: replaces..From: <sip:203@172.17.4.22 >;tag=hssUA_3795992784-846..To: <sip:3525@172.17.4.22:5060>;tag=61645575ae2 45b55..Call-ID: 3795992784-846..CSeq: 5 NOTIFY..Contact: <sip:203@172.17.2. 11:5060>..Event: refer..Subscription-State: terminated;reason=noresource..C ontent-Type: message/sipfrag..Content-Length: 756....SIP/2.0 200 OK..To: <s ip:5524@172.17.4.22;user=phone>;tag=8cb5cce9fbff0a22i1..From: <sip:203@172. 17.4.22>;tag=hssUA_3806597784-846..Call-ID: 3806597784-846..CSeq: 2 INVITE. .Via: SIP/2.0/UDP 172.17.2.11:5060;received=172.17.4.22;branch=z9hG4bK38066 42784-846..Record-Route: <sip:172.17.4.22;lr=on;ftag=hssUA_3806597784-846;d id=0e3.7c5bd92>..Contact: 5524 <sip:5524@172.17.2.168:5061>..Server: Linksy s/PAP2-3.1.3(LS)..Content-Length: 210..Allow: ACK,BYE,CANCEL,INFO,INVITE,NO TIFY,OPTIONS,REFER..Supported: x-sipura..Content-Type: application/sdp....v =0..o=- 23586680 23586680 IN IP4 172.17.2.168..s=-..c=IN IP4 172.17.2.168.. t=0 0..m=audio 16388 RTP/AVP 0 101..a=rtpmap:0 PCMU/800 U 2007/03/18 12:54:23.361462 172.17.4.22:5060 -> 172.17.2.14:5060 50085@0:1480 .....I..NOTIFY sip:3525@172.17.2.14;user=phone SIP/2.0..Record-Route: <sip: 172.17.4.22;lr=on;ftag=hssUA_3795992784-846>..Via: SIP/2.0/UDP 172.17.4.22; branch=z9hG4bKad8b.016fb321.0..Via: SIP/2.0/UDP 172.17.2.11:5060;branch=z9h G4bK3809632784-846..Max-Forwards: 69..Proxy-Authorization: Digest username= "613",realm="172.17.4.22",nonce="45fd6fdd9e385352f9c63342cc574c454939f3c a", uri="sip:3525@172.17.4.22:5060",response="7156ea61b864a4ab937d17f42c7cd4 5a" ,algorithm=md5..Allow: INVITE,OPTIONS,CANCEL,ACK,BYE,PRACK,INFO,REFER,NOTIF Y..Supported: replaces..From: <sip:203@172.17.4.22>;tag=hssUA_3795992784-84 6..To: <sip:3525@172.17.4.22:5060>;tag=61645575ae245b55..Call-ID: 379599278 4-846..CSeq: 5 NOTIFY..Contact: <sip:203@172.17.2.11:5060>..Event: refer..S ubscription-State: terminated;reason=noresource..Content-Type: message/sipf rag..Content-Length: 756....SIP/2.0 200 OK..To: <sip:5524@172.17.4.22;user= phone>;tag=8cb5cce9fbff0a22i1..From: <sip:203@172.17.4.22>;tag=hssUA_380659 7784-846..Call-ID: 3806597784-846..CSeq: 2 INVITE..Via: SIP/2.0/UDP 172.17. 2.11:5060;received=172.17.4.22;branch=z9hG4bK3806642784-846..Record-Rout e: <sip:172.17.4.22;lr=on;ftag=hssUA_3806597784-846;did=0e3.7c5bd92>..Conta ct: 5524 <sip:5524@172.17.2.168:5061>..Server: Linksys/PAP2-3.1.3(LS)..Content -Length: 210..Allow: ACK,BYE,CANCEL,INFO,INVITE,NOTIFY,OPTIONS,REFER..Suppo rted: x-sipura..Content-Type: application/sdp....v=0..o=- 23586680 23586680 IN IP4 172.17.2.168..s=-..c=IN IP4 172.17.2.168..t=0 0 U 2007/03/18 12:54:23.371944 172.17.2.11:5060 -> 172.17.4.22:5060 ACK sip:5524@172.17.2.168:5061 SIP/2.0..Via: SIP/2.0/UDP 172.17.2.11:5060;b ranch=z9hG4bK3809647784-846..Route: <sip:172.17.4.22;lr=on;ftag=hssUA_38065 97784-846;did=0e3.7c5bd92>..Max-Forwards: 70..Proxy-Authorization: Digest u sername="613",realm="172.17.4.22",nonce="45fd6fe80721e4ce9c9b2eef4c93a66 ef8 8b9f2c",uri="sip:5524@172.17.4.22",response="3fb20f7d6e67668e07b862b9941 216 2d",algorithm=md5..User-Agent: Claro BS3202 A454..From: <sip:203@172.17.4.2 2>;tag=hssUA_3806597784-846..To: <sip:5524@172.17.4.22;user=phone>;tag=8cb5 cce9fbff0a22i1..Call-ID: 3806597784-846..CSeq: 2 ACK..Contact: <sip:203@172 .17.2.11:5060>..Content-Length: 0.... U 2007/03/18 12:54:23.372334 172.17.2.14:5060 -> 172.17.4.22:5060 SIP/2.0 200 OK..Via: SIP/2.0/UDP 172.17.4.22;branch=z9hG4bKad8b.016fb321.0. .Via: SIP/2.0/UDP 172.17.2.11:5060;branch=z9hG4bK3809632784-846..Record-Rou te: <sip:172.17.4.22;lr=on;ftag=hssUA_3795992784-846>..From: <sip:203@172.1 7.4.22>;tag=hssUA_3795992784-846..To: <sip:3525@172.17.4.22:5060>;tag=61645 575ae245b55..Call-ID: 3795992784-846..CSeq: 5 NOTIFY..User-Agent: Grandstre am BT110 1.0.8.16..Contact: <sip:3525@172.17.2.14;user=phone>..Allow: INVIT E,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE..Supported: replaces.. Content-Length: 0.... U 2007/03/18 12:54:23.373917 172.17.4.22:5060 -> 172.17.2.168:5061 ACK sip:5524@172.17.2.168:5061 SIP/2.0..Record-Route: <sip:172.17.4.22;lr=o n;ftag=hssUA_3806597784-846>..Via: SIP/2.0/UDP 172.17.4.22;branch=z9hG4bK95 c6.337d9f56.2..Via: SIP/2.0/UDP 172.17.2.11:5060;branch=z9hG4bK3809647784-8 46..Max-Forwards: 69..Proxy-Authorization: Digest username="613",realm="172 .17.4.22",nonce="45fd6fe80721e4ce9c9b2eef4c93a66ef88b9f2c",uri="sip:5524 @17 2.17.4.22",response="3fb20f7d6e67668e07b862b99412162d",algorithm=md5..Us er- Agent: Claro BS3202 A454..From: <sip:203@172.17.4.22>;tag=hssUA_3806597784- 846..To: <sip:5524@172.17.4.22;user=phone>;tag=8cb5cce9fbff0a22i1..Call-ID: 3806597784-846..CSeq: 2 ACK..Contact: <sip:203@172.17.2.11:5060>..Content- Length: 0.... U 2007/03/18 12:54:23.375179 172.17.4.22:5060 -> 172.17.2.11:5060 SIP/2.0 200 OK..Via: SIP/2.0/UDP 172.17.2.11:5060;branch=z9hG4bK3809632784- 846..Record-Route: <sip:172.17.4.22;lr=on;ftag=hssUA_3795992784-846>..From: <sip:203@172.17.4.22>;tag=hssUA_3795992784-846..To: <sip:3525@172.17.4.22: 5060>;tag=61645575ae245b55..Call-ID: 3795992784-846..CSeq: 5 NOTIFY..User-A gent: Grandstream BT110 1.0.8.16..Contact: <sip:3525@172.17.2.14:5060;user= phone>..Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE..S upported: replaces..Content-Length: 0.... 4. ****** The message BYE doesn't have the did parameter. U 2007/03/18 12:54:23.490685 172.17.2.14:5060 -> 172.17.4.22:5060 BYE sip:203@172.17.2.11:5060 SIP/2.0..Via: SIP/2.0/UDP 172.17.2.14;branch=z 9hG4bKa419f2aaf11a7b40..Route: <sip:172.17.4.22;lr=on;ftag=61645575ae245b55 >..From: <sip:3525@172.17.4.22:5060>;tag=61645575ae245b55..To: <sip:203@172 .17.4.22>;tag=hssUA_3795992784-846..Supported: replaces..Call-ID: 379599278 4-846..CSeq: 323 BYE..User-Agent: Grandstream BT110 1.0.8.16..Max-Forwards: 70..Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE..Cont ent-Length: 0.... U 2007/03/18 12:54:23.494656 172.17.4.22:5060 -> 172.17.2.11:5060 BYE sip:203@172.17.2.11:5060 SIP/2.0..Record-Route: <sip:172.17.4.22;lr=on; ftag=61645575ae245b55>..Via: SIP/2.0/UDP 172.17.4.22;branch=z9hG4bK2751.609 47d11.0..Via: SIP/2.0/UDP 172.17.2.14;branch=z9hG4bKa419f2aaf11a7b40..From: <sip:3525@172.17.4.22:5060>;tag=61645575ae245b55..To: <sip:203@172.17.4.22 >;tag=hssUA_3795992784-846..Supported: replaces..Call-ID: 3795992784-846..C Seq: 323 BYE..User-Agent: Grandstream BT110 1.0.8.16..Max-Forwards: 69..All ow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE..Content-Leng th: 0.... U 2007/03/18 12:54:23.517688 172.17.2.11:5060 -> 172.17.4.22:5060 SIP/2.0 200 OK..Via: SIP/2.0/UDP 172.17.4.22;branch=z9hG4bK2751.60947d11.0, SIP/2.0/UDP 172.17.2.14;branch=z9hG4bKa419f2aaf11a7b40..Record-Route: <sip: 172.17.4.22;lr=on;ftag=61645575ae245b55>..Server: Claro BS3202 A454..From: <sip:3525@172.17.4.22:5060>;tag=61645575ae245b55..To: <sip:203@172.17.4.22> ;tag=hssUA_3795992784-846..Call-ID: 3795992784-846..CSeq: 323 BYE..Contact: <sip:203@172.17.2.11:5060>..Allow: INVITE,OPTIONS,CANCEL,ACK,BYE,PRACK,INF O,REFER,NOTIFY..Content-Length: 0.... U 2007/03/18 12:54:23.519138 172.17.4.22:5060 -> 172.17.2.14:5060 SIP/2.0 200 OK..Via: SIP/2.0/UDP 172.17.2.14;branch=z9hG4bKa419f2aaf11a7b40 ..Record-Route: <sip:172.17.4.22;lr=on;ftag=61645575ae245b55>..Server: Clar o BS3202 A454..From: <sip:3525@172.17.4.22:5060>;tag=61645575ae245b55..To: <sip:203@172.17.4.22>;tag=hssUA_3795992784-846..Call-ID: 3795992784-846..CS eq: 323 BYE..Contact: <sip:203@172.17.2.11:5060>..Allow: INVITE,OPTIONS,CAN CEL,ACK,BYE,PRACK,INFO,REFER,NOTIFY..Content-Length: 0.... U 2007/03/18 12:54:29.780666 172.17.2.11:5060 -> 172.17.4.22:5060 BYE sip:5524@172.17.2.168:5061 SIP/2.0..Via: SIP/2.0/UDP 172.17.2.11:5060;b ranch=z9hG4bK3816062784-846..Route: <sip:172.17.4.22;lr=on;ftag=hssUA_38065 97784-846;did=0e3.7c5bd92>..Max-Forwards: 70..Proxy-Authorization: Digest u sername="613",realm="172.17.4.22",nonce="45fd6fe80721e4ce9c9b2eef4c93a66 ef8 8b9f2c",uri="sip:5524@172.17.4.22",response="3fb20f7d6e67668e07b862b9941 216 2d",algorithm=md5..User-Agent: Claro BS3202 A454..From: <sip:203@172.17.4.2 2>;tag=hssUA_3806597784-846..To: <sip:5524@172.17.4.22;user=phone>;tag=8cb5 cce9fbff0a22i1..Call-ID: 3806597784-846..CSeq: 3 BYE..Content-Length: 0.... U 2007/03/18 12:54:29.784698 172.17.4.22:5060 -> 172.17.2.168:5061 BYE sip:5524@172.17.2.168:5061 SIP/2.0..Record-Route: <sip:172.17.4.22;lr=o n;ftag=hssUA_3806597784-846>..Via: SIP/2.0/UDP 172.17.4.22;branch=z9hG4bKa5 c6.704043c7.0..Via: SIP/2.0/UDP 172.17.2.11:5060;branch=z9hG4bK3816062784-8 46..Max-Forwards: 69..Proxy-Authorization: Digest username="613",realm="172 .17.4.22",nonce="45fd6fe80721e4ce9c9b2eef4c93a66ef88b9f2c",uri="sip:5524 @17 2.17.4.22",response="3fb20f7d6e67668e07b862b99412162d",algorithm=md5..Us er- Agent: Claro BS3202 A454..From: <sip:203@172.17.4.22>;tag=hssUA_3806597784- 846..To: <sip:5524@172.17.4.22;user=phone>;tag=8cb5cce9fbff0a22i1..Call-ID: 3806597784-846..CSeq: 3 BYE..Content-Length: 0.... U 2007/03/18 12:54:29.804689 172.17.2.168:5061 -> 172.17.4.22:5060 SIP/2.0 200 OK..To: <sip:5524@172.17.4.22;user=phone>;tag=8cb5cce9fbff0a22i 1..From: <sip:203@172.17.4.22>;tag=hssUA_3806597784-846..Call-ID: 380659778 4-846..CSeq: 3 BYE..Via: SIP/2.0/UDP 172.17.4.22;branch=z9hG4bKa5c6.704043c 7.0..Via: SIP/2.0/UDP 172.17.2.11:5060;branch=z9hG4bK3816062784-846..Record -Route: <sip:172.17.4.22;lr=on;ftag=hssUA_3806597784-846>..Server: Linksys/ PAP2-3.1.3(LS)..P-RTP-Stat: PS=146,OS=34640,PR=303,OR=48162,PL=1,JI=0,LA=10 ,DU=6,EN=G711u,DE=G711u..Content-Length: 0.... U 2007/03/18 12:54:29.806174 172.17.4.22:5060 -> 172.17.2.11:5060 SIP/2.0 200 OK..To: <sip:5524@172.17.4.22;user=phone>;tag=8cb5cce9fbff0a22i 1..From: <sip:203@172.17.4.22>;tag=hssUA_3806597784-846..Call-ID: 380659778 4-846..CSeq: 3 BYE..Via: SIP/2.0/UDP 172.17.2.11:5060;branch=z9hG4bK3816062 784-846..Record-Route: <sip:172.17.4.22;lr=on;ftag=hssUA_3806597784-846>..S erver: Linksys/PAP2-3.1.3(LS)..P-RTP-Stat: PS=146,OS=34640,PR=303,OR=48162, PL=1,JI=0,LA=10,DU=6,EN=G711u,DE=G711u..Content-Length: 0.... As you can see, the dialog (callid=3795992784-846) still exists... /usr/local/sbin/openserctl fifo dlg_list 200 OK hash=3925, label=727521604, ptr=0x405c2d78 state=3, timeout=236218 callid='3795992784-846' from uri='sip:203@172.17.4.22', tag='hssUA_3795992784-846' to uri='sip:3525@172.17.4.22:5060', tag='61645575ae245b55' Thnk you in advance, Leonid Fainshtein -----Original Message----- From: Bogdan-Andrei Iancu [mailto:bogdan@voice-system.ro] Sent: Friday, March 16, 2007 2:51 PM To: Leonid Fainshtein Cc: users(a)openser.org Subject: Re: [Users] Problem with dialog module Hi Leonid, what do you mean by "removes"?. When sequential requests are processed, the Route header corresponding to your server will be completely removed. regards, bogdan Leonid Fainshtein wrote: > Hi, > I see that when Openser 1.1 receives re-INVITE it removes parameter > "did=" from header field Route before sending it to the second call > party. > Any idea? > > Thank you in advance, > Leonid > > > ******************************************** > This outgoing mail message was scanned by McAfee GroupShield Engine > > > _______________________________________________ > Users mailing list > Users(a)openser.org > http://openser.org/cgi-bin/mailman/listinfo/users > > ******************************************** This outgoing mail message was scanned by McAfee GroupShield Engine

2 2

[Serusers] SER with TLS
by Katty Xiong 04 Apr '07

04 Apr '07

I am using SER ottendorf with TLS protocol and have the following issues. Does anybody experience similar problems? SER cannot run with the following setup in the configuration file: (I follow this link to setup key and certificate: http://cvs.berlios.de/cgi-bin/viewcvs.cgi/ser/sip_router/modules/tls/README…) modparam("tls", "private_key", "cakey.pem") modparam("tls", "certificate", "cacert.pem") modparam("tls", "ca_list", "calist.pem") modparam("tls", "cipher_list", "HIGH"); With the last line commented out: #modparam("tls", "cipher_list", "HIGH"); SER can start, but the tls connection cannot be established. Network trace shows SER does not responde to ClientHello sent by client. Thanks, Joy ____________________________________________________________________________________ Food fight? Enjoy some healthy debate in the Yahoo! Answers Food & Drink Q&A. http://answers.yahoo.com/dir/?link=list&sid=396545367

3 9

[Users] response message content
by Victor Gamov 03 Apr '07

03 Apr '07

Hi all! Can somebody explain me how I can fill response with my useful headers? For example, I need to send 305 "Use proxy" response with Contact headers. Is it possible? If so, how can I populate it? Thanks! -- CU, Victor Gamov

3 5

Re: [Serusers] How to disable RTP proxy connection in
by Amanda Mattiuz 03 Apr '07

03 Apr '07

What happens if I disable rtpproxy but still load the nathelper? Can I still solve NAT problems with that?? -- ------------------------------------------------------------------- Amanda Remes Mattiuz amattiuz(a)gmail.com

3 2

[Users] RFC 3428
by Helmut Kuper 03 Apr '07

03 Apr '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I have a question about openser: Does openser support RFC 3428 (Instant Messaging (IM))? If so, How do I have to configure openser to relay SIP method MESSAGE ? regards helmut -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGERzN4tZeNddg3dwRAkNgAJ9t+ffNXs8+tiISFPEZlSyf7A5m2ACfSzJM rKsinfXGvAWBBW6mMSO9a8Y= =ixv4 -----END PGP SIGNATURE-----

3 3

Re: Fwd: [Users] SNMPstats module not returning data
by Terry Robert 03 Apr '07

03 Apr '07

I experienced the same problem with the SNMPstats module. If you run openser in foreground mode (fork=no), the module doesn't initialize. Running in background mode fixes the problem.

3 3

Re: [Users] Openser fails when compiled on Solaris 64bit
by Sergio Gutierrez 03 Apr '07

03 Apr '07

Hi Daniel. This is the backtrace of the core. Thanks #0 0xffffffff7d90ee9c in preload_udomain (_c=0x10026b7d800, _d=0x0) at /home/operador/openser-1.2.0-notls/modules/usrloc//udomain.c:404 #1 0xffffffff7d9131c4 in child_init (_rank=1344858528) at /home/operador/openser-1.2.0-notls/modules/usrloc//ul_mod.c:344 #2 0x0000000100082500 in init_mod_child (m=0x1, rank=1, type=0x1000f41b0 "CHILD") at /home/operador/openser-1.2.0-notls//sr_module.c:400 #3 0x0000000100082460 in init_mod_child (m=0x1, rank=1, type=0x1000f41b0 "CHILD") at /home/operador/openser-1.2.0-notls//sr_module.c:394 #4 0x0000000100082460 in init_mod_child (m=0x1, rank=1, type=0x1000f41b0 "CHILD") at /home/operador/openser-1.2.0-notls//sr_module.c:394 #5 0x0000000100082770 in init_child (rank=1) at /home/operador/openser- 1.2.0-notls//sr_module.c:394 #6 0x0000000100032414 in main_loop () at /home/operador/openser-1.2.0-notls //main.c:724 #7 0x00000001000345a4 in main (argc=2, argv=0xffffff7e7007a000) at /home/operador/openser-1.2.0-notls//main.c:1399 On 3/26/07, Daniel-Constantin Mierla <daniel(a)voice-system.ro> wrote: > > Hello, > > can you send a gdb backtrace :-D -- I cannot read adb backtrace. > > Cheers, > Daniel > > > On 03/26/07 19:42, Sergio Gutierrez wrote: > > Hi Daniel. > > > > This is the backtrace, obtained with adb: > > > > usrloc.so`preload_udomain+0x4cc(1, ffffffff7228e9f0, 100215a00, > > ffffffff7d919e58, ffffffffffefe3f8, 0) > > 0xffffffff7d9131bc(2, ffffffff7da1c9b0, ffffffff7d91a170, > > ffffffff7228e9a0, ffffffff7da1b0a8, ffffffffffeff0c8) > > init_mod_child+0xd8(100269930, 1, 1000f41b0, 1000f40f0, 1, 100269870) > > init_mod_child+0x38(100269bb0, 1, 1000f41b0, 1000f40f0, 1, 1002699f0) > > init_mod_child+0x38(100269d30, 1, 1000f41b0, 1000f40f0, 1, 100269c70) > > init_child+0xa8(1, 100269df0, 1, 1000f4168, 10020d000, 100269eb0) > > main_loop+0xf34(0, 8c, 1000eefd8, ffffffff720083c4, 1002694b0, 0) > > main+0x1e10(100215, 9, 0, 10020d000, 1000ef5b8, 10020d000) > > _start+0x7c(0, 0, 0, 0, 0, 0) > > > > On 3/26/07, *Sergio Gutierrez* <saguti(a)gmail.com > > <mailto:saguti@gmail.com>> wrote: > > > > Hi Daniel. > > > > I used 512 for -m parameter. > > > > Would you like the backtrace of the core file? > > > > Thanks. > > > > > > On 3/26/07, *Daniel-Constantin Mierla* < daniel(a)voice-system.ro > > <mailto:daniel@voice-system.ro>> wrote: > > > > Hello, > > > > could you send a backtrace? What was the value for parameter -m? > > > > Cheers, > > Daniel > > > > > > On 03/26/07 19:29, Sergio Gutierrez wrote: > > > Hi > > > > > > I am trying to run Openser compiled on 64 bits on a SPARC > > Machine > > > running Solaris 10. > > > > > > When I create a simple configuration file for testing radius > > > integration, Openser starts to consume the whole memory > > reservation > > > (-m parameter) and fails with segmentation fault error. > > > > > > after several tests, I have found that the error is caused by > > save() > > > function (registrar module). > > > > > > This is the main route my configuration file: > > > > > > route { > > > if(method=="REGISTER") > > > { > > > if(!radius_www_authorize("")) > > > { > > > www_challenge("", "0"); > > > return; > > > }; > > > > > > if(!save("location")) > > > { > > > sl_reply_error(); > > > }; > > > return; > > > > > > } > > > else > > > { > > > } > > > } > > > > > > Thanks in advance for your help. > > > > > > Sergio G. > > > > > > > ------------------------------------------------------------------------ > > > > > > _______________________________________________ > > > Users mailing list > > > Users(a)openser.org <mailto:Users@openser.org> > > > http://openser.org/cgi-bin/mailman/listinfo/users > > > > > > > > > >

3 10

[Users] Module Permission (register.allow and register.deny)
by Andrew And 03 Apr '07

03 Apr '07

In http://www.openser.org/docs/modules/1.2.x/permissions.html don´t have example with files register.allow and register.deny. Does someone has one example with rules these files?

1 0

[Users] does openser support QoS ?
by yanlin 03 Apr '07

03 Apr '07

Hi, does openser support some kind of QoS ? like, band width management, when there has no more usable bandwidth, then new INVITE should be rejected. so far, i know that dialog module has a bit dialog awareness. Any clues? thanks. yan lin

4 3

[Users] Serial forking broken wrt dst_uri/path?
by Frey, Daniel (external) 03 Apr '07

03 Apr '07

Hi, I tried to use append_branch() with dst_uri and path parameters set (and using set_dst_uri() / set_path_vector() for the first message). It works well as long as only parallel forking is involved, but when I use serialize_branches and next_branches and serial forking is required, the information given in dst_uri and path is discarded. This also seems obvious when reading the code from serialize.c, which simply doesn't store it on the contacts[n]-structs. I could add it to the sturct, but I'm at a loss how to store/retrieve it from the AVP. Are there any plans to fix this? Or any help on how I can fix it myself? Regards, Daniel

2 1

[Users] expires in Register message
by Dimo 03 Apr '07

03 Apr '07

Hi guys, Congratulations on the recent release, I will be testing it soon. I wonder if you can help me with a problem. I am trying to set UAs with a certain user-agent header to have different max_expires than all the rest. I am trying to override the default min_expires and max_expires values from within the config, after the definitions. So far i cannot do it - the modparam("registrar", "min_expires", xx) does not seem to accept an AVP for the xx part. Do you know if it is possible to change these timers per client from the code? Do they accept AVPs or is there any other way i can make it work? Thanks in advance Dimo

2 1

[Users] RTP without proxying, Linksys 3102
by Amanda Mattiuz 03 Apr '07

03 Apr '07

Hello Bill... it would be great if you could send me the cfg file you used.... -- ------------------------------------------------------------------- Amanda Remes Mattiuz amattiuz(a)gmail.com

1 0

[Serusers] mail client for SER UA
by Meidiana Ten 03 Apr '07

03 Apr '07

Hi there, I'm setting up voicemail server using SER. Do I need to setup mail client in client machine so it can access mailbox in server? If so, please tell me the software and how to configure the mail client. Thanx Regards, Meidiana ____________________________________________________________________________________ Never miss an email again! Yahoo! Toolbar alerts you the instant new Mail arrives. http://tools.search.yahoo.com/toolbar/features/mail/

1 0

RE: [Serusers] global contact list
by Barta János 03 Apr '07

03 Apr '07

Hello! Thanks for your answer. I'm using the standard config file (http://ftp.iptel.org/pub/ser/presence/cfg/full-no-failover.cfg), with a little modification, because I'm using radius authentication, accounting and media proxy. loadmodule "/opt/lib/ser/modules/acc_radius.so" loadmodule "/opt/lib/ser/modules/mediaproxy.so" loadmodule "/opt/lib/ser/modules/auth_radius.so" modparam("acc_radius","radius_config","/etc/radiusclient-ng/radiusclient.conf") modparam("acc_radius", "log_flag", 1) modparam("acc_radius", "log_missed_flag", 2) modparam("rls", "db_url", "mysql://yyyyyyy:xxxxxx@10.22.1.222/ser_pa") modparam("domain|uri_db|auth_db|usrloc|msilo", "db_url", "mysql://yyyyyyy:xxxxxx@10.22.1.222/ser_pa") if ((method=="INVITE") or (method=="BYE") or (method=="CANCEL")) { setflag(1); } if (!radius_www_authorize("test.intra")) { www_challenge("test.intra", "0"); break; }; handle_rls_subscription("1"); route[1] { if (method=="INVITE") { t_on_reply("1"); t_on_failure("1"); use_media_proxy(); } else if (method=="BYE|CANCEL") { end_media_session(); } # send it out now; use stateful forwarding as it works reliably # even for UDP2TCP if (!t_relay()) { sl_reply_error(); }; } onreply_route[1] { if (status=~"(183)|2[0-9][0-9]") { use_media_proxy(); }; if (status=~"[3-6]0[0-9]") { end_media_session(); break; } } failure_route[1] { # forwarding failed -- check if the request was a MESSAGE if (!method=="MESSAGE") { break; }; log(1, "MSILO: MESSAGE forward failed - storing it\n"); # we have changed the R-URI with the contact address, ignore it now if (m_store("0", "")) { t_reply("202", "Accepted"); } else { log(1, "MSILO: offline message NOT stored\n"); t_reply("503", "Service Unavailable"); }; end_media_session(); } ----------------- I made a capture with Ethereal, and I can see that eyeBeam sent the "Supported: eventlist" field. I inserted the lists of both type: Global-list: Message Header Via: SIP/2.0/UDP 10.22.2.134:9510;branch=z9hG4bK-d87543-dd118615e6316f41-1--d87543- Max-Forwards: 70 Contact: <sip:12345@10.22.2.134:9510> To: <sip:bartaj-list@test.intra> SIP to address: sip:bartaj-list@test.intra From: "12345"<sip:12345@test.intra>;tag=0a48df34 SIP Display info: "12345" SIP from address: sip:12345@test.intra SIP tag: 0a48df34 Call-ID: ee79a62abd227204@S2FhbGlhLXhwLndlc3RlbC53ZXN0ZWw5MDAuaHU. CSeq: 1 SUBSCRIBE Expires: 60 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO Supported: eventlist User-Agent: CounterPath eyeBeam Event: presence Content-Length: 0 User-list: Message Header Via: SIP/2.0/UDP 10.22.2.134:9510;branch=z9hG4bK-d87543-6300f275d049656e-1--d87543- Max-Forwards: 70 Contact: <sip:12345@10.22.2.134:9510> To: <sip:12345@test.intra> SIP to address: sip:12345@test.intra From: "12345"<sip:12345@test.intra>;tag=cb3e2c5c SIP Display info: "12345" SIP from address: sip:12345@test.intra SIP tag: cb3e2c5c Call-ID: a46e4b35e4754144@S2FhbGlhLXhwLndlc3RlbC53ZXN0ZWw5MDAuaHU. CSeq: 1 SUBSCRIBE Expires: 3600 Accept: message/external-body Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO Supported: eventlist User-Agent: CounterPath eyeBeam Event: sip-profile;profile-type=application;app-id=resource-lists Content-Length: 0 The second case is working, but the first one is not. Is this maybe an EyeBeam problem? Which version of EyeBeam works fine (or which other client can I test it with)? And I have another question. What can I do with those clients, that does not support the presence information (can I do something anyway?). For example: I have a "Cisco Call Manager Express" box, and some Cisco IP Phones, that reach other PC clients through the SER. The Cisco makes the registration (and reregistration) with the phone's identifiers too into the SER (but the presence information is not handled by the Cisco), and therefore if a PC client would like to add the Cisco phone into his buddy list, the presence won't be working. ...Record(0x405cc588)... domain: 'location' aor : '101$' ~~~Contact(0x405cc5c8)~~~ domain : 'location' aor : '101$' Contact : 'sip:101$@10.22.2.233:5060' Expires : Expired q : Call-ID : '9C5717E5-D7D211DB-804EA958-71810899' CSeq : 4103 User-Agent: 'Cisco-SIPGateway/IOS-12.x' received : '' State : CS_SYNC Flags : 0 next : (nil) prev : (nil) ~~~/Contact~~~~ .../Record... ...Record(0x405cc698)... domain: 'location' aor : '100$' ~~~Contact(0x405cc6d8)~~~ domain : 'location' aor : '100$' Contact : 'sip:100$@10.22.2.233:5060' Expires : Expired q : Call-ID : '9C5717E5-D7D211DB-804DA958-71810899' CSeq : 1364 User-Agent: 'Cisco-SIPGateway/IOS-12.x' received : '' State : CS_SYNC Flags : 0 next : (nil) prev : (nil) ~~~/Contact~~~~ .../Record... Is it possible, that the SER (in these cases) simulates a presence client (if the user registration is active, then the user is online, anyway offline)? Thanks, Jani -----Original Message----- From: Vaclav Kubart [mailto:vaclav.kubart@iptel.org] Sent: Wednesday, March 28, 2007 3:46 PM To: Barta János Cc: serusers(a)iptel.org Subject: Re: [Serusers] global contact list Hi, please can you send here your config file? By the way, in some EyeBeam versions was not possible to use "Subscribe to contact list" feature because in such cases EyeBeam didn't send header "Supported: eventlist". Vaclav On Tue, Mar 27, 2007 at 08:54:15AM +0200, Barta János wrote: > Hello! > > I have a little problem with the (global) contact list subscription > of the presence, please help me. > I installed the presence server (0.10.99-dev35-pa-4.1), and it works > without any problems. > But I can not use the "Subscribe to contact list" of the eyeBeam. (The > user subscribe list works fine.) I typed the next content into this > field (of the eyeBeam): > > sip:bartaj-list@test.intra > > > and my config file contains: > > sip:/var/xcap-root/rls-services/global# cat ./index <?xml > version="1.0" encoding="UTF-8"?> <rls-services> > > <service uri="sip:bartaj-list@test.intra"> > <list name="Human resources"> > <entry uri="sip:test1@test.intra"> > > <display-name>bartaj</display-name> > </entry> > <entry uri="sip:test2@test.intra"> > > <display-name>12345</display-name> > </entry> > </list> > <packages> > <package>presence</package> > </packages> > </service> > > </rls-services> > > But I can see only the user subscribe list, and can't see the global > one. > Why? > Can anybody help me? > Thx, > Jani > _____________________________________________________________________________________________________ Jean Michel Jarre: Téo és Téa, az új, ünnepi album 1990 Forintért, kizárólag a T-Online Zeneáruházban! http://zenearuhaz.t-online.hu/index.php?m=info&albumid=30593&sp=1&sty=21

2 1

[Users] [resolv] radius problem in 1.2
by Bodin Bruno 03 Apr '07

03 Apr '07

Hello, During few days I've a problem with openser 1.2 and radius authentication but I just solve it ! This is a little note about my method. *Please, you're welcome to check and comment it for a better solution.* *Issue* : Radius authentication fail for openser 1.2 but not for 1.1.1 version with the same config. *Description* : freeradius server sucess (Sending Access-Accept in log) but it's not good in openser log. *Search method* : analyse of differences between 1.1.1 and 1.2 version >lsof | grep radius | grep -v radiusd /_openser 1.1.1_/ : openser 6226 root mem REG 8,2 50984 1333396 /usr/lib64/libradiusclient-ng.so.2.0.0 openser 6226 root mem REG 8,2 71642 30076344 /opt/openser-1.1.1/lib64/openser/modules/auth_radius.so openser 6226 root mem REG 8,2 41637 30076357 /opt/openser-1.1.1/lib64/openser/modules/group_radius.so openser 6226 root mem REG 8,2 43683 30076346 /opt/openser-1.1.1/lib64/openser/modules/avp_radius.so openser 6226 root mem REG 8,2 38171 30389824 /opt/openser-1.1.1/lib64/openser/modules/uri_radius.so _/openser1.2 :/_ openser 6299 root mem REG 8,2 50952 1333316 /usr/lib64/libfreeradius-client.so.2.0.0 openser 6299 root mem REG 8,2 76493 30356347 /opt/openser-1.2/lib64/openser/modules/auth_radius.so openser 6299 root mem REG 8,2 41769 30356361 /opt/openser-1.2/lib64/openser/modules/group_radius.so openser 6299 root mem REG 8,2 44923 30356349 /opt/openser-1.2/lib64/openser/modules/avp_radius.so openser 6299 root mem REG 8,2 39411 30076331 /opt/openser-1.2/lib64/openser/modules/uri_radius.so *openser 1.2.0 use libfreeradius-client.so.2.0.0 openser 1.1.1 use libradiusclient-ng.so.2.0.0 * * my solve method :* >cd /usr/lib64/ >mv libfreeradius-client.so.2.0.0 libfreeradius-client.so.2.0.0.old >ln -s libradiusclient-ng.so.2.0.0 libfreeradius-client.so.2.0.0

2 1

[Users] DLG: BYE not detected because of route reccord
by Michel Bensoussan 03 Apr '07

03 Apr '07

Hello The dialog module checks SIP messages only if the OpenSER in on record-route header in function dlg_onroute(). When the callee in registered on another SIP Server and the callee sends BYE, the OpenSER is not on record-route header. In this case, the dialog module doesn't detect end of call. Is there a way to callback the dlg_onroute() function not only in case of record-route? The configuration is as following: - Tel 101 registered to 192.168.13.8 (siproxd) (URI: 101(a)192.168.13.8) (IP: 192.168.13.101) - Tel 155 registered to 192.168.13.86 (OpenSER) (URI: 155(a)192.168.13.86) (IP: 192.168.13.155) - 155 is the caller and 101 is the callee. Attached, message capture (ethereal) when the callee (101) terminate the call. Thanks. Regards, Michel.

2 5

[Users] BUG in TM
by Sam Lee 03 Apr '07

03 Apr '07

Hey guys, I'm getting BUG:tm:run_failure_handlers: stack level is 1!! in my syslog. It is generating when i place a call out to PSTN. Any ideas ? Sam

2 5

Re: [Users] Module UAC to authentication and redirect calls
by Bogdan-Andrei Iancu 03 Apr '07

03 Apr '07

See the "credential" module parameter: http://www.openser.org/docs/modules/1.2.x/uac.html#AEN106 regards, bogdan Thiago Maluf wrote: > what`s parameters I will use to do this authentication? > > 2007/3/2, Bogdan-Andrei Iancu < bogdan(a)voice-system.ro > <mailto:bogdan@voice-system.ro>>: > > Hi, > > try something like: > > failure_route[1] { > xlog("-----------$T_reply_code ---------\n"); > if (t_check_status("401|407")) { > log(1,"doing auth\n"); > if (uac_auth()) { > append_branch(); > t_relay(); > } > } > } > > regards, > bogdan > > Thiago Maluf wrote: > > Hi List, > > I need config one module UAC to do authentication and redirect my > > calls to other Voip Provider. > > Somebody already did it? If can tell me what functions you used. > > Thanks in advanced! > > Thiago Maluf. > > > > ---------------------------------------------------------------- > > THIAGO MALUF RESENDE > > Consultor Voip e Programador WEB (Voip Developer and Web Developer) > > e-mail: malufrj(a)gmail.com <mailto:malufrj@gmail.com> <mailto: > malufrj(a)gmail.com <mailto:malufrj@gmail.com>> > > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > Users mailing list > > Users(a)openser.org <mailto:Users@openser.org> > > http://openser.org/cgi-bin/mailman/listinfo/users > > > > > > > -- > ---------------------------------------------------------------- > THIAGO MALUF RESENDE > Consultor Voip e Programador WEB (Voip Developer and Web Developer) > Tel: +55 21 86042100 > e-mail: malufrj(a)gmail.com <mailto:malufrj@gmail.com>

1 0

Re: [Users] 3xx requests and t_relay
by Bogdan-Andrei Iancu 03 Apr '07

03 Apr '07

Hi Shane, please post the network trace from the the server and the full debug log of openser (use debug=9). regards, bogdan Shane Burrell wrote: > I used that as an example. On the sip side I see the 302 come back and the > openser ack it. Then I never see the new call go out. The user gets a busy > or not avaible message from the switch. In openser I have some logging and > it seems to start a new route after the ACK but bombs somewhere. > > -----Original Message----- > From: Bogdan-Andrei Iancu [mailto:bogdan@voice-system.ro] > Sent: Wednesday, February 28, 2007 12:54 PM > To: Shane Burrell; users openser.org > Subject: Re: [Users] 3xx requests and t_relay > > Hi Shane, > > have you followed this ex: > http://www.openser.org/docs/modules/1.2.x/uac_redirect.html#AEN251 > > can you be more specific about the errors you see? > > regards, > bogdan > > Shane Burrell wrote: > >> I am calling the t_relay after getting the contacts. However internally I >> see in openser it makes it back to the route and then dies in loose route. >> I assumed there was something I need to check to allow the new call to be >> processed. >> >> -----Original Message----- >> From: Bogdan-Andrei Iancu [mailto:bogdan@voice-system.ro] >> Sent: Wednesday, February 28, 2007 12:26 PM >> To: Shane Burrell >> Cc: users(a)openser.org >> Subject: Re: [Users] 3xx requests and t_relay >> >> Hi, >> >> let me see if I get it right...you get a 3xx reply and try to generate >> INVITE to the new contacts? if so, take a look at the uac_redirect module. >> >> regards, >> bogdan >> >> Shane Burrell wrote: >> >> >>> I have this working to the point it tries to relay the call but I see >>> that internally openser is not making the new call. I assume t_relay >>> calls a new route but how to I make sure that all relays get >>> forwarded. Some of my logic else where seems to be killing the >>> rerouted call and I need any 302 routed calls to be accepted and routed. >>> >>> >>> >>> TIA, >>> >>> >>> >>> Shane >>> >>> >>> *************************************************************** >>> >>> >>> >>> ------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> Users mailing list >>> Users(a)openser.org >>> http://openser.org/cgi-bin/mailman/listinfo/users >>> >>> >>> >> >> > > >

1 0

[Users] TCP lifetime
by Klaus Darilion 03 Apr '07

03 Apr '07

Hi! I thought setting the tcp_connection_lifetime to 0 should keep them open endlessly, but in my case the proxy closes the TCP connection ~10 seconds after the last SIP message. What am I doing wrong? regards klaus -- Klaus Darilion nic.at

2 7

[Users] NEW FEATURE: IP blacklists
by Bogdan-Andrei Iancu 03 Apr '07

03 Apr '07

Hi everybody, OpenSER 1.2.0 has new feature - IP Blacklist support. This is a low level filtering engine for the outgoing requests; low level, because the filtering is done based on IP, protocol, port, etc. Its primary purposes will be to prevent sending requests to critical IPs (like GWs) due DNS or to avoid sending to destinations that are known to be unavailable (temporary or permanent). Because of flexibility concerns, the filtering rules can be groups inside multiple lists. A rule: - matches based on IP/mask, proto, port and text pattern criteria - can be reversed applied A list: - can be read-only - it does not change during execution - have timeout per elements - elements expires after a configured timeout. How to use: =========== currently there are 2 ways of using the blacklists: 1) statically defining list in the configuration file and selecting which ones should be used for each request. You can define blacklists as follow: # filter out requests going to ips of my gws dst_blacklist = gw:{( tcp , 192.168.2.100 , 5060 , "" ),( any , 192.168.2.101 , 0 , "" )} # block requests going to "evil" networks dst_blacklist = net_filter:{ ( any , 192.168.1.100/255.255.255.0 , 0 , "" )} # block message requests with nasty words dst_blacklist = msg_filter:{ ( any , 192.168.20.0/255.255.255.0 , 0 , "MESSAGE*ugly_word" )} # block requests not going to a specific subnet dst_blacklist = net_filter2:{ !( any , 192.168.30.0/255.255.255.0 , 0 , "" )} a rule is defined by: protocol : TCP, UDP, TLS or "any" for anything port : number or 0 for any ip/mask test patter - is a filename like matching (see "man 3 fnmatch") applied on the outgoing request buffer (first_line+hdrs+body) From routing script, you can use the use_blacklist("name") function to select what blacklist to be applied for the current request. More than one list can be selected. If the destination address matches on of the selected rules, the send will fail. 2) via DNS The DNS resolver, when configured with failover, can automatically store in a temporary blacklist the failed destinations. This will prevent (for a limited period of time) openser to send requests to destination known as failed. So, the blacklist can be used as a memory for the DNS resolver. To use it, you have to enabled it - the rest is done automatically. disable_dns_blacklist = no By default is enabled. The temporary blacklist created by DNS resolver is named "dns" and it is by default selected for usage (no need use the use_blacklist() function. The rules from this list have a life time of 4 minutes - you can change it at compile time, from blacklists.h . To give you an internal snapshot, a new MI function - "list_blacklists" - was added to print all existent blacklists and their rules. Any suggestions/reports are welcome! regards, bogdan

2 5

re: [Users] SIPp and registration
by yanlin 03 Apr '07

03 Apr '07

Hi, Scott Yagel, you could find some clues in the file scenario.cpp of sipp project. there were some embeded scenario scripts in sipp, stored in char* default_scenario[], you can sent a register sip message by doing this: " <send retrans=\"500\">\n" " <![CDATA[\n" "\n" " REGISTER sip:CA.cym.com SIP/2.0\n" " Via: SIP/2.0/[transport] [local_ip]:[local_port];branch=[branch]\n" " From: ua1 <sip:ua1@nnl.cym:[local_port]>;tag=[pid]SIPpTag07[call_number]\n" " To: ua1 <sip:ua1@nnl.cym:[local_port]>\n" " Call-ID: [call_id]\n" " CSeq: 1 REGISTER\n" " Contact: sip:ua1@[local_ip]:[local_port]\n" " Content-Length: 0\n" " Expires: 300\n" "\n" " ]]>\n" " </send>\n" regards. Yan Lin

2 1

[Users] What does this mean?
by nick 03 Apr '07

03 Apr '07

pre_auth(): Credentials with given realm not found After looking around google it seems to be based on the fact that the first sip: value doesn't contain the userid (if I understand correctly...) I can't figure out exactly why the RURI is coming in this fashion.. Should I be changing something in the clients, or my config?? These worked on an older config, now with this section, they just don't get accepted. I've tried it with and without sipserver.mobilia.it in the realm. I've also tried it with the server generating ha1 and static ha1 (from the ha1 and ha1b fields in the db), no difference. I have use domain 1 in registrar and auth_db, and strip "sipserver." sl_send_reply("100", "Trying"); if(!www_authorize("", "subscriber")) { xlog("L_INFO", "Register authentication failed - M=$rm RURI=$ru F=$fu T=$tu IP=$si ID=$ci\n"); www_challenge("", "1"); exit; } Mar 29 12:07:40 sipserver /usr/local/sbin/openser[22732]: New request - M=REGISTER RURI=sip:mobilia.it F=sip:rice@mobilia.it T=sip:rice@mobilia.it IP=x.x.x.105 ID=fmq-17240(a)x.x.x.105 Mar 29 12:07:40 sipserver /usr/local/sbin/openser[22732]: parse_headers: flags=100 Mar 29 12:07:40 sipserver /usr/local/sbin/openser[22732]: get_hdr_field: cseq <CSeq>: <100> <REGISTER> Mar 29 12:07:40 sipserver /usr/local/sbin/openser[22732]: DEBUG:maxfwd:is_maxfwd_present: value = 70 Mar 29 12:07:40 sipserver /usr/local/sbin/openser[22732]: parse_headers: flags=200 Mar 29 12:07:40 sipserver /usr/local/sbin/openser[22732]: DEBUG: get_hdr_body : content_length=0 Mar 29 12:07:40 sipserver /usr/local/sbin/openser[22732]: found end of header Mar 29 12:07:40 sipserver /usr/local/sbin/openser[22732]: find_first_route: No Route headers found Mar 29 12:07:40 sipserver /usr/local/sbin/openser[22732]: loose_route: There is no Route HF Mar 29 12:07:40 sipserver /usr/local/sbin/openser[22732]: parse_headers: flags=ffffffffffffffff Mar 29 12:07:40 sipserver /usr/local/sbin/openser[22732]: check_via_address(x.x.x.105, x.x.x.105, 0) Mar 29 12:07:40 sipserver /usr/local/sbin/openser[22732]: parse_headers: flags=4000 Mar 29 12:07:40 sipserver /usr/local/sbin/openser[22732]: pre_auth(): Credentials with given realm not found Mar 29 12:07:40 sipserver /usr/local/sbin/openser[22732]: Register authentication failed - M=REGISTER RURI=sip:mobilia.it F=sip:rice@mobilia.it T=sip:rice@mobilia.it IP=x.x.x.105 ID=fmq-17240(a)x.x.x.105 Mar 29 12:07:40 sipserver /usr/local/sbin/openser[22732]: build_auth_hf(): 'WWW-Authenticate: Digest realm="mobilia.it", nonce="460b9118a6a044d8837a01f924be2a9a3b7e0271", qop="auth"^M '

4 5

[Users] Simple xcap-emulator for OpenSER
by Adrian Georgescu 02 Apr '07

02 Apr '07

Hello, We wrote a simple xcap emulator to be able to manage the XCAP documents used by OpenSER presence agent, by using PHP scripts in combination with Apache web server. I have tested it against OpenSER with MySQL and Eyebeam for Apple. Klaus Darilion has tested it against Postgress and Eyebeam for Windows. The software can be downloaded from: http://download.dns-hosting.info/XCAP/xcap-0.5.tar.gz Regards, Adrian

2 3

[Serusers] How to disable RTP proxy connection in nathelper module
by tzieleniewski 02 Apr '07

02 Apr '07

Hi, I am using nathelper and because I have an CISCO router in front of the SER I don't need to use RTP Proxy. Whenever I start SER I get the following errors: Apr 2 09:13:33 sen ser[3442]: ERROR: send_rtpp_command: can't connect to RTP proxy Apr 2 09:13:33 sen ser[3442]: send_rtpp_command(): proxy <unix:/var/run/rtpproxy.sock> does not responding, disable it Apr 2 09:13:33 sen ser[3442]: WARNING: rtpp_test: can't get version of the RTP proxy Apr 2 09:13:33 sen ser[3442]: WARNING: rtpp_test: support for RTP proxy <unix:/var/run/rtpproxy.sock>has been disabled temporarily Apr 2 09:13:33 sen ser[3444]: ERROR: send_rtpp_command: can't connect to RTP proxy Is there a way to disable this trials through ser.cfg by nathelper mod parameter in order not to get those errors? Cheers Tomasz

2 1

[Users] WeSIP C2C and freeswitch
by Helmut Kuper 02 Apr '07

02 Apr '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I try to use WeSIP C2C with UACs registered to freeswitch. freeswitch never answeres the INVITEs for caller (that INVITE with no SDP and from=to=caller's sip address). So my question is, is it because freeswitch maybe doesn't support rfc 3725? If so, is there any C2C proven SIP-PBX I can use instead? Helmut -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFF7s8L4tZeNddg3dwRArGjAKCRJ+Kqi4FqdE2J9S/Q6t8L3VEVzwCgncCc G2rxVs9s3fqs+XgUXnsefRs= =RqW7 -----END PGP SIGNATURE-----

4 9

[Users] How URI is parsed...
by Stuart Sheldon 02 Apr '07

02 Apr '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Newbe question: Can someone explain what causes a match when lookup() and does_uri_exist() is used? Does it look at the least significant characters is the URI? Does it drop certain leading numbers like '1'? Stu -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFGDs0BK69Y+xPZrWYRAg5XAJ9kL3FNuImfu6wasPZ9z32uDYmoGwCfWKhW 5al96b0dhkmFNYnwBzyHmoY= =mNnn -----END PGP SIGNATURE-----

2 2

[Users] use of AVPs in core functions
by Jens Carl 02 Apr '07

02 Apr '07

Hello List, is it possible to use AVPs in core function like rewritehost(), etc. Regards Jens

2 1

Re: [Users] Openser on Sun Ultrasparc T1 Processors - Mismatch architecture detection
by Henning Westerholt 02 Apr '07

02 Apr '07

On Tuesday 27 March 2007 17:41, you wrote: > Hi Henning. > > I tested the compilation and it does not detect the architecture. > > I think that maybe is because of uname -p outputs sparc, and uname -m > outputs sun4v. > [..] Hi Sergio, thank you for the testing. I add another check to the patch according your suggestions, could please try it another time? Cheers, Henning

3 2

re: [Users] postgres
by Mark Price 02 Apr '07

02 Apr '07

On 12/20/06, Klaus Darilion <klaus.mailinglists(a)pernau.at > wrote: > > Hi Mark! > > Postgres should work well - I use it since ser 0.8. Just make sure that > the hard disk does not get full, because this breaks the index inside > postgres and postgres is getting real slow (re-create the index if it > happens). > > Last time I tested openser_postgres.sh it worked fine. If you find a bug > please let us know. > > Please check to use the latest versions from CVS (for 1.1 use CVS > rel_1_1_0) The latest version from cvs doesn't work out of the box with openser build from the release tarball, because the release tarball doesn't included /usr/sbin/openser_gen_ha1 (although I could get past this by replacing it with the md5sum equivelant). However, the release tarball doesn't work because of this bug: https://sourceforge.net/tracker/?func=detail&atid=743020&aid=1518732&group_… So, 1. is the cvs version of rel_1_1_0 considered safe for production use? 2. if so and there are important fixes such as this in CVS, would openser.org consider releasing a point release containing such changes? Thanks, Mark Price

6 8

RE: [Users] out of memory
by Papadopoulos Georgios 02 Apr '07

02 Apr '07

Hi Bogdan, I increased PKG_MEM_POOL_SIZE to 2MB and of course it took much longer to run out of memory. Usually it happens once every day, this time it ran for 3 days before running out of memory. If you don't mind, I will send the memory dump by personal email since I don't have easy access to an ftp server. Can you explain what you mean by 1.1.x? The version I am using is openser-1.1.1-notls_src.tar.gz, downloaded from your site under 1.1.1/. I am guessing that to get the fix I should use whatever is under latest-1.1.x/ Is this right? thank you George > -----Original Message----- > From: Bogdan-Andrei Iancu [mailto:bogdan@voice-system.ro] > Sent: Friday, March 30, 2007 3:33 PM > To: Papadopoulos Georgios > Cc: users(a)openser.org > Subject: Re: [Users] out of memory > > Papadopoulos Georgios wrote: > > > > Hi Bogdan, > > > > I found the following thread in the list > > http://www.openser.org/pipermail/users/2006-June/005339.html > > I suspect that I have the same issue. If I assume that our DNS is > > strange, then my 1.1.1-notls version will be affected, > right? Is there > > a patch to fix this? Eventually I want to go to 1.2 but I > have to do a > > lot of testing before I can put it in production. So for > the moment I > > need a fix for 1.1.1. > > > that fix is present in 1.1.x also. > > Also back in December I sent this to the list > > http://www.openser.org/pipermail/users/2006-December/008205.html > > >From the start, we had the issue of openser stopping to process any > > incoming requests. On December I thought it was DNS related. I am > > still in the dark about this. Lately I added logging and I > discovered > > the "out of memory" error. I am guessing that the error was > there from > > the start, I just did not know about it. Do all of these make any > > sense to you? And is there a way to test our DNS to > determine whether it is buggy? > > > I;m afraid not :) > > In the meantime I will follow the instructions on the wiki > to get the > > memory dump. > > > yes - that will be the most relevant info. > > regards, > bogdan > > thank you > > > > George > > > > > > > > > >> -----Original Message----- > >> From: Bogdan-Andrei Iancu [mailto:bogdan@voice-system.ro] > >> Sent: Wednesday, March 28, 2007 11:54 AM > >> To: Papadopoulos Georgios > >> Cc: users(a)openser.org > >> Subject: Re: [Users] out of memory > >> > >> Hi Papadopoulos, > >> > >> the error you get complains about the lack of private memory (per > >> process) - the statistics show info about the shared memory. See: > >> http://www.openser.org/dokuwiki/doku.php/troubleshooting:memory > >> > >> but look for pkg instead of shm..... > >> > >> regards, > >> bogdan > >> > >> Papadopoulos Georgios wrote: > >> > >>> Hello, > >>> > >>> Lately our OpenSER 1.1.1 is running out of memory and I get the > >>> following message > >>> 4(25190) get_hdr_field: out of memory The result is that > it stops > >>> processing any incoming request. This is a production > system and of > >>> course it causes a great deal of frustration. > >>> > >>> The last time this happened I got the following statistics before > >>> restarting > >>> > >>>> ./openserctl fifo get_statistics > >>>> > >>> Total statistics = 37 > >>> Total modules = 5 > >>> Module name = core; statistics=8 > >>> core:rcv_requests = 3259334 > >>> core:rcv_replies = 8816 > >>> core:fwd_requests = 736 > >>> core:fwd_replies = 137 > >>> core:drop_requests = 743 > >>> core:drop_replies = 0 > >>> core:err_requests = 0 > >>> core:err_replies = 43 > >>> Module name = shmem; statistics=6 > >>> shmem:total_size = 268435456 > >>> shmem:used_size = 1675864 > >>> shmem:real_used_size = 1835104 > >>> shmem:max_used_size = 4399048 > >>> shmem:free_size = 266600352 > >>> shmem:fragments = 17710 > >>> Module name = sl; statistics=9 > >>> sl:1xx_replies = 0 > >>> sl:2xx_replies = 1690410 > >>> sl:3xx_replies = 43 > >>> sl:4xx_replies = 334827 > >>> sl:5xx_replies = 1185629 > >>> sl:6xx_replies = 0 > >>> sl:sent_replies = 3210909 > >>> sl:sent_err_replies = 0 > >>> sl:received_ACKs = 743 > >>> Module name = tm; statistics=11 > >>> tm:received_replies = 8636 > >>> tm:relayed_replies = 7096 > >>> tm:local_replies = 1718 > >>> tm:UAS_transactions = 7003 > >>> tm:UAC_transactions = 94 > >>> tm:2xx_transactions = 1528 > >>> tm:3xx_transactions = 3 > >>> tm:4xx_transactions = 5129 > >>> tm:5xx_transactions = 468 > >>> tm:6xx_transactions = 0 > >>> tm:inuse_transactions = 0 > >>> Module name = usrloc; statistics=3 > >>> usrloc:location-users = 0 > >>> usrloc:location-contacts = 0 > >>> usrloc:location-expires = 7282 > >>> > >>> I am not sure how to read these numbers but I see a big > "free_size" > >>> and still OpenSER is out of memory. Any suggestions? > >>> > >>> 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 > >>> > >>> > >> > > > > > >

3 2

[Users] OpenSER v1.2.0 released
by Daniel-Constantin Mierla 02 Apr '07

02 Apr '07

Hello, version 1.2.0 of OpenSER has been released. It is major release, which means that you get along a lot of new features and improvements to existing ones in old versions. The configuration file and database structure suffered some changers, please read careful release notes to learn how to update. Just to list few of the new features: - SIMPLE Presence support (http://openser.org/dokuwiki/doku.php/presence:presence-module) - SNMP (http://openser.org/docs/modules/devel/snmpstats.html) - PERL API (http://openser.org/docs/modules/devel/perl.html) - JAVA SIP Servlet Application Server (http://wesip.eu) - script variables and transformations (http://openser.org/dokuwiki/doku.php/transformations:devel) - DNS failover - IP blacklists - XMPP IM gateway - XMLRPC - SIP session timers - secure federation peering - retransmission timer accuracy - usrloc refurbished for better performances - automatic error handling - AVPs in reply routes Read full release notes at: http://www.openser.org/mos/view/OpenSER-v1.2.x-Release-Notes/ Source tarball can be downloaded from: http://www.openser.org/pub/openser/latest/src/ Or SourceForge: http://sourceforge.net/project/showfiles.php?group_id=139143&package_id=224… This is the first release coming out o SVN. Old CVS repository was migrated to SVN, and with these, a few changes apply to get sources from repository. Please read instructions from download page: http://www.openser.org/mos/view/Download/ Migration instructions (although not complete, I'm sure) are available at: http://openser.org/dokuwiki/doku.php/install:1.1.x-to-1.2.x The documentation for modules is posted at: http://openser.org/docs/modules/1.2.x/ We would like to thank to all developers and contributors for their work with coding and testing for this new release. Cheers, Daniel

9 20

[Serusers] Header Selects
by Andrey Kuprianov 02 Apr '07

02 Apr '07

Hi, @msg.event or @msg.supported, or even @msg.["header-name"] is not implemented yet? im using latest ser from CVS.. btw, is it ok to use latest SER 2.0 for presence instead of the suggested snapshot v.4? I've noticed xcap-root and auth_xcap_root params were removed from rls and pa modules, so i've set xcap_root param in xcap module instead.

3 6

[Users] presence logging....
by Helge Waastad 02 Apr '07

02 Apr '07

Hi, I'm just wondering if it's possible to turn off logging of some presence status messages? I have debug=0 But still I see a lot of: pr 2 08:06:11 proxy-02 /usr/sbin/openser[28662]: PRESENCE: generate_ETag: etag= a.1175493921.28662.1 / 20 Apr 2 08:06:11 proxy-02 /usr/sbin/openser[28662]: PRESENCE: get_subs_dialog:The query for subscribtion for [user]= xxx,[domain]= yyy for [event]= presence returned no result Apr 2 08:06:11 proxy-02 /usr/sbin/openser[28662]: PRESENCE:query_db_notify: Could not get subs_dialog from database /32] 08:06:11 proxy-02 /usr/sbin/openser[28662]: PRESENCE: handle_publish: sip-etag: [SIP-ETag: a.1175493921.28662.1 Is the only way do only have L_ERR filtered in syslog daemon? br hw

1 0

[Serusers] About avp_db_store()
by chungyu 02 Apr '07

02 Apr '07

Hi all, I am trying to use avp_db_store() stores my table "contact" with caller uri ex: table name: contact ----------------------------- | username | domain | ----------------------------- | | | ----------------------------- | | | ----------------------------- If (method=="INVITE"){ avp_write("$ruri/username", "s:name"); avp_db_store("$ruri", "s:name/contact"); }; if the incoming call then save username and domain of caller in contact caller: bob(a)iptel.org => ----------------------------- | username | domain | ----------------------------- | bob | iptel.org | ----------------------------- | | | ----------------------------- but not success, system reply ERROR:avpops:db_store: insert faild Please help me in the problem Thanks a lot in advance chungyu

1 0

[Users] Call dropped after 6 ACKs. Branch=0 problem?
by kjcsb 02 Apr '07

02 Apr '07

I have the following scenario: PSTN gateway (202.180.nnn.nnn) -> OpenSER 1.0.1 (147.202.nnn.nnn) -> Asterisk 1.2.16 (203.89.nnn.nnn) When an incoming call is received, the call is established but often (but not always) eventually dropped. In the following dialogue, it can be seen that when the ACK is passed from the gateway on to Asterisk, OpenSER appends a Via with branch=0. After a number of these ACKs are passed on, the call is eventually dropped. It has been suggested by someone on the Asterisk list that "While "branch=0" is valid in RFC 2543, I don't think an INVITE can start-off as RFC 3261 and then the ACK can switch over to RFC 2543 in the middle of the transaction." i.e. the implication is that it's an OpenSER problem. Does that seem right? If so how can it be corrected? If not, could anyone advise what the problem might be or suggest any resolutions? U 202.180.nnn.nnn:5060 -> 147.202.nnn.nnn:5060 INVITE sip:6499777777@domain.co.nz SIP/2.0 Via: SIP/2.0/UDP 202.180.nnn.nnn:5060;branch=z9hG4bK0b505d2b;rport From: "6494444444" <sip:6494444444@202.180.nnn.nnn>;tag=as3f0f7d93 To: <sip:6499777777@domain.co.nz> Contact: <sip:6494444444@202.180.nnn.nnn> Call-ID: 2f573abd3cd80bd369495e322ec5ab4a(a)202.180.nnn.nnn CSeq: 102 INVITE User-Agent: Asterisk PBX Max-Forwards: 70 Date: Mon, 02 Apr 2007 02:53:24 GMT Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY Content-Type: application/sdp Content-Length: 336 v=0 o=root 8802 8802 IN IP4 202.180.nnn.nnn s=session c=IN IP4 202.180.nnn.nnn t=0 0 m=audio 35268 RTP/AVP 18 97 3 0 8 101 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:97 iLBC/8000 a=rtpmap:3 GSM/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=silenceSupp:off - - - - U 147.202.nnn.nnn:5060 -> 202.180.nnn.nnn:5060 SIP/2.0 100 trying -- your call is important to us Via: SIP/2.0/UDP 202.180.nnn.nnn:5060;branch=z9hG4bK0b505d2b;rport=5060 From: "6494444444" <sip:6494444444@202.180.nnn.nnn>;tag=as3f0f7d93 To: <sip:6499777777@domain.co.nz> Call-ID: 2f573abd3cd80bd369495e322ec5ab4a(a)202.180.nnn.nnn CSeq: 102 INVITE Server: OpenSer (1.0.1 (i386/linux)) Content-Length: 0 Warning: 392 147.202.nnn.nnn:5060 "Noisy feedback tells: pid=29716 req_src_ip=202.180.nnn.nnn req_src_port=5060 in_uri=sip:6499777777@domain.co.nz out_uri=sip:6499777777@203.89.nnn.nnn via_cnt==1" U 147.202.nnn.nnn:5060 -> 203.89.nnn.nnn:5060 INVITE sip:6499777777@203.89.nnn.nnn SIP/2.0 Record-Route: <sip:147.202.nnn.nnn;ftag=as3f0f7d93;lr=on> Via: SIP/2.0/UDP 147.202.nnn.nnn;branch=z9hG4bKd5ab.736d6085.0 Via: SIP/2.0/UDP 202.180.nnn.nnn:5060;branch=z9hG4bK0b505d2b;rport=5060 From: "6494444444" <sip:6494444444@202.180.nnn.nnn>;tag=as3f0f7d93 To: <sip:6499777777@domain.co.nz> Contact: <sip:6494444444@202.180.nnn.nnn> Call-ID: 2f573abd3cd80bd369495e322ec5ab4a(a)202.180.nnn.nnn CSeq: 102 INVITE User-Agent: Asterisk PBX Max-Forwards: 69 Date: Mon, 02 Apr 2007 02:53:24 GMT Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY Content-Type: application/sdp Content-Length: 336 v=0 o=root 8802 8802 IN IP4 202.180.nnn.nnn s=session c=IN IP4 202.180.nnn.nnn t=0 0 m=audio 35268 RTP/AVP 18 97 3 0 8 101 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:97 iLBC/8000 a=rtpmap:3 GSM/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=silenceSupp:off - - - - U 147.202.nnn.nnn:5060 -> 203.89.nnn.nnn:5060 INVITE sip:6499777777@203.89.nnn.nnn SIP/2.0 Record-Route: <sip:147.202.nnn.nnn;ftag=as3f0f7d93;lr=on> Via: SIP/2.0/UDP 147.202.nnn.nnn;branch=z9hG4bKd5ab.736d6085.0 Via: SIP/2.0/UDP 202.180.nnn.nnn:5060;branch=z9hG4bK0b505d2b;rport=5060 From: "6494444444" <sip:6494444444@202.180.nnn.nnn>;tag=as3f0f7d93 To: <sip:6499777777@domain.co.nz> Contact: <sip:6494444444@202.180.nnn.nnn> Call-ID: 2f573abd3cd80bd369495e322ec5ab4a(a)202.180.nnn.nnn CSeq: 102 INVITE User-Agent: Asterisk PBX Max-Forwards: 69 Date: Mon, 02 Apr 2007 02:53:24 GMT Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY Content-Type: application/sdp Content-Length: 336 v=0 o=root 8802 8802 IN IP4 202.180.nnn.nnn s=session c=IN IP4 202.180.nnn.nnn t=0 0 m=audio 35268 RTP/AVP 18 97 3 0 8 101 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:97 iLBC/8000 a=rtpmap:3 GSM/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=silenceSupp:off - - - - U 203.89.nnn.nnn:5060 -> 147.202.nnn.nnn:5060 SIP/2.0 100 Trying Via: SIP/2.0/UDP 147.202.nnn.nnn;branch=z9hG4bKd5ab.736d6085.0;received=147.202.nnn.nnn Via: SIP/2.0/UDP 202.180.nnn.nnn:5060;branch=z9hG4bK0b505d2b;rport=5060 From: "6494444444" <sip:6494444444@202.180.nnn.nnn>;tag=as3f0f7d93 To: <sip:6499777777@domain.co.nz> Call-ID: 2f573abd3cd80bd369495e322ec5ab4a(a)202.180.nnn.nnn CSeq: 102 INVITE User-Agent: Asterisk PBX Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY Contact: <sip:6499777777@203.89.nnn.nnn> Content-Length: 0 U 203.89.nnn.nnn:5060 -> 147.202.nnn.nnn:5060 SIP/2.0 200 OK Via: SIP/2.0/UDP 147.202.nnn.nnn;branch=z9hG4bKd5ab.736d6085.0;received=147.202.nnn.nnn Via: SIP/2.0/UDP 202.180.nnn.nnn:5060;branch=z9hG4bK0b505d2b;rport=5060 Record-Route: <sip:147.202.nnn.nnn;ftag=as3f0f7d93;lr=on> From: "6494444444" <sip:6494444444@202.180.nnn.nnn>;tag=as3f0f7d93 To: <sip:6499777777@domain.co.nz>;tag=as060f43a9 Call-ID: 2f573abd3cd80bd369495e322ec5ab4a(a)202.180.nnn.nnn CSeq: 102 INVITE User-Agent: Asterisk PBX Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY Contact: <sip:6499777777@203.89.nnn.nnn> Content-Type: application/sdp Content-Length: 244 v=0 o=root 16300 16300 IN IP4 203.89.nnn.nnn s=session c=IN IP4 203.89.nnn.nnn t=0 0 m=audio 19952 RTP/AVP 0 8 101 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=silenceSupp:off - - - - U 147.202.nnn.nnn:5060 -> 202.180.nnn.nnn:5060 SIP/2.0 200 OK Via: SIP/2.0/UDP 202.180.nnn.nnn:5060;branch=z9hG4bK0b505d2b;rport=5060 Record-Route: <sip:147.202.nnn.nnn;ftag=as3f0f7d93;lr=on> From: "6494444444" <sip:6494444444@202.180.nnn.nnn>;tag=as3f0f7d93 To: <sip:6499777777@domain.co.nz>;tag=as060f43a9 Call-ID: 2f573abd3cd80bd369495e322ec5ab4a(a)202.180.nnn.nnn CSeq: 102 INVITE User-Agent: Asterisk PBX Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY Contact: <sip:6499777777@203.89.nnn.nnn> Content-Type: application/sdp Content-Length: 244 v=0 o=root 16300 16300 IN IP4 203.89.nnn.nnn s=session c=IN IP4 203.89.nnn.nnn t=0 0 m=audio 19952 RTP/AVP 0 8 101 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=silenceSupp:off - - - - U 203.89.nnn.nnn:5060 -> 147.202.nnn.nnn:5060 SIP/2.0 200 OK Via: SIP/2.0/UDP 147.202.nnn.nnn;branch=z9hG4bKd5ab.736d6085.0;received=147.202.nnn.nnn Via: SIP/2.0/UDP 202.180.nnn.nnn:5060;branch=z9hG4bK0b505d2b;rport=5060 Record-Route: <sip:147.202.nnn.nnn;ftag=as3f0f7d93;lr=on> From: "6494444444" <sip:6494444444@202.180.nnn.nnn>;tag=as3f0f7d93 To: <sip:6499777777@domain.co.nz>;tag=as060f43a9 Call-ID: 2f573abd3cd80bd369495e322ec5ab4a(a)202.180.nnn.nnn CSeq: 102 INVITE User-Agent: Asterisk PBX Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY Contact: <sip:6499777777@203.89.nnn.nnn> Content-Type: application/sdp Content-Length: 244 v=0 o=root 16300 16301 IN IP4 203.89.nnn.nnn s=session c=IN IP4 203.89.nnn.nnn t=0 0 m=audio 19952 RTP/AVP 0 8 101 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=silenceSupp:off - - - - U 147.202.nnn.nnn:5060 -> 202.180.nnn.nnn:5060 SIP/2.0 200 OK Via: SIP/2.0/UDP 202.180.nnn.nnn:5060;branch=z9hG4bK0b505d2b;rport=5060 Record-Route: <sip:147.202.nnn.nnn;ftag=as3f0f7d93;lr=on> From: "6494444444" <sip:6494444444@202.180.nnn.nnn>;tag=as3f0f7d93 To: <sip:6499777777@domain.co.nz>;tag=as060f43a9 Call-ID: 2f573abd3cd80bd369495e322ec5ab4a(a)202.180.nnn.nnn CSeq: 102 INVITE User-Agent: Asterisk PBX Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY Contact: <sip:6499777777@203.89.nnn.nnn> Content-Type: application/sdp Content-Length: 244 v=0 o=root 16300 16301 IN IP4 203.89.nnn.nnn s=session c=IN IP4 203.89.nnn.nnn t=0 0 m=audio 19952 RTP/AVP 0 8 101 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=silenceSupp:off - - - - U 202.180.nnn.nnn:5060 -> 147.202.nnn.nnn:5060 ACK sip:6499777777@203.89.nnn.nnn SIP/2.0 Via: SIP/2.0/UDP 202.180.nnn.nnn:5060;branch=z9hG4bK013cd54d;rport Route: <sip:147.202.nnn.nnn;ftag=as3f0f7d93;lr=on> From: "6494444444" <sip:6494444444@202.180.nnn.nnn>;tag=as3f0f7d93 To: <sip:6499777777@domain.co.nz>;tag=as060f43a9 Contact: <sip:6494444444@202.180.nnn.nnn> Call-ID: 2f573abd3cd80bd369495e322ec5ab4a(a)202.180.nnn.nnn CSeq: 102 ACK User-Agent: Asterisk PBX Max-Forwards: 70 Content-Length: 0 U 147.202.nnn.nnn:5060 -> 203.89.nnn.nnn:5060 ACK sip:6499777777@203.89.nnn.nnn SIP/2.0 Record-Route: <sip:147.202.nnn.nnn;ftag=as3f0f7d93;lr=on> Via: SIP/2.0/UDP 147.202.nnn.nnn;branch=0 Via: SIP/2.0/UDP 202.180.nnn.nnn:5060;branch=z9hG4bK013cd54d;rport=5060 From: "6494444444" <sip:6494444444@202.180.nnn.nnn>;tag=as3f0f7d93 To: <sip:6499777777@domain.co.nz>;tag=as060f43a9 Contact: <sip:6494444444@202.180.nnn.nnn> Call-ID: 2f573abd3cd80bd369495e322ec5ab4a(a)202.180.nnn.nnn CSeq: 102 ACK User-Agent: Asterisk PBX Max-Forwards: 69 Content-Length: 0 U 202.180.nnn.nnn:5060 -> 147.202.nnn.nnn:5060 ACK sip:6499777777@203.89.nnn.nnn SIP/2.0 Via: SIP/2.0/UDP 202.180.nnn.nnn:5060;branch=z9hG4bK54b95a19;rport Route: <sip:147.202.nnn.nnn;ftag=as3f0f7d93;lr=on> From: "6494444444" <sip:6494444444@202.180.nnn.nnn>;tag=as3f0f7d93 To: <sip:6499777777@domain.co.nz>;tag=as060f43a9 Contact: <sip:6494444444@202.180.nnn.nnn> Call-ID: 2f573abd3cd80bd369495e322ec5ab4a(a)202.180.nnn.nnn CSeq: 102 ACK User-Agent: Asterisk PBX Max-Forwards: 70 Content-Length: 0 U 147.202.nnn.nnn:5060 -> 203.89.nnn.nnn:5060 ACK sip:6499777777@203.89.nnn.nnn SIP/2.0 Record-Route: <sip:147.202.nnn.nnn;ftag=as3f0f7d93;lr=on> Via: SIP/2.0/UDP 147.202.nnn.nnn;branch=0 Via: SIP/2.0/UDP 202.180.nnn.nnn:5060;branch=z9hG4bK54b95a19;rport=5060 From: "6494444444" <sip:6494444444@202.180.nnn.nnn>;tag=as3f0f7d93 To: <sip:6499777777@domain.co.nz>;tag=as060f43a9 Contact: <sip:6494444444@202.180.nnn.nnn> Call-ID: 2f573abd3cd80bd369495e322ec5ab4a(a)202.180.nnn.nnn CSeq: 102 ACK User-Agent: Asterisk PBX Max-Forwards: 69 Content-Length: 0 U 203.89.nnn.nnn:5060 -> 147.202.nnn.nnn:5060 SIP/2.0 200 OK Via: SIP/2.0/UDP 147.202.nnn.nnn;branch=z9hG4bKd5ab.736d6085.0;received=147.202.nnn.nnn Via: SIP/2.0/UDP 202.180.nnn.nnn:5060;branch=z9hG4bK0b505d2b;rport=5060 Record-Route: <sip:147.202.nnn.nnn;ftag=as3f0f7d93;lr=on> From: "6494444444" <sip:6494444444@202.180.nnn.nnn>;tag=as3f0f7d93 To: <sip:6499777777@domain.co.nz>;tag=as060f43a9 Call-ID: 2f573abd3cd80bd369495e322ec5ab4a(a)202.180.nnn.nnn CSeq: 102 INVITE User-Agent: Asterisk PBX Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY Contact: <sip:6499777777@203.89.nnn.nnn> Content-Type: application/sdp Content-Length: 244 v=0 o=root 16300 16300 IN IP4 203.89.nnn.nnn s=session c=IN IP4 203.89.nnn.nnn t=0 0 m=audio 19952 RTP/AVP 0 8 101 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=silenceSupp:off - - - - U 147.202.nnn.nnn:5060 -> 202.180.nnn.nnn:5060 SIP/2.0 200 OK Via: SIP/2.0/UDP 202.180.nnn.nnn:5060;branch=z9hG4bK0b505d2b;rport=5060 Record-Route: <sip:147.202.nnn.nnn;ftag=as3f0f7d93;lr=on> From: "6494444444" <sip:6494444444@202.180.nnn.nnn>;tag=as3f0f7d93 To: <sip:6499777777@domain.co.nz>;tag=as060f43a9 Call-ID: 2f573abd3cd80bd369495e322ec5ab4a(a)202.180.nnn.nnn CSeq: 102 INVITE User-Agent: Asterisk PBX Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY Contact: <sip:6499777777@203.89.nnn.nnn> Content-Type: application/sdp Content-Length: 244 v=0 o=root 16300 16300 IN IP4 203.89.nnn.nnn s=session c=IN IP4 203.89.nnn.nnn t=0 0 m=audio 19952 RTP/AVP 0 8 101 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=silenceSupp:off - - - - U 202.180.nnn.nnn:5060 -> 147.202.nnn.nnn:5060 ACK sip:6499777777@203.89.nnn.nnn SIP/2.0 Via: SIP/2.0/UDP 202.180.nnn.nnn:5060;branch=z9hG4bK46a352b9;rport Route: <sip:147.202.nnn.nnn;ftag=as3f0f7d93;lr=on> From: "6494444444" <sip:6494444444@202.180.nnn.nnn>;tag=as3f0f7d93 To: <sip:6499777777@domain.co.nz>;tag=as060f43a9 Contact: <sip:6494444444@202.180.nnn.nnn> Call-ID: 2f573abd3cd80bd369495e322ec5ab4a(a)202.180.nnn.nnn CSeq: 102 ACK User-Agent: Asterisk PBX Max-Forwards: 70 Content-Length: 0 U 147.202.nnn.nnn:5060 -> 203.89.nnn.nnn:5060 ACK sip:6499777777@203.89.nnn.nnn SIP/2.0 Record-Route: <sip:147.202.nnn.nnn;ftag=as3f0f7d93;lr=on> Via: SIP/2.0/UDP 147.202.nnn.nnn;branch=0 Via: SIP/2.0/UDP 202.180.nnn.nnn:5060;branch=z9hG4bK46a352b9;rport=5060 From: "6494444444" <sip:6494444444@202.180.nnn.nnn>;tag=as3f0f7d93 To: <sip:6499777777@domain.co.nz>;tag=as060f43a9 Contact: <sip:6494444444@202.180.nnn.nnn> Call-ID: 2f573abd3cd80bd369495e322ec5ab4a(a)202.180.nnn.nnn CSeq: 102 ACK User-Agent: Asterisk PBX Max-Forwards: 69 Content-Length: 0 U 203.89.nnn.nnn:5060 -> 147.202.nnn.nnn:5060 SIP/2.0 200 OK Via: SIP/2.0/UDP 147.202.nnn.nnn;branch=z9hG4bKd5ab.736d6085.0;received=147.202.nnn.nnn Via: SIP/2.0/UDP 202.180.nnn.nnn:5060;branch=z9hG4bK0b505d2b;rport=5060 Record-Route: <sip:147.202.nnn.nnn;ftag=as3f0f7d93;lr=on> From: "6494444444" <sip:6494444444@202.180.nnn.nnn>;tag=as3f0f7d93 To: <sip:6499777777@domain.co.nz>;tag=as060f43a9 Call-ID: 2f573abd3cd80bd369495e322ec5ab4a(a)202.180.nnn.nnn CSeq: 102 INVITE User-Agent: Asterisk PBX Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY Contact: <sip:6499777777@203.89.nnn.nnn> Content-Type: application/sdp Content-Length: 244 v=0 o=root 16300 16300 IN IP4 203.89.nnn.nnn s=session c=IN IP4 203.89.nnn.nnn t=0 0 m=audio 19952 RTP/AVP 0 8 101 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=silenceSupp:off - - - - U 147.202.nnn.nnn:5060 -> 202.180.nnn.nnn:5060 SIP/2.0 200 OK Via: SIP/2.0/UDP 202.180.nnn.nnn:5060;branch=z9hG4bK0b505d2b;rport=5060 Record-Route: <sip:147.202.nnn.nnn;ftag=as3f0f7d93;lr=on> From: "6494444444" <sip:6494444444@202.180.nnn.nnn>;tag=as3f0f7d93 To: <sip:6499777777@domain.co.nz>;tag=as060f43a9 Call-ID: 2f573abd3cd80bd369495e322ec5ab4a(a)202.180.nnn.nnn CSeq: 102 INVITE User-Agent: Asterisk PBX Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY Contact: <sip:6499777777@203.89.nnn.nnn> Content-Type: application/sdp Content-Length: 244 v=0 o=root 16300 16300 IN IP4 203.89.nnn.nnn s=session c=IN IP4 203.89.nnn.nnn t=0 0 m=audio 19952 RTP/AVP 0 8 101 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=silenceSupp:off - - - - U 202.180.nnn.nnn:5060 -> 147.202.nnn.nnn:5060 ACK sip:6499777777@203.89.nnn.nnn SIP/2.0 Via: SIP/2.0/UDP 202.180.nnn.nnn:5060;branch=z9hG4bK2da46c51;rport Route: <sip:147.202.nnn.nnn;ftag=as3f0f7d93;lr=on> From: "6494444444" <sip:6494444444@202.180.nnn.nnn>;tag=as3f0f7d93 To: <sip:6499777777@domain.co.nz>;tag=as060f43a9 Contact: <sip:6494444444@202.180.nnn.nnn> Call-ID: 2f573abd3cd80bd369495e322ec5ab4a(a)202.180.nnn.nnn CSeq: 102 ACK User-Agent: Asterisk PBX Max-Forwards: 70 Content-Length: 0 U 147.202.nnn.nnn:5060 -> 203.89.nnn.nnn:5060 ACK sip:6499777777@203.89.nnn.nnn SIP/2.0 Record-Route: <sip:147.202.nnn.nnn;ftag=as3f0f7d93;lr=on> Via: SIP/2.0/UDP 147.202.nnn.nnn;branch=0 Via: SIP/2.0/UDP 202.180.nnn.nnn:5060;branch=z9hG4bK2da46c51;rport=5060 From: "6494444444" <sip:6494444444@202.180.nnn.nnn>;tag=as3f0f7d93 To: <sip:6499777777@domain.co.nz>;tag=as060f43a9 Contact: <sip:6494444444@202.180.nnn.nnn> Call-ID: 2f573abd3cd80bd369495e322ec5ab4a(a)202.180.nnn.nnn CSeq: 102 ACK User-Agent: Asterisk PBX Max-Forwards: 69 Content-Length: 0 U 203.89.nnn.nnn:5060 -> 147.202.nnn.nnn:5060 SIP/2.0 200 OK Via: SIP/2.0/UDP 147.202.nnn.nnn;branch=z9hG4bKd5ab.736d6085.0;received=147.202.nnn.nnn Via: SIP/2.0/UDP 202.180.nnn.nnn:5060;branch=z9hG4bK0b505d2b;rport=5060 Record-Route: <sip:147.202.nnn.nnn;ftag=as3f0f7d93;lr=on> From: "6494444444" <sip:6494444444@202.180.nnn.nnn>;tag=as3f0f7d93 To: <sip:6499777777@domain.co.nz>;tag=as060f43a9 Call-ID: 2f573abd3cd80bd369495e322ec5ab4a(a)202.180.nnn.nnn CSeq: 102 INVITE User-Agent: Asterisk PBX Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY Contact: <sip:6499777777@203.89.nnn.nnn> Content-Type: application/sdp Content-Length: 244 v=0 o=root 16300 16300 IN IP4 203.89.nnn.nnn s=session c=IN IP4 203.89.nnn.nnn t=0 0 m=audio 19952 RTP/AVP 0 8 101 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=silenceSupp:off - - - - U 147.202.nnn.nnn:5060 -> 202.180.nnn.nnn:5060 SIP/2.0 200 OK Via: SIP/2.0/UDP 202.180.nnn.nnn:5060;branch=z9hG4bK0b505d2b;rport=5060 Record-Route: <sip:147.202.nnn.nnn;ftag=as3f0f7d93;lr=on> From: "6494444444" <sip:6494444444@202.180.nnn.nnn>;tag=as3f0f7d93 To: <sip:6499777777@domain.co.nz>;tag=as060f43a9 Call-ID: 2f573abd3cd80bd369495e322ec5ab4a(a)202.180.nnn.nnn CSeq: 102 INVITE User-Agent: Asterisk PBX Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY Contact: <sip:6499777777@203.89.nnn.nnn> Content-Type: application/sdp Content-Length: 244 v=0 o=root 16300 16300 IN IP4 203.89.nnn.nnn s=session c=IN IP4 203.89.nnn.nnn t=0 0 m=audio 19952 RTP/AVP 0 8 101 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=silenceSupp:off - - - - U 202.180.nnn.nnn:5060 -> 147.202.nnn.nnn:5060 ACK sip:6499777777@203.89.nnn.nnn SIP/2.0 Via: SIP/2.0/UDP 202.180.nnn.nnn:5060;branch=z9hG4bK23a5accc;rport Route: <sip:147.202.nnn.nnn;ftag=as3f0f7d93;lr=on> From: "6494444444" <sip:6494444444@202.180.nnn.nnn>;tag=as3f0f7d93 To: <sip:6499777777@domain.co.nz>;tag=as060f43a9 Contact: <sip:6494444444@202.180.nnn.nnn> Call-ID: 2f573abd3cd80bd369495e322ec5ab4a(a)202.180.nnn.nnn CSeq: 102 ACK User-Agent: Asterisk PBX Max-Forwards: 70 Content-Length: 0 U 147.202.nnn.nnn:5060 -> 203.89.nnn.nnn:5060 ACK sip:6499777777@203.89.nnn.nnn SIP/2.0 Record-Route: <sip:147.202.nnn.nnn;ftag=as3f0f7d93;lr=on> Via: SIP/2.0/UDP 147.202.nnn.nnn;branch=0 Via: SIP/2.0/UDP 202.180.nnn.nnn:5060;branch=z9hG4bK23a5accc;rport=5060 From: "6494444444" <sip:6494444444@202.180.nnn.nnn>;tag=as3f0f7d93 To: <sip:6499777777@domain.co.nz>;tag=as060f43a9 Contact: <sip:6494444444@202.180.nnn.nnn> Call-ID: 2f573abd3cd80bd369495e322ec5ab4a(a)202.180.nnn.nnn CSeq: 102 ACK User-Agent: Asterisk PBX Max-Forwards: 69 Content-Length: 0 U 203.89.nnn.nnn:5060 -> 147.202.nnn.nnn:5060 SIP/2.0 200 OK Via: SIP/2.0/UDP 147.202.nnn.nnn;branch=z9hG4bKd5ab.736d6085.0;received=147.202.nnn.nnn Via: SIP/2.0/UDP 202.180.nnn.nnn:5060;branch=z9hG4bK0b505d2b;rport=5060 Record-Route: <sip:147.202.nnn.nnn;ftag=as3f0f7d93;lr=on> From: "6494444444" <sip:6494444444@202.180.nnn.nnn>;tag=as3f0f7d93 To: <sip:6499777777@domain.co.nz>;tag=as060f43a9 Call-ID: 2f573abd3cd80bd369495e322ec5ab4a(a)202.180.nnn.nnn CSeq: 102 INVITE User-Agent: Asterisk PBX Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY Contact: <sip:6499777777@203.89.nnn.nnn> Content-Type: application/sdp Content-Length: 244 v=0 o=root 16300 16300 IN IP4 203.89.nnn.nnn s=session c=IN IP4 203.89.nnn.nnn t=0 0 m=audio 19952 RTP/AVP 0 8 101 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=silenceSupp:off - - - - U 147.202.nnn.nnn:5060 -> 202.180.nnn.nnn:5060 SIP/2.0 200 OK Via: SIP/2.0/UDP 202.180.nnn.nnn:5060;branch=z9hG4bK0b505d2b;rport=5060 Record-Route: <sip:147.202.nnn.nnn;ftag=as3f0f7d93;lr=on> From: "6494444444" <sip:6494444444@202.180.nnn.nnn>;tag=as3f0f7d93 To: <sip:6499777777@domain.co.nz>;tag=as060f43a9 Call-ID: 2f573abd3cd80bd369495e322ec5ab4a(a)202.180.nnn.nnn CSeq: 102 INVITE User-Agent: Asterisk PBX Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY Contact: <sip:6499777777@203.89.nnn.nnn> Content-Type: application/sdp Content-Length: 244 v=0 o=root 16300 16300 IN IP4 203.89.nnn.nnn s=session c=IN IP4 203.89.nnn.nnn t=0 0 m=audio 19952 RTP/AVP 0 8 101 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=silenceSupp:off - - - - U 202.180.nnn.nnn:5060 -> 147.202.nnn.nnn:5060 ACK sip:6499777777@203.89.nnn.nnn SIP/2.0 Via: SIP/2.0/UDP 202.180.nnn.nnn:5060;branch=z9hG4bK153c7273;rport Route: <sip:147.202.nnn.nnn;ftag=as3f0f7d93;lr=on> From: "6494444444" <sip:6494444444@202.180.nnn.nnn>;tag=as3f0f7d93 To: <sip:6499777777@domain.co.nz>;tag=as060f43a9 Contact: <sip:6494444444@202.180.nnn.nnn> Call-ID: 2f573abd3cd80bd369495e322ec5ab4a(a)202.180.nnn.nnn CSeq: 102 ACK User-Agent: Asterisk PBX Max-Forwards: 70 Content-Length: 0 U 147.202.nnn.nnn:5060 -> 203.89.nnn.nnn:5060 ACK sip:6499777777@203.89.nnn.nnn SIP/2.0 Record-Route: <sip:147.202.nnn.nnn;ftag=as3f0f7d93;lr=on> Via: SIP/2.0/UDP 147.202.nnn.nnn;branch=0 Via: SIP/2.0/UDP 202.180.nnn.nnn:5060;branch=z9hG4bK153c7273;rport=5060 From: "6494444444" <sip:6494444444@202.180.nnn.nnn>;tag=as3f0f7d93 To: <sip:6499777777@domain.co.nz>;tag=as060f43a9 Contact: <sip:6494444444@202.180.nnn.nnn> Call-ID: 2f573abd3cd80bd369495e322ec5ab4a(a)202.180.nnn.nnn CSeq: 102 ACK User-Agent: Asterisk PBX Max-Forwards: 69 Content-Length: 0 U 203.89.nnn.nnn:5060 -> 147.202.nnn.nnn:5060 SIP/2.0 200 OK Via: SIP/2.0/UDP 147.202.nnn.nnn;branch=z9hG4bKd5ab.736d6085.0;received=147.202.nnn.nnn Via: SIP/2.0/UDP 202.180.nnn.nnn:5060;branch=z9hG4bK0b505d2b;rport=5060 Record-Route: <sip:147.202.nnn.nnn;ftag=as3f0f7d93;lr=on> From: "6494444444" <sip:6494444444@202.180.nnn.nnn>;tag=as3f0f7d93 To: <sip:6499777777@domain.co.nz>;tag=as060f43a9 Call-ID: 2f573abd3cd80bd369495e322ec5ab4a(a)202.180.nnn.nnn CSeq: 102 INVITE User-Agent: Asterisk PBX Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY Contact: <sip:6499777777@203.89.nnn.nnn> Content-Type: application/sdp Content-Length: 244 v=0 o=root 16300 16300 IN IP4 203.89.nnn.nnn s=session c=IN IP4 203.89.nnn.nnn t=0 0 m=audio 19952 RTP/AVP 0 8 101 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=silenceSupp:off - - - - U 147.202.nnn.nnn:5060 -> 202.180.nnn.nnn:5060 SIP/2.0 200 OK Via: SIP/2.0/UDP 202.180.nnn.nnn:5060;branch=z9hG4bK0b505d2b;rport=5060 Record-Route: <sip:147.202.nnn.nnn;ftag=as3f0f7d93;lr=on> From: "6494444444" <sip:6494444444@202.180.nnn.nnn>;tag=as3f0f7d93 To: <sip:6499777777@domain.co.nz>;tag=as060f43a9 Call-ID: 2f573abd3cd80bd369495e322ec5ab4a(a)202.180.nnn.nnn CSeq: 102 INVITE User-Agent: Asterisk PBX Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY Contact: <sip:6499777777@203.89.nnn.nnn> Content-Type: application/sdp Content-Length: 244 v=0 o=root 16300 16300 IN IP4 203.89.nnn.nnn s=session c=IN IP4 203.89.nnn.nnn t=0 0 m=audio 19952 RTP/AVP 0 8 101 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=silenceSupp:off - - - - U 202.180.nnn.nnn:5060 -> 147.202.nnn.nnn:5060 ACK sip:6499777777@203.89.nnn.nnn SIP/2.0 Via: SIP/2.0/UDP 202.180.nnn.nnn:5060;branch=z9hG4bK01e676a5;rport Route: <sip:147.202.nnn.nnn;ftag=as3f0f7d93;lr=on> From: "6494444444" <sip:6494444444@202.180.nnn.nnn>;tag=as3f0f7d93 To: <sip:6499777777@domain.co.nz>;tag=as060f43a9 Contact: <sip:6494444444@202.180.nnn.nnn> Call-ID: 2f573abd3cd80bd369495e322ec5ab4a(a)202.180.nnn.nnn CSeq: 102 ACK User-Agent: Asterisk PBX Max-Forwards: 70 Content-Length: 0 U 147.202.nnn.nnn:5060 -> 203.89.nnn.nnn:5060 ACK sip:6499777777@203.89.nnn.nnn SIP/2.0 Record-Route: <sip:147.202.nnn.nnn;ftag=as3f0f7d93;lr=on> Via: SIP/2.0/UDP 147.202.nnn.nnn;branch=0 Via: SIP/2.0/UDP 202.180.nnn.nnn:5060;branch=z9hG4bK01e676a5;rport=5060 From: "6494444444" <sip:6494444444@202.180.nnn.nnn>;tag=as3f0f7d93 To: <sip:6499777777@domain.co.nz>;tag=as060f43a9 Contact: <sip:6494444444@202.180.nnn.nnn> Call-ID: 2f573abd3cd80bd369495e322ec5ab4a(a)202.180.nnn.nnn CSeq: 102 ACK User-Agent: Asterisk PBX Max-Forwards: 69 Content-Length: 0 U 203.89.nnn.nnn:5060 -> 147.202.nnn.nnn:5060 SIP/2.0 200 OK Via: SIP/2.0/UDP 147.202.nnn.nnn;branch=z9hG4bKd5ab.736d6085.0;received=147.202.nnn.nnn Via: SIP/2.0/UDP 202.180.nnn.nnn:5060;branch=z9hG4bK0b505d2b;rport=5060 Record-Route: <sip:147.202.nnn.nnn;ftag=as3f0f7d93;lr=on> From: "6494444444" <sip:6494444444@202.180.nnn.nnn>;tag=as3f0f7d93 To: <sip:6499777777@domain.co.nz>;tag=as060f43a9 Call-ID: 2f573abd3cd80bd369495e322ec5ab4a(a)202.180.nnn.nnn CSeq: 102 INVITE User-Agent: Asterisk PBX Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY Contact: <sip:6499777777@203.89.nnn.nnn> Content-Type: application/sdp Content-Length: 244 v=0 o=root 16300 16300 IN IP4 203.89.nnn.nnn s=session c=IN IP4 203.89.nnn.nnn t=0 0 m=audio 19952 RTP/AVP 0 8 101 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=silenceSupp:off - - - - U 147.202.nnn.nnn:5060 -> 202.180.nnn.nnn:5060 SIP/2.0 200 OK Via: SIP/2.0/UDP 202.180.nnn.nnn:5060;branch=z9hG4bK0b505d2b;rport=5060 Record-Route: <sip:147.202.nnn.nnn;ftag=as3f0f7d93;lr=on> From: "6494444444" <sip:6494444444@202.180.nnn.nnn>;tag=as3f0f7d93 To: <sip:6499777777@domain.co.nz>;tag=as060f43a9 Call-ID: 2f573abd3cd80bd369495e322ec5ab4a(a)202.180.nnn.nnn CSeq: 102 INVITE User-Agent: Asterisk PBX Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY Contact: <sip:6499777777@203.89.nnn.nnn> Content-Type: application/sdp Content-Length: 244 v=0 o=root 16300 16300 IN IP4 203.89.nnn.nnn s=session c=IN IP4 203.89.nnn.nnn t=0 0 m=audio 19952 RTP/AVP 0 8 101 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=silenceSupp:off - - - - U 202.180.nnn.nnn:5060 -> 147.202.nnn.nnn:5060 ACK sip:6499777777@203.89.nnn.nnn SIP/2.0 Via: SIP/2.0/UDP 202.180.nnn.nnn:5060;branch=z9hG4bK0a0ddae8;rport Route: <sip:147.202.nnn.nnn;ftag=as3f0f7d93;lr=on> From: "6494444444" <sip:6494444444@202.180.nnn.nnn>;tag=as3f0f7d93 To: <sip:6499777777@domain.co.nz>;tag=as060f43a9 Contact: <sip:6494444444@202.180.nnn.nnn> Call-ID: 2f573abd3cd80bd369495e322ec5ab4a(a)202.180.nnn.nnn CSeq: 102 ACK User-Agent: Asterisk PBX Max-Forwards: 70 Content-Length: 0 U 147.202.nnn.nnn:5060 -> 203.89.nnn.nnn:5060 ACK sip:6499777777@203.89.nnn.nnn SIP/2.0 Record-Route: <sip:147.202.nnn.nnn;ftag=as3f0f7d93;lr=on> Via: SIP/2.0/UDP 147.202.nnn.nnn;branch=0 Via: SIP/2.0/UDP 202.180.nnn.nnn:5060;branch=z9hG4bK0a0ddae8;rport=5060 From: "6494444444" <sip:6494444444@202.180.nnn.nnn>;tag=as3f0f7d93 To: <sip:6499777777@domain.co.nz>;tag=as060f43a9 Contact: <sip:6494444444@202.180.nnn.nnn> Call-ID: 2f573abd3cd80bd369495e322ec5ab4a(a)202.180.nnn.nnn CSeq: 102 ACK User-Agent: Asterisk PBX Max-Forwards: 69 Content-Length: 0 U 202.180.nnn.nnn:5060 -> 147.202.nnn.nnn:5060 BYE sip:6499777777@203.89.nnn.nnn SIP/2.0 Via: SIP/2.0/UDP 202.180.nnn.nnn:5060;branch=z9hG4bK12646817;rport Route: <sip:147.202.nnn.nnn;ftag=as3f0f7d93;lr=on> From: "6494444444" <sip:6494444444@202.180.nnn.nnn>;tag=as3f0f7d93 To: <sip:6499777777@domain.co.nz>;tag=as060f43a9 Contact: <sip:6494444444@202.180.nnn.nnn> Call-ID: 2f573abd3cd80bd369495e322ec5ab4a(a)202.180.nnn.nnn CSeq: 103 BYE User-Agent: Asterisk PBX Max-Forwards: 70 Content-Length: 0 U 147.202.nnn.nnn:5060 -> 203.89.nnn.nnn:5060 BYE sip:6499777777@203.89.nnn.nnn SIP/2.0 Record-Route: <sip:147.202.nnn.nnn;ftag=as3f0f7d93;lr=on> Via: SIP/2.0/UDP 147.202.nnn.nnn;branch=z9hG4bKe5ab.311dd295.0 Via: SIP/2.0/UDP 202.180.nnn.nnn:5060;branch=z9hG4bK12646817;rport=5060 From: "6494444444" <sip:6494444444@202.180.nnn.nnn>;tag=as3f0f7d93 To: <sip:6499777777@domain.co.nz>;tag=as060f43a9 Contact: <sip:6494444444@202.180.nnn.nnn> Call-ID: 2f573abd3cd80bd369495e322ec5ab4a(a)202.180.nnn.nnn CSeq: 103 BYE User-Agent: Asterisk PBX Max-Forwards: 69 Content-Length: 0 U 203.89.nnn.nnn:5060 -> 147.202.nnn.nnn:5060 SIP/2.0 481 Call leg/transaction does not exist Via: SIP/2.0/UDP 147.202.nnn.nnn;branch=z9hG4bKe5ab.311dd295.0;received=147.202.nnn.nnn Via: SIP/2.0/UDP 202.180.nnn.nnn:5060;branch=z9hG4bK12646817;rport=5060 From: "6494444444" <sip:6494444444@202.180.nnn.nnn>;tag=as3f0f7d93 To: <sip:6499777777@domain.co.nz>;tag=as060f43a9 Call-ID: 2f573abd3cd80bd369495e322ec5ab4a(a)202.180.nnn.nnn CSeq: 103 BYE User-Agent: Asterisk PBX Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY Content-Length: 0 U 147.202.nnn.nnn:5060 -> 202.180.nnn.nnn:5060 SIP/2.0 481 Call leg/transaction does not exist Via: SIP/2.0/UDP 202.180.nnn.nnn:5060;branch=z9hG4bK12646817;rport=5060 From: "6494444444" <sip:6494444444@202.180.nnn.nnn>;tag=as3f0f7d93 To: <sip:6499777777@domain.co.nz>;tag=as060f43a9 Call-ID: 2f573abd3cd80bd369495e322ec5ab4a(a)202.180.nnn.nnn CSeq: 103 BYE User-Agent: Asterisk PBX Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY Content-Length: 0 Thanks Cameron

1 0

[Serusers] Unreacheable destination problems
by Amanda Mattiuz 01 Apr '07

01 Apr '07

Hello! I'm using SER + rtpproxy, but altough the NAT problem seems to be solved, I get no audio ... analysing the traffic with ethereal, I realized that the traffic going from the proxy to the UAs never arrives (ICMP unreacheable destination)... I assume it is because the users have their ports blocked, is that correct? I changed the rtpproxy port range (PORT_MIN and PORT_MAX ) to lower ports, but still I got the same messages... Does anybody knows anything that can be done by me in terms of configurations of the rtpproxy or ser.cfg or whatever, given the fact that I don't have power to open the ports??..... Thanks, Amanda -- ------------------------------------------------------------------- Amanda Remes Mattiuz amattiuz(a)gmail.com

1 0

[Users] Re: Digest Authentication Problem with header parsing problem
by Abdurrahman Sahin 01 Apr '07

01 Apr '07

hi all; i solved my problem; i was setting my server's ip address as the realm, and i guess providing an ip address as the realm causes problem. so i changed the realm name to a domain name , then set a sip proxy address for the client i also changed SIP_DOMAIN to a domain name. ----- Original Message ----- From: Abdurrahman Sahin To: users(a)openser.org Sent: Sunday, April 01, 2007 3:00 PM Subject: Digest Authentication Problem with header parsing problem hi all; i'm trying to activate digest authentication with mysql, but i see a strange parsing error in the logs. here is my logser log ================== Apr 1 13:39:04 testsrv200 /usr/local/sbin/openser[577]: New request - M=REGISTER RURI=sip:server_public_ip_address F=<null> T=sip:apo@server_public_ip_address IP=ua_public_ip_address ID=NWYyZGNjMWRjYjFlNTk5YjlhMjE5ODA4MWQ0ZGFiNTY. Apr 1 13:39:04 testsrv200 /usr/local/sbin/openser[577]: DEBUG:maxfwd:is_maxfwd_present: value = 70 Apr 1 13:39:04 testsrv200 /usr/local/sbin/openser[577]: parse_headers: flags=200 Apr 1 13:39:04 testsrv200 /usr/local/sbin/openser[577]: get_hdr_field: cseq <CSeq>: <1> <REGISTER> Apr 1 13:39:04 testsrv200 /usr/local/sbin/openser[577]: DEBUG: get_hdr_body : content_length=0 Apr 1 13:39:04 testsrv200 /usr/local/sbin/openser[577]: found end of header Apr 1 13:39:04 testsrv200 /usr/local/sbin/openser[577]: find_first_route: No Route headers found Apr 1 13:39:04 testsrv200 /usr/local/sbin/openser[577]: loose_route: There is no Route HF Apr 1 13:39:04 testsrv200 /usr/local/sbin/openser[577]: parse_headers: flags=ffffffffffffffff Apr 1 13:39:04 testsrv200 /usr/local/sbin/openser[577]: check_via_address(ua_public_ip_address, ua_public_ip_address, 0) Apr 1 13:39:04 testsrv200 /usr/local/sbin/openser[577]: parse_headers: flags=4000 Apr 1 13:39:04 testsrv200 /usr/local/sbin/openser[577]: pre_auth(): Credentials with given realm not found ] in status 6: <<"apo"<sip:apo@ua_public_ip_address;tag=5d692f7d>> . R: parse_to : unexpected char [ Apr 1 13:39:05 testsrv200 /usr/local/sbin/openser[577]: ERROR:parse_from_header: bad from header Apr 1 13:39:05 testsrv200 /usr/local/sbin/openser[577]: set_err_info: ec: 1, el: 3, ei: 'error parsing From' Apr 1 13:39:05 testsrv200 /usr/local/sbin/openser[577]: xl_get_from_attr: ERROR cannot parse FROM header Apr 1 13:39:05 testsrv200 /usr/local/sbin/openser[577]: Register authentication failed - M=REGISTER RURI=sip:server_public_ip_address F=<null> T=sip:apo@server_public_ip_address IP=ua_public_ip_address ID=NWYyZGNjMWRjYjFlNTk5YjlhMjE5ODA4MWQ0ZGFiNTY. Apr 1 13:39:05 testsrv200 /usr/local/sbin/openser[577]: build_auth_hf(): 'WWW-Authenticate: Digest realm="server_public_ip_address", nonce ' 60f8cf5a7a5eb40c26f914280272b51f58caaa7" Apr 1 13:39:05 testsrv200 /usr/local/sbin/openser[577]: parse_headers: flags=ffffffffffffffff Apr 1 13:39:05 testsrv200 /usr/local/sbin/openser[577]: check_via_address(ua_public_ip_address, ua_public_ip_address, 0) Apr 1 13:39:05 testsrv200 /usr/local/sbin/openser[577]: DEBUG:destroy_avp_list: destroying list (nil) Apr 1 13:39:05 testsrv200 /usr/local/sbin/openser[577]: receive_msg: cleaning up and sip msg received at the server side ============================== U ua_public_ip_address:28443 -> 192.168.200.2:5060 REGISTER sip:server_public_ip_address SIP/2.0. Via: SIP/2.0/UDP ua_public_ip_address:28443;branch=z9hG4bK-d87543-08523511e5151c18-1--d87543-;rport. Max-Forwards: 70. Contact: <sip:apo@ua_public_ip_address:28443;rinstance=1ff3024a97431241>. To: "apo"<sip:apo@server_public_ip_address>. From: "apo"<sip:apo@ua_public_ip_address;tag=5d692f7d. Call-ID: NWYyZGNjMWRjYjFlNTk5YjlhMjE5ODA4MWQ0ZGFiNTY.. CSeq: 1 REGISTER. Expires: 3600. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO. User-Agent: X-Lite release 1006e stamp 34025. Content-Length: 0. . # U 192.168.200.2:5060 -> ua_public_ip_address:28443 SIP/2.0 100 Trying. Via: SIP/2.0/UDP ua_public_ip_address:28443;branch=z9hG4bK-d87543-08523511e5151c18-1--d87543-;rport=28443. To: "apo"<sip:apo@server_public_ip_address>. From: "apo"<sip:apo@ua_public_ip_address;tag=5d692f7d. Call-ID: NWYyZGNjMWRjYjFlNTk5YjlhMjE5ODA4MWQ0ZGFiNTY.. CSeq: 1 REGISTER. Server: OpenSER (1.2.0-notls (x86_64/linux)). Content-Length: 0. . # U 192.168.200.2:5060 -> ua_public_ip_address:28443 SIP/2.0 401 Unauthorized. Via: SIP/2.0/UDP ua_public_ip_address:28443;branch=z9hG4bK-d87543-08523511e5151c18-1--d87543-;rport=28443. To: "apo"<sip:apo@server_public_ip_address>;tag=329cfeaa6ded039da25ff8cbb8668bd2.4f01. From: "apo"<sip:apo@ua_public_ip_address;tag=5d692f7d. Call-ID: NWYyZGNjMWRjYjFlNTk5YjlhMjE5ODA4MWQ0ZGFiNTY.. CSeq: 1 REGISTER. WWW-Authenticate: Digest realm="server_public_ip_address", nonce="460f8cf5a7a5eb40c26f914280272b51f58caaa7". Server: OpenSER (1.2.0-notls (x86_64/linux)). Content-Length: 0. openser.cfg file register section ======================================= # Request route 'base-route-register' ######################################################################## route[2] { sl_send_reply("100", "Trying"); if(!www_authorize("server_public_ip_address", "subscriber")) { xlog("L_INFO", "Register authentication failed - M=$rm RURI=$ru F=$fu T=$tu IP=$si ID=$ci\n"); www_challenge("server_public_ip_address", "0"); exit; } if(!check_to()) { xlog("L_INFO", "Spoofed To-URI detected - M=$rm RURI=$ru F=$fu T=$tu IP=$si ID=$ci\n"); sl_send_reply("403", "Spoofed To-URI Detected"); exit; } consume_credentials(); if(!search("^Contact:[ ]*\*") && nat_uac_test("19")) { fix_nated_register(); setbflag(6); } if(!save("location")) { xlog("L_ERR", "Saving contact failed - M=$rm RURI=$ru F=$fu T=$tu IP=$si ID=$ci\n"); sl_reply_error(); exit; } xlog("L_INFO", "Registration successful - M=$rm RURI=$ru F=$fu T=$tu IP=$si ID=$ci\n"); exit; }

1 0

[Users] Digest Authentication Problem with header parsing problem
by Abdurrahman Sahin 01 Apr '07

01 Apr '07

hi all; i'm trying to activate digest authentication with mysql, but i see a strange parsing error in the logs. here is my logser log ================== Apr 1 13:39:04 testsrv200 /usr/local/sbin/openser[577]: New request - M=REGISTER RURI=sip:server_public_ip_address F=<null> T=sip:apo@server_public_ip_address IP=ua_public_ip_address ID=NWYyZGNjMWRjYjFlNTk5YjlhMjE5ODA4MWQ0ZGFiNTY. Apr 1 13:39:04 testsrv200 /usr/local/sbin/openser[577]: DEBUG:maxfwd:is_maxfwd_present: value = 70 Apr 1 13:39:04 testsrv200 /usr/local/sbin/openser[577]: parse_headers: flags=200 Apr 1 13:39:04 testsrv200 /usr/local/sbin/openser[577]: get_hdr_field: cseq <CSeq>: <1> <REGISTER> Apr 1 13:39:04 testsrv200 /usr/local/sbin/openser[577]: DEBUG: get_hdr_body : content_length=0 Apr 1 13:39:04 testsrv200 /usr/local/sbin/openser[577]: found end of header Apr 1 13:39:04 testsrv200 /usr/local/sbin/openser[577]: find_first_route: No Route headers found Apr 1 13:39:04 testsrv200 /usr/local/sbin/openser[577]: loose_route: There is no Route HF Apr 1 13:39:04 testsrv200 /usr/local/sbin/openser[577]: parse_headers: flags=ffffffffffffffff Apr 1 13:39:04 testsrv200 /usr/local/sbin/openser[577]: check_via_address(ua_public_ip_address, ua_public_ip_address, 0) Apr 1 13:39:04 testsrv200 /usr/local/sbin/openser[577]: parse_headers: flags=4000 Apr 1 13:39:04 testsrv200 /usr/local/sbin/openser[577]: pre_auth(): Credentials with given realm not found ] in status 6: <<"apo"<sip:apo@ua_public_ip_address;tag=5d692f7d>> . R: parse_to : unexpected char [ Apr 1 13:39:05 testsrv200 /usr/local/sbin/openser[577]: ERROR:parse_from_header: bad from header Apr 1 13:39:05 testsrv200 /usr/local/sbin/openser[577]: set_err_info: ec: 1, el: 3, ei: 'error parsing From' Apr 1 13:39:05 testsrv200 /usr/local/sbin/openser[577]: xl_get_from_attr: ERROR cannot parse FROM header Apr 1 13:39:05 testsrv200 /usr/local/sbin/openser[577]: Register authentication failed - M=REGISTER RURI=sip:server_public_ip_address F=<null> T=sip:apo@server_public_ip_address IP=ua_public_ip_address ID=NWYyZGNjMWRjYjFlNTk5YjlhMjE5ODA4MWQ0ZGFiNTY. Apr 1 13:39:05 testsrv200 /usr/local/sbin/openser[577]: build_auth_hf(): 'WWW-Authenticate: Digest realm="server_public_ip_address", nonce ' 60f8cf5a7a5eb40c26f914280272b51f58caaa7" Apr 1 13:39:05 testsrv200 /usr/local/sbin/openser[577]: parse_headers: flags=ffffffffffffffff Apr 1 13:39:05 testsrv200 /usr/local/sbin/openser[577]: check_via_address(ua_public_ip_address, ua_public_ip_address, 0) Apr 1 13:39:05 testsrv200 /usr/local/sbin/openser[577]: DEBUG:destroy_avp_list: destroying list (nil) Apr 1 13:39:05 testsrv200 /usr/local/sbin/openser[577]: receive_msg: cleaning up and sip msg received at the server side ============================== U ua_public_ip_address:28443 -> 192.168.200.2:5060 REGISTER sip:server_public_ip_address SIP/2.0. Via: SIP/2.0/UDP ua_public_ip_address:28443;branch=z9hG4bK-d87543-08523511e5151c18-1--d87543-;rport. Max-Forwards: 70. Contact: <sip:apo@ua_public_ip_address:28443;rinstance=1ff3024a97431241>. To: "apo"<sip:apo@server_public_ip_address>. From: "apo"<sip:apo@ua_public_ip_address;tag=5d692f7d. Call-ID: NWYyZGNjMWRjYjFlNTk5YjlhMjE5ODA4MWQ0ZGFiNTY.. CSeq: 1 REGISTER. Expires: 3600. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO. User-Agent: X-Lite release 1006e stamp 34025. Content-Length: 0. . # U 192.168.200.2:5060 -> ua_public_ip_address:28443 SIP/2.0 100 Trying. Via: SIP/2.0/UDP ua_public_ip_address:28443;branch=z9hG4bK-d87543-08523511e5151c18-1--d87543-;rport=28443. To: "apo"<sip:apo@server_public_ip_address>. From: "apo"<sip:apo@ua_public_ip_address;tag=5d692f7d. Call-ID: NWYyZGNjMWRjYjFlNTk5YjlhMjE5ODA4MWQ0ZGFiNTY.. CSeq: 1 REGISTER. Server: OpenSER (1.2.0-notls (x86_64/linux)). Content-Length: 0. . # U 192.168.200.2:5060 -> ua_public_ip_address:28443 SIP/2.0 401 Unauthorized. Via: SIP/2.0/UDP ua_public_ip_address:28443;branch=z9hG4bK-d87543-08523511e5151c18-1--d87543-;rport=28443. To: "apo"<sip:apo@server_public_ip_address>;tag=329cfeaa6ded039da25ff8cbb8668bd2.4f01. From: "apo"<sip:apo@ua_public_ip_address;tag=5d692f7d. Call-ID: NWYyZGNjMWRjYjFlNTk5YjlhMjE5ODA4MWQ0ZGFiNTY.. CSeq: 1 REGISTER. WWW-Authenticate: Digest realm="server_public_ip_address", nonce="460f8cf5a7a5eb40c26f914280272b51f58caaa7". Server: OpenSER (1.2.0-notls (x86_64/linux)). Content-Length: 0. openser.cfg file register section ======================================= # Request route 'base-route-register' ######################################################################## route[2] { sl_send_reply("100", "Trying"); if(!www_authorize("server_public_ip_address", "subscriber")) { xlog("L_INFO", "Register authentication failed - M=$rm RURI=$ru F=$fu T=$tu IP=$si ID=$ci\n"); www_challenge("server_public_ip_address", "0"); exit; } if(!check_to()) { xlog("L_INFO", "Spoofed To-URI detected - M=$rm RURI=$ru F=$fu T=$tu IP=$si ID=$ci\n"); sl_send_reply("403", "Spoofed To-URI Detected"); exit; } consume_credentials(); if(!search("^Contact:[ ]*\*") && nat_uac_test("19")) { fix_nated_register(); setbflag(6); } if(!save("location")) { xlog("L_ERR", "Saving contact failed - M=$rm RURI=$ru F=$fu T=$tu IP=$si ID=$ci\n"); sl_reply_error(); exit; } xlog("L_INFO", "Registration successful - M=$rm RURI=$ru F=$fu T=$tu IP=$si ID=$ci\n"); exit; }

1 0

[Users] UA simulator
by Michel Bensoussan 01 Apr '07

01 Apr '07

Hello This question is for openser developers. How do you test your code? Is there a UA simulator to generate many SIP messages and tests different scenarios? Thanks and regards, Michel.

2 1

[Users] how to handle REFER 302-moved temporarily
by zm23 31 Mar '07

31 Mar '07

Hello All, I am trying to find out the proper/best way to handle REFERs coming from phone. My setup is as follows: Cisco gw openser phone gw 2 DID 1234 -----> Invite -----------------> --------------------> <----- 302 refer <--------------------- <--------------------302 moved.... new #5678 sent back After receiving new invite, openser sends it out to another gateway 5678 ----> invite ----------------------> ---------------------------------------------------> yet i am still seeing the 302 messages sent back from proxy to cisco gw. <------------------------------- -- 302 moved Call does connect to 5678 but is dropped after few seconds with only one way audio. What needs to be done so that when second invite hits proxy, there are no more 302s sent back? Should I process the 302 in proxy itself? What is the best way to make the 2nd call to 5678 so that it can be identified as a separate call? Thank you in advance for your help in this regards. -- Zahid

2 3

[Users] bad user name/uid number: -u openser
by Abdurrahman Sahin 31 Mar '07

31 Mar '07

hi all; i just received "bad user name/uid number: -u openser" error msg when i try to start openser server, after installing openser database on mysql and using openser.cfg generator scpript at sipwise.com /rtpproxy section any help about this msg is appreciated.

2 1

Re: [Users] Re: openser behind nat UAs behind NAT
by Abdurrahman Sahin 31 Mar '07

31 Mar '07

hi; when i use a stun server i can register my UAs , but i didnt like this method, i think i should be able to do it without a stun server at first, i see nathelper Module in the documentatios. is there somebody to show how to use nathelper module? ----- Original Message ----- From: raviprakash sunkara To: asahin Sent: Saturday, March 31, 2007 7:25 AM Subject: Re: [Users] Re: openser behind nat UAs behind NAT Hi Asahin, When U with OpenSER Behind NAT, I need to know that is OpenSER is Behind the NAT, which having the Firewall router/NAT. Is the OpenSER is private IP or Public IP (ISP) if the OpenSER is Having the Private IP, of that IP is should forwards the SIP port and RTP ports, and in openserclt, SIP Domain is the public ip. alias should be the Sip domain name In Register Section if!www_authorize("alias name or realm", " subscriber" ) On 3/31/07, asahin <abdsahin(a)gmail.com> wrote: hi all; i am now able to register my client with the openserver server. i used STUN server option of x-lite and stun.voipuser.org as the stun server i also set/exported SIP_DOMAIN variable to my public openser server ip address. i wonder do i have to use a stun server ? ----- Original Message ----- From: asahin To: users(a)openser.org Sent: Friday, March 30, 2007 10:26 PM Subject: openser behind nat UAs behind NAT hi; i installed and tested openser on the internal network, it was working. i tried to test it behind NAT with x-lite sip client, but it failed. i defined a port mapping on the adsl modem for udp/tcp 5060 ports to forward the packets to the openser installed machine. when i try to register to openser i received a 408 request timeout message. i guess its due to external ip of the openser server. i think i should define external ip of the modem to the openser as if it's its own ip, but dont where to define it. here is the ngrep dump at the server. U external_ip_of_ua:23975 -> 192.168.200.2:5060 REGISTER sip:external_ip_of_openser SIP/2.0..Via: SIP/2.0/UDP external_ip_of_ua:23975;branch=z9hG4bK-d87543-307c62021a71bf6d-1--d87543-;rport..Max-Forwards: 70..Contact: <sip:apo@external_ip_of_ua:23975;rinstance=6a2c0ccf1a30b6bf>..To: "apo"<sip:apo@external_ip_of_openser>..From: "apo"<sip:apo@external_ip_of_ua;tag=da6a3851..Call-ID: ODJmOTVkNmIxNjE0NWM3MWNiNTQ4ZjFlMmVkZDZmYjQ...CSeq: 1 REGISTER.. Expires: 3600..Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO..User-Agent: X-Lite release 1006e stamp 34025..Content-Length: 0....#U 192.168.200.2:5060 -> external_ip_of_openser:5060 REGISTER sip:external_ip_of_openser SIP/2.0..Via: SIP/2.0/UDP 192.168.200.2;branch=z9hG4bKd734.53940821.0..Via: SIP/2.0/UDP external_ip_of_ua:23975;branch=z9hG4bK-d87543-307c62021a71bf6d-1--d87543-;rport=23975..Max-Forwards: 69..Contact: <sip:apo@external_ip_of_ua:23975;rinstance=6a2c0ccf1a30b6bf>..To: "apo"<sip:apo@external_ip_of_openser>..From: "apo"<sip:apo@external_ip_of_ua;tag=da6a3851..Call- ID: ODJmOTVkNmIxNjE0NWM3MWNiNTQ4ZjFlMmVkZDZmYjQ...CSeq: 1 REGISTER..Expires: 3600..Allow: INVITE, ACK, CANCEL, OPTIONS, B YE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO..User-Agent: X-Lite release 1006e stamp 34025..Content-Length: 0..P-hint: out bound.... my openser.cfg file is the initial openser openser.cfg file i didnt change it. ------------- # # $Id: openser.cfg 1676 2007-02-21 13:16:34Z bogdan_iancu $ # # simple quick-start config script # Please refer to the Core CookBook at http://www.openser.org/dokuwiki/doku.php # for a explanation of possible statements, functions and parameters. # # ----------- global configuration parameters ------------------------ debug=3 # debug level (cmd line: -dddddddddd) fork=yes log_stderror=no # (cmd line: -E) children=4 # Uncomment these lines to enter debugging mode #fork=no #log_stderror=yes # port=5060 # uncomment the following lines for TLS support #disable_tls = 0 #listen = tls:your_IP:5061 #tls_verify_server = 1 #tls_verify_client = 1 #tls_require_client_certificate = 0 #tls_method = TLSv1 #tls_certificate = "/usr/local/etc/openser/tls/user/user-cert.pem" #tls_private_key = "/usr/local/etc/openser/tls/user/user-privkey.pem" #tls_ca_list = "/usr/local/etc/openser/tls/user/user-calist.pem" # ------------------ module loading ---------------------------------- #set module path mpath="/usr/local/lib64/openser/modules/" # Uncomment this if you want to use SQL database #loadmodule "mysql.so" loadmodule "sl.so" loadmodule "tm.so" loadmodule "rr.so" loadmodule "maxfwd.so" loadmodule "usrloc.so" loadmodule "registrar.so" loadmodule "textops.so" loadmodule "mi_fifo.so" # Uncomment this if you want digest authentication # mysql.so must be loaded ! #loadmodule "auth.so" #loadmodule "auth_db.so" # ----------------- setting module-specific parameters --------------- # -- mi_fifo params -- modparam("mi_fifo", "fifo_name", "/tmp/openser_fifo") # -- usrloc params -- modparam("usrloc", "db_mode", 0) # Uncomment this if you want to use SQL database # for persistent storage and comment the previous line #modparam("usrloc", "db_mode", 2) # -- auth params -- # Uncomment if you are using auth module # #modparam("auth_db", "calculate_ha1", yes) # # If you set "calculate_ha1" parameter to yes (which true in this config), # uncomment also the following parameter) # #modparam("auth_db", "password_column", "password") # -- rr params -- # add value to ;lr param to make some broken UAs happy modparam("rr", "enable_full_lr", 1) # ------------------------- request routing logic ------------------- # main routing logic route{ # initial sanity checks -- messages with # max_forwards==0, or excessively long requests if (!mf_process_maxfwd_header("10")) { sl_send_reply("483","Too Many Hops"); exit; }; if (msg:len >= 2048 ) { sl_send_reply("513", "Message too big"); exit; }; # we record-route all messages -- to make sure that # subsequent messages will go through our proxy; that's # particularly good if upstream and downstream entities # use different transport protocol if (!method=="REGISTER") record_route(); # subsequent messages withing a dialog should take the # path determined by record-routing if (loose_route()) { # mark routing logic in request append_hf("P-hint: rr-enforced\r\n"); route(1); }; if (!uri==myself) { # mark routing logic in request append_hf("P-hint: outbound\r\n"); # if you have some interdomain connections via TLS #if(uri=~"@tls_domain1.net") { # t_relay("tls:domain1.net"); # exit; #} else if(uri=~"@tls_domain2.net") { # t_relay("tls:domain2.net"); # exit; #} route(1); }; # if the request is for other domain use UsrLoc # (in case, it does not work, use the following command # with proper names and addresses in it) if (uri==myself) { if (method=="REGISTER") { # Uncomment this if you want to use digest authentication #if (!www_authorize("openser.org", "subscriber")) { # www_challenge("openser.org", "0"); # exit; #}; save("location"); exit; }; lookup("aliases"); if (!uri==myself) { append_hf("P-hint: outbound alias\r\n"); route(1); }; # native SIP destinations are handled using our USRLOC DB if (!lookup("location")) { sl_send_reply("404", "Not Found"); exit; }; append_hf("P-hint: usrloc applied\r\n"); }; route(1); } route[1] { # send it out now; use stateful forwarding as it works reliably # even for UDP2TCP if (!t_relay()) { sl_reply_error(); }; exit; } _______________________________________________ Users mailing list Users(a)openser.org http://openser.org/cgi-bin/mailman/listinfo/users -- Thanks and Regards Ravi Prakash Sunkara ravi.sunkara(a)hyperion-tech.com M:+91 9985077535 www.hyperion-tech.com Client and Parent company :- www.august-networks.com

2 1

[Users] Re: openser behind nat UAs behind NAT
by asahin 30 Mar '07

30 Mar '07

hi all; i am now able to register my client with the openserver server. i used STUN server option of x-lite and stun.voipuser.org as the stun server i also set/exported SIP_DOMAIN variable to my public openser server ip address. i wonder do i have to use a stun server ? ----- Original Message ----- From: asahin To: users(a)openser.org Sent: Friday, March 30, 2007 10:26 PM Subject: openser behind nat UAs behind NAT hi; i installed and tested openser on the internal network, it was working. i tried to test it behind NAT with x-lite sip client, but it failed. i defined a port mapping on the adsl modem for udp/tcp 5060 ports to forward the packets to the openser installed machine. when i try to register to openser i received a 408 request timeout message. i guess its due to external ip of the openser server. i think i should define external ip of the modem to the openser as if it's its own ip, but dont where to define it. here is the ngrep dump at the server. U external_ip_of_ua:23975 -> 192.168.200.2:5060 REGISTER sip:external_ip_of_openser SIP/2.0..Via: SIP/2.0/UDP external_ip_of_ua:23975;branch=z9hG4bK-d87543-307c62021a71bf6d-1--d87543-;rport..Max-Forwards: 70..Contact: <sip:apo@external_ip_of_ua:23975;rinstance=6a2c0ccf1a30b6bf>..To: "apo"<sip:apo@external_ip_of_openser>..From: "apo"<sip:apo@external_ip_of_ua;tag=da6a3851..Call-ID: ODJmOTVkNmIxNjE0NWM3MWNiNTQ4ZjFlMmVkZDZmYjQ...CSeq: 1 REGISTER.. Expires: 3600..Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO..User-Agent: X-Lite release 1006e stamp 34025..Content-Length: 0....#U 192.168.200.2:5060 -> external_ip_of_openser:5060 REGISTER sip:external_ip_of_openser SIP/2.0..Via: SIP/2.0/UDP 192.168.200.2;branch=z9hG4bKd734.53940821.0..Via: SIP/2.0/UDP external_ip_of_ua:23975;branch=z9hG4bK-d87543-307c62021a71bf6d-1--d87543-;rport=23975..Max-Forwards: 69..Contact: <sip:apo@external_ip_of_ua:23975;rinstance=6a2c0ccf1a30b6bf>..To: "apo"<sip:apo@external_ip_of_openser>..From: "apo"<sip:apo@external_ip_of_ua;tag=da6a3851..Call- ID: ODJmOTVkNmIxNjE0NWM3MWNiNTQ4ZjFlMmVkZDZmYjQ...CSeq: 1 REGISTER..Expires: 3600..Allow: INVITE, ACK, CANCEL, OPTIONS, B YE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO..User-Agent: X-Lite release 1006e stamp 34025..Content-Length: 0..P-hint: out bound.... my openser.cfg file is the initial openser openser.cfg file i didnt change it. ------------- # # $Id: openser.cfg 1676 2007-02-21 13:16:34Z bogdan_iancu $ # # simple quick-start config script # Please refer to the Core CookBook at http://www.openser.org/dokuwiki/doku.php # for a explanation of possible statements, functions and parameters. # # ----------- global configuration parameters ------------------------ debug=3 # debug level (cmd line: -dddddddddd) fork=yes log_stderror=no # (cmd line: -E) children=4 # Uncomment these lines to enter debugging mode #fork=no #log_stderror=yes # port=5060 # uncomment the following lines for TLS support #disable_tls = 0 #listen = tls:your_IP:5061 #tls_verify_server = 1 #tls_verify_client = 1 #tls_require_client_certificate = 0 #tls_method = TLSv1 #tls_certificate = "/usr/local/etc/openser/tls/user/user-cert.pem" #tls_private_key = "/usr/local/etc/openser/tls/user/user-privkey.pem" #tls_ca_list = "/usr/local/etc/openser/tls/user/user-calist.pem" # ------------------ module loading ---------------------------------- #set module path mpath="/usr/local/lib64/openser/modules/" # Uncomment this if you want to use SQL database #loadmodule "mysql.so" loadmodule "sl.so" loadmodule "tm.so" loadmodule "rr.so" loadmodule "maxfwd.so" loadmodule "usrloc.so" loadmodule "registrar.so" loadmodule "textops.so" loadmodule "mi_fifo.so" # Uncomment this if you want digest authentication # mysql.so must be loaded ! #loadmodule "auth.so" #loadmodule "auth_db.so" # ----------------- setting module-specific parameters --------------- # -- mi_fifo params -- modparam("mi_fifo", "fifo_name", "/tmp/openser_fifo") # -- usrloc params -- modparam("usrloc", "db_mode", 0) # Uncomment this if you want to use SQL database # for persistent storage and comment the previous line #modparam("usrloc", "db_mode", 2) # -- auth params -- # Uncomment if you are using auth module # #modparam("auth_db", "calculate_ha1", yes) # # If you set "calculate_ha1" parameter to yes (which true in this config), # uncomment also the following parameter) # #modparam("auth_db", "password_column", "password") # -- rr params -- # add value to ;lr param to make some broken UAs happy modparam("rr", "enable_full_lr", 1) # ------------------------- request routing logic ------------------- # main routing logic route{ # initial sanity checks -- messages with # max_forwards==0, or excessively long requests if (!mf_process_maxfwd_header("10")) { sl_send_reply("483","Too Many Hops"); exit; }; if (msg:len >= 2048 ) { sl_send_reply("513", "Message too big"); exit; }; # we record-route all messages -- to make sure that # subsequent messages will go through our proxy; that's # particularly good if upstream and downstream entities # use different transport protocol if (!method=="REGISTER") record_route(); # subsequent messages withing a dialog should take the # path determined by record-routing if (loose_route()) { # mark routing logic in request append_hf("P-hint: rr-enforced\r\n"); route(1); }; if (!uri==myself) { # mark routing logic in request append_hf("P-hint: outbound\r\n"); # if you have some interdomain connections via TLS #if(uri=~"@tls_domain1.net") { # t_relay("tls:domain1.net"); # exit; #} else if(uri=~"@tls_domain2.net") { # t_relay("tls:domain2.net"); # exit; #} route(1); }; # if the request is for other domain use UsrLoc # (in case, it does not work, use the following command # with proper names and addresses in it) if (uri==myself) { if (method=="REGISTER") { # Uncomment this if you want to use digest authentication #if (!www_authorize("openser.org", "subscriber")) { # www_challenge("openser.org", "0"); # exit; #}; save("location"); exit; }; lookup("aliases"); if (!uri==myself) { append_hf("P-hint: outbound alias\r\n"); route(1); }; # native SIP destinations are handled using our USRLOC DB if (!lookup("location")) { sl_send_reply("404", "Not Found"); exit; }; append_hf("P-hint: usrloc applied\r\n"); }; route(1); } route[1] { # send it out now; use stateful forwarding as it works reliably # even for UDP2TCP if (!t_relay()) { sl_reply_error(); }; exit; }

1 0

[Users] openser behind nat UAs behind NAT
by asahin 30 Mar '07

30 Mar '07

hi; i installed and tested openser on the internal network, it was working. i tried to test it behind NAT with x-lite sip client, but it failed. i defined a port mapping on the adsl modem for udp/tcp 5060 ports to forward the packets to the openser installed machine. when i try to register to openser i received a 408 request timeout message. i guess its due to external ip of the openser server. i think i should define external ip of the modem to the openser as if it's its own ip, but dont where to define it. here is the ngrep dump at the server. U external_ip_of_ua:23975 -> 192.168.200.2:5060 REGISTER sip:external_ip_of_openser SIP/2.0..Via: SIP/2.0/UDP external_ip_of_ua:23975;branch=z9hG4bK-d87543-307c62021a71bf6d-1--d87543-;rport..Max-Forwards: 70..Contact: <sip:apo@external_ip_of_ua:23975;rinstance=6a2c0ccf1a30b6bf>..To: "apo"<sip:apo@external_ip_of_openser>..From: "apo"<sip:apo@external_ip_of_ua;tag=da6a3851..Call-ID: ODJmOTVkNmIxNjE0NWM3MWNiNTQ4ZjFlMmVkZDZmYjQ...CSeq: 1 REGISTER.. Expires: 3600..Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO..User-Agent: X-Lite release 1006e stamp 34025..Content-Length: 0....#U 192.168.200.2:5060 -> external_ip_of_openser:5060 REGISTER sip:external_ip_of_openser SIP/2.0..Via: SIP/2.0/UDP 192.168.200.2;branch=z9hG4bKd734.53940821.0..Via: SIP/2.0/UDP external_ip_of_ua:23975;branch=z9hG4bK-d87543-307c62021a71bf6d-1--d87543-;rport=23975..Max-Forwards: 69..Contact: <sip:apo@external_ip_of_ua:23975;rinstance=6a2c0ccf1a30b6bf>..To: "apo"<sip:apo@external_ip_of_openser>..From: "apo"<sip:apo@external_ip_of_ua;tag=da6a3851..Call- ID: ODJmOTVkNmIxNjE0NWM3MWNiNTQ4ZjFlMmVkZDZmYjQ...CSeq: 1 REGISTER..Expires: 3600..Allow: INVITE, ACK, CANCEL, OPTIONS, B YE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO..User-Agent: X-Lite release 1006e stamp 34025..Content-Length: 0..P-hint: out bound.... my openser.cfg file is the initial openser openser.cfg file i didnt change it. ------------- # # $Id: openser.cfg 1676 2007-02-21 13:16:34Z bogdan_iancu $ # # simple quick-start config script # Please refer to the Core CookBook at http://www.openser.org/dokuwiki/doku.php # for a explanation of possible statements, functions and parameters. # # ----------- global configuration parameters ------------------------ debug=3 # debug level (cmd line: -dddddddddd) fork=yes log_stderror=no # (cmd line: -E) children=4 # Uncomment these lines to enter debugging mode #fork=no #log_stderror=yes # port=5060 # uncomment the following lines for TLS support #disable_tls = 0 #listen = tls:your_IP:5061 #tls_verify_server = 1 #tls_verify_client = 1 #tls_require_client_certificate = 0 #tls_method = TLSv1 #tls_certificate = "/usr/local/etc/openser/tls/user/user-cert.pem" #tls_private_key = "/usr/local/etc/openser/tls/user/user-privkey.pem" #tls_ca_list = "/usr/local/etc/openser/tls/user/user-calist.pem" # ------------------ module loading ---------------------------------- #set module path mpath="/usr/local/lib64/openser/modules/" # Uncomment this if you want to use SQL database #loadmodule "mysql.so" loadmodule "sl.so" loadmodule "tm.so" loadmodule "rr.so" loadmodule "maxfwd.so" loadmodule "usrloc.so" loadmodule "registrar.so" loadmodule "textops.so" loadmodule "mi_fifo.so" # Uncomment this if you want digest authentication # mysql.so must be loaded ! #loadmodule "auth.so" #loadmodule "auth_db.so" # ----------------- setting module-specific parameters --------------- # -- mi_fifo params -- modparam("mi_fifo", "fifo_name", "/tmp/openser_fifo") # -- usrloc params -- modparam("usrloc", "db_mode", 0) # Uncomment this if you want to use SQL database # for persistent storage and comment the previous line #modparam("usrloc", "db_mode", 2) # -- auth params -- # Uncomment if you are using auth module # #modparam("auth_db", "calculate_ha1", yes) # # If you set "calculate_ha1" parameter to yes (which true in this config), # uncomment also the following parameter) # #modparam("auth_db", "password_column", "password") # -- rr params -- # add value to ;lr param to make some broken UAs happy modparam("rr", "enable_full_lr", 1) # ------------------------- request routing logic ------------------- # main routing logic route{ # initial sanity checks -- messages with # max_forwards==0, or excessively long requests if (!mf_process_maxfwd_header("10")) { sl_send_reply("483","Too Many Hops"); exit; }; if (msg:len >= 2048 ) { sl_send_reply("513", "Message too big"); exit; }; # we record-route all messages -- to make sure that # subsequent messages will go through our proxy; that's # particularly good if upstream and downstream entities # use different transport protocol if (!method=="REGISTER") record_route(); # subsequent messages withing a dialog should take the # path determined by record-routing if (loose_route()) { # mark routing logic in request append_hf("P-hint: rr-enforced\r\n"); route(1); }; if (!uri==myself) { # mark routing logic in request append_hf("P-hint: outbound\r\n"); # if you have some interdomain connections via TLS #if(uri=~"@tls_domain1.net") { # t_relay("tls:domain1.net"); # exit; #} else if(uri=~"@tls_domain2.net") { # t_relay("tls:domain2.net"); # exit; #} route(1); }; # if the request is for other domain use UsrLoc # (in case, it does not work, use the following command # with proper names and addresses in it) if (uri==myself) { if (method=="REGISTER") { # Uncomment this if you want to use digest authentication #if (!www_authorize("openser.org", "subscriber")) { # www_challenge("openser.org", "0"); # exit; #}; save("location"); exit; }; lookup("aliases"); if (!uri==myself) { append_hf("P-hint: outbound alias\r\n"); route(1); }; # native SIP destinations are handled using our USRLOC DB if (!lookup("location")) { sl_send_reply("404", "Not Found"); exit; }; append_hf("P-hint: usrloc applied\r\n"); }; route(1); } route[1] { # send it out now; use stateful forwarding as it works reliably # even for UDP2TCP if (!t_relay()) { sl_reply_error(); }; exit; }

1 0

Re: [Users] 1.1.1 to 1.2 : radius failed
by Bogdan-Andrei Iancu 30 Mar '07

30 Mar '07

Bodin, looks like the error has its roots in the radiusclient library: rc_check_reply: received invalid reply digest from RADIUS server I'm not a RADIUS expert, so I cannot say more than this.....:( ...maybe try to use wireshark to see the packages between server and client radius. regards, bogdan Bodin Bruno wrote: > Bogdan-Andrei Iancu a écrit : >> Hi Bodin, >> >> Have you try to see if your radius cfg is ok? see: >> >> http://www.openser.org/docs/openser-radius-1.0.x.html#testing_radius_commun… >> >> >> regards, >> bogdan >> >> >> Bodin Bruno wrote: >>> Bogdan-Andrei Iancu a écrit : >>>> Hi Bodin, >>>> >>>> look into the system log (/var/log/{syslog|messages}) to get the >>>> error generated by the radius library. >>>> >>>> regards, >>>> bogdan >>>> >>>> Bodin Bruno wrote: >>>>> Same radius client config, same radius server config, just 1.2 >>>>> from 1.1.1 but an error : >>>>> >>>>> 5(23229) ERROR:auth_radius:radius_authorize_sterman: rc_auth failed >>>>> >>>>> Radius server get a good authenticate but openser failed this >>>>> after :( >>>> >>> On radius side, no error, in /var/log/messages there is only thise >>> line : >>> Mar 28 14:26:21 zebulon openser: rc_check_reply: received invalid >>> reply digest from RADIUS server >>> >>> >> > Hi, > Yes for sure. When a use 1.1.1 it work , and when I use 1.2 that > doesnt work, I thin k there is a difference between the two ... > > thank >

4 6

[Users] 0-terminated packet
by Tobias Lindgren 30 Mar '07

30 Mar '07

Hi all, Can anyone explain what this error mean? Mar 30 16:50:05 openser /sbin/openser[22632]: WARNING: udp_rcv_loop: upstream bug - 0-terminated packet from 192.168.0.1 50195 I'm getting this after an "Accepted" of a NOTIFY-message. Br, /Tobias

2 1

[Users] users authentication
by Joao Pereira 30 Mar '07

30 Mar '07

Hello I already have an OpenSER runnig nicely. Now I installed a second OpenSER (with other a newdomain) with the same database configuration and the same ser.cfg (except the IP). Everyting works fine... except the authentication... OpenSER always answers 401 Unauthorized. It only accepts clients when I comment this part: if (!www_authorize("newdomain.com", "subscriber")) { www_challenge("newdomain.com", "0"); break; }; The users exist in the database and I know the username / password. Whats happening? Thanks regards Joao Pereira

3 5

[Users] Unauthorized Calls - PLEASE HELP!
by Daryl Sanders 30 Mar '07

30 Mar '07

Hi Everyone, I aparently have something in my openser.cfg that is allowing unauthorized calls to go through to our PSTN gateways. I have included my config below for review. I would appreciate any help understanding how this might be happening. I am currently reviewing the CDRs from my PSTN gateways for clues as well. This is a pretty basic configuration with no NAT involved. Regards, Daryl route { # ----------------------------------------------------------------- # Sanity Check Section # ----------------------------------------------------------------- if (!mf_process_maxfwd_header("10")) { sl_send_reply("483", "Too Many Hops"); exit; }; if (msg:len > max_len) { sl_send_reply("513", "Message Overflow"); exit; }; if (method=="INVITE" || method=="ACK" || method=="BYE") { setflag(1); }; if (method=="INVITE") { if (is_user_in("From","inactive")) { if (uri =~ "^sip:911@") { xlog("L_NOTICE", "[$Tf] R1: $ci -- Allowing 911 Emergency Call on Inactive User\n" ); } else { sl_send_reply("403", "Forbidden"); xlog("L_NOTICE", "[$Tf] R1: $ci -- User Inactive\n" ); return; }; }; }; # ----------------------------------------------------------------- # Record Route Section # ----------------------------------------------------------------- if (method!="REGISTER") { record_route(); }; # ----------------------------------------------------------------- # Loose Route Section # ----------------------------------------------------------------- if (loose_route()) { xlog( "L_NOTICE", "[$Tf] RR: $ci -- Loose Route $rm ($rd).\n" ); if (!t_relay()) { sl_reply_error(); }; return; }; # ----------------------------------------------------------------- # Call Type Processing Section # ----------------------------------------------------------------- if (uri!=myself) { route(1); return; }; if (method=="ACK") { route(1); return; } else if (method=="REGISTER") { route(2); return; } else if (method=="INVITE") { route(3); return; } else if (method=="BYE" || method=="CANCEL") { t_relay(); exit; } lookup("aliases"); if (uri!=myself) { route(1); return; }; if (!lookup("location")) { sl_send_reply("404", "User Not Found"); return; }; route(1); } route[1] { # ----------------------------------------------------------------- # Default Message Handler # ----------------------------------------------------------------- t_on_reply("1"); t_on_failure("2"); if (!t_relay()) { sl_reply_error(); }; } route[2] { # ----------------------------------------------------------------- # REGISTER Message Handler # ----------------------------------------------------------------- sl_send_reply("100", "Trying"); if (!www_authorize("","subscriber")) { www_challenge("","0"); exit; }; consume_credentials(); if (!save("location")) { sl_reply_error(); }; } route[3] { # ----------------------------------------------------------------- # INVITE Message Handler # ----------------------------------------------------------------- # Trusted Provider IPs if (!src_ip==x.x.x.x)&&(!src_ip==x.x.x.x)&&(!src_ip==x.x.x.x) { if (!proxy_authorize("","subscriber")) { proxy_challenge("","0"); exit; }; consume_credentials(); }; lookup("aliases"); if (uri!=myself) { route(1); return; }; if (uri=~"[@:](192\.168\.|10\.|172\.16)" && !search("^Route:")){ sl_send_reply("479", "We do not forward to private IP addresses"); }; if ((uri =~ "^sip:0@")|| /* Operator Assistance */ (uri =~ "^sip:911@")|| /* 911 Emergency */ (uri =~ "^sip:411@")|| /* Directory Assistance */ (uri =~ "^sip:1[0-9]{10}@")) { /* Domestic PSTN */ route(4); return; }; if (uri=~"^sip:0111[0-9]*@") { # Kill calls to 011+1... (invalid dialing) sl_send_reply("406", "Not Acceptable"); return; } if (uri=~"^sip:011[0-9]*@") { # International PSTN if(!is_user_in("From","gateway1")) { strip(3); # Remove 011 for Gateway2 } route(4); return; }; if (!lookup("location")) { sl_send_reply("404", "User Not Found"); return; }; route(1); } route[4] { # ----------------------------------------------------------------- # PSTN Handler # ----------------------------------------------------------------- prefix("+"); # add "+" to Request URI append_hf("P-Asserted-Identity: \"User\"<sip:+1$avp(s:rpid)@x.x.x.x>\r\n"); uac_replace_from("$fn","sip:+$fU@$fd:5060"); if(is_user_in("From","gateway1")) { force_send_socket(x.x.x.x:5060); xlog("L_NOTICE", "[$Tf] Message sent via IP-1\n" ); } else { force_send_socket(x.x.x.x:5060); xlog("L_NOTICE", "[$Tf] Message sent via IP-2\n" ); }; ds_select_domain("1","0"); route(1); } onreply_route[1] { # we are checking here for a progressing return... ie a 180 Ringing or # 183 session progress -- if this occurs we don't care from here on # about failures as a gateway is handling the call... if( status =~ "18[0-9]" ) { xlog( "L_INFO", "[$Tf] ORR: $ci -- SIP-$rs Reset t_on_failure()\n"); t_on_failure("0"); } else { xlog( "L_INFO", "[$Tf] ORR: $ci -- $rs $rr\n" ); } } failure_route[2] { # 408 -- timeout -- typically the end party has not answered # Since we cancel t_on_failure() on a provisional response we should not be # getting a 408 timeout from a gateway at this stage.. it will just "fall through" # If fr_timer expires t_check_status("408") is true, although $rs is <null> if( t_check_status("408") ){ xlog( "L_NOTICE", "[$Tf] FR: $ci -- TIMEOUT for Gateway $rd\n" ); } else { xlog( "L_NOTICE", "[$Tf] FR: $ci -- $rs reason $rr\n" ); } # 403 -- Not a valid number, or possibly no permission to use the gateway if( t_check_status("403") ){ xlog("L_NOTICE", "[$Tf] FR: $ci -- SIP-$rs Forbidden\n" ); return; } # 486 -- User Busy if( t_check_status("486") ){ xlog("L_NOTICE", "[$Tf] FR: $ci -- SIP-$rs Destination Busy\n" ); return; } # 487 -- Request Cancelled (usually in response to a CANCEL transaction) if( t_check_status("487") ){ xlog("L_NOTICE", "[$Tf] FR: $ci -- SIP-$rs Request Cancelled\n" ); return; } # At this stage we try the next gateway, if no next gateway we bail. if( ds_next_domain() ){ t_on_reply("1"); t_on_failure("2"); xlog( "L_NOTICE", "[$Tf] FR: $ci Next gateway $fU -> $tU via $rd\n" ); if( !t_relay() ){ xlog( "L_WARN", "[$Tf] FR: $ci -- ERROR - Can not t_relay()\n" ); return; } return; } else { xlog( "L_WARN", "[$Tf] FR: $ci No more gateways -> 503.\n" ); t_reply("503", "Service unavailable -- no more gateways" ); return; } }

3 3

[Users] t_relay() with variables(proto:ip:port)
by Benko 30 Mar '07

30 Mar '07

Hello! I would like to relay messages to a location("proto:ip:port") i retrieve from a db-table with avp_db_query, unfortunately t_relay doesn't allow using avps or pseudo-variables currently(iirc). Do you know a workaround without using t_relay or is there a way to use avps/pseudo-variables with t_relay() since 1.2? Thx Christian

3 7

[Users] A Problem with Serweb server monitoring
by Jarkko Nevala 30 Mar '07

30 Mar '07

Hi. I'm having problems with Serweb server monitoring script. As Instructed Serweb install file I have cron job, that executes "read_ser_moni.php" once in a minute. Every time the script is executed I get this error on serweb log: "serweb [error] server monitoring - 500 command 't_stats' not available" It also happens, when I'm executing the script from command line or executing manually fifo command with openserctl ("openserctl fifo t_stat"). It seems, that openser receives the command, but doesen't know what to do with it, because I get this error on syslog from openser: ERROR: fifo_server: command t_stats is not available **** done consume INFO: fifo_server: command empty Has the t_stat fifo command depricated or am I just missing some parameter from my cfg. thanks. JN

2 1

Re: [Users] Radius and OpenSer
by raviprakash sunkara 30 Mar '07

30 Mar '07

Sorry , U can use Alepo radius server , this Alepo radius server should communicate with Radiusclient of the OpenSER radiusclient dictionary should mached the Alepo radius server. I think U have Alepo radius server On 3/30/07, Jidntt <jidntt(a)yahoo.com.ar> wrote: > > Hi list, > > > > I've a question… I've a billing system named Alepo. > > I need to know if OpenSer support radius for connect to Alepo and how to > configure this. > > > > Thanks > > > > Pablo > > _______________________________________________ > Users mailing list > Users(a)openser.org > http://openser.org/cgi-bin/mailman/listinfo/users > > -- Thanks and Regards Ravi Prakash Sunkara ravi.sunkara(a)hyperion-tech.com M:+91 9985077535 www.hyperion-tech.com Client and Parent company :- www.august-networks.com

1 0

[Users] authentication with other DB
by Joao Pereira 30 Mar '07

30 Mar '07

Hello I just installed OpenSER and configured digest authentication with a local database. The content of the database was copied from other server. The ser.cfg and the database are the same... but OpenSER dont allow the users to register.... :( Whats the problem of doing a postgresql dump and then recover the DB in other PC? OpenSER doesnt allow it? Thanks regards Joao pereira

2 1

[Users] Radius and OpenSer
by Jidntt 30 Mar '07

30 Mar '07

Hi list, I've a question. I've a billing system named Alepo. I need to know if OpenSer support radius for connect to Alepo and how to configure this. Thanks Pablo

1 0

[Users] 1.1.1 to 1.2 : radius failed
by Bodin Bruno 30 Mar '07

30 Mar '07

Same radius client config, same radius server config, just 1.2 from 1.1.1 but an error : 5(23229) ERROR:auth_radius:radius_authorize_sterman: rc_auth failed Radius server get a good authenticate but openser failed this after :(

3 4

RE: [Users] out of memory
by Papadopoulos Georgios 30 Mar '07

30 Mar '07

Hi Bogdan, I found the following thread in the list http://www.openser.org/pipermail/users/2006-June/005339.html I suspect that I have the same issue. If I assume that our DNS is strange, then my 1.1.1-notls version will be affected, right? Is there a patch to fix this? Eventually I want to go to 1.2 but I have to do a lot of testing before I can put it in production. So for the moment I need a fix for 1.1.1. Also back in December I sent this to the list http://www.openser.org/pipermail/users/2006-December/008205.html >From the start, we had the issue of openser stopping to process any incoming requests. On December I thought it was DNS related. I am still in the dark about this. Lately I added logging and I discovered the "out of memory" error. I am guessing that the error was there from the start, I just did not know about it. Do all of these make any sense to you? And is there a way to test our DNS to determine whether it is buggy? In the meantime I will follow the instructions on the wiki to get the memory dump. thank you George > -----Original Message----- > From: Bogdan-Andrei Iancu [mailto:bogdan@voice-system.ro] > Sent: Wednesday, March 28, 2007 11:54 AM > To: Papadopoulos Georgios > Cc: users(a)openser.org > Subject: Re: [Users] out of memory > > Hi Papadopoulos, > > the error you get complains about the lack of private memory (per > process) - the statistics show info about the shared memory. See: > http://www.openser.org/dokuwiki/doku.php/troubleshooting:memory > > but look for pkg instead of shm..... > > regards, > bogdan > > Papadopoulos Georgios wrote: > > Hello, > > > > Lately our OpenSER 1.1.1 is running out of memory and I get the > > following message > > 4(25190) get_hdr_field: out of memory The result is that it stops > > processing any incoming request. This is a production system and of > > course it causes a great deal of frustration. > > > > The last time this happened I got the following statistics before > > restarting > > > ./openserctl fifo get_statistics > > Total statistics = 37 > > Total modules = 5 > > Module name = core; statistics=8 > > core:rcv_requests = 3259334 > > core:rcv_replies = 8816 > > core:fwd_requests = 736 > > core:fwd_replies = 137 > > core:drop_requests = 743 > > core:drop_replies = 0 > > core:err_requests = 0 > > core:err_replies = 43 > > Module name = shmem; statistics=6 > > shmem:total_size = 268435456 > > shmem:used_size = 1675864 > > shmem:real_used_size = 1835104 > > shmem:max_used_size = 4399048 > > shmem:free_size = 266600352 > > shmem:fragments = 17710 > > Module name = sl; statistics=9 > > sl:1xx_replies = 0 > > sl:2xx_replies = 1690410 > > sl:3xx_replies = 43 > > sl:4xx_replies = 334827 > > sl:5xx_replies = 1185629 > > sl:6xx_replies = 0 > > sl:sent_replies = 3210909 > > sl:sent_err_replies = 0 > > sl:received_ACKs = 743 > > Module name = tm; statistics=11 > > tm:received_replies = 8636 > > tm:relayed_replies = 7096 > > tm:local_replies = 1718 > > tm:UAS_transactions = 7003 > > tm:UAC_transactions = 94 > > tm:2xx_transactions = 1528 > > tm:3xx_transactions = 3 > > tm:4xx_transactions = 5129 > > tm:5xx_transactions = 468 > > tm:6xx_transactions = 0 > > tm:inuse_transactions = 0 > > Module name = usrloc; statistics=3 > > usrloc:location-users = 0 > > usrloc:location-contacts = 0 > > usrloc:location-expires = 7282 > > > > I am not sure how to read these numbers but I see a big "free_size" > > and still OpenSER is out of memory. Any suggestions? > > > > 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 > > > >

2 1

RE: [Users] out of memory
by Papadopoulos Georgios 30 Mar '07

30 Mar '07

Hi Bogdan I followed the instructions to get the memory dump. Now openser will not start. Mar 28 13:44:56 ser1 openser[1567]: convert_row: No memory left Mar 28 13:44:56 ser1 openser[1567]: convert_rows: Error while converting row #2536 Mar 28 13:44:56 ser1 openser[1567]: convert_result: Error while converting rows Mar 28 13:44:56 ser1 openser[1567]: store_result: Error while converting result Mar 28 13:44:56 ser1 openser[1567]: preload_udomain(): Error while doing db_query Mar 28 13:44:56 ser1 openser[1567]: register_udomain(): Error while preloading domain 'location' Mar 28 13:44:56 ser1 openser[1567]: domain_fixup(): Error while registering domain Mar 28 13:44:56 ser1 openser[1567]: ERROR: fix_actions: fixing failed (code=-1) at cfg line 282 Mar 28 13:44:56 ser1 openser[1567]: ERROR: fix_expr : fix_actions error In MySQL location table we have around 2600 rows. The default version of openser has no problem loading them at startup. The version compiled with DBG_QM_MALLOC and without F_MALLOC cannot load the location table. The same happens if I increase the shared memory with the -m option. Does this mean that ul is stored in private memory? Does this mean I should increase PKG_MEM_POOL_SIZE? thank you George > -----Original Message----- > From: Bogdan-Andrei Iancu [mailto:bogdan@voice-system.ro] > Sent: Wednesday, March 28, 2007 11:54 AM > To: Papadopoulos Georgios > Cc: users(a)openser.org > Subject: Re: [Users] out of memory > > Hi Papadopoulos, > > the error you get complains about the lack of private memory (per > process) - the statistics show info about the shared memory. See: > http://www.openser.org/dokuwiki/doku.php/troubleshooting:memory > > but look for pkg instead of shm..... > > regards, > bogdan > > Papadopoulos Georgios wrote: > > Hello, > > > > Lately our OpenSER 1.1.1 is running out of memory and I get the > > following message > > 4(25190) get_hdr_field: out of memory The result is that it stops > > processing any incoming request. This is a production system and of > > course it causes a great deal of frustration. > > > > The last time this happened I got the following statistics before > > restarting > > > ./openserctl fifo get_statistics > > Total statistics = 37 > > Total modules = 5 > > Module name = core; statistics=8 > > core:rcv_requests = 3259334 > > core:rcv_replies = 8816 > > core:fwd_requests = 736 > > core:fwd_replies = 137 > > core:drop_requests = 743 > > core:drop_replies = 0 > > core:err_requests = 0 > > core:err_replies = 43 > > Module name = shmem; statistics=6 > > shmem:total_size = 268435456 > > shmem:used_size = 1675864 > > shmem:real_used_size = 1835104 > > shmem:max_used_size = 4399048 > > shmem:free_size = 266600352 > > shmem:fragments = 17710 > > Module name = sl; statistics=9 > > sl:1xx_replies = 0 > > sl:2xx_replies = 1690410 > > sl:3xx_replies = 43 > > sl:4xx_replies = 334827 > > sl:5xx_replies = 1185629 > > sl:6xx_replies = 0 > > sl:sent_replies = 3210909 > > sl:sent_err_replies = 0 > > sl:received_ACKs = 743 > > Module name = tm; statistics=11 > > tm:received_replies = 8636 > > tm:relayed_replies = 7096 > > tm:local_replies = 1718 > > tm:UAS_transactions = 7003 > > tm:UAC_transactions = 94 > > tm:2xx_transactions = 1528 > > tm:3xx_transactions = 3 > > tm:4xx_transactions = 5129 > > tm:5xx_transactions = 468 > > tm:6xx_transactions = 0 > > tm:inuse_transactions = 0 > > Module name = usrloc; statistics=3 > > usrloc:location-users = 0 > > usrloc:location-contacts = 0 > > usrloc:location-expires = 7282 > > > > I am not sure how to read these numbers but I see a big "free_size" > > and still OpenSER is out of memory. Any suggestions? > > > > 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 > > > >

2 1

[Serusers] authentication with other DB
by Joao Pereira 30 Mar '07

30 Mar '07

Hello I just installed SER and configured digest authentication with a local database. The content of the database was copied from other server. The ser.cfg and the database are the same... but SER dont allow the users to register.... :( Whats the problem of doing a postgresql dump and then recover the DB in other PC? SER doenst allow it? Thanks regards Joao pereira

1 0

[Serusers] MySql Module Error!!
by KUMAR 30 Mar '07

30 Mar '07

I was using SER 0.9.6 earlier. Recently, I downloaded the SER 2.0 source code and installed it as follows. make group_include="standard standard-dep stable experimental presence" all It went without any problems. But there seems to be some kind of problem with loading of mysql module. I have also removed the references for fifo from my old configuration file. When i check the configuration file with ser -c i get the following error message: 0(13302) ERROR: load_module: could not open module </usr/local/lib/ser/modules/mysql.so>: /usr/local/lib/ser/modules/mysql.so: undefined symbol: fm_malloc 0(13302) parse error (34,13-14): failed to load module Can anyone please help me as soon as possible. Am i missing something?? Thank you in advance kumar

1 0

Re: Fwd: [Users] Openser fails when compiled on Solaris 64bit
by Sergio Gutierrez 30 Mar '07

30 Mar '07

Hi Daniel. In the meantime, I have begun to test using more standard conditions; I am not using the optimized compiler and I am running openser compiled on 32 bits. I have discovered an even nastier issue. When Openser is configured in forking mode, and with or without log_stderror, it presents the same symptom I reported when compiled on 64 bits (it exhausts the shared memory reservation, and crashes with core dumping). This is the backtrace: (gdb) bt #0 0x00000000 in ?? () #1 0xfe989b3c in getRow (ipType=1, ipAddress=0x141888) at openserSIPPortTable.c:125 #2 0xfe989c5c in createRowsFromIPList (theList=0x141a50, listSize=1, protocol=0, snmpIndex=0xffbff870) at openserSIPPortTable.c:201 #3 0xfe98a07c in init_openserSIPPortTable () at openserSIPPortTable.c:241 #4 0xfe98d708 in spawn_agentx_child () at sub_agent.c:74 #5 0xfe98cf04 in mod_child_init (rank=0) at snmpstats.c:271 #6 0x00059ca8 in init_mod_child (m=0x133840, rank=0, type=0xc3c08 "PROC_MAIN") at sr_module.c:406 #7 0x00059c24 in init_mod_child (m=0x1338e0, rank=0, type=0xc3c08 "PROC_MAIN") at sr_module.c:395 #8 0x000336c4 in main_loop () at main.c:952 #9 0x00035be4 in main (argc=9, argv=0xe7800) at main.c:1399 When I configure fork=no, openser does not crash, and works right. I apologize if I should better create a new thread. If you suggest so I will do it. Thanks in advance for your attention. Kind regards Sergio Gutierrez. EPM Telecomunicaciones Medellín, Colombia Tel: 574 - 3950022 > ---------- Forwarded message ---------- > > > From: *Sergio Gutierrez* <saguti(a)gmail.com <mailto: saguti(a)gmail.com>> > > > Date: Mar 27, 2007 9:52 AM > > > Subject: Re: [Users] Openser fails when compiled on Solaris 64bit > > > To: daniel(a)voice-system.ro <mailto: daniel(a)voice-system.ro> > > > Cc: users(a)openser.org <mailto:users@openser.org> > > > > > > Hi Daniel. > > > > > > I am using mysql version 5.0.37, compiled on 64 bits too. > > > > > > These are the printing of the symbols you asked: > > > > > > (gdb) print row > > > $1 = (db_row_t *) 0x10026bf68 > > > (gdb) print ROW_VALUES(row) > > > No symbol "ROW_VALUES" in current context. > > > (gdb) print VAL_NULL(ROW_VALUES(row) > > > No symbol "VAL_NULL" in current context. > > > (gdb) > > > > > > > > > Thanks. > > > > > > > > > On 3/27/07, *Daniel-Constantin Mierla* < daniel(a)voice-system.ro > > > <mailto:daniel@voice-system.ro >> wrote: > > > > > > Hello Sergio, > > > > > > seems to be some data corrupted from what database returned. What > > > is the > > > database type you use, mysql? > > > > > > Could you print the the content of row and ROW_VALUES(row) (via > > print > > > command in gdb)? > > > > > > Thanks, > > > Daniel > > > > > > > > > On 03/26/07 23:46, Sergio Gutierrez wrote: > > > > Hi again Daniel. > > > > > > > > Testing other things trying to solve the problem I found that > > the > > > > segmentation fault occurs when Openser is restarted and there > > are > > > > records within location database table. > > > > If the table is empty initially, openser starts OK, and users > > can > > > > register without problem. > > > > > > > > Below is the backtrace of a error when the location table is not > > > empty: > > > > > > > > #0 0xffffffff7d90e2a0 in preload_udomain (_c=0x10026ad90, > > > > _d=0xffffffff5028e9f0) at udomain.c:404 > > > > 404 if (VAL_NULL(ROW_VALUES(row)) > > > > (gdb) bt > > > > #0 0xffffffff7d90e2a0 in preload_udomain (_c=0x10026ad90, > > > > _d=0xffffffff5028e9f0) at udomain.c:404 > > > > #1 0xffffffff7d915844 in child_init (_rank=1) at ul_mod.c:344 > > > > #2 0x0000000100082500 in init_mod_child (m=0x1, rank=1, > > > > type=0x1000f41b0 "CHILD") at > > > > /home/operador/openser-1.2.0-notls//sr_module.c:400 > > > > #3 0x0000000100082460 in init_mod_child (m=0x1, rank=1, > > > > type=0x1000f41b0 "CHILD") at > > > > /home/operador/openser-1.2.0-notls//sr_module.c:394 > > > > #4 0x0000000100082460 in init_mod_child (m=0x1, rank=1, > > > > type=0x1000f41b0 "CHILD") at > > > > /home/operador/openser-1.2.0-notls//sr_module.c:394 > > > > #5 0x0000000100082770 in init_child (rank=1) at > > > > /home/operador/openser-1.2.0-notls//sr_module.c:394 > > > > #6 0x0000000100032414 in main_loop () at > > > > /home/operador/openser-1.2.0-notls//main.c:724 > > > > #7 0x00000001000345a4 in main (argc=2, argv=0xffffff7eaeeec4ff) > > at > > > > /home/operador/openser-1.2.0-notls//main.c:1399 > > > > > > > > > > > > Thanks. > > > > > > > > > > > > > > > > > > > > > > > > On 3/26/07, *Sergio Gutierrez* < saguti(a)gmail.com > > > <mailto:saguti@gmail.com> > > > > <mailto: saguti(a)gmail.com <mailto:saguti@gmail.com >>> wrote: > > > > > > > > Hi Daniel. > > > > > > > > This is the backtrace of the core. > > > > Thanks > > > > > > > > #0 0xffffffff7d90ee9c in preload_udomain (_c=0x10026b7d800, > > > > > > _d=0x0) at > > > > /home/operador/openser- 1.2.0-notls > > /modules/usrloc//udomain.c:404 > > > > #1 0xffffffff7d9131c4 in child_init (_rank=1344858528) at > > > > /home/operador/openser- 1.2.0-notls > > /modules/usrloc//ul_mod.c:344 > > > > #2 0x0000000100082500 in init_mod_child (m=0x1, rank=1, > > > > type=0x1000f41b0 "CHILD") at > > > > /home/operador/openser- 1.2.0-notls//sr_module.c:400 > > > > #3 0x0000000100082460 in init_mod_child (m=0x1, rank=1, > > > > type=0x1000f41b0 "CHILD") at > > > > /home/operador/openser-1.2.0-notls //sr_module.c:394 > > > > #4 0x0000000100082460 in init_mod_child (m=0x1, rank=1, > > > > type=0x1000f41b0 "CHILD") at > > > > /home/operador/openser- 1.2.0-notls //sr_module.c:394 > > > > #5 0x0000000100082770 in init_child (rank=1) at > > > > /home/operador/openser-1.2.0-notls//sr_module.c:394 > > > > #6 0x0000000100032414 in main_loop () at > > > > /home/operador/openser- 1.2.0-notls//main.c:724 > > > > #7 0x00000001000345a4 in main (argc=2, > > argv=0xffffff7e7007a000) > > > > at /home/operador/openser-1.2.0-notls//main.c:1399 > > > > > > > > > > > > > > > > > > > > On 3/26/07, *Daniel-Constantin Mierla* < > > > daniel(a)voice-system.ro <mailto: daniel(a)voice-system.ro> > > > > <mailto: daniel(a)voice-system.ro > > > <mailto:daniel@voice-system.ro>>> wrote: > > > > > > > > Hello, > > > > > > > > can you send a gdb backtrace :-D -- I cannot read adb > > > backtrace. > > > > > > > > Cheers, > > > > Daniel > > > > > > > > > > > > On 03/26/07 19:42, Sergio Gutierrez wrote: > > > > > Hi Daniel. > > > > > > > > > > This is the backtrace, obtained with adb: > > > > > > > > > > usrloc.so`preload_udomain+0x4cc (1, ffffffff7228e9f0, > > > 100215a00, > > > > > ffffffff7d919e58, ffffffffffefe3f8, 0) > > > > > 0xffffffff7d9131bc(2, ffffffff7da1c9b0, > > ffffffff7d91a170, > > > > > ffffffff7228e9a0, ffffffff7da1b0a8, ffffffffffeff0c8) > > > > > init_mod_child+0xd8(100269930, 1, 1000f41b0, > > 1000f40f0, 1, > > > > 100269870) > > > > > init_mod_child+0x38(100269bb0, 1, 1000f41b0, > > 1000f40f0, 1, > > > > 1002699f0) > > > > > init_mod_child+0x38(100269d30, 1, 1000f41b0, > > 1000f40f0, 1, > > > > 100269c70) > > > > > init_child+0xa8(1, 100269df0, 1, 1000f4168, 10020d000, > > > 100269eb0) > > > > > main_loop+0xf34(0, 8c, 1000eefd8, ffffffff720083c4, > > > 1002694b0, 0) > > > > > main+0x1e10(100215, 9, 0, 10020d000, 1000ef5b8, > > 10020d000) > > > > > _start+0x7c(0, 0, 0, 0, 0, 0) > > > > > > > > > > On 3/26/07, *Sergio Gutierrez* <saguti(a)gmail.com > > > <mailto: saguti(a)gmail.com> > > > > <mailto: saguti(a)gmail.com <mailto: saguti(a)gmail.com>> > > > > > <mailto: saguti(a)gmail.com <mailto: saguti(a)gmail.com> > > > <mailto:saguti@gmail.com <mailto: saguti(a)gmail.com>>>> wrote: > > > > > > > > > > Hi Daniel. > > > > > > > > > > I used 512 for -m parameter. > > > > > > > > > > Would you like the backtrace of the core file? > > > > > > > > > > Thanks. > > > > > > > > > > > > > > > On 3/26/07, *Daniel-Constantin Mierla* < > > > > daniel(a)voice-system.ro <mailto: daniel(a)voice-system.ro> > > > <mailto: daniel(a)voice-system.ro <mailto:daniel@voice-system.ro>> > > > > > <mailto: daniel(a)voice-system.ro > > > <mailto: daniel(a)voice-system.ro> > > > > <mailto: daniel(a)voice-system.ro > > > <mailto:daniel@voice-system.ro>>>> wrote: > > > > > > > > > > Hello, > > > > > > > > > > could you send a backtrace? What was the value > > for > > > > parameter -m? > > > > > > > > > > Cheers, > > > > > Daniel > > > > > > > > > > > > > > > On 03/26/07 19:29, Sergio Gutierrez wrote: > > > > > > Hi > > > > > > > > > > > > I am trying to run Openser compiled on 64 > > > bits on a > > > > SPARC > > > > > Machine > > > > > > running Solaris 10. > > > > > > > > > > > > When I create a simple configuration file > > for > > > > testing radius > > > > > > integration, Openser starts to consume the > > whole > > > > memory > > > > > reservation > > > > > > (-m parameter) and fails with segmentation > > > fault error. > > > > > > > > > > > > after several tests, I have found that the > > > error is > > > > caused by > > > > > save() > > > > > > function (registrar module). > > > > > > > > > > > > This is the main route my configuration > > file: > > > > > > > > > > > > route { > > > > > > if(method=="REGISTER") > > > > > > { > > > > > > if(!radius_www_authorize("")) > > > > > > { > > > > > > www_challenge("", > > "0"); > > > > > > return; > > > > > > }; > > > > > > > > > > > > if(!save("location")) > > > > > > { > > > > > > sl_reply_error(); > > > > > > }; > > > > > > return; > > > > > > > > > > > > } > > > > > > else > > > > > > { > > > > > > } > > > > > > } > > > > > > > > > > > > Thanks in advance for your help. > > > > > > > > > > > > Sergio G. > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------------------------ > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > Users mailing list > > > > > > Users(a)openser.org <mailto: Users(a)openser.org > > > > > > <mailto: Users(a)openser.org <mailto: Users(a)openser.org>> > > > > <mailto: Users(a)openser.org <mailto: Users(a)openser.org> > > > <mailto: Users(a)openser.org <mailto: Users(a)openser.org>>> > > > > > > > > http://openser.org/cgi-bin/mailman/listinfo/users > > > > < http://openser.org/cgi-bin/mailman/listinfo/users > > > <http://openser.org/cgi-bin/mailman/listinfo/users>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >

3 12

[Users] rtpproxy redundancy
by Daniel Corbe 29 Mar '07

29 Mar '07

For various reasons we've elected to go with Porta/Maxim Sobalov's rtpproxy as opposed to the MediaProxy code; however, we would like to know if its possible to do any of the following with rtpproxy or if we should consider going to MediaProxy instead 1) Multiple Load Balanced rtpproxy servers 2) Voice path fail over, so that if we lose 1 RTP proxy the call continues on another. I was thinking 2 could be implemented using an OpenBSD/CARP FreeBSD/CARP type of scenario, where 2 rtpproxy servers share 1 IP address; however, OpenSER would need to set up an rtpproxy session on BOTH servers to accomplish this and the OS can do the rest. Any opinions or comments are welcome.

2 1

Fwd: [Users] SNMPstats module not returning data
by Sergio Gutierrez 29 Mar '07

29 Mar '07

Hi Jefrey Thanks for your answer. I will reply every point: # /opt/net-snmp/bin/snmpwalk -v 2c -c community localhost .1.3.6.1.4.1.27483 OPENSER-REG-MIB::openser = No Such Object available on this agent at this OID # ps -ef | grep snmpd root 1649 579 0 17:50:07 pts/2 0:17 /opt/net-snmp/sbin/snmpd -d -f -Dagentx -x tcp:localhost:705 root 2935 2778 0 09:59:21 pts/3 0:00 grep snmpd (I am running debug mode; the syntax of ps command is a little bti different because I am using Solaris) # grep -i agentx /var/log/snmpd.log agentx_build: packet built okay agentx/master: handle pdu (req=0x3ac55fdb,trans=0x0,sess=0xf) agentx/master: send response, stat 0 (req=0x3ac55fdb,trans=0x0,sess=0xf) agentx_build: packet built okay agentx/master: handle pdu (req=0x3ac55fdc,trans=0x0,sess=0xf) agentx/master: send response, stat 0 (req=0x3ac55fdc,trans=0x0,sess=0xf) agentx_build: packet built okay agentx/master: handle pdu (req=0x3ac55fdd,trans=0x0,sess=0xf) agentx/master: send response, stat 0 (req=0x3ac55fdd,trans=0x0,sess=0xf) agentx_build: packet built okay ... # cat /opt/net-snmp/share/snmp/snmpstats.conf agentXsocket tcp:localhost:705 # cat /opt/net-snmp/share/snmp/snmpd.conf syslocation XXXX syscontact XXXX agentaddress udp:161 rocommunity community localhost master agentx As you can see, both of the files are located at the same directory. Finally, I do have tried the check. I can see Openser starts OK and the master agent receives the connection of the sub agent. Thank you very much for your help. Kind regards. Sergio G. On 3/29/07, jmagder <jmagder(a)somanetworks.com > wrote: > > Hi Sergio, > > First off, could you try running "/opt/net-snmp/bin/snmpwalk -v 2c -c > community sipserver .1.3.6.1.4.1.27483"? If that isn't succeeding, > then it would greatly help me debug your problem if you could answer the > following questions: > > 1) What is the output of "ps aux | grep snmpd"? > > 2) What is the output of "cat /var/log/messages | grep AgentX" > > 3) Can you show me the contents of snmpstats.conf ? > > 4) Does snmpd.conf contain "master agentx"? > > 5) Is snmpd.conf located in the same directory as snmpstats.conf? > > 6) Have you tried the steps in "Testing for a proper Configuration" in > section 1.6.4? > > Thanks Sergio! > > - Jeffrey Magder > > Sergio Gutierrez wrote: > > Hi list. > > > > I have installed Openser 1.2.0, with Net-snmp version 5.4 to support > > the SNMPstats module. I have configured the subagent according to the > > instructions on the documentation, but I am not being able to obtain > > any data. > > > > I am running both products on Solaris 10 Sparc. > > > > # /opt/net-snmp/bin/snmpwalk -v 2c -c community sipserver > > .1.3.6.1.4.1.27483.3.1.1.1.1.1.1 > > SNMPv2-SMI::enterprises.27483.3.1.1.1.1.1 = No Such Object available > > on this agent at this OID > > > > # /opt/net-snmp/bin/snmpwalk -v 2c -c community sipserver > > openserSIPProtocolVersion > > SNMPv2-SMI::enterprises.27483.3.1.1.1.1.1 = No Such Object available > > on this agent at this OID > > > > Is there any other thing I should do after compiling and configuring? > > > > Thanks in advance for your attention > > > > Kind Regards. > > > > Sergio Gutiérrez > > > > > > > > ------------------------------------------------------------------------ > > > > > _______________________________________________ > > Users mailing list > > Users(a)openser.org > > http://openser.org/cgi-bin/mailman/listinfo/users > > > >

2 2

[Users] SNMPstats module not returning data
by Sergio Gutierrez 29 Mar '07

29 Mar '07

Hi list. I have installed Openser 1.2.0, with Net-snmp version 5.4 to support the SNMPstats module. I have configured the subagent according to the instructions on the documentation, but I am not being able to obtain any data. I am running both products on Solaris 10 Sparc. # /opt/net-snmp/bin/snmpwalk -v 2c -c community sipserver .1.3.6.1.4.1.27483.3.1.1.1.1.1.1 SNMPv2-SMI::enterprises.27483.3.1.1.1.1.1 = No Such Object available on this agent at this OID # /opt/net-snmp/bin/snmpwalk -v 2c -c community sipserver openserSIPProtocolVersion SNMPv2-SMI::enterprises.27483.3.1.1.1.1.1 = No Such Object available on this agent at this OID Is there any other thing I should do after compiling and configuring? Thanks in advance for your attention Kind Regards. Sergio Gutiérrez

3 2

[Users] how to check openser server is functional after initial setup
by Abdurrahman Sahin 29 Mar '07

29 Mar '07

hi; i just compiled openser on a machine with amd64 cpu and Fedora Core 5 as the OS. just set export CPU=athlon64. then make all is there any tool to test openser functionalities(seeing a process is running doesnt mean anything for me).? after successfull compilation i can see openser is listening tcp/udp 5060 ports. there are 3 executables in /usr/local/sbin directory -rwxr-xr-x 1 root root 2.9M Mar 29 09:37 openser -rwxr-xr-x 1 root root 41K Mar 29 09:37 openserctl -rwxr-xr-x 1 root root 15K Mar 29 09:37 openserunix and some configuration files in /usr/local/etc/openser -rw-r--r-- 1 root root 1.8K Mar 29 09:37 dictionary.radius -rw-r--r-- 1 root root 4.1K Mar 29 09:37 openser.cfg -rw-r--r-- 1 root root 1.2K Mar 29 09:37 openserctlrc netstat status tcp 0 0 192.168.200.2:5060 0.0.0.0:* LISTEN 31533/openser off (0.00/0/0) tcp 0 0 127.0.0.1:5060 0.0.0.0:* LISTEN 31533/openser off (0.00/0/0) udp 0 0 192.168.200.2:5060 0.0.0.0:* 31533/openser off (0.00/0/0) udp 0 0 127.0.0.1:5060 0.0.0.0:* 31533/openser off (0.00/0/0)

2 1

RE: [Users] Simple xcap-emulator for OpenSER
by Toni Barata 29 Mar '07

29 Mar '07

Hi Sukerry, Klaus, It was really a missing ";" after the "require_once('db_mysql.php')". Thanks, Toni -----Original Message----- From: sukerry [mailto:sukerry@126.com] Sent: quinta-feira, 29 de Março de 2007 0:41 To: Toni Barata; Klaus Darilion Cc: users openser.org Subject: [Spam?] Re: RE: [Users] Simple xcap-emulator for OpenSER Toni Barata, in Config.php, a ";" is missed before the term "class" ======= 2007-03-28 23:47:03 ======= >Hi Klaus, > > >I have been using xcap-0.2.1 without problems until yesterday. Today I have upgrade to the xcap-0.5 but the following error occurs: > >PHP Parse error: parse error, unexpected T_CLASS in /var/www/xcap-root/config.php on line 19 > >I have php4 on my system and the db_mysql.php file is php3 version. Could this be the problem? Should I downgrade php4 to php3? > >Thanks, >Toni > >-----Original Message----- >From: users-bounces(a)openser.org [mailto:users-bounces@openser.org] On Behalf Of Klaus Darilion >Sent: quarta-feira, 28 de Mar?o de 2007 10:54 >To: sukerry >Cc: Klaus Darilion; Adrian Georgescu; users openser.org >Subject: Re: [Users] Simple xcap-emulator for OpenSER > >there is nothing to compile. Read the Readme. you have to install PEAR >and the modules mentioned in the READ. > >e.g. >pear install Auth_HTTP >pear install Log >pear install DB > >regards >klaus > > >sukerry wrote: >> Adrian Georgescu, >> >> >> Thanks for your great job! >> >> However , when I compile php, an error says that Log.php can not be found! >> >> Thanks >> >> sukerry >> >> >> >> ======= 2007-03-28 00:56:33======= >> >>> Hello, >>> >>> We wrote a simple xcap emulator to be able to manage the XCAP >>> documents used by OpenSER presence agent, by using PHP scripts in >>> combination with Apache web server. >>> >>> I have tested it against OpenSER with MySQL and Eyebeam for Apple. >>> Klaus Darilion has tested it against Postgress and Eyebeam for Windows. >>> >>> The software can be downloaded from: >>> >>> http://download.dns-hosting.info/XCAP/xcap-0.5.tar.gz >>> >>> Regards, >>> Adrian >>> >>> >>> _______________________________________________ >>> Users mailing list >>> Users(a)openser.org >>> http://openser.org/cgi-bin/mailman/listinfo/users >>> >> >> >> 　　　　　　　　sukerry >> 　　　　　　　　sukerry(a)126.com >> 　　　　　　　　　　2007-03-28 >> >> >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Users mailing list >> Users(a)openser.org >> http://openser.org/cgi-bin/mailman/listinfo/users > >_______________________________________________ >Users mailing list >Users(a)openser.org >http://openser.org/cgi-bin/mailman/listinfo/users >_______________________________________________ >Users mailing list >Users(a)openser.org >http://openser.org/cgi-bin/mailman/listinfo/users > = = = = = = = = = = = = = = = = = = = = 　　　　　　　　sukerry 　　　　　　　　sukerry(a)126.com 　　　　　　　　　　2007-03-29

1 0

Re: [Users] ReInvite Issue
by Klaus Darilion 29 Mar '07

29 Mar '07

I think the problem is the gateway of bandwidth.com The 183 session progress have all the same To-tag and the same branch value in the topmost via header, although the 3 INVITEs sent to bandwidth.com have different branch value in the Via header. Thus, I suspect the dialog matching of the gateways is broken and it thinks the second and third INVITE is a retransmission of the first INVITE? Although I'm not sure as the gateway sends the 183 reply 3 times in a row. Strange. What happens in the PSTN? Which of the 3 phones ring? +17144828306 ? regards klaus Brandon Armstead wrote: > Hello, here is the sipcap: > > interface: eth0 (74.52.58.48/255.255.255.240) > filter: ip and ( port 5060 ) > match: 9492666205 > ################### > U +0.000000 ATA:5062 -> OpenSER:5060

1 0

[Users] OpenSER @ Von @ San Jose
by Bogdan-Andrei Iancu 29 Mar '07

29 Mar '07

Hi, OpenSER made a nice presence at Von Spring in San Jose. There were several presentation on the OpenSER topic, both in the expo area -in the Von Theatre- and in the conference sessions. For more, see: http://www.openser.org/events/2007-03-20-VoN-Spring/ There are other related presentations, but I'm still struggling to get them all. OpenSER drew and got a lot of attention - many people were aware of OpenSER and its potential, there were also quite some solutions (from expo area) using OpenSER and I personally met people using it for a large set of scenarios. And most important, I find more and more people are attracted by OpenSER as a viable solution for VoIP systems. As usual, VoN was an interesting experience. There is a changed of focus since last year - based on both the presented solution (expos) and on the conference topic, the interest shifted from IMS to "mobile VoIP" (fix mobile convergence). At least that was my personal impression and I find it most interesting as I think it reflects the real current needs (or requirements) of the VoIP solutions. Regards, Bogdan

1 0

[Serusers] SER + Prepaid with Radius AAA.
by Shafraz Thawfeek 29 Mar '07

29 Mar '07

Hello All, Its really feels nice to have joined the list. I'm in the process of deploying a SER based solution for prepaid users. We're using a FreeRadius based billing solution from a provider. If I'm not mistaken, SER is not aware of the call state, what this means to me is, in case the user account on the radius runs out of credit, SER will not know about it and will not be able to disconnect the call. Am I correct on this? If I am correct, I would like to know what would be the workaround for this? I'm I am wrong, then I would like to know on how we could get the call disconnection working? I have a Nextone which would be sitting in front of the SER and acting as a Mirror Proxy for SER. The purpose of this is to overcome NAT traversal issues and free SER from that. Nextone doesn't understand or talk radius. SER will be the registrar and handle AAA. The user call will be sent back into the Nextone and then terminated from there. SER will not be handling media. If to get my disconnect upon credit exhaust scenario working, what changes should I introduce into my existing network model? Thank you. Shaf.

3 9

[Users] G729 Codec question
by Andreas M. 29 Mar '07

29 Mar '07

Hello, i have a question regarding codec G729. We want to implement this in our client software, but there exists many flavours. Are all G.729 codec flavours compatible to each other? For example: G729 to G729A or B ? or G729B to A and vice versa ? We are currently using Cisco AS5300 Gateways, that supports G729 and G729B. But we want to change our gateways, then only G729A is available. i know this question has nothing to do with openser, but i think there are many readers with experience. best regards, Andreas M.

2 1

Re: [Users] ReInvite Issue
by Brandon Armstead 29 Mar '07

29 Mar '07

Hello, here is the sipcap below: match: 9492666205 ################### U +0.538693 GATEWAY_1:5060 -> OpenSER:5060 INVITE sip:9492666205@OpenSER:5060 SIP/2.0. Record-Route: <sip:GATEWAY_1;lr=on;ftag=as0f6730bc>. Via: SIP/2.0/UDP GATEWAY_1;branch=z9hG4bK49bd.5c8e4a8.0. Via: SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. From: "7135178240" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. To: <sip:9492666205@GATEWAY_1>. Contact: <sip:7135178240@64.24.35.73>. Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. CSeq: 102 INVITE. User-Agent: US LEC VOIP. Max-Forwards: 69. Date: Thu, 29 Mar 2007 09:46:26 GMT. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY. Content-Type: application/sdp. Content-Length: 156. . v=0. o=root 7184 7184 IN IP4 64.24.35.73. s=session. c=IN IP4 64.24.35.73. t=0 0. m=audio 31806 RTP/AVP 0. a=rtpmap:0 PCMU/8000. a=silenceSupp:off - - - -. # U +0.002135 OpenSER:5060 -> GATEWAY_1:5060 SIP/2.0 100 trying -- your call is important to us. Via: SIP/2.0/UDP GATEWAY_1;branch=z9hG4bK49bd.5c8e4a8.0;rport=5060. Via: SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. From: "7135178240" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. To: <sip:9492666205@GATEWAY_1>. Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. CSeq: 102 INVITE. Server: OpenSer (1.1.1-notls (x86_64/linux)). Content-Length: 0. Warning: 392 OpenSER:5060 "Noisy feedback tells: pid=15173 req_src_ip=GATEWAY_1 req_src_port=5060 in_uri=sip:9492666205@OpenSER:5060 out_uri=sip:9492666205@OpenSER:5060 via_cnt==2". . # U +0.000088 OpenSER:5060 -> GATEWAY_2:5060 INVITE sip:+17144828306@GATEWAY_2:5060 SIP/2.0. Record-Route: <sip:OpenSER;lr=on;ftag=as0f6730bc>. Record-Route: <sip:GATEWAY_1;lr=on;ftag=as0f6730bc>. Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK49bd.98a53e2.1. Via: SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0. Via: SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. From: "7135178240" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. To: <sip:9492666205@GATEWAY_1>. Contact: <sip:7135178240@64.24.35.73>. Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. CSeq: 102 INVITE. Max-Forwards: 68. Date: Thu, 29 Mar 2007 09:46:26 GMT. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY. Content-Type: application/sdp. Content-Length: 174. . v=0. o=root 7184 7184 IN IP4 64.24.35.73. s=session. c=IN IP4 OpenSER. t=0 0. m=audio 37158 RTP/AVP 0. a=rtpmap:0 PCMU/8000. a=silenceSupp:off - - - -. a=nortpproxy:yes. # U +0.000015 OpenSER:5060 -> GATEWAY_2:5060 INVITE sip:+17608263100@GATEWAY_2:5060 SIP/2.0. Record-Route: <sip:OpenSER;lr=on;ftag=as0f6730bc>. Record-Route: <sip:GATEWAY_1;lr=on;ftag=as0f6730bc>. Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK49bd.98a53e2.2. Via: SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0. Via: SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. From: "7135178240" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. To: <sip:9492666205@GATEWAY_1>. Contact: <sip:7135178240@64.24.35.73>. Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. CSeq: 102 INVITE. Max-Forwards: 68. Date: Thu, 29 Mar 2007 09:46:26 GMT. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY. Content-Type: application/sdp. Content-Length: 174. . v=0. o=root 7184 7184 IN IP4 64.24.35.73. s=session. c=IN IP4 OpenSER. t=0 0. m=audio 37158 RTP/AVP 0. a=rtpmap:0 PCMU/8000. a=silenceSupp:off - - - -. a=nortpproxy:yes. # U +0.000019 OpenSER:5060 -> GATEWAY_2:5060 INVITE sip:+19496164708@GATEWAY_2:5060 SIP/2.0. Record-Route: <sip:OpenSER;lr=on;ftag=as0f6730bc>. Record-Route: <sip:GATEWAY_1;lr=on;ftag=as0f6730bc>. Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK49bd.98a53e2.3. Via: SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0. Via: SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. From: "7135178240" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. To: <sip:9492666205@GATEWAY_1>. Contact: <sip:7135178240@64.24.35.73>. Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. CSeq: 102 INVITE. Max-Forwards: 68. Date: Thu, 29 Mar 2007 09:46:26 GMT. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY. Content-Type: application/sdp. Content-Length: 174. . v=0. o=root 7184 7184 IN IP4 64.24.35.73. s=session. c=IN IP4 OpenSER. t=0 0. m=audio 37158 RTP/AVP 0. a=rtpmap:0 PCMU/8000. a=silenceSupp:off - - - -. a=nortpproxy:yes. # U +0.022478 GATEWAY_2:5060 -> OpenSER:5060 SIP/2.0 100 Trying bandwidth.com. Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK49bd.98a53e2.1. Via: SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0. Via: SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. From: "7135178240" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. To: <sip:9492666205@GATEWAY_1>. Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. CSeq: 102 INVITE. Server: Bandwidth.com SDE (v1.0). Content-Length: 0. Warning: 392 GATEWAY_2:5060 "Noisy feedback tells: pid=32282 req_src_ip=OpenSER req_src_port=5060 in_uri=sip:+17144828306@GATEWAY_2:5060 out_uri=sip:+17144828306@4.68.250.148:5060 via_cnt==3". . # U +0.000376 GATEWAY_2:5060 -> OpenSER:5060 SIP/2.0 100 Trying bandwidth.com. Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK49bd.98a53e2.2. Via: SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0. Via: SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. From: "7135178240" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. To: <sip:9492666205@GATEWAY_1>. Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. CSeq: 102 INVITE. Server: Bandwidth.com SDE (v1.0). Content-Length: 0. Warning: 392 GATEWAY_2:5060 "Noisy feedback tells: pid=32282 req_src_ip=OpenSER req_src_port=5060 in_uri=sip:+17608263100@GATEWAY_2:5060 out_uri=sip:+17608263100@4.68.250.148:5060 via_cnt==3". . # U +0.000124 GATEWAY_2:5060 -> OpenSER:5060 SIP/2.0 100 Trying bandwidth.com. Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK49bd.98a53e2.3. Via: SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0. Via: SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. From: "7135178240" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. To: <sip:9492666205@GATEWAY_1>. Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. CSeq: 102 INVITE. Server: Bandwidth.com SDE (v1.0). Content-Length: 0. Warning: 392 GATEWAY_2:5060 "Noisy feedback tells: pid=32282 req_src_ip=OpenSER req_src_port=5060 in_uri=sip:+19496164708@GATEWAY_2:5060 out_uri=sip:+19496164708@4.68.250.148:5060 via_cnt==3". . ####### U +0.110379 OpenSER:5060 -> ATA:5062 INVITE sip:9492666205@192.168.1.126:5062 SIP/2.0. Record-Route: <sip:OpenSER;lr=on;ftag=as0f6730bc>. Record-Route: <sip:OpenSER;lr=on;ftag=as0f6730bc>. Record-Route: <sip:GATEWAY_1;lr=on;ftag=as0f6730bc>. Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK49bd.a8a53e2.0. Via: SIP/2.0/UDP OpenSER;rport=5060;branch=z9hG4bK49bd.98a53e2.0. Via: SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0. Via: SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. From: "Cell Phone TX" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. To: <sip:9492666205@GATEWAY_1>. Contact: <sip:7135178240@OpenSER:5060>. Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. CSeq: 102 INVITE. Max-Forwards: 67. Date: Thu, 29 Mar 2007 09:46:26 GMT. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY. Content-Type: application/sdp. Content-Length: 174. . v=0. o=root 7184 7184 IN IP4 64.24.35.73. s=session. c=IN IP4 OpenSER. t=0 0. m=audio 37158 RTP/AVP 0. a=rtpmap:0 PCMU/8000. a=silenceSupp:off - - - -. a=nortpproxy:yes. # U +0.035038 ATA:5062 -> OpenSER:5060 SIP/2.0 100 Trying. To: <sip:9492666205@GATEWAY_1>. From: "Cell Phone TX" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. CSeq: 102 INVITE. Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK49bd.a8a53e2.0. Via: SIP/2.0/UDP OpenSER;rport=5060;branch=z9hG4bK49bd.98a53e2.0. Via: SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0. Via: SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. Record-Route: <sip:OpenSER;lr=on;ftag=as0f6730bc>. Record-Route: <sip:OpenSER;lr=on;ftag=as0f6730bc>. Record-Route: <sip:GATEWAY_1;lr=on;ftag=as0f6730bc>. Server: Sipura/SPA841-3.1.4(a). Content-Length: 0. . # U +0.035106 ATA:5062 -> OpenSER:5060 SIP/2.0 180 Ringing. To: <sip:9492666205@GATEWAY_1>;tag=cf04e5d3f5afda4fi0. From: "Cell Phone TX" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. CSeq: 102 INVITE. Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK49bd.a8a53e2.0. Via: SIP/2.0/UDP OpenSER;rport=5060;branch=z9hG4bK49bd.98a53e2.0. Via: SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0. Via: SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. Record-Route: <sip:OpenSER;lr=on;ftag=as0f6730bc>. Record-Route: <sip:OpenSER;lr=on;ftag=as0f6730bc>. Record-Route: <sip:GATEWAY_1;lr=on;ftag=as0f6730bc>. Server: Sipura/SPA841-3.1.4(a). Content-Length: 0. . # U +0.000287 OpenSER:5060 -> GATEWAY_1:5060 SIP/2.0 180 Ringing. To: <sip:9492666205@GATEWAY_1>;tag=cf04e5d3f5afda4fi0. From: "Cell Phone TX" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. CSeq: 102 INVITE. Via: SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0. Via: SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. Record-Route: <sip:OpenSER;lr=on;ftag=as0f6730bc>. Record-Route: <sip:OpenSER;lr=on;ftag=as0f6730bc>. Record-Route: <sip:GATEWAY_1;lr=on;ftag=as0f6730bc>. Server: Sipura/SPA841-3.1.4(a). Content-Length: 0. . ######################################## U +6.689904 GATEWAY_2:5060 -> OpenSER:5060 SIP/2.0 183 Session Progress. Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK49bd.98a53e2.1,SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0,SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. Record-Route: <sip:GATEWAY_2;lr;ftag=as0f6730bc>,<sip:OpenSER;lr=on;ftag=as0f6730bc>,<sip:GATEWAY_1;lr=on;ftag=as0f6730bc>. From: "7135178240" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. To: <sip:9492666205@GATEWAY_1>;tag=VPST506071629460. Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. CSeq: 102 INVITE. Contact: <sip:+17144828306@4.68.250.148:5060;transport=udp>. Content-Type: application/sdp. Content-Length: 128. . v=0. o=- 1175161585 1175161586 IN IP4 209.244.42.237. s=-. c=IN IP4 209.244.42.237. t=0 0. m=audio 64520 RTP/AVP 0. a=ptime:20. # U +0.000286 OpenSER:5060 -> GATEWAY_1:5060 SIP/2.0 183 Session Progress. Via: SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0,SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. Record-Route: <sip:GATEWAY_2;lr;ftag=as0f6730bc>,<sip:OpenSER;lr=on;ftag=as0f6730bc>,<sip:GATEWAY_1;lr=on;ftag=as0f6730bc>. From: "7135178240" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. To: <sip:9492666205@GATEWAY_1>;tag=VPST506071629460. Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. CSeq: 102 INVITE. Contact: <sip:+17144828306@4.68.250.148:5060;transport=udp>. Content-Type: application/sdp. Content-Length: 143. . v=0. o=- 1175161585 1175161586 IN IP4 209.244.42.237. s=-. c=IN IP4 OpenSER. t=0 0. m=audio 37160 RTP/AVP 0. a=ptime:20. a=nortpproxy:yes. # U +0.139883 GATEWAY_2:5060 -> OpenSER:5060 SIP/2.0 183 Session Progress. Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK49bd.98a53e2.1,SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0,SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. Record-Route: <sip:GATEWAY_2;lr;ftag=as0f6730bc>,<sip:OpenSER;lr=on;ftag=as0f6730bc>,<sip:GATEWAY_1;lr=on;ftag=as0f6730bc>. From: "7135178240" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. To: <sip:9492666205@GATEWAY_1>;tag=VPST506071629460. Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. CSeq: 102 INVITE. Contact: <sip:+17144828306@4.68.250.148:5060;transport=udp>. Content-Type: application/sdp. Content-Length: 128. . v=0. o=- 1175161585 1175161586 IN IP4 209.244.42.237. s=-. c=IN IP4 209.244.42.237. t=0 0. m=audio 64520 RTP/AVP 0. a=ptime:20. # U +0.000251 GATEWAY_2:5060 -> OpenSER:5060 SIP/2.0 183 Session Progress. Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK49bd.98a53e2.1,SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0,SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. Record-Route: <sip:GATEWAY_2;lr;ftag=as0f6730bc>,<sip:OpenSER;lr=on;ftag=as0f6730bc>,<sip:GATEWAY_1;lr=on;ftag=as0f6730bc>. From: "7135178240" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. To: <sip:9492666205@GATEWAY_1>;tag=VPST506071629460. Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. CSeq: 102 INVITE. Contact: <sip:+17144828306@4.68.250.148:5060;transport=udp>. Content-Type: application/sdp. Content-Length: 128. . v=0. o=- 1175161585 1175161586 IN IP4 209.244.42.237. s=-. c=IN IP4 209.244.42.237. t=0 0. m=audio 64520 RTP/AVP 0. a=ptime:20. # U +0.003394 OpenSER:5060 -> GATEWAY_1:5060 SIP/2.0 183 Session Progress. Via: SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0,SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. Record-Route: <sip:GATEWAY_2;lr;ftag=as0f6730bc>,<sip:OpenSER;lr=on;ftag=as0f6730bc>,<sip:GATEWAY_1;lr=on;ftag=as0f6730bc>. From: "7135178240" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. To: <sip:9492666205@GATEWAY_1>;tag=VPST506071629460. Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. CSeq: 102 INVITE. Contact: <sip:+17144828306@4.68.250.148:5060;transport=udp>. Content-Type: application/sdp. Content-Length: 143. . v=0. o=- 1175161585 1175161586 IN IP4 209.244.42.237. s=-. c=IN IP4 OpenSER. t=0 0. m=audio 37160 RTP/AVP 0. a=ptime:20. a=nortpproxy:yes. # U +0.000090 OpenSER:5060 -> GATEWAY_1:5060 SIP/2.0 183 Session Progress. Via: SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0,SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. Record-Route: <sip:GATEWAY_2;lr;ftag=as0f6730bc>,<sip:OpenSER;lr=on;ftag=as0f6730bc>,<sip:GATEWAY_1;lr=on;ftag=as0f6730bc>. From: "7135178240" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. To: <sip:9492666205@GATEWAY_1>;tag=VPST506071629460. Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. CSeq: 102 INVITE. Contact: <sip:+17144828306@4.68.250.148:5060;transport=udp>. Content-Type: application/sdp. Content-Length: 143. . v=0. o=- 1175161585 1175161586 IN IP4 209.244.42.237. s=-. c=IN IP4 OpenSER. t=0 0. m=audio 37160 RTP/AVP 0. a=ptime:20. a=nortpproxy:yes. ####### U +4.012603 GATEWAY_2:5060 -> OpenSER:5060 SIP/2.0 183 Session Progress. Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK49bd.98a53e2.1,SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0,SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. Record-Route: <sip:GATEWAY_2;lr;ftag=as0f6730bc>,<sip:OpenSER;lr=on;ftag=as0f6730bc>,<sip:GATEWAY_1;lr=on;ftag=as0f6730bc>. From: "7135178240" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. To: <sip:9492666205@GATEWAY_1>;tag=VPST506071629460. Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. CSeq: 102 INVITE. Contact: <sip:+17144828306@4.68.250.148:5060;transport=udp>. Content-Type: application/sdp. Content-Length: 128. . v=0. o=- 1175161585 1175161586 IN IP4 209.244.42.237. s=-. c=IN IP4 209.244.42.237. t=0 0. m=audio 64520 RTP/AVP 0. a=ptime:20. # U +0.000126 GATEWAY_2:5060 -> OpenSER:5060 SIP/2.0 183 Session Progress. Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK49bd.98a53e2.1,SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0,SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. Record-Route: <sip:GATEWAY_2;lr;ftag=as0f6730bc>,<sip:OpenSER;lr=on;ftag=as0f6730bc>,<sip:GATEWAY_1;lr=on;ftag=as0f6730bc>. From: "7135178240" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. To: <sip:9492666205@GATEWAY_1>;tag=VPST506071629460. Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. CSeq: 102 INVITE. Contact: <sip:+17144828306@4.68.250.148:5060;transport=udp>. Content-Type: application/sdp. Content-Length: 128. . v=0. o=- 1175161585 1175161586 IN IP4 209.244.42.237. s=-. c=IN IP4 209.244.42.237. t=0 0. m=audio 64520 RTP/AVP 0. a=ptime:20. # U +0.007244 OpenSER:5060 -> GATEWAY_1:5060 SIP/2.0 183 Session Progress. Via: SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0,SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. Record-Route: <sip:GATEWAY_2;lr;ftag=as0f6730bc>,<sip:OpenSER;lr=on;ftag=as0f6730bc>,<sip:GATEWAY_1;lr=on;ftag=as0f6730bc>. From: "7135178240" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. To: <sip:9492666205@GATEWAY_1>;tag=VPST506071629460. Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. CSeq: 102 INVITE. Contact: <sip:+17144828306@4.68.250.148:5060;transport=udp>. Content-Type: application/sdp. Content-Length: 143. . v=0. o=- 1175161585 1175161586 IN IP4 209.244.42.237. s=-. c=IN IP4 OpenSER. t=0 0. m=audio 37160 RTP/AVP 0. a=ptime:20. a=nortpproxy:yes. # U +0.000041 OpenSER:5060 -> GATEWAY_1:5060 SIP/2.0 183 Session Progress. Via: SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0,SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. Record-Route: <sip:GATEWAY_2;lr;ftag=as0f6730bc>,<sip:OpenSER;lr=on;ftag=as0f6730bc>,<sip:GATEWAY_1;lr=on;ftag=as0f6730bc>. From: "7135178240" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. To: <sip:9492666205@GATEWAY_1>;tag=VPST506071629460. Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. CSeq: 102 INVITE. Contact: <sip:+17144828306@4.68.250.148:5060;transport=udp>. Content-Type: application/sdp. Content-Length: 143. . v=0. o=- 1175161585 1175161586 IN IP4 209.244.42.237. s=-. c=IN IP4 OpenSER. t=0 0. m=audio 37160 RTP/AVP 0. a=ptime:20. a=nortpproxy:yes. ## U +0.575203 GATEWAY_2:5060 -> OpenSER:5060 SIP/2.0 183 Session Progress. Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK49bd.98a53e2.1,SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0,SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. Record-Route: <sip:GATEWAY_2;lr;ftag=as0f6730bc>,<sip:OpenSER;lr=on;ftag=as0f6730bc>,<sip:GATEWAY_1;lr=on;ftag=as0f6730bc>. From: "7135178240" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. To: <sip:9492666205@GATEWAY_1>;tag=VPST506071629460. Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. CSeq: 102 INVITE. Contact: <sip:+17144828306@4.68.250.148:5060;transport=udp>. Content-Type: application/sdp. Content-Length: 128. . v=0. o=- 1175161585 1175161586 IN IP4 209.244.42.237. s=-. c=IN IP4 209.244.42.237. t=0 0. m=audio 64520 RTP/AVP 0. a=ptime:20. # U +0.000125 GATEWAY_2:5060 -> OpenSER:5060 SIP/2.0 183 Session Progress. Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK49bd.98a53e2.1,SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0,SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. Record-Route: <sip:GATEWAY_2;lr;ftag=as0f6730bc>,<sip:OpenSER;lr=on;ftag=as0f6730bc>,<sip:GATEWAY_1;lr=on;ftag=as0f6730bc>. From: "7135178240" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. To: <sip:9492666205@GATEWAY_1>;tag=VPST506071629460. Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. CSeq: 102 INVITE. Contact: <sip:+17144828306@4.68.250.148:5060;transport=udp>. Content-Type: application/sdp. Content-Length: 128. . v=0. o=- 1175161585 1175161586 IN IP4 209.244.42.237. s=-. c=IN IP4 209.244.42.237. t=0 0. m=audio 64520 RTP/AVP 0. a=ptime:20. # U +0.003655 OpenSER:5060 -> GATEWAY_1:5060 SIP/2.0 183 Session Progress. Via: SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0,SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. Record-Route: <sip:GATEWAY_2;lr;ftag=as0f6730bc>,<sip:OpenSER;lr=on;ftag=as0f6730bc>,<sip:GATEWAY_1;lr=on;ftag=as0f6730bc>. From: "7135178240" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. To: <sip:9492666205@GATEWAY_1>;tag=VPST506071629460. Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. CSeq: 102 INVITE. Contact: <sip:+17144828306@4.68.250.148:5060;transport=udp>. Content-Type: application/sdp. Content-Length: 143. . v=0. o=- 1175161585 1175161586 IN IP4 209.244.42.237. s=-. c=IN IP4 OpenSER. t=0 0. m=audio 37160 RTP/AVP 0. a=ptime:20. a=nortpproxy:yes. # U +0.000041 OpenSER:5060 -> GATEWAY_1:5060 SIP/2.0 183 Session Progress. Via: SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0,SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. Record-Route: <sip:GATEWAY_2;lr;ftag=as0f6730bc>,<sip:OpenSER;lr=on;ftag=as0f6730bc>,<sip:GATEWAY_1;lr=on;ftag=as0f6730bc>. From: "7135178240" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. To: <sip:9492666205@GATEWAY_1>;tag=VPST506071629460. Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. CSeq: 102 INVITE. Contact: <sip:+17144828306@4.68.250.148:5060;transport=udp>. Content-Type: application/sdp. Content-Length: 143. . v=0. o=- 1175161585 1175161586 IN IP4 209.244.42.237. s=-. c=IN IP4 OpenSER. t=0 0. m=audio 37160 RTP/AVP 0. a=ptime:20. a=nortpproxy:yes. ################### U +4.011642 GATEWAY_2:5060 -> OpenSER:5060 SIP/2.0 183 Session Progress. Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK49bd.98a53e2.1,SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0,SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. Record-Route: <sip:GATEWAY_2;lr;ftag=as0f6730bc>,<sip:OpenSER;lr=on;ftag=as0f6730bc>,<sip:GATEWAY_1;lr=on;ftag=as0f6730bc>. From: "7135178240" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. To: <sip:9492666205@GATEWAY_1>;tag=VPST506071629460. Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. CSeq: 102 INVITE. Contact: <sip:+17144828306@4.68.250.148:5060;transport=udp>. Content-Type: application/sdp. Content-Length: 128. . v=0. o=- 1175161585 1175161586 IN IP4 209.244.42.237. s=-. c=IN IP4 209.244.42.237. t=0 0. m=audio 64520 RTP/AVP 0. a=ptime:20. # U +0.000377 GATEWAY_2:5060 -> OpenSER:5060 SIP/2.0 183 Session Progress. Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK49bd.98a53e2.1,SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0,SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. Record-Route: <sip:GATEWAY_2;lr;ftag=as0f6730bc>,<sip:OpenSER;lr=on;ftag=as0f6730bc>,<sip:GATEWAY_1;lr=on;ftag=as0f6730bc>. From: "7135178240" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. To: <sip:9492666205@GATEWAY_1>;tag=VPST506071629460. Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. CSeq: 102 INVITE. Contact: <sip:+17144828306@4.68.250.148:5060;transport=udp>. Content-Type: application/sdp. Content-Length: 128. . v=0. o=- 1175161585 1175161586 IN IP4 209.244.42.237. s=-. c=IN IP4 209.244.42.237. t=0 0. m=audio 64520 RTP/AVP 0. a=ptime:20. # U +0.000192 OpenSER:5060 -> GATEWAY_1:5060 SIP/2.0 183 Session Progress. Via: SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0,SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. Record-Route: <sip:GATEWAY_2;lr;ftag=as0f6730bc>,<sip:OpenSER;lr=on;ftag=as0f6730bc>,<sip:GATEWAY_1;lr=on;ftag=as0f6730bc>. From: "7135178240" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. To: <sip:9492666205@GATEWAY_1>;tag=VPST506071629460. Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. CSeq: 102 INVITE. Contact: <sip:+17144828306@4.68.250.148:5060;transport=udp>. Content-Type: application/sdp. Content-Length: 143. . v=0. o=- 1175161585 1175161586 IN IP4 209.244.42.237. s=-. c=IN IP4 OpenSER. t=0 0. m=audio 37160 RTP/AVP 0. a=ptime:20. a=nortpproxy:yes. # U +0.011882 OpenSER:5060 -> GATEWAY_1:5060 SIP/2.0 183 Session Progress. Via: SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0,SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. Record-Route: <sip:GATEWAY_2;lr;ftag=as0f6730bc>,<sip:OpenSER;lr=on;ftag=as0f6730bc>,<sip:GATEWAY_1;lr=on;ftag=as0f6730bc>. From: "7135178240" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. To: <sip:9492666205@GATEWAY_1>;tag=VPST506071629460. Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. CSeq: 102 INVITE. Contact: <sip:+17144828306@4.68.250.148:5060;transport=udp>. Content-Type: application/sdp. Content-Length: 143. . v=0. o=- 1175161585 1175161586 IN IP4 209.244.42.237. s=-. c=IN IP4 OpenSER. t=0 0. m=audio 37160 RTP/AVP 0. a=ptime:20. a=nortpproxy:yes. ############### U +4.003638 GATEWAY_2:5060 -> OpenSER:5060 SIP/2.0 183 Session Progress. Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK49bd.98a53e2.1,SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0,SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. Record-Route: <sip:GATEWAY_2;lr;ftag=as0f6730bc>,<sip:OpenSER;lr=on;ftag=as0f6730bc>,<sip:GATEWAY_1;lr=on;ftag=as0f6730bc>. From: "7135178240" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. To: <sip:9492666205@GATEWAY_1>;tag=VPST506071629460. Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. CSeq: 102 INVITE. Contact: <sip:+17144828306@4.68.250.148:5060;transport=udp>. Content-Type: application/sdp. Content-Length: 128. . v=0. o=- 1175161585 1175161586 IN IP4 209.244.42.237. s=-. c=IN IP4 209.244.42.237. t=0 0. m=audio 64520 RTP/AVP 0. a=ptime:20. # U +0.008482 OpenSER:5060 -> GATEWAY_1:5060 SIP/2.0 183 Session Progress. Via: SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0,SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. Record-Route: <sip:GATEWAY_2;lr;ftag=as0f6730bc>,<sip:OpenSER;lr=on;ftag=as0f6730bc>,<sip:GATEWAY_1;lr=on;ftag=as0f6730bc>. From: "7135178240" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. To: <sip:9492666205@GATEWAY_1>;tag=VPST506071629460. Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. CSeq: 102 INVITE. Contact: <sip:+17144828306@4.68.250.148:5060;transport=udp>. Content-Type: application/sdp. Content-Length: 143. . v=0. o=- 1175161585 1175161586 IN IP4 209.244.42.237. s=-. c=IN IP4 OpenSER. t=0 0. m=audio 37160 RTP/AVP 0. a=ptime:20. a=nortpproxy:yes. ######################################################### U +2.220013 OpenSER:5060 -> GATEWAY_2:5060 CANCEL sip:+17608263100@GATEWAY_2:5060 SIP/2.0. Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK49bd.98a53e2.2. From: "7135178240" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. To: <sip:9492666205@GATEWAY_1>. CSeq: 102 CANCEL. User-Agent: OpenSer (1.1.1-notls (x86_64/linux)). Content-Length: 0. . # U +0.000015 OpenSER:5060 -> GATEWAY_2:5060 CANCEL sip:+19496164708@GATEWAY_2:5060 SIP/2.0. Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK49bd.98a53e2.3. From: "7135178240" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. To: <sip:9492666205@GATEWAY_1>. CSeq: 102 CANCEL. User-Agent: OpenSer (1.1.1-notls (x86_64/linux)). Content-Length: 0. . # U +0.008073 OpenSER:5060 -> ATA:5062 CANCEL sip:9492666205@192.168.1.126:5062 SIP/2.0. Max-Forwards: 10. Record-Route: <sip:OpenSER;lr=on;ftag=as0f6730bc>. Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK49bd.a8a53e2.0. Via: SIP/2.0/UDP OpenSER;rport=5060;branch=z9hG4bK49bd.98a53e2.0. From: "7135178240" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. To: <sip:9492666205@GATEWAY_1>. CSeq: 102 CANCEL. Content-Length: 0. . # U +0.023630 GATEWAY_2:5060 -> OpenSER:5060 SIP/2.0 487 Request Terminated. Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK49bd.98a53e2.2. Via: SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0. Via: SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. From: "7135178240" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. To: <sip:9492666205@GATEWAY_1>;tag=2a6c315af837f0a6a989449d0bd9acf6-91e7. Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. CSeq: 102 INVITE. Server: Bandwidth.com SDE (v1.0). Content-Length: 0. Warning: 392 GATEWAY_2:5060 "Noisy feedback tells: pid=32286 req_src_ip=OpenSER req_src_port=5060 in_uri=sip:+17608263100@GATEWAY_2:5060 out_uri=sip:+17608263100@4.68.250.148:5060 via_cnt==1". . # U +0.000096 OpenSER:5060 -> GATEWAY_2:5060 ACK sip:+17608263100@GATEWAY_2:5060 SIP/2.0. Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK49bd.98a53e2.2. From: "7135178240" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. To: <sip:9492666205@GATEWAY_1>;tag=2a6c315af837f0a6a989449d0bd9acf6-91e7. CSeq: 102 ACK. User-Agent: OpenSer (1.1.1-notls (x86_64/linux)). Content-Length: 0. . # U +0.005775 GATEWAY_2:5060 -> OpenSER:5060 SIP/2.0 487 Request Terminated. Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK49bd.98a53e2.3. Via: SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0. Via: SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. From: "7135178240" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. To: <sip:9492666205@GATEWAY_1>;tag=2a6c315af837f0a6a989449d0bd9acf6-09f6. Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. CSeq: 102 INVITE. Server: Bandwidth.com SDE (v1.0). Content-Length: 0. Warning: 392 GATEWAY_2:5060 "Noisy feedback tells: pid=32277 req_src_ip=OpenSER req_src_port=5060 in_uri=sip:+19496164708@GATEWAY_2:5060 out_uri=sip:+19496164708@4.68.250.148:5060 via_cnt==1". . # U +0.000089 OpenSER:5060 -> GATEWAY_2:5060 ACK sip:+19496164708@GATEWAY_2:5060 SIP/2.0. Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK49bd.98a53e2.3. From: "7135178240" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. To: <sip:9492666205@GATEWAY_1>;tag=2a6c315af837f0a6a989449d0bd9acf6-09f6. CSeq: 102 ACK. User-Agent: OpenSer (1.1.1-notls (x86_64/linux)). Content-Length: 0. . # U +0.012529 ATA:5062 -> OpenSER:5060 SIP/2.0 487 Request Terminated. To: <sip:9492666205@GATEWAY_1>;tag=cf04e5d3f5afda4fi0. From: "Cell Phone TX" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. CSeq: 102 INVITE. Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK49bd.a8a53e2.0. Via: SIP/2.0/UDP OpenSER;rport=5060;branch=z9hG4bK49bd.98a53e2.0. Via: SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0. Via: SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. Record-Route: <sip:OpenSER;lr=on;ftag=as0f6730bc>. Record-Route: <sip:OpenSER;lr=on;ftag=as0f6730bc>. Record-Route: <sip:GATEWAY_1;lr=on;ftag=as0f6730bc>. Server: Sipura/SPA841-3.1.4(a). Content-Length: 0. . # U +0.000074 OpenSER:5060 -> ATA:5062 ACK sip:9492666205@192.168.1.126:5062 SIP/2.0. Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK49bd.a8a53e2.0. From: "7135178240" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. To: <sip:9492666205@GATEWAY_1>;tag=cf04e5d3f5afda4fi0. CSeq: 102 ACK. User-Agent: OpenSer (1.1.1-notls (x86_64/linux)). Content-Length: 0. . # U +0.003301 ATA:5062 -> OpenSER:5060 SIP/2.0 200 OK. To: <sip:9492666205@GATEWAY_1>;tag=cf04e5d3f5afda4fi0. From: "7135178240" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. CSeq: 102 CANCEL. Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK49bd.a8a53e2.0. Via: SIP/2.0/UDP OpenSER;rport=5060;branch=z9hG4bK49bd.98a53e2.0. Record-Route: <sip:OpenSER;lr=on;ftag=as0f6730bc>. Server: Sipura/SPA841-3.1.4(a). Content-Length: 0. . # U +0.002123 GATEWAY_2:5060 -> OpenSER:5060 SIP/2.0 200 ok -- no more pending branches. Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK49bd.98a53e2.2. From: "7135178240" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. To: <sip:9492666205@GATEWAY_1>;tag=2a6c315af837f0a6a989449d0bd9acf6-91e7. CSeq: 102 CANCEL. Server: Bandwidth.com SDE (v1.0). Content-Length: 0. Warning: 392 GATEWAY_2:5060 "Noisy feedback tells: pid=32286 req_src_ip=OpenSER req_src_port=5060 in_uri=sip:+17608263100@GATEWAY_2:5060 out_uri=sip:+17608263100@GATEWAY_2:5060 via_cnt==1". . # U +0.005996 GATEWAY_2:5060 -> OpenSER:5060 SIP/2.0 200 ok -- no more pending branches. Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK49bd.98a53e2.3. From: "7135178240" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. To: <sip:9492666205@GATEWAY_1>;tag=2a6c315af837f0a6a989449d0bd9acf6-09f6. CSeq: 102 CANCEL. Server: Bandwidth.com SDE (v1.0). Content-Length: 0. Warning: 392 GATEWAY_2:5060 "Noisy feedback tells: pid=32277 req_src_ip=OpenSER req_src_port=5060 in_uri=sip:+19496164708@GATEWAY_2:5060 out_uri=sip:+19496164708@GATEWAY_2:5060 via_cnt==1". . ########exit 450 received, 0 dropped On 3/29/07, Brandon Armstead <brandon.armstead(a)gmail.com> wrote: > > Hello, here is the sipcap: > > interface: eth0 (74.52.58.48/255.255.255.240) > filter: ip and ( port 5060 ) > match: 9492666205 > ################### > U +0.000000 ATA:5062 -> OpenSER:5060 > NOTIFY sip:demo.demo.com SIP/2.0. > Via: SIP/2.0/UDP 192.168.1.126:5062;branch=z9hG4bK-73d5713f. > From: "Brandon Armstead" < sip:9492666205@demo.demo.com > >;tag=cb22d7a7f754d0o0. > To: <sip:demo.demo.com>. > Call-ID: 69b08a3a-8a5e9f10(a)192.168.1.126 . > CSeq: 176 NOTIFY. > Max-Forwards: 70. > Event: keep-alive. > User-Agent: Sipura/SPA841-3.1.4(a). > Content-Length: 0. > . > > # > U +0.000125 OpenSER:5060 -> ATA:5062 > SIP/2.0 200 ok. > Via: SIP/2.0/UDP 192.168.1.126:5062 > ;branch=z9hG4bK-73d5713f;rport=5062;received=ATA. > From: "Brandon Armstead" <sip:9492666205@demo.demo.com > >;tag=cb22d7a7f754d0o0. > To: <sip:demo.demo.com>;tag=329cfeaa6ded039da25ff8cbb8668bd2.a9e4. > Call-ID: 69b08a3a-8a5e9f10(a)192.168.1.126 . > CSeq: 176 NOTIFY. > Server: OpenSer (1.1.1-notls (x86_64/linux)). > Content-Length: 0. > Warning: 392 OpenSER:5060 "Noisy feedback tells: pid=15173 req_src_ip=ATA > req_src_port=5062 in_uri=sip: demo.demo.com out_uri=sip:demo.demo.comvia_cnt==1". > . > > ### > U +0.538693 GATEWAY_1:5060 -> OpenSER:5060 > INVITE sip:9492666205@OpenSER:5060 SIP/2.0. > Record-Route: <sip:GATEWAY_1;lr=on;ftag=as0f6730bc>. > Via: SIP/2.0/UDP GATEWAY_1;branch=z9hG4bK49bd.5c8e4a8.0. > Via: SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. > From: "7135178240" < sip:7135178240@64.24.35.73>;tag=as0f6730bc. > To: <sip:9492666205@GATEWAY_1>. > Contact: <sip:7135178240@64.24.35.73>. > Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. > CSeq: 102 INVITE. > User-Agent: US LEC VOIP. > Max-Forwards: 69. > Date: Thu, 29 Mar 2007 09:46:26 GMT. > Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY. > Content-Type: application/sdp. > Content-Length: 156. > . > v=0. > o=root 7184 7184 IN IP4 64.24.35.73. > s=session. > c=IN IP4 64.24.35.73. > t=0 0. > m=audio 31806 RTP/AVP 0. > a=rtpmap:0 PCMU/8000. > a=silenceSupp:off - - - -. > > # > U +0.002135 OpenSER:5060 -> GATEWAY_1:5060 > SIP/2.0 100 trying -- your call is important to us. > Via: SIP/2.0/UDP GATEWAY_1;branch= z9hG4bK49bd.5c8e4a8.0;rport=5060. > Via: SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. > From: "7135178240" < sip:7135178240@64.24.35.73>;tag=as0f6730bc. > To: <sip:9492666205@GATEWAY_1>. > Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. > CSeq: 102 INVITE. > Server: OpenSer (1.1.1-notls (x86_64/linux)). > Content-Length: 0. > Warning: 392 OpenSER:5060 "Noisy feedback tells: pid=15173 > req_src_ip=GATEWAY_1 req_src_port=5060 in_uri=sip:9492666205@OpenSER:5060 > out_uri= sip:9492666205@OpenSER:5060 via_cnt==2". > . > > # > U +0.000088 OpenSER:5060 -> GATEWAY_2:5060 > INVITE sip:+17144828306@GATEWAY_2:5060 SIP/2.0. > Record-Route: <sip:OpenSER;lr=on;ftag=as0f6730bc>. > Record-Route: <sip:GATEWAY_1;lr=on;ftag=as0f6730bc>. > Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK49bd.98a53e2.1. > Via: SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0. > Via: SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. > From: "7135178240" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. > To: <sip:9492666205@GATEWAY_1>. > Contact: <sip:7135178240@64.24.35.73>. > Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. > CSeq: 102 INVITE. > Max-Forwards: 68. > Date: Thu, 29 Mar 2007 09:46:26 GMT. > Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY. > Content-Type: application/sdp. > Content-Length: 174. > . > v=0. > o=root 7184 7184 IN IP4 64.24.35.73. > s=session. > c=IN IP4 OpenSER. > t=0 0. > m=audio 37158 RTP/AVP 0. > a=rtpmap:0 PCMU/8000. > a=silenceSupp:off - - - -. > a=nortpproxy:yes. > > # > U +0.000015 OpenSER:5060 -> GATEWAY_2:5060 > INVITE sip:+17608263100@GATEWAY_2:5060 SIP/2.0. > Record-Route: <sip:OpenSER;lr=on;ftag=as0f6730bc>. > Record-Route: <sip:GATEWAY_1;lr=on;ftag=as0f6730bc>. > Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK49bd.98a53e2.2. > Via: SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0. > Via: SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. > From: "7135178240" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. > To: <sip:9492666205@GATEWAY_1>. > Contact: < sip:7135178240@64.24.35.73>. > Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. > CSeq: 102 INVITE. > Max-Forwards: 68. > Date: Thu, 29 Mar 2007 09:46:26 GMT. > Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY. > Content-Type: application/sdp. > Content-Length: 174. > . > v=0. > o=root 7184 7184 IN IP4 64.24.35.73. > s=session. > c=IN IP4 OpenSER. > t=0 0. > m=audio 37158 RTP/AVP 0. > a=rtpmap:0 PCMU/8000. > a=silenceSupp:off - - - -. > a=nortpproxy:yes. > > # > U +0.000019 OpenSER:5060 -> GATEWAY_2:5060 > INVITE sip:+19496164708@GATEWAY _2:5060 SIP/2.0. > Record-Route: <sip:OpenSER;lr=on;ftag=as0f6730bc>. > Record-Route: <sip:GATEWAY_1;lr=on;ftag=as0f6730bc>. > Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK49bd.98a53e2.3. > Via: SIP/2.0/UDP GATEWAY_1;rport=5060;branch= z9hG4bK49bd.5c8e4a8.0. > Via: SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. > From: "7135178240" <sip:7135178240@64.24.35.73 >;tag=as0f6730bc. > To: <sip:9492666205@GATEWAY_1>. > Contact: <sip:7135178240@64.24.35.73>. > Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. > CSeq: 102 INVITE. > Max-Forwards: 68. > Date: Thu, 29 Mar 2007 09:46:26 GMT. > Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY. > Content-Type: application/sdp. > Content-Length: 174. > . > v=0. > o=root 7184 7184 IN IP4 64.24.35.73. > s=session. > c=IN IP4 OpenSER. > t=0 0. > m=audio 37158 RTP/AVP 0. > a=rtpmap:0 PCMU/8000. > a=silenceSupp:off - - - -. > a=nortpproxy:yes. > > # > U +0.022478 GATEWAY_2:5060 -> OpenSER:5060 > SIP/2.0 100 Trying bandwidth.com. > Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK49bd.98a53e2.1. > Via: SIP/2.0/UDP GATEWAY_1;rport=5060;branch= z9hG4bK49bd.5c8e4a8.0. > Via: SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. > From: "7135178240" <sip:7135178240@64.24.35.73 >;tag=as0f6730bc. > To: <sip:9492666205@GATEWAY_1>. > Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. > CSeq: 102 INVITE. > Server: Bandwidth.com SDE (v1.0). > Content-Length: 0. > Warning: 392 GATEWAY_2:5060 "Noisy feedback tells: pid=32282 > req_src_ip=OpenSER req_src_port=5060 in_uri=sip:+17144828306@GATEWAY_2:5060 out_uri= > sip:+17144828306@4.68.250.148:5060 via_cnt==3". > . > > # > U +0.000376 GATEWAY_2:5060 -> OpenSER:5060 > SIP/2.0 100 Trying bandwidth.com. > Via: SIP/2.0/UDP OpenSER;branch= z9hG4bK49bd.98a53e2.2. > Via: SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0. > Via: SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. > From: "7135178240" < sip:7135178240@64.24.35.73>;tag=as0f6730bc. > To: <sip:9492666205@GATEWAY_1>. > Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73 . > CSeq: 102 INVITE. > Server: Bandwidth.com SDE (v1.0). > Content-Length: 0. > Warning: 392 GATEWAY_2:5060 "Noisy feedback tells: pid=32282 > req_src_ip=OpenSER req_src_port=5060 in_uri= sip:+17608263100@GATEWAY_2:5060 > out_uri=sip:+17608263100@4.68.250.148:5060 via_cnt==3". > . > > # > U +0.000124 GATEWAY_2:5060 -> OpenSER:5060 > SIP/2.0 100 Trying bandwidth.com . > Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK49bd.98a53e2.3. > Via: SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0. > Via: SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. > From: "7135178240" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. > To: <sip:9492666205@GATEWAY_1>. > Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. > CSeq: 102 INVITE. > Server: Bandwidth.com SDE (v1.0). > Content-Length: 0. > Warning: 392 GATEWAY_2:5060 "Noisy feedback tells: pid=32282 > req_src_ip=OpenSER req_src_port=5060 in_uri= sip:+19496164708@GATEWAY_2:5060 > out_uri=sip:+19496164708@4.68.250.148:5060 via_cnt==3". > . > > ####### > U +0.110379 OpenSER:5060 -> ATA:5062 > INVITE sip:9492666205@192.168.1.126:5062 SIP/2.0. > Record-Route: <sip:OpenSER;lr=on;ftag=as0f6730bc>. > Record-Route: <sip:OpenSER;lr=on;ftag=as0f6730bc>. > Record-Route: <sip:GATEWAY_1;lr=on;ftag=as0f6730bc>. > Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK49bd.a8a53e2.0. > Via: SIP/2.0/UDP OpenSER;rport=5060;branch= z9hG4bK49bd.98a53e2.0. > Via: SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0. > Via: SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. > From: "Cell Phone TX" < sip:7135178240@64.24.35.73>;tag=as0f6730bc. > To: <sip:9492666205@GATEWAY_1>. > Contact: <sip:7135178240@OpenSER:5060>. > Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. > CSeq: 102 INVITE. > Max-Forwards: 67. > Date: Thu, 29 Mar 2007 09:46:26 GMT. > Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY. > Content-Type: application/sdp. > Content-Length: 174. > . > v=0. > o=root 7184 7184 IN IP4 64.24.35.73. > s=session. > c=IN IP4 OpenSER. > t=0 0. > m=audio 37158 RTP/AVP 0. > a=rtpmap:0 PCMU/8000. > a=silenceSupp:off - - - -. > a=nortpproxy:yes. > > # > U +0.035038 ATA:5062 -> OpenSER:5060 > SIP/2.0 100 Trying. > To: <sip:9492666205@GATEWAY_1>. > From: "Cell Phone TX" < sip:7135178240@64.24.35.73>;tag=as0f6730bc. > Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. > CSeq: 102 INVITE. > Via: SIP/2.0/UDP OpenSER;branch= z9hG4bK49bd.a8a53e2.0. > Via: SIP/2.0/UDP OpenSER;rport=5060;branch=z9hG4bK49bd.98a53e2.0. > Via: SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0. > Via: SIP/2.0/UDP 64.24.35.73:5060 ;branch=z9hG4bK529c9661;rport=5060. > Record-Route: <sip:OpenSER;lr=on;ftag=as0f6730bc>. > Record-Route: <sip:OpenSER;lr=on;ftag=as0f6730bc>. > Record-Route: <sip:GATEWAY_1;lr=on;ftag=as0f6730bc>. > Server: Sipura/SPA841-3.1.4(a). > Content-Length: 0. > . > > # > U +0.035106 ATA:5062 -> OpenSER:5060 > SIP/2.0 180 Ringing. > To: <sip:9492666205@GATEWAY_1>;tag=cf04e5d3f5afda4fi0. > From: "Cell Phone TX" < sip:7135178240@64.24.35.73>;tag=as0f6730bc. > Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. > CSeq: 102 INVITE. > Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK49bd.a8a53e2.0. > Via: SIP/2.0/UDP OpenSER;rport=5060;branch=z9hG4bK49bd.98a53e2.0. > Via: SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0. > Via: SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. > Record-Route: <sip:OpenSER;lr=on;ftag=as0f6730bc>. > Record-Route: <sip:OpenSER;lr=on;ftag=as0f6730bc>. > Record-Route: <sip:GATEWAY_1;lr=on;ftag=as0f6730bc>. > Server: Sipura/SPA841-3.1.4(a). > Content-Length: 0. > . > > # > U +0.000287 OpenSER:5060 -> GATEWAY_1:5060 > SIP/2.0 180 Ringing. > To: <sip:9492666205@GATEWAY_1>;tag=cf04e5d3f5afda4fi0. > From: "Cell Phone TX" < sip:7135178240@64.24.35.73>;tag=as0f6730bc. > Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. > CSeq: 102 INVITE. > Via: SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0. > Via: SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. > Record-Route: <sip:OpenSER;lr=on;ftag=as0f6730bc>. > Record-Route: <sip:OpenSER;lr=on;ftag=as0f6730bc>. > Record-Route: <sip:GATEWAY_1;lr=on;ftag=as0f6730bc>. > Server: Sipura/SPA841-3.1.4(a). > Content-Length: 0. > . > > ######################################## > U +6.689904 GATEWAY_2:5060 -> OpenSER:5060 > SIP/2.0 183 Session Progress. > Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK49bd.98a53e2.1,SIP/2.0/UDP > GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0,SIP/2.0/UDP > 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. > Record-Route: > <sip:GATEWAY_2;lr;ftag=as0f6730bc>,<sip:OpenSER;lr=on;ftag=as0f6730bc>,<sip:GATEWAY_1;lr=on;ftag=as0f6730bc>. > From: "7135178240" < sip:7135178240@64.24.35.73>;tag=as0f6730bc. > To: <sip:9492666205@GATEWAY_1>;tag=VPST506071629460. > Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. > CSeq: 102 INVITE. > Contact: <sip:+17144828306@4.68.250.148:5060;transport=udp>. > Content-Type: application/sdp. > Content-Length: 128. > . > v=0. > o=- 1175161585 1175161586 IN IP4 209.244.42.237. > s=-. > c=IN IP4 209.244.42.237. > t=0 0. > m=audio 64520 RTP/AVP 0. > a=ptime:20. > > # > U +0.000286 OpenSER:5060 -> GATEWAY_1:5060 > SIP/2.0 183 Session Progress. > Via: SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0,SIP/2.0/UDP > 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. > Record-Route: > <sip:GATEWAY_2;lr;ftag=as0f6730bc>,<sip:OpenSER;lr=on;ftag=as0f6730bc>,<sip:GATEWAY_1;lr=on;ftag=as0f6730bc>. > > From: "7135178240" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. > To: <sip:9492666205@GATEWAY_1>;tag=VPST506071629460. > Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. > CSeq: 102 INVITE. > Contact: <sip:+17144828306@4.68.250.148:5060;transport=udp>. > Content-Type: application/sdp. > Content-Length: 143. > . > v=0. > o=- 1175161585 1175161586 IN IP4 209.244.42.237. > s=-. > c=IN IP4 OpenSER. > t=0 0. > m=audio 37160 RTP/AVP 0. > a=ptime:20. > a=nortpproxy:yes. > > # > U +0.139883 GATEWAY_2:5060 -> OpenSER:5060 > SIP/2.0 183 Session Progress. > Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK49bd.98a53e2.1,SIP/2.0/UDP > GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0,SIP/2.0/UDP > 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. > Record-Route: > <sip:GATEWAY_2;lr;ftag=as0f6730bc>,<sip:OpenSER;lr=on;ftag=as0f6730bc>,<sip:GATEWAY_1;lr=on;ftag=as0f6730bc>. > From: "7135178240" < sip:7135178240@64.24.35.73>;tag=as0f6730bc. > To: <sip:9492666205@GATEWAY_1>;tag=VPST506071629460. > Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73 . > CSeq: 102 INVITE. > Contact: <sip:+17144828306@4.68.250.148:5060;transport=udp>. > Content-Type: application/sdp. > Content-Length: 128. > . > v=0. > o=- 1175161585 1175161586 IN IP4 209.244.42.237. > s=-. > c=IN IP4 209.244.42.237. > t=0 0. > m=audio 64520 RTP/AVP 0. > a=ptime:20. > > # > U +0.000251 GATEWAY_2:5060 -> OpenSER:5060 > SIP/2.0 183 Session Progress. > Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK49bd.98a53e2.1,SIP/2.0/UDP > GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0,SIP/2.0/UDP > 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. > Record-Route: > <sip:GATEWAY_2;lr;ftag=as0f6730bc>,<sip:OpenSER;lr=on;ftag=as0f6730bc>,<sip:GATEWAY_1;lr=on;ftag=as0f6730bc>. > From: "7135178240" < sip:7135178240@64.24.35.73>;tag=as0f6730bc. > To: <sip:9492666205@GATEWAY_1>;tag=VPST506071629460. > Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73 . > CSeq: 102 INVITE. > Contact: <sip:+17144828306@4.68.250.148:5060;transport=udp>. > Content-Type: application/sdp. > Content-Length: 128. > . > v=0. > o=- 1175161585 1175161586 IN IP4 209.244.42.237. > s=-. > c=IN IP4 209.244.42.237. > t=0 0. > m=audio 64520 RTP/AVP 0. > a=ptime:20. > > # > U +0.003394 OpenSER:5060 -> GATEWAY_1:5060 > SIP/2.0 183 Session Progress. > Via: SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0,SIP/2.0/UDP > 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. > Record-Route: > <sip:GATEWAY_2;lr;ftag=as0f6730bc>,<sip:OpenSER;lr=on;ftag=as0f6730bc>,<sip:GATEWAY_1;lr=on;ftag=as0f6730bc>. > > From: "7135178240" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. > To: <sip:9492666205@GATEWAY_1>;tag=VPST506071629460. > Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. > CSeq: 102 INVITE. > Contact: <sip:+17144828306@4.68.250.148:5060;transport=udp>. > Content-Type: application/sdp. > Content-Length: 143. > . > v=0. > o=- 1175161585 1175161586 IN IP4 209.244.42.237. > s=-. > c=IN IP4 OpenSER. > t=0 0. > m=audio 37160 RTP/AVP 0. > a=ptime:20. > a=nortpproxy:yes. > > # > U +0.000090 OpenSER:5060 -> GATEWAY_1:5060 > SIP/2.0 183 Session Progress. > Via: SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0,SIP/2.0/UDP > 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. > Record-Route: > <sip:GATEWAY_2;lr;ftag=as0f6730bc>,<sip:OpenSER;lr=on;ftag=as0f6730bc>,<sip:GATEWAY_1;lr=on;ftag=as0f6730bc>. > > From: "7135178240" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. > To: <sip:9492666205@GATEWAY_1>;tag=VPST506071629460. > Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. > CSeq: 102 INVITE. > Contact: <sip:+17144828306@4.68.250.148:5060;transport=udp>. > Content-Type: application/sdp. > Content-Length: 143. > . > v=0. > o=- 1175161585 1175161586 IN IP4 209.244.42.237. > s=-. > c=IN IP4 OpenSER. > t=0 0. > m=audio 37160 RTP/AVP 0. > a=ptime:20. > a=nortpproxy:yes. > > ####### > U +4.012603 GATEWAY_2:5060 -> OpenSER:5060 > SIP/2.0 183 Session Progress. > Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK49bd.98a53e2.1,SIP/2.0/UDP > GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0,SIP/2.0/UDP > 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. > Record-Route: > <sip:GATEWAY_2;lr;ftag=as0f6730bc>,<sip:OpenSER;lr=on;ftag=as0f6730bc>,<sip:GATEWAY_1;lr=on;ftag=as0f6730bc>. > From: "7135178240" < sip:7135178240@64.24.35.73>;tag=as0f6730bc. > To: <sip:9492666205@GATEWAY_1>;tag=VPST506071629460. > Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73 . > CSeq: 102 INVITE. > Contact: <sip:+17144828306@4.68.250.148:5060;transport=udp>. > Content-Type: application/sdp. > Content-Length: 128. > . > v=0. > o=- 1175161585 1175161586 IN IP4 209.244.42.237. > s=-. > c=IN IP4 209.244.42.237. > t=0 0. > m=audio 64520 RTP/AVP 0. > a=ptime:20. > > # > U +0.000126 GATEWAY_2:5060 -> OpenSER:5060 > SIP/2.0 183 Session Progress. > Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK49bd.98a53e2.1,SIP/2.0/UDP > GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0,SIP/2.0/UDP > 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. > Record-Route: > <sip:GATEWAY_2;lr;ftag=as0f6730bc>,<sip:OpenSER;lr=on;ftag=as0f6730bc>,<sip:GATEWAY_1;lr=on;ftag=as0f6730bc>. > From: "7135178240" < sip:7135178240@64.24.35.73>;tag=as0f6730bc. > To: <sip:9492666205@GATEWAY_1>;tag=VPST506071629460. > Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73 . > CSeq: 102 INVITE. > Contact: <sip:+17144828306@4.68.250.148:5060;transport=udp>. > Content-Type: application/sdp. > Content-Length: 128. > . > v=0. > o=- 1175161585 1175161586 IN IP4 209.244.42.237. > s=-. > c=IN IP4 209.244.42.237. > t=0 0. > m=audio 64520 RTP/AVP 0. > a=ptime:20. > > # > U +0.007244 OpenSER:5060 -> GATEWAY_1:5060 > SIP/2.0 183 Session Progress. > Via: SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0,SIP/2.0/UDP > 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. > Record-Route: > <sip:GATEWAY_2;lr;ftag=as0f6730bc>,<sip:OpenSER;lr=on;ftag=as0f6730bc>,<sip:GATEWAY_1;lr=on;ftag=as0f6730bc>. > > From: "7135178240" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. > To: <sip:9492666205@GATEWAY_1>;tag=VPST506071629460. > Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. > CSeq: 102 INVITE. > Contact: <sip:+17144828306@4.68.250.148:5060;transport=udp>. > Content-Type: application/sdp. > Content-Length: 143. > . > v=0. > o=- 1175161585 1175161586 IN IP4 209.244.42.237. > s=-. > c=IN IP4 OpenSER. > t=0 0. > m=audio 37160 RTP/AVP 0. > a=ptime:20. > a=nortpproxy:yes. > > # > U +0.000041 OpenSER:5060 -> GATEWAY_1:5060 > SIP/2.0 183 Session Progress. > Via: SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0,SIP/2.0/UDP > 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. > Record-Route: > <sip:GATEWAY_2;lr;ftag=as0f6730bc>,<sip:OpenSER;lr=on;ftag=as0f6730bc>,<sip:GATEWAY_1;lr=on;ftag=as0f6730bc>. > > From: "7135178240" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. > To: <sip:9492666205@GATEWAY_1>;tag=VPST506071629460. > Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. > CSeq: 102 INVITE. > Contact: <sip:+17144828306@4.68.250.148:5060;transport=udp>. > Content-Type: application/sdp. > Content-Length: 143. > . > v=0. > o=- 1175161585 1175161586 IN IP4 209.244.42.237. > s=-. > c=IN IP4 OpenSER. > t=0 0. > m=audio 37160 RTP/AVP 0. > a=ptime:20. > a=nortpproxy:yes. > > ########## > U +3.433005 ATA:5062 -> OpenSER:5060 > NOTIFY sip: demo.demo.com SIP/2.0. > Via: SIP/2.0/UDP 192.168.1.126:5062;branch=z9hG4bK-689dad84. > From: "Brandon Armstead" < sip:9492666205@demo.demo.com > >;tag=cb22d7a7f754d0o0. > To: <sip:demo.demo.com>. > Call-ID: 69b08a3a-8a5e9f10(a)192.168.1.126 . > CSeq: 177 NOTIFY. > Max-Forwards: 70. > Event: keep-alive. > User-Agent: Sipura/SPA841-3.1.4(a). > Content-Length: 0. > . > > # > U +0.000095 OpenSER:5060 -> ATA:5062 > SIP/2.0 200 ok. > Via: SIP/2.0/UDP 192.168.1.126:5062 > ;branch=z9hG4bK-689dad84;rport=5062;received=ATA. > From: "Brandon Armstead" <sip:9492666205@demo.demo.com > >;tag=cb22d7a7f754d0o0. > To: <sip:demo.demo.com>;tag=329cfeaa6ded039da25ff8cbb8668bd2.2d30. > Call-ID: 69b08a3a-8a5e9f10(a)192.168.1.126 . > CSeq: 177 NOTIFY. > Server: OpenSer (1.1.1-notls (x86_64/linux)). > Content-Length: 0. > Warning: 392 OpenSER:5060 "Noisy feedback tells: pid=15175 req_src_ip=ATA > req_src_port=5062 in_uri=sip: demo.demo.com out_uri=sip:demo.demo.comvia_cnt==1". > . > > ## > U +0.575203 GATEWAY_2:5060 -> OpenSER:5060 > SIP/2.0 183 Session Progress. > Via: SIP/2.0/UDP OpenSER;branch= z9hG4bK49bd.98a53e2.1,SIP/2.0/UDP > GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0,SIP/2.0/UDP > 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. > Record-Route: > <sip:GATEWAY_2;lr;ftag=as0f6730bc>,<sip:OpenSER;lr=on;ftag=as0f6730bc>,<sip:GATEWAY_1;lr=on;ftag=as0f6730bc>. > > From: "7135178240" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. > To: <sip:9492666205@GATEWAY_1>;tag=VPST506071629460. > Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. > CSeq: 102 INVITE. > Contact: <sip:+17144828306@4.68.250.148:5060;transport=udp>. > Content-Type: application/sdp. > Content-Length: 128. > . > v=0. > o=- 1175161585 1175161586 IN IP4 209.244.42.237. > s=-. > c=IN IP4 209.244.42.237. > t=0 0. > m=audio 64520 RTP/AVP 0. > a=ptime:20. > > # > U +0.000125 GATEWAY_2:5060 -> OpenSER:5060 > SIP/2.0 183 Session Progress. > Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK49bd.98a53e2.1,SIP/2.0/UDP > GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0,SIP/2.0/UDP > 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. > Record-Route: > <sip:GATEWAY_2;lr;ftag=as0f6730bc>,<sip:OpenSER;lr=on;ftag=as0f6730bc>,<sip:GATEWAY_1;lr=on;ftag=as0f6730bc>. > From: "7135178240" < sip:7135178240@64.24.35.73>;tag=as0f6730bc. > To: <sip:9492666205@GATEWAY_1>;tag=VPST506071629460. > Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73 . > CSeq: 102 INVITE. > Contact: <sip:+17144828306@4.68.250.148:5060;transport=udp>. > Content-Type: application/sdp. > Content-Length: 128. > . > v=0. > o=- 1175161585 1175161586 IN IP4 209.244.42.237. > s=-. > c=IN IP4 209.244.42.237. > t=0 0. > m=audio 64520 RTP/AVP 0. > a=ptime:20. > > # > U +0.003655 OpenSER:5060 -> GATEWAY_1:5060 > SIP/2.0 183 Session Progress. > Via: SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0,SIP/2.0/UDP > 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. > Record-Route: > <sip:GATEWAY_2;lr;ftag=as0f6730bc>,<sip:OpenSER;lr=on;ftag=as0f6730bc>,<sip:GATEWAY_1;lr=on;ftag=as0f6730bc>. > > From: "7135178240" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. > To: <sip:9492666205@GATEWAY_1>;tag=VPST506071629460. > Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. > CSeq: 102 INVITE. > Contact: <sip:+17144828306@4.68.250.148:5060;transport=udp>. > Content-Type: application/sdp. > Content-Length: 143. > . > v=0. > o=- 1175161585 1175161586 IN IP4 209.244.42.237. > s=-. > c=IN IP4 OpenSER. > t=0 0. > m=audio 37160 RTP/AVP 0. > a=ptime:20. > a=nortpproxy:yes. > > # > U +0.000041 OpenSER:5060 -> GATEWAY_1:5060 > SIP/2.0 183 Session Progress. > Via: SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0,SIP/2.0/UDP > 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. > Record-Route: > <sip:GATEWAY_2;lr;ftag=as0f6730bc>,<sip:OpenSER;lr=on;ftag=as0f6730bc>,<sip:GATEWAY_1;lr=on;ftag=as0f6730bc>. > > From: "7135178240" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. > To: <sip:9492666205@GATEWAY_1>;tag=VPST506071629460. > Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. > CSeq: 102 INVITE. > Contact: <sip:+17144828306@4.68.250.148:5060;transport=udp>. > Content-Type: application/sdp. > Content-Length: 143. > . > v=0. > o=- 1175161585 1175161586 IN IP4 209.244.42.237. > s=-. > c=IN IP4 OpenSER. > t=0 0. > m=audio 37160 RTP/AVP 0. > a=ptime:20. > a=nortpproxy:yes. > > ################### > U +4.011642 GATEWAY_2:5060 -> OpenSER:5060 > SIP/2.0 183 Session Progress. > Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK49bd.98a53e2.1,SIP/2.0/UDP > GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0,SIP/2.0/UDP > 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. > Record-Route: > <sip:GATEWAY_2;lr;ftag=as0f6730bc>,<sip:OpenSER;lr=on;ftag=as0f6730bc>,<sip:GATEWAY_1;lr=on;ftag=as0f6730bc>. > From: "7135178240" < sip:7135178240@64.24.35.73>;tag=as0f6730bc. > To: <sip:9492666205@GATEWAY_1>;tag=VPST506071629460. > Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73 . > CSeq: 102 INVITE. > Contact: <sip:+17144828306@4.68.250.148:5060;transport=udp>. > Content-Type: application/sdp. > Content-Length: 128. > . > v=0. > o=- 1175161585 1175161586 IN IP4 209.244.42.237. > s=-. > c=IN IP4 209.244.42.237. > t=0 0. > m=audio 64520 RTP/AVP 0. > a=ptime:20. > > # > U +0.000377 GATEWAY_2:5060 -> OpenSER:5060 > SIP/2.0 183 Session Progress. > Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK49bd.98a53e2.1,SIP/2.0/UDP > GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0,SIP/2.0/UDP > 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. > Record-Route: > <sip:GATEWAY_2;lr;ftag=as0f6730bc>,<sip:OpenSER;lr=on;ftag=as0f6730bc>,<sip:GATEWAY_1;lr=on;ftag=as0f6730bc>. > From: "7135178240" < sip:7135178240@64.24.35.73>;tag=as0f6730bc. > To: <sip:9492666205@GATEWAY_1>;tag=VPST506071629460. > Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73 . > CSeq: 102 INVITE. > Contact: <sip:+17144828306@4.68.250.148:5060;transport=udp>. > Content-Type: application/sdp. > Content-Length: 128. > . > v=0. > o=- 1175161585 1175161586 IN IP4 209.244.42.237. > s=-. > c=IN IP4 209.244.42.237. > t=0 0. > m=audio 64520 RTP/AVP 0. > a=ptime:20. > > # > U +0.000192 OpenSER:5060 -> GATEWAY_1:5060 > SIP/2.0 183 Session Progress. > Via: SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0,SIP/2.0/UDP > 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. > Record-Route: > <sip:GATEWAY_2;lr;ftag=as0f6730bc>,<sip:OpenSER;lr=on;ftag=as0f6730bc>,<sip:GATEWAY_1;lr=on;ftag=as0f6730bc>. > > From: "7135178240" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. > To: <sip:9492666205@GATEWAY_1>;tag=VPST506071629460. > Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. > CSeq: 102 INVITE. > Contact: <sip:+17144828306@4.68.250.148:5060;transport=udp>. > Content-Type: application/sdp. > Content-Length: 143. > . > v=0. > o=- 1175161585 1175161586 IN IP4 209.244.42.237. > s=-. > c=IN IP4 OpenSER. > t=0 0. > m=audio 37160 RTP/AVP 0. > a=ptime:20. > a=nortpproxy:yes. > > # > U +0.011882 OpenSER:5060 -> GATEWAY_1:5060 > SIP/2.0 183 Session Progress. > Via: SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0,SIP/2.0/UDP > 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. > Record-Route: > <sip:GATEWAY_2;lr;ftag=as0f6730bc>,<sip:OpenSER;lr=on;ftag=as0f6730bc>,<sip:GATEWAY_1;lr=on;ftag=as0f6730bc>. > > From: "7135178240" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. > To: <sip:9492666205@GATEWAY_1>;tag=VPST506071629460. > Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. > CSeq: 102 INVITE. > Contact: <sip:+17144828306@4.68.250.148:5060;transport=udp>. > Content-Type: application/sdp. > Content-Length: 143. > . > v=0. > o=- 1175161585 1175161586 IN IP4 209.244.42.237. > s=-. > c=IN IP4 OpenSER. > t=0 0. > m=audio 37160 RTP/AVP 0. > a=ptime:20. > a=nortpproxy:yes. > > ############### > U +4.003638 GATEWAY_2:5060 -> OpenSER:5060 > SIP/2.0 183 Session Progress. > Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK49bd.98a53e2.1,SIP/2.0/UDP > GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0,SIP/2.0/UDP > 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. > Record-Route: > <sip:GATEWAY_2;lr;ftag=as0f6730bc>,<sip:OpenSER;lr=on;ftag=as0f6730bc>,<sip:GATEWAY_1;lr=on;ftag=as0f6730bc>. > From: "7135178240" < sip:7135178240@64.24.35.73>;tag=as0f6730bc. > To: <sip:9492666205@GATEWAY_1>;tag=VPST506071629460. > Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73 . > CSeq: 102 INVITE. > Contact: <sip:+17144828306@4.68.250.148:5060;transport=udp>. > Content-Type: application/sdp. > Content-Length: 128. > . > v=0. > o=- 1175161585 1175161586 IN IP4 209.244.42.237. > s=-. > c=IN IP4 209.244.42.237. > t=0 0. > m=audio 64520 RTP/AVP 0. > a=ptime:20. > > # > U +0.008482 OpenSER:5060 -> GATEWAY_1:5060 > SIP/2.0 183 Session Progress. > Via: SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0,SIP/2.0/UDP > 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. > Record-Route: > <sip:GATEWAY_2;lr;ftag=as0f6730bc>,<sip:OpenSER;lr=on;ftag=as0f6730bc>,<sip:GATEWAY_1;lr=on;ftag=as0f6730bc>. > > From: "7135178240" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. > To: <sip:9492666205@GATEWAY_1>;tag=VPST506071629460. > Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. > CSeq: 102 INVITE. > Contact: <sip:+17144828306@4.68.250.148:5060;transport=udp>. > Content-Type: application/sdp. > Content-Length: 143. > . > v=0. > o=- 1175161585 1175161586 IN IP4 209.244.42.237. > s=-. > c=IN IP4 OpenSER. > t=0 0. > m=audio 37160 RTP/AVP 0. > a=ptime:20. > a=nortpproxy:yes. > > ######################################################### > U +2.220013 OpenSER:5060 -> GATEWAY_2:5060 > CANCEL sip:+17608263100@GATEWAY_2:5060 SIP/2.0. > Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK49bd.98a53e2.2. > From: "7135178240" < sip:7135178240@64.24.35.73>;tag=as0f6730bc. > Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. > To: <sip:9492666205@GATEWAY_1>. > CSeq: 102 CANCEL. > User-Agent: OpenSer (1.1.1-notls (x86_64/linux)). > Content-Length: 0. > . > > # > U +0.000015 OpenSER:5060 -> GATEWAY_2:5060 > CANCEL sip:+19496164708@GATEWAY_2:5060 SIP/2.0. > Via: SIP/2.0/UDP OpenSER;branch= z9hG4bK49bd.98a53e2.3. > From: "7135178240" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. > Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. > To: <sip:9492666205@GATEWAY_1>. > CSeq: 102 CANCEL. > User-Agent: OpenSer (1.1.1-notls (x86_64/linux)). > Content-Length: 0. > . > > # > U +0.008073 OpenSER:5060 -> ATA:5062 > CANCEL sip:9492666205@192.168.1.126:5062 SIP/2.0. > Max-Forwards: 10. > Record-Route: <sip:OpenSER;lr=on;ftag=as0f6730bc>. > Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK49bd.a8a53e2.0. > Via: SIP/2.0/UDP OpenSER;rport=5060;branch= z9hG4bK49bd.98a53e2.0. > From: "7135178240" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. > Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. > To: <sip:9492666205@GATEWAY_1>. > CSeq: 102 CANCEL. > Content-Length: 0. > . > > # > U +0.023630 GATEWAY_2:5060 -> OpenSER:5060 > SIP/2.0 487 Request Terminated. > Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK49bd.98a53e2.2. > Via: SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0. > Via: SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. > From: "7135178240" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. > To: <sip:9492666205@GATEWAY_1>;tag=2a6c315af837f0a6a989449d0bd9acf6-91e7. > Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. > CSeq: 102 INVITE. > Server: Bandwidth.com SDE (v1.0). > Content-Length: 0. > Warning: 392 GATEWAY_2:5060 "Noisy feedback tells: pid=32286 > req_src_ip=OpenSER req_src_port=5060 in_uri=sip:+17608263100@GATEWAY_2:5060 > out_uri=sip:+17608263100@4.68.250.148:5060 via_cnt==1". > . > > # > U +0.000096 OpenSER:5060 -> GATEWAY_2:5060 > ACK sip:+17608263100@GATEWAY_2:5060 SIP/2.0. > Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK49bd.98a53e2.2. > From: "7135178240" < sip:7135178240@64.24.35.73>;tag=as0f6730bc. > Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. > To: <sip:9492666205@GATEWAY_1>;tag=2a6c315af837f0a6a989449d0bd9acf6-91e7. > CSeq: 102 ACK. > User-Agent: OpenSer (1.1.1-notls (x86_64/linux)). > Content-Length: 0. > . > > # > U +0.005775 GATEWAY_2:5060 -> OpenSER:5060 > SIP/2.0 487 Request Terminated. > Via: SIP/2.0/UDP OpenSER;branch= z9hG4bK49bd.98a53e2.3. > Via: SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0. > Via: SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK529c9661;rport=5060. > From: "7135178240" < sip:7135178240@64.24.35.73>;tag=as0f6730bc. > To: <sip:9492666205@GATEWAY_1>;tag=2a6c315af837f0a6a989449d0bd9acf6-09f6. > Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. > CSeq: 102 INVITE. > Server: Bandwidth.com SDE (v1.0). > Content-Length: 0. > Warning: 392 GATEWAY_2:5060 "Noisy feedback tells: pid=32277 > req_src_ip=OpenSER req_src_port=5060 in_uri= sip:+19496164708@GATEWAY_2:5060 > out_uri=sip:+19496164708@4.68.250.148:5060 via_cnt==1". > . > > # > U +0.000089 OpenSER:5060 -> GATEWAY_2:5060 > ACK sip:+19496164708@GATEWAY_2:5060 SIP/2.0. > Via: SIP/2.0/UDP OpenSER;branch= z9hG4bK49bd.98a53e2.3. > From: "7135178240" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. > Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. > To: <sip:9492666205@GATEWAY_1>;tag=2a6c315af837f0a6a989449d0bd9acf6-09f6. > CSeq: 102 ACK. > User-Agent: OpenSer (1.1.1-notls (x86_64/linux)). > Content-Length: 0. > . > > # > U +0.012529 ATA:5062 -> OpenSER:5060 > SIP/2.0 487 Request Terminated. > To: <sip:9492666205@GATEWAY_1>;tag=cf04e5d3f5afda4fi0. > From: "Cell Phone TX" < sip:7135178240@64.24.35.73>;tag=as0f6730bc. > Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. > CSeq: 102 INVITE. > Via: SIP/2.0/UDP OpenSER;branch= z9hG4bK49bd.a8a53e2.0. > Via: SIP/2.0/UDP OpenSER;rport=5060;branch=z9hG4bK49bd.98a53e2.0. > Via: SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK49bd.5c8e4a8.0. > Via: SIP/2.0/UDP 64.24.35.73:5060 ;branch=z9hG4bK529c9661;rport=5060. > Record-Route: <sip:OpenSER;lr=on;ftag=as0f6730bc>. > Record-Route: <sip:OpenSER;lr=on;ftag=as0f6730bc>. > Record-Route: <sip:GATEWAY_1;lr=on;ftag=as0f6730bc>. > Server: Sipura/SPA841-3.1.4(a). > Content-Length: 0. > . > > # > U +0.000074 OpenSER:5060 -> ATA:5062 > ACK sip:9492666205@192.168.1.126:5062 SIP/2.0. > Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK49bd.a8a53e2.0 . > From: "7135178240" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. > Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73 . > To: <sip:9492666205@GATEWAY_1>;tag=cf04e5d3f5afda4fi0. > CSeq: 102 ACK. > User-Agent: OpenSer (1.1.1-notls (x86_64/linux)). > Content-Length: 0. > . > > # > U +0.003301 ATA:5062 -> OpenSER:5060 > SIP/2.0 200 OK. > To: <sip:9492666205@GATEWAY_1>;tag=cf04e5d3f5afda4fi0. > From: "7135178240" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. > Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. > CSeq: 102 CANCEL. > Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK49bd.a8a53e2.0. > Via: SIP/2.0/UDP OpenSER;rport=5060;branch= z9hG4bK49bd.98a53e2.0. > Record-Route: <sip:OpenSER;lr=on;ftag=as0f6730bc>. > Server: Sipura/SPA841-3.1.4(a). > Content-Length: 0. > . > > # > U +0.002123 GATEWAY_2:5060 -> OpenSER:5060 > SIP/2.0 200 ok -- no more pending branches. > Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK49bd.98a53e2.2. > From: "7135178240" <sip:7135178240@64.24.35.73>;tag=as0f6730bc. > Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. > To: <sip:9492666205@GATEWAY_1>;tag=2a6c315af837f0a6a989449d0bd9acf6-91e7. > CSeq: 102 CANCEL. > Server: Bandwidth.com SDE (v1.0 ). > Content-Length: 0. > Warning: 392 GATEWAY_2:5060 "Noisy feedback tells: pid=32286 > req_src_ip=OpenSER req_src_port=5060 in_uri=sip:+17608263100@GATEWAY_2:5060 > out_uri=sip:+17608263100@GATEWAY_2:5060 via_cnt==1". > . > > # > U +0.005996 GATEWAY_2:5060 -> OpenSER:5060 > SIP/2.0 200 ok -- no more pending branches. > Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK49bd.98a53e2.3. > From: "7135178240" < sip:7135178240@64.24.35.73>;tag=as0f6730bc. > Call-ID: 132193751d2413ea41f9f02e378ec608(a)64.24.35.73. > To: <sip:9492666205@GATEWAY_1>;tag=2a6c315af837f0a6a989449d0bd9acf6-09f6. > CSeq: 102 CANCEL. > Server: Bandwidth.com SDE (v1.0). > Content-Length: 0. > Warning: 392 GATEWAY_2:5060 "Noisy feedback tells: pid=32277 > req_src_ip=OpenSER req_src_port=5060 in_uri= sip:+19496164708@GATEWAY_2:5060 > out_uri=sip:+19496164708@GATEWAY_2:5060 via_cnt==1". > . > > ########exit > 450 received, 0 dropped > > > On 3/29/07, Klaus Darilion <klaus.mailinglists(a)pernau.at> wrote: > > > > > > > > Brandon Armstead wrote: > > > Hello Klaus, > > > Any ideas, > > > > > > not without a SIP dump (ngrep port 5060) > > > > btw: please Cc: the list > > > > regards > > klaus > > > > > > > > > > > > thanks! > > > > > > On 3/29/07, Klaus Darilion <klaus.mailinglists(a)pernau.at> wrote: > > >> > > >> > > >> > > >> Brandon Armstead wrote: > > >> > Hello everyone, > > >> > > > >> > I'm running into a issue, where I'm trying to implement parallel > > >> > forking, so basically on incoming calls from gateway, I want to > > then > > >> > Re-Invite, and send out the calls to multiple destinations, I am > > >> currently, > > >> > > >> FYI: The term "Re-INVITE" is wrong in this scenario. The proxy just > > >> forwards the INVITE doing parallel forking (in openser terminology: > > >> creates multiple branches). As sson as one phone picks up, this > > branch > > >> is the winning branch and the other branches will be canceled. > > >> > > >> A reINVITE is an in-dialog INVITE, e.g. used for modifying the media > > >> session (putting the call on hold, enable/disable video ...) > > >> > > >> regards > > >> klaus > > >> > > >> > using avp_db_query to grab the sip uri's and throwing them into an > > avp > > >> > list, > > >> > and avp_pushto("$ru", "$avp(i:1)/g"); This all works fine and > > good, > > >> invite > > >> > comes in, and then sends Re-Invites, however, there seems to be > > some > > >> > kind of > > >> > race condition where, it is not properly processing all of the > > >> Re-Invites, > > >> > to fork the calls out, and basically one of the calls picks up 183 > > >> early > > >> > media, then 200 OK, and terminates the other branches / > > calls. However > > >> > they > > >> > were never executed / no phone was ever picked up. Any ideas on > > what > > >> I'm > > >> > doing wrong, or what could possibly be happening? Any help is > > >> appreciated, > > >> > thank you. > > >> > > > >> > I am using OpenSER v1.1.1, example sipcap posted below: > > >> > > > >> > match: CALLEE > > >> > ################# > > >> > U +0.000000 GATEWAY_1:5060 -> OpenSER:5060 > > >> > INVITE sip:CALLEE@OpenSER:5060 SIP/2.0. > > >> > Record-Route: <sip:GATEWAY_1;lr=on;ftag=as17d625b5>. > > >> > Via: SIP/2.0/UDP GATEWAY_1;branch=z9hG4bK0b52.a5ddb76.0. > > >> > Via: SIP/2.0/UDP 64.24.35.73:5060 > > ;branch=z9hG4bK5dce8d77;rport=5060. > > >> > From: "CALLER" < sip:CALLER@64.24.35.73>;tag=as17d625b5. > > >> > To: <sip:CALLEE@GATEWAY_1>. > > >> > Contact: <sip:CALLER@64.24.35.73 >. > > >> > Call-ID: 681bcb047355d7d85d939d542534d721(a)64.24.35.73. > > >> > CSeq: 102 INVITE. > > >> > User-Agent: US LEC VOIP. > > >> > Max-Forwards: 69. > > >> > Date: Wed, 28 Mar 2007 13:58:45 GMT. > > >> > Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY. > > >> > Content-Type: application/sdp. > > >> > Content-Length: 156. > > >> > . > > >> > v=0. > > >> > o=root 7184 7184 IN IP4 64.24.35.73. > > >> > s=session. > > >> > c=IN IP4 64.24.35.73. > > >> > t=0 0. > > >> > m=audio 17990 RTP/AVP 0. > > >> > a=rtpmap:0 PCMU/8000. > > >> > a=silenceSupp:off - - - -. > > >> > > > >> > # > > >> > U +0.002597 OpenSER:5060 -> GATEWAY_1:5060 > > >> > SIP/2.0 100 trying -- your call is important to us. > > >> > Via: SIP/2.0/UDP GATEWAY_1;branch=z9hG4bK0b52.a5ddb76.0;rport=5060. > > >> > Via: SIP/2.0/UDP 64.24.35.73:5060 > > ;branch=z9hG4bK5dce8d77;rport=5060. > > >> > From: "CALLER" <sip:CALLER@64.24.35.73 >;tag=as17d625b5. > > >> > To: <sip:CALLEE@GATEWAY_1>. > > >> > Call-ID: 681bcb047355d7d85d939d542534d721(a)64.24.35.73. > > >> > CSeq: 102 INVITE. > > >> > Server: OpenSer (1.1.1-notls (x86_64/linux)). > > >> > Content-Length: 0. > > >> > Warning: 392 OpenSER:5060 "Noisy feedback tells: pid=10278 > > >> > req_src_ip=GATEWAY_1 req_src_port=5060 in_uri= sip:CALLEE@OpenSER > > :5060 > > >> > out_uri=sip:+RE-INVITE_CALLEE_1@GATEWAY_2:5060 via_cnt==2". > > >> > . > > >> > > > >> > # > > >> > U +0.000090 OpenSER:5060 -> GATEWAY_2:5060 > > >> > INVITE sip:+RE-INVITE_CALLEE_1@GATEWAY_2:5060 SIP/2.0. > > >> > Record-Route: <sip:OpenSER;lr=on;ftag=as17d625b5>. > > >> > Record-Route: <sip:GATEWAY_1;lr=on;ftag=as17d625b5>. > > >> > Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK0b52.7164f3d6.0. > > >> > Via: SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK0b52.a5ddb76.0. > > >> > Via: SIP/2.0/UDP 64.24.35.73:5060 > > ;branch=z9hG4bK5dce8d77;rport=5060. > > >> > From: "CALLER" <sip:CALLER@64.24.35.73>;tag=as17d625b5. > > >> > To: <sip:CALLEE@GATEWAY _1>. > > >> > Contact: <sip:CALLER@64.24.35.73>. > > >> > Call-ID: 681bcb047355d7d85d939d542534d721(a)64.24.35.73 . > > >> > CSeq: 102 INVITE. > > >> > Max-Forwards: 68. > > >> > Date: Wed, 28 Mar 2007 13:58:45 GMT. > > >> > Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY. > > >> > Content-Type: application/sdp. > > >> > Content-Length: 174. > > >> > . > > >> > v=0. > > >> > o=root 7184 7184 IN IP4 64.24.35.73. > > >> > s=session. > > >> > c=IN IP4 OpenSER. > > >> > t=0 0. > > >> > m=audio 35998 RTP/AVP 0. > > >> > a=rtpmap:0 PCMU/8000. > > >> > a=silenceSupp:off - - - -. > > >> > a=nortpproxy:yes. > > >> > > > >> > # > > >> > U +0.000023 OpenSER:5060 -> GATEWAY_2:5060 > > >> > INVITE sip:+RE-INVITE_CALLEE_2@GATEWAY_2:5060 SIP/2.0. > > >> > Record-Route: <sip:OpenSER;lr=on;ftag=as17d625b5>. > > >> > Record-Route: <sip:GATEWAY_1;lr=on;ftag=as17d625b5>. > > >> > Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK0b52.7164f3d6.1. > > >> > Via: SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK0b52.a5ddb76.0. > > >> > Via: SIP/2.0/UDP 64.24.35.73:5060 > > ;branch=z9hG4bK5dce8d77;rport=5060. > > >> > From: "CALLER" <sip:CALLER@64.24.35.73>;tag=as17d625b5. > > >> > To: <sip:CALLEE@GATEWAY _1>. > > >> > Contact: <sip:CALLER@64.24.35.73>. > > >> > Call-ID: 681bcb047355d7d85d939d542534d721(a)64.24.35.73 . > > >> > CSeq: 102 INVITE. > > >> > Max-Forwards: 68. > > >> > Date: Wed, 28 Mar 2007 13:58:45 GMT. > > >> > Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY. > > >> > Content-Type: application/sdp. > > >> > Content-Length: 174. > > >> > . > > >> > v=0. > > >> > o=root 7184 7184 IN IP4 64.24.35.73. > > >> > s=session. > > >> > c=IN IP4 OpenSER. > > >> > t=0 0. > > >> > m=audio 35998 RTP/AVP 0. > > >> > a=rtpmap:0 PCMU/8000. > > >> > a=silenceSupp:off - - - -. > > >> > a=nortpproxy:yes. > > >> > > > >> > # > > >> > U +0.022891 GATEWAY_2:5060 -> OpenSER:5060 > > >> > SIP/2.0 100 Trying bandwidth.com. > > >> > Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK0b52.7164f3d6.0. > > >> > Via: SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK0b52.a5ddb76.0. > > >> > Via: SIP/2.0/UDP 64.24.35.73:5060 > > ;branch=z9hG4bK5dce8d77;rport=5060. > > >> > From: "CALLER" < sip:CALLER@64.24.35.73>;tag=as17d625b5. > > >> > To: <sip:CALLEE@GATEWAY_1>. > > >> > Call-ID: 681bcb047355d7d85d939d542534d721(a)64.24.35.73. > > >> > CSeq: 102 INVITE. > > >> > Server: Bandwidth.com SDE (v1.0). > > >> > Content-Length: 0. > > >> > Warning: 392 GATEWAY_2:5060 "Noisy feedback tells: pid=13590 > > >> > req_src_ip=OpenSER req_src_port=5060 > > >> > in_uri=sip:+RE-INVITE_CALLEE_1@GATEWAY_2:5060 > > >> > out_uri=sip:+RE-INVITE_CALLEE_1@4.68.250.148:5060 via_cnt==3". > > >> > . > > >> > > > >> > # > > >> > U +0.000007 GATEWAY_2:5060 -> OpenSER:5060 > > >> > SIP/2.0 100 Trying bandwidth.com. > > >> > Via: SIP/2.0/UDP OpenSER;branch= z9hG4bK0b52.7164f3d6.1. > > >> > Via: SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK0b52.a5ddb76.0. > > >> > Via: SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK5dce8d77;rport=5060. > > > > >> > From: "CALLER" <sip:CALLER@64.24.35.73>;tag=as17d625b5. > > >> > To: <sip:CALLEE@GATEWAY_1>. > > >> > Call-ID: 681bcb047355d7d85d939d542534d721(a)64.24.35.73. > > >> > CSeq: 102 INVITE. > > >> > Server: Bandwidth.com SDE (v1.0). > > >> > Content-Length: 0. > > >> > Warning: 392 GATEWAY_2:5060 "Noisy feedback tells: pid=13590 > > >> > req_src_ip=OpenSER req_src_port=5060 > > >> > in_uri=sip:+RE-INVITE_CALLEE_2@GATEWAY_2:5060 > > >> > out_uri=sip:+RE-INVITE_CALLEE_2@4.68.250.148:5060 via_cnt==3". > > >> > . > > >> > > > >> > ############## > > >> > U +2.054324 GATEWAY_2:5060 -> OpenSER:5060 > > >> > SIP/2.0 183 Session Progress. > > >> > Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK0b52.7164f3d6.0 ,SIP/2.0/UDP > > >> > GATEWAY_1;rport=5060;branch=z9hG4bK0b52.a5ddb76.0,SIP/2.0/UDP > > >> > 64.24.35.73:5060;branch=z9hG4bK5dce8d77;rport=5060. > > >> > Record-Route: > > >> > > > >> > > <sip:GATEWAY_2;lr;ftag=as17d625b5>,<sip:OpenSER;lr=on;ftag=as17d625b5>,<sip:GATEWAY_1;lr=on;ftag=as17d625b5>. > > >> > > >> > > > >> > From: "CALLER" < sip:CALLER@64.24.35.73>;tag=as17d625b5. > > >> > To: <sip:CALLEE@GATEWAY_1>;tag=VPST506071629460. > > >> > Call-ID: 681bcb047355d7d85d939d542534d721(a)64.24.35.73. > > >> > CSeq: 102 INVITE. > > >> > Contact: <sip:+RE-INVITE_CALLEE_1@4.68.250.148:5060;transport=udp>. > > >> > Content-Type: application/sdp. > > >> > Content-Length: 128. > > >> > . > > >> > v=0. > > >> > o=- 1175090325 1175090326 IN IP4 209.244.42.250. > > >> > s=-. > > >> > c=IN IP4 209.244.42.250. > > >> > t=0 0. > > >> > m=audio 61138 RTP/AVP 0. > > >> > a=ptime:20. > > >> > > > >> > # > > >> > U +0.000244 OpenSER:5060 -> GATEWAY_1:5060 > > >> > SIP/2.0 183 Session Progress. > > >> > Via: SIP/2.0/UDP > > >> > GATEWAY_1;rport=5060;branch=z9hG4bK0b52.a5ddb76.0,SIP/2.0/UDP > > >> > 64.24.35.73:5060 ;branch=z9hG4bK5dce8d77;rport=5060. > > >> > Record-Route: > > >> > > > >> > > <sip:GATEWAY_2;lr;ftag=as17d625b5>,<sip:OpenSER;lr=on;ftag=as17d625b5>,<sip:GATEWAY_1;lr=on;ftag=as17d625b5>. > > > > >> > > >> > > > >> > From: "CALLER" <sip:CALLER@64.24.35.73>;tag=as17d625b5. > > >> > To: <sip:CALLEE@GATEWAY_1>;tag=VPST506071629460. > > >> > Call-ID: 681bcb047355d7d85d939d542534d721(a)64.24.35.73. > > >> > CSeq: 102 INVITE. > > >> > Contact: <sip:+RE-INVITE_CALLEE_1@4.68.250.148:5060;transport=udp>. > > >> > Content-Type: application/sdp. > > >> > Content-Length: 143. > > >> > . > > >> > v=0. > > >> > o=- 1175090325 1175090326 IN IP4 209.244.42.250. > > >> > s=-. > > >> > c=IN IP4 OpenSER. > > >> > t=0 0. > > >> > m=audio 36002 RTP/AVP 0. > > >> > a=ptime:20. > > >> > a=nortpproxy:yes. > > >> > > > >> > ## > > >> > U +0.213133 GATEWAY_2:5060 -> OpenSER:5060 > > >> > SIP/2.0 200 OK. > > >> > Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK0b52.7164f3d6.0,SIP/2.0/UDP > > >> > GATEWAY_1;rport=5060;branch= z9hG4bK0b52.a5ddb76.0,SIP/2.0/UDP > > >> > 64.24.35.73:5060;branch=z9hG4bK5dce8d77;rport=5060. > > >> > Record-Route: > > >> > > > >> > > <sip:GATEWAY_2;lr;ftag=as17d625b5>,<sip:OpenSER;lr=on;ftag=as17d625b5>,<sip:GATEWAY_1;lr=on;ftag=as17d625b5>. > > > > >> > > >> > > > >> > From: "CALLER" <sip:CALLER@64.24.35.73>;tag=as17d625b5. > > >> > To: <sip:CALLEE@GATEWAY_1>;tag=VPST506071629460. > > >> > Call-ID: 681bcb047355d7d85d939d542534d721(a)64.24.35.73. > > >> > CSeq: 102 INVITE. > > >> > Contact: <sip:+RE-INVITE_CALLEE_1@4.68.250.148:5060;transport=udp>. > > >> > Content-Type: application/sdp. > > >> > Content-Length: 128. > > >> > . > > >> > v=0. > > >> > o=- 1175090325 1175090326 IN IP4 209.244.42.250. > > >> > s=-. > > >> > c=IN IP4 209.244.42.250. > > >> > t=0 0. > > >> > m=audio 61138 RTP/AVP 0. > > >> > a=ptime:20. > > >> > > > >> > # > > >> > U +0.004792 OpenSER:5060 -> GATEWAY_1:5060 > > >> > SIP/2.0 200 OK. > > >> > Via: SIP/2.0/UDP > > >> > GATEWAY_1;rport=5060;branch=z9hG4bK0b52.a5ddb76.0,SIP/2.0/UDP > > >> > 64.24.35.73:5060;branch=z9hG4bK5dce8d77;rport=5060. > > >> > Record-Route: > > >> > > > >> > > <sip:GATEWAY_2;lr;ftag=as17d625b5>,<sip:OpenSER;lr=on;ftag=as17d625b5>,<sip:GATEWAY_1;lr=on;ftag=as17d625b5>. > > > > >> > > >> > > > >> > From: "CALLER" <sip:CALLER@64.24.35.73>;tag=as17d625b5. > > >> > To: <sip:CALLEE@GATEWAY_1>;tag=VPST506071629460. > > >> > Call-ID: 681bcb047355d7d85d939d542534d721(a)64.24.35.73. > > >> > CSeq: 102 INVITE. > > >> > Contact: <sip:+RE-INVITE_CALLEE_1@4.68.250.148:5060;transport=udp>. > > >> > Content-Type: application/sdp. > > >> > Content-Length: 143. > > >> > . > > >> > v=0. > > >> > o=- 1175090325 1175090326 IN IP4 209.244.42.250. > > >> > s=-. > > >> > c=IN IP4 OpenSER. > > >> > t=0 0. > > >> > m=audio 36002 RTP/AVP 0. > > >> > a=ptime:20. > > >> > a=nortpproxy:yes. > > >> > > > >> > # > > >> > U +0.000146 OpenSER:5060 -> GATEWAY_2:5060 > > >> > CANCEL sip:+RE-INVITE_CALLEE_2@GATEWAY_2:5060 SIP/2.0. > > >> > Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK0b52.7164f3d6.1 . > > >> > From: "CALLER" <sip:CALLER@64.24.35.73>;tag=as17d625b5. > > >> > Call-ID: 681bcb047355d7d85d939d542534d721(a)64.24.35.73. > > >> > To: <sip:CALLEE@GATEWAY_1>. > > >> > CSeq: 102 CANCEL. > > >> > User-Agent: OpenSer (1.1.1-notls (x86_64/linux)). > > >> > Content-Length: 0. > > >> > . > > >> > > > >> > # > > >> > U +0.028419 GATEWAY_2:5060 -> OpenSER:5060 > > >> > SIP/2.0 487 Request Terminated. > > >> > Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK0b52.7164f3d6.1 . > > >> > Via: SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK0b52.a5ddb76.0. > > >> > Via: SIP/2.0/UDP 64.24.35.73:5060 > > ;branch=z9hG4bK5dce8d77;rport=5060. > > >> > From: "CALLER" < sip:CALLER@64.24.35.73>;tag=as17d625b5. > > >> > To: <sip:CALLEE@GATEWAY > > _1>;tag=2a6c315af837f0a6a989449d0bd9acf6-fcd9. > > >> > Call-ID: 681bcb047355d7d85d939d542534d721(a)64.24.35.73. > > >> > CSeq: 102 INVITE. > > >> > Server: Bandwidth.com SDE (v1.0). > > >> > Content-Length: 0. > > >> > Warning: 392 GATEWAY_2:5060 "Noisy feedback tells: pid=13600 > > >> > req_src_ip=OpenSER req_src_port=5060 > > >> > in_uri=sip:+RE-INVITE_CALLEE_2@GATEWAY_2:5060 > > >> > out_uri=sip:+RE-INVITE_CALLEE_2@4.68.250.148:5060 via_cnt==1". > > >> > . > > >> > > > >> > # > > >> > U +0.000098 OpenSER:5060 -> GATEWAY_2:5060 > > >> > ACK sip:+RE-INVITE_CALLEE_2@GATEWAY_2:5060 SIP/2.0. > > >> > Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK0b52.7164f3d6.1 . > > >> > From: "CALLER" <sip:CALLER@64.24.35.73>;tag=as17d625b5. > > >> > Call-ID: 681bcb047355d7d85d939d542534d721(a)64.24.35.73. > > >> > To: <sip:CALLEE@GATEWAY > > _1>;tag=2a6c315af837f0a6a989449d0bd9acf6-fcd9. > > >> > CSeq: 102 ACK. > > >> > User-Agent: OpenSer (1.1.1-notls (x86_64/linux)). > > >> > Content-Length: 0. > > >> > . > > >> > > > >> > # > > >> > U +0.011645 GATEWAY_2:5060 -> OpenSER:5060 > > >> > SIP/2.0 200 ok -- no more pending branches. > > >> > Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK0b52.7164f3d6.1. > > >> > From: "CALLER" <sip:CALLER@64.24.35.73>;tag=as17d625b5. > > >> > Call-ID: 681bcb047355d7d85d939d542534d721(a)64.24.35.73. > > >> > To: <sip:CALLEE@GATEWAY > > _1>;tag=2a6c315af837f0a6a989449d0bd9acf6-fcd9. > > >> > CSeq: 102 CANCEL. > > >> > Server: Bandwidth.com SDE (v1.0). > > >> > Content-Length: 0. > > >> > Warning: 392 GATEWAY_2:5060 "Noisy feedback tells: pid=13600 > > >> > req_src_ip=OpenSER req_src_port=5060 > > >> > in_uri=sip:+RE-INVITE_CALLEE_2@GATEWAY_2:5060 > > >> > out_uri=sip:+RE-INVITE_CALLEE_2@GATEWAY_2:5060 via_cnt==1". > > >> > . > > >> > > > >> > # > > >> > U +0.030857 GATEWAY_1:5060 -> OpenSER:5060 > > >> > ACK sip:+RE-INVITE_CALLEE_1@4.68.250.148:5060;transport=udp > > SIP/2.0. > > >> > Via: SIP/2.0/UDP GATEWAY_1;branch=z9hG4bK0b52.a5ddb76.2. > > >> > Via: SIP/2.0/UDP 64.24.35.73:5060 > > ;branch=z9hG4bK29c21d5a;rport=5060. > > >> > Route: > > >> > > > <sip:OpenSER;lr=on;ftag=as17d625b5>,<sip:GATEWAY_2;lr;ftag=as17d625b5>. > > >> > From: "CALLER" < sip:CALLER@64.24.35.73>;tag=as17d625b5. > > >> > To: <sip:CALLEE@GATEWAY_1>;tag=VPST506071629460. > > >> > Contact: < sip:CALLER@64.24.35.73>. > > >> > Call-ID: 681bcb047355d7d85d939d542534d721(a)64.24.35.73. > > >> > CSeq: 102 ACK. > > >> > User-Agent: US LEC VOIP. > > >> > Max-Forwards: 69. > > >> > Content-Length: 0. > > >> > . > > >> > > > >> > # > > >> > U +0.000183 OpenSER:5060 -> GATEWAY_2:5060 > > >> > ACK sip:+RE-INVITE_CALLEE_1@4.68.250.148 :5060;transport=udp > > SIP/2.0. > > >> > Record-Route: <sip:OpenSER;lr=on;ftag=as17d625b5>. > > >> > Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK0b52.7164f3d6.3. > > >> > Via: SIP/2.0/UDP GATEWAY_1;rport=5060;branch= z9hG4bK0b52.a5ddb76.2 > > . > > >> > Via: SIP/2.0/UDP 64.24.35.73:5060 > > ;branch=z9hG4bK29c21d5a;rport=5060. > > >> > Route: <sip:GATEWAY_2;lr;ftag=as17d625b5>. > > >> > From: "CALLER" < sip:CALLER@64.24.35.73>;tag=as17d625b5. > > >> > To: <sip:CALLEE@GATEWAY_1>;tag=VPST506071629460. > > >> > Contact: < sip:CALLER@64.24.35.73>. > > >> > Call-ID: 681bcb047355d7d85d939d542534d721(a)64.24.35.73. > > >> > CSeq: 102 ACK. > > >> > Max-Forwards: 68. > > >> > Content-Length: 0. > > >> > P-hint: rr-enforced. > > >> > . > > >> > > > >> > > > >> > > ##################################################################################################################################################################################################################################################################################################################################################################################################################################################################### > > > > >> > > >> > > > >> > U +71.203150 GATEWAY_1:5060 -> OpenSER:5060 > > >> > BYE sip:+RE-INVITE_CALLEE_1@4.68.250.148:5060;transport=udp > > SIP/2.0. > > >> > Via: SIP/2.0/UDP GATEWAY_1;branch= z9hG4bK1b52.5ebf0565.0. > > >> > Via: SIP/2.0/UDP 64.24.35.73:5060 > > ;branch=z9hG4bK53c03317;rport=5060. > > >> > Route: > > >> > > > <sip:OpenSER;lr=on;ftag=as17d625b5>,<sip:GATEWAY_2;lr;ftag=as17d625b5>. > > >> > From: "CALLER" <sip:CALLER@64.24.35.73>;tag=as17d625b5. > > >> > To: <sip:CALLEE@GATEWAY_1>;tag=VPST506071629460. > > >> > Contact: < sip:CALLER@64.24.35.73>. > > >> > Call-ID: 681bcb047355d7d85d939d542534d721(a)64.24.35.73. > > >> > CSeq: 103 BYE. > > >> > User-Agent: US LEC VOIP. > > >> > Max-Forwards: 69. > > >> > Content-Length: 0. > > >> > . > > >> > > > >> > # > > >> > U +0.003835 OpenSER:5060 -> GATEWAY_2:5060 > > >> > BYE sip:+RE-INVITE_CALLEE_1@4.68.250.148:5060;transport=udp > > SIP/2.0. > > >> > Record-Route: <sip:OpenSER;lr=on;ftag=as17d625b5>. > > >> > Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK1b52.25391854.0 . > > >> > Via: SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK1b52.5ebf0565.0 > > . > > >> > Via: SIP/2.0/UDP 64.24.35.73:5060 > > ;branch=z9hG4bK53c03317;rport=5060. > > >> > Route: <sip:GATEWAY_2;lr;ftag=as17d625b5>. > > >> > From: "CALLER" <sip:CALLER@64.24.35.73>;tag=as17d625b5. > > >> > To: <sip:CALLEE@GATEWAY_1>;tag=VPST506071629460. > > >> > Contact: < sip:CALLER@64.24.35.73>. > > >> > Call-ID: 681bcb047355d7d85d939d542534d721(a)64.24.35.73. > > >> > CSeq: 103 BYE. > > >> > Max-Forwards: 68. > > >> > Content-Length: 0. > > >> > P-hint: rr-enforced. > > >> > . > > >> > > > >> > # > > >> > U +0.073996 GATEWAY_2:5060 -> OpenSER:5060 > > >> > SIP/2.0 200 OK. > > >> > Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK1b52.25391854.0,SIP/2.0/UDP > > >> > GATEWAY_1;rport=5060;branch=z9hG4bK1b52.5ebf0565.0,SIP/2.0/UDP > > >> > 64.24.35.73:5060;branch=z9hG4bK53c03317;rport=5060. > > >> > Record-Route: > > >> > > > <sip:GATEWAY_2;lr;ftag=as17d625b5>,<sip:OpenSER;lr=on;ftag=as17d625b5>. > > >> > From: "CALLER" < sip:CALLER@64.24.35.73>;tag=as17d625b5. > > >> > To: <sip:CALLEE@GATEWAY_1>;tag=VPST506071629460. > > >> > Call-ID: 681bcb047355d7d85d939d542534d721(a)64.24.35.73. > > >> > CSeq: 103 BYE. > > >> > Contact: <sip:+RE-INVITE_CALLEE_1@4.68.250.148:5060;transport=udp>. > > >> > Content-Length: 0. > > >> > . > > >> > > > >> > # > > >> > U +0.000100 OpenSER:5060 -> GATEWAY_1:5060 > > >> > SIP/2.0 200 OK. > > >> > Via: SIP/2.0/UDP > > >> > GATEWAY_1;rport=5060;branch=z9hG4bK1b52.5ebf0565.0 ,SIP/2.0/UDP > > >> > 64.24.35.73:5060;branch=z9hG4bK53c03317;rport=5060. > > >> > Record-Route: > > >> > > > <sip:GATEWAY_2;lr;ftag=as17d625b5>,<sip:OpenSER;lr=on;ftag=as17d625b5>. > > >> > From: "CALLER" <sip:CALLER@64.24.35.73>;tag=as17d625b5. > > >> > To: <sip:CALLEE@GATEWAY_1>;tag=VPST506071629460. > > >> > Call-ID: 681bcb047355d7d85d939d542534d721(a)64.24.35.73. > > >> > CSeq: 103 BYE. > > >> > Contact: <sip:+RE-INVITE_CALLEE_1@4.68.250.148:5060;transport=udp>. > > > > >> > Content-Length: 0. > > >> > . > > >> > > > >> > ################exit > > >> > 1036 received, 0 dropped > > >> > > > >> > Thanks Again everyone. > > >> > > > >> > > > >> > > > >> > > ------------------------------------------------------------------------ > > >> > > > >> > _______________________________________________ > > >> > Users mailing list > > >> > Users(a)openser.org > > >> > http://openser.org/cgi-bin/mailman/listinfo/users > > >> > > > > > > > > > > > > > > > -- > Brandon Armstead -- Brandon Armstead

1 0

Re: [Users] openser on AMD64 or intel Xeon64
by Abdurrahman Sahin 29 Mar '07

29 Mar '07

hi again; so just setting CPU will be OK? We have 2 fedora linux machines, one on Intel Xeon 64 bit and one on AMD64 bit. i'll go on with CPU setting. is there anything else to configure? best regards. 2007/3/29, Bodin Bruno <bbodin01(a)univ-lr.fr>: > Abdurrahman Sahin a écrit : > > hi; > > i'm new to this maillist; > > is there any openser distribution for AMD64 or Intel Xeon 64. > > i read sth on the site claims that it can be build via modifying > > parameters in make config files. > > but there is nothing which parameters need to be edited > > > > _______________________________________________ > > Users mailing list > > Users(a)openser.org > > http://openser.org/cgi-bin/mailman/listinfo/users > In Suse I'have just to type : > > CPU=athlon64 make etc.... > or > export CPU=athlon64 > and normal commands > >

1 0

[Users] openser on AMD64 or intel Xeon64
by Abdurrahman Sahin 29 Mar '07

29 Mar '07

hi; i'm new to this maillist; is there any openser distribution for AMD64 or Intel Xeon 64. i read sth on the site claims that it can be build via modifying parameters in make config files. but there is nothing which parameters need to be edited

2 1

[Users] ReInvite Issue
by Brandon Armstead 29 Mar '07

29 Mar '07

Hello everyone, I'm running into a issue, where I'm trying to implement parallel forking, so basically on incoming calls from gateway, I want to then Re-Invite, and send out the calls to multiple destinations, I am currently, using avp_db_query to grab the sip uri's and throwing them into an avp list, and avp_pushto("$ru", "$avp(i:1)/g"); This all works fine and good, invite comes in, and then sends Re-Invites, however, there seems to be some kind of race condition where, it is not properly processing all of the Re-Invites, to fork the calls out, and basically one of the calls picks up 183 early media, then 200 OK, and terminates the other branches / calls. However they were never executed / no phone was ever picked up. Any ideas on what I'm doing wrong, or what could possibly be happening? Any help is appreciated, thank you. I am using OpenSER v1.1.1, example sipcap posted below: match: CALLEE ################# U +0.000000 GATEWAY_1:5060 -> OpenSER:5060 INVITE sip:CALLEE@OpenSER:5060 SIP/2.0. Record-Route: <sip:GATEWAY_1;lr=on;ftag=as17d625b5>. Via: SIP/2.0/UDP GATEWAY_1;branch=z9hG4bK0b52.a5ddb76.0. Via: SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK5dce8d77;rport=5060. From: "CALLER" <sip:CALLER@64.24.35.73>;tag=as17d625b5. To: <sip:CALLEE@GATEWAY_1>. Contact: <sip:CALLER@64.24.35.73>. Call-ID: 681bcb047355d7d85d939d542534d721(a)64.24.35.73. CSeq: 102 INVITE. User-Agent: US LEC VOIP. Max-Forwards: 69. Date: Wed, 28 Mar 2007 13:58:45 GMT. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY. Content-Type: application/sdp. Content-Length: 156. . v=0. o=root 7184 7184 IN IP4 64.24.35.73. s=session. c=IN IP4 64.24.35.73. t=0 0. m=audio 17990 RTP/AVP 0. a=rtpmap:0 PCMU/8000. a=silenceSupp:off - - - -. # U +0.002597 OpenSER:5060 -> GATEWAY_1:5060 SIP/2.0 100 trying -- your call is important to us. Via: SIP/2.0/UDP GATEWAY_1;branch=z9hG4bK0b52.a5ddb76.0;rport=5060. Via: SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK5dce8d77;rport=5060. From: "CALLER" <sip:CALLER@64.24.35.73>;tag=as17d625b5. To: <sip:CALLEE@GATEWAY_1>. Call-ID: 681bcb047355d7d85d939d542534d721(a)64.24.35.73. CSeq: 102 INVITE. Server: OpenSer (1.1.1-notls (x86_64/linux)). Content-Length: 0. Warning: 392 OpenSER:5060 "Noisy feedback tells: pid=10278 req_src_ip=GATEWAY_1 req_src_port=5060 in_uri=sip:CALLEE@OpenSER:5060 out_uri=sip:+RE-INVITE_CALLEE_1@GATEWAY_2:5060 via_cnt==2". . # U +0.000090 OpenSER:5060 -> GATEWAY_2:5060 INVITE sip:+RE-INVITE_CALLEE_1@GATEWAY_2:5060 SIP/2.0. Record-Route: <sip:OpenSER;lr=on;ftag=as17d625b5>. Record-Route: <sip:GATEWAY_1;lr=on;ftag=as17d625b5>. Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK0b52.7164f3d6.0. Via: SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK0b52.a5ddb76.0. Via: SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK5dce8d77;rport=5060. From: "CALLER" <sip:CALLER@64.24.35.73>;tag=as17d625b5. To: <sip:CALLEE@GATEWAY_1>. Contact: <sip:CALLER@64.24.35.73>. Call-ID: 681bcb047355d7d85d939d542534d721(a)64.24.35.73. CSeq: 102 INVITE. Max-Forwards: 68. Date: Wed, 28 Mar 2007 13:58:45 GMT. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY. Content-Type: application/sdp. Content-Length: 174. . v=0. o=root 7184 7184 IN IP4 64.24.35.73. s=session. c=IN IP4 OpenSER. t=0 0. m=audio 35998 RTP/AVP 0. a=rtpmap:0 PCMU/8000. a=silenceSupp:off - - - -. a=nortpproxy:yes. # U +0.000023 OpenSER:5060 -> GATEWAY_2:5060 INVITE sip:+RE-INVITE_CALLEE_2@GATEWAY_2:5060 SIP/2.0. Record-Route: <sip:OpenSER;lr=on;ftag=as17d625b5>. Record-Route: <sip:GATEWAY_1;lr=on;ftag=as17d625b5>. Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK0b52.7164f3d6.1. Via: SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK0b52.a5ddb76.0. Via: SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK5dce8d77;rport=5060. From: "CALLER" <sip:CALLER@64.24.35.73>;tag=as17d625b5. To: <sip:CALLEE@GATEWAY_1>. Contact: <sip:CALLER@64.24.35.73>. Call-ID: 681bcb047355d7d85d939d542534d721(a)64.24.35.73. CSeq: 102 INVITE. Max-Forwards: 68. Date: Wed, 28 Mar 2007 13:58:45 GMT. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY. Content-Type: application/sdp. Content-Length: 174. . v=0. o=root 7184 7184 IN IP4 64.24.35.73. s=session. c=IN IP4 OpenSER. t=0 0. m=audio 35998 RTP/AVP 0. a=rtpmap:0 PCMU/8000. a=silenceSupp:off - - - -. a=nortpproxy:yes. # U +0.022891 GATEWAY_2:5060 -> OpenSER:5060 SIP/2.0 100 Trying bandwidth.com. Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK0b52.7164f3d6.0. Via: SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK0b52.a5ddb76.0. Via: SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK5dce8d77;rport=5060. From: "CALLER" <sip:CALLER@64.24.35.73>;tag=as17d625b5. To: <sip:CALLEE@GATEWAY_1>. Call-ID: 681bcb047355d7d85d939d542534d721(a)64.24.35.73. CSeq: 102 INVITE. Server: Bandwidth.com SDE (v1.0). Content-Length: 0. Warning: 392 GATEWAY_2:5060 "Noisy feedback tells: pid=13590 req_src_ip=OpenSER req_src_port=5060 in_uri=sip:+RE-INVITE_CALLEE_1@GATEWAY_2:5060 out_uri=sip:+RE-INVITE_CALLEE_1@4.68.250.148:5060 via_cnt==3". . # U +0.000007 GATEWAY_2:5060 -> OpenSER:5060 SIP/2.0 100 Trying bandwidth.com. Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK0b52.7164f3d6.1. Via: SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK0b52.a5ddb76.0. Via: SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK5dce8d77;rport=5060. From: "CALLER" <sip:CALLER@64.24.35.73>;tag=as17d625b5. To: <sip:CALLEE@GATEWAY_1>. Call-ID: 681bcb047355d7d85d939d542534d721(a)64.24.35.73. CSeq: 102 INVITE. Server: Bandwidth.com SDE (v1.0). Content-Length: 0. Warning: 392 GATEWAY_2:5060 "Noisy feedback tells: pid=13590 req_src_ip=OpenSER req_src_port=5060 in_uri=sip:+RE-INVITE_CALLEE_2@GATEWAY_2:5060 out_uri=sip:+RE-INVITE_CALLEE_2@4.68.250.148:5060 via_cnt==3". . ############## U +2.054324 GATEWAY_2:5060 -> OpenSER:5060 SIP/2.0 183 Session Progress. Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK0b52.7164f3d6.0,SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK0b52.a5ddb76.0,SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK5dce8d77;rport=5060. Record-Route: <sip:GATEWAY_2;lr;ftag=as17d625b5>,<sip:OpenSER;lr=on;ftag=as17d625b5>,<sip:GATEWAY_1;lr=on;ftag=as17d625b5>. From: "CALLER" <sip:CALLER@64.24.35.73>;tag=as17d625b5. To: <sip:CALLEE@GATEWAY_1>;tag=VPST506071629460. Call-ID: 681bcb047355d7d85d939d542534d721(a)64.24.35.73. CSeq: 102 INVITE. Contact: <sip:+RE-INVITE_CALLEE_1@4.68.250.148:5060;transport=udp>. Content-Type: application/sdp. Content-Length: 128. . v=0. o=- 1175090325 1175090326 IN IP4 209.244.42.250. s=-. c=IN IP4 209.244.42.250. t=0 0. m=audio 61138 RTP/AVP 0. a=ptime:20. # U +0.000244 OpenSER:5060 -> GATEWAY_1:5060 SIP/2.0 183 Session Progress. Via: SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK0b52.a5ddb76.0,SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK5dce8d77;rport=5060. Record-Route: <sip:GATEWAY_2;lr;ftag=as17d625b5>,<sip:OpenSER;lr=on;ftag=as17d625b5>,<sip:GATEWAY_1;lr=on;ftag=as17d625b5>. From: "CALLER" <sip:CALLER@64.24.35.73>;tag=as17d625b5. To: <sip:CALLEE@GATEWAY_1>;tag=VPST506071629460. Call-ID: 681bcb047355d7d85d939d542534d721(a)64.24.35.73. CSeq: 102 INVITE. Contact: <sip:+RE-INVITE_CALLEE_1@4.68.250.148:5060;transport=udp>. Content-Type: application/sdp. Content-Length: 143. . v=0. o=- 1175090325 1175090326 IN IP4 209.244.42.250. s=-. c=IN IP4 OpenSER. t=0 0. m=audio 36002 RTP/AVP 0. a=ptime:20. a=nortpproxy:yes. ## U +0.213133 GATEWAY_2:5060 -> OpenSER:5060 SIP/2.0 200 OK. Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK0b52.7164f3d6.0,SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK0b52.a5ddb76.0,SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK5dce8d77;rport=5060. Record-Route: <sip:GATEWAY_2;lr;ftag=as17d625b5>,<sip:OpenSER;lr=on;ftag=as17d625b5>,<sip:GATEWAY_1;lr=on;ftag=as17d625b5>. From: "CALLER" <sip:CALLER@64.24.35.73>;tag=as17d625b5. To: <sip:CALLEE@GATEWAY_1>;tag=VPST506071629460. Call-ID: 681bcb047355d7d85d939d542534d721(a)64.24.35.73. CSeq: 102 INVITE. Contact: <sip:+RE-INVITE_CALLEE_1@4.68.250.148:5060;transport=udp>. Content-Type: application/sdp. Content-Length: 128. . v=0. o=- 1175090325 1175090326 IN IP4 209.244.42.250. s=-. c=IN IP4 209.244.42.250. t=0 0. m=audio 61138 RTP/AVP 0. a=ptime:20. # U +0.004792 OpenSER:5060 -> GATEWAY_1:5060 SIP/2.0 200 OK. Via: SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK0b52.a5ddb76.0,SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK5dce8d77;rport=5060. Record-Route: <sip:GATEWAY_2;lr;ftag=as17d625b5>,<sip:OpenSER;lr=on;ftag=as17d625b5>,<sip:GATEWAY_1;lr=on;ftag=as17d625b5>. From: "CALLER" <sip:CALLER@64.24.35.73>;tag=as17d625b5. To: <sip:CALLEE@GATEWAY_1>;tag=VPST506071629460. Call-ID: 681bcb047355d7d85d939d542534d721(a)64.24.35.73. CSeq: 102 INVITE. Contact: <sip:+RE-INVITE_CALLEE_1@4.68.250.148:5060;transport=udp>. Content-Type: application/sdp. Content-Length: 143. . v=0. o=- 1175090325 1175090326 IN IP4 209.244.42.250. s=-. c=IN IP4 OpenSER. t=0 0. m=audio 36002 RTP/AVP 0. a=ptime:20. a=nortpproxy:yes. # U +0.000146 OpenSER:5060 -> GATEWAY_2:5060 CANCEL sip:+RE-INVITE_CALLEE_2@GATEWAY_2:5060 SIP/2.0. Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK0b52.7164f3d6.1. From: "CALLER" <sip:CALLER@64.24.35.73>;tag=as17d625b5. Call-ID: 681bcb047355d7d85d939d542534d721(a)64.24.35.73. To: <sip:CALLEE@GATEWAY_1>. CSeq: 102 CANCEL. User-Agent: OpenSer (1.1.1-notls (x86_64/linux)). Content-Length: 0. . # U +0.028419 GATEWAY_2:5060 -> OpenSER:5060 SIP/2.0 487 Request Terminated. Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK0b52.7164f3d6.1. Via: SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK0b52.a5ddb76.0. Via: SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK5dce8d77;rport=5060. From: "CALLER" <sip:CALLER@64.24.35.73>;tag=as17d625b5. To: <sip:CALLEE@GATEWAY_1>;tag=2a6c315af837f0a6a989449d0bd9acf6-fcd9. Call-ID: 681bcb047355d7d85d939d542534d721(a)64.24.35.73. CSeq: 102 INVITE. Server: Bandwidth.com SDE (v1.0). Content-Length: 0. Warning: 392 GATEWAY_2:5060 "Noisy feedback tells: pid=13600 req_src_ip=OpenSER req_src_port=5060 in_uri=sip:+RE-INVITE_CALLEE_2@GATEWAY_2:5060 out_uri=sip:+RE-INVITE_CALLEE_2@4.68.250.148:5060 via_cnt==1". . # U +0.000098 OpenSER:5060 -> GATEWAY_2:5060 ACK sip:+RE-INVITE_CALLEE_2@GATEWAY_2:5060 SIP/2.0. Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK0b52.7164f3d6.1. From: "CALLER" <sip:CALLER@64.24.35.73>;tag=as17d625b5. Call-ID: 681bcb047355d7d85d939d542534d721(a)64.24.35.73. To: <sip:CALLEE@GATEWAY_1>;tag=2a6c315af837f0a6a989449d0bd9acf6-fcd9. CSeq: 102 ACK. User-Agent: OpenSer (1.1.1-notls (x86_64/linux)). Content-Length: 0. . # U +0.011645 GATEWAY_2:5060 -> OpenSER:5060 SIP/2.0 200 ok -- no more pending branches. Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK0b52.7164f3d6.1. From: "CALLER" <sip:CALLER@64.24.35.73>;tag=as17d625b5. Call-ID: 681bcb047355d7d85d939d542534d721(a)64.24.35.73. To: <sip:CALLEE@GATEWAY_1>;tag=2a6c315af837f0a6a989449d0bd9acf6-fcd9. CSeq: 102 CANCEL. Server: Bandwidth.com SDE (v1.0). Content-Length: 0. Warning: 392 GATEWAY_2:5060 "Noisy feedback tells: pid=13600 req_src_ip=OpenSER req_src_port=5060 in_uri=sip:+RE-INVITE_CALLEE_2@GATEWAY_2:5060 out_uri=sip:+RE-INVITE_CALLEE_2@GATEWAY_2:5060 via_cnt==1". . # U +0.030857 GATEWAY_1:5060 -> OpenSER:5060 ACK sip:+RE-INVITE_CALLEE_1@4.68.250.148:5060;transport=udp SIP/2.0. Via: SIP/2.0/UDP GATEWAY_1;branch=z9hG4bK0b52.a5ddb76.2. Via: SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK29c21d5a;rport=5060. Route: <sip:OpenSER;lr=on;ftag=as17d625b5>,<sip:GATEWAY_2;lr;ftag=as17d625b5>. From: "CALLER" <sip:CALLER@64.24.35.73>;tag=as17d625b5. To: <sip:CALLEE@GATEWAY_1>;tag=VPST506071629460. Contact: <sip:CALLER@64.24.35.73>. Call-ID: 681bcb047355d7d85d939d542534d721(a)64.24.35.73. CSeq: 102 ACK. User-Agent: US LEC VOIP. Max-Forwards: 69. Content-Length: 0. . # U +0.000183 OpenSER:5060 -> GATEWAY_2:5060 ACK sip:+RE-INVITE_CALLEE_1@4.68.250.148:5060;transport=udp SIP/2.0. Record-Route: <sip:OpenSER;lr=on;ftag=as17d625b5>. Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK0b52.7164f3d6.3. Via: SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK0b52.a5ddb76.2. Via: SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK29c21d5a;rport=5060. Route: <sip:GATEWAY_2;lr;ftag=as17d625b5>. From: "CALLER" <sip:CALLER@64.24.35.73>;tag=as17d625b5. To: <sip:CALLEE@GATEWAY_1>;tag=VPST506071629460. Contact: <sip:CALLER@64.24.35.73>. Call-ID: 681bcb047355d7d85d939d542534d721(a)64.24.35.73. CSeq: 102 ACK. Max-Forwards: 68. Content-Length: 0. P-hint: rr-enforced. . ##################################################################################################################################################################################################################################################################################################################################################################################################################################################################### U +71.203150 GATEWAY_1:5060 -> OpenSER:5060 BYE sip:+RE-INVITE_CALLEE_1@4.68.250.148:5060;transport=udp SIP/2.0. Via: SIP/2.0/UDP GATEWAY_1;branch=z9hG4bK1b52.5ebf0565.0. Via: SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK53c03317;rport=5060. Route: <sip:OpenSER;lr=on;ftag=as17d625b5>,<sip:GATEWAY_2;lr;ftag=as17d625b5>. From: "CALLER" <sip:CALLER@64.24.35.73>;tag=as17d625b5. To: <sip:CALLEE@GATEWAY_1>;tag=VPST506071629460. Contact: <sip:CALLER@64.24.35.73>. Call-ID: 681bcb047355d7d85d939d542534d721(a)64.24.35.73. CSeq: 103 BYE. User-Agent: US LEC VOIP. Max-Forwards: 69. Content-Length: 0. . # U +0.003835 OpenSER:5060 -> GATEWAY_2:5060 BYE sip:+RE-INVITE_CALLEE_1@4.68.250.148:5060;transport=udp SIP/2.0. Record-Route: <sip:OpenSER;lr=on;ftag=as17d625b5>. Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK1b52.25391854.0. Via: SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK1b52.5ebf0565.0. Via: SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK53c03317;rport=5060. Route: <sip:GATEWAY_2;lr;ftag=as17d625b5>. From: "CALLER" <sip:CALLER@64.24.35.73>;tag=as17d625b5. To: <sip:CALLEE@GATEWAY_1>;tag=VPST506071629460. Contact: <sip:CALLER@64.24.35.73>. Call-ID: 681bcb047355d7d85d939d542534d721(a)64.24.35.73. CSeq: 103 BYE. Max-Forwards: 68. Content-Length: 0. P-hint: rr-enforced. . # U +0.073996 GATEWAY_2:5060 -> OpenSER:5060 SIP/2.0 200 OK. Via: SIP/2.0/UDP OpenSER;branch=z9hG4bK1b52.25391854.0,SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK1b52.5ebf0565.0,SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK53c03317;rport=5060. Record-Route: <sip:GATEWAY_2;lr;ftag=as17d625b5>,<sip:OpenSER;lr=on;ftag=as17d625b5>. From: "CALLER" <sip:CALLER@64.24.35.73>;tag=as17d625b5. To: <sip:CALLEE@GATEWAY_1>;tag=VPST506071629460. Call-ID: 681bcb047355d7d85d939d542534d721(a)64.24.35.73. CSeq: 103 BYE. Contact: <sip:+RE-INVITE_CALLEE_1@4.68.250.148:5060;transport=udp>. Content-Length: 0. . # U +0.000100 OpenSER:5060 -> GATEWAY_1:5060 SIP/2.0 200 OK. Via: SIP/2.0/UDP GATEWAY_1;rport=5060;branch=z9hG4bK1b52.5ebf0565.0,SIP/2.0/UDP 64.24.35.73:5060;branch=z9hG4bK53c03317;rport=5060. Record-Route: <sip:GATEWAY_2;lr;ftag=as17d625b5>,<sip:OpenSER;lr=on;ftag=as17d625b5>. From: "CALLER" <sip:CALLER@64.24.35.73>;tag=as17d625b5. To: <sip:CALLEE@GATEWAY_1>;tag=VPST506071629460. Call-ID: 681bcb047355d7d85d939d542534d721(a)64.24.35.73. CSeq: 103 BYE. Contact: <sip:+RE-INVITE_CALLEE_1@4.68.250.148:5060;transport=udp>. Content-Length: 0. . ################exit 1036 received, 0 dropped Thanks Again everyone. -- Brandon Armstead

3 2

[Users] XCAP for php4
by Helge Waastad 29 Mar '07

29 Mar '07

I, some reported T_Class error on xcap. Try adding a ';' at the end og require_once........ br hw

1 0

Re: RE: [Users] Simple xcap-emulator for OpenSER
by sukerry 28 Mar '07

28 Mar '07

Toni Barata, in Config.php, a ";" is missed before the term "class" ======= 2007-03-28 23:47:03 ======= >Hi Klaus, > > >I have been using xcap-0.2.1 without problems until yesterday. Today I have upgrade to the xcap-0.5 but the following error occurs: > >PHP Parse error: parse error, unexpected T_CLASS in /var/www/xcap-root/config.php on line 19 > >I have php4 on my system and the db_mysql.php file is php3 version. Could this be the problem? Should I downgrade php4 to php3? > >Thanks, >Toni > >-----Original Message----- >From: users-bounces(a)openser.org [mailto:users-bounces@openser.org] On Behalf Of Klaus Darilion >Sent: quarta-feira, 28 de Mar?o de 2007 10:54 >To: sukerry >Cc: Klaus Darilion; Adrian Georgescu; users openser.org >Subject: Re: [Users] Simple xcap-emulator for OpenSER > >there is nothing to compile. Read the Readme. you have to install PEAR >and the modules mentioned in the READ. > >e.g. >pear install Auth_HTTP >pear install Log >pear install DB > >regards >klaus > > >sukerry wrote: >> Adrian Georgescu, >> >> >> Thanks for your great job! >> >> However , when I compile php, an error says that Log.php can not be found! >> >> Thanks >> >> sukerry >> >> >> >> ======= 2007-03-28 00:56:33======= >> >>> Hello, >>> >>> We wrote a simple xcap emulator to be able to manage the XCAP >>> documents used by OpenSER presence agent, by using PHP scripts in >>> combination with Apache web server. >>> >>> I have tested it against OpenSER with MySQL and Eyebeam for Apple. >>> Klaus Darilion has tested it against Postgress and Eyebeam for Windows. >>> >>> The software can be downloaded from: >>> >>> http://download.dns-hosting.info/XCAP/xcap-0.5.tar.gz >>> >>> Regards, >>> Adrian >>> >>> >>> _______________________________________________ >>> Users mailing list >>> Users(a)openser.org >>> http://openser.org/cgi-bin/mailman/listinfo/users >>> >> >> >> 　　　　　　　　sukerry >> 　　　　　　　　sukerry(a)126.com >> 　　　　　　　　　　2007-03-28 >> >> >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Users mailing list >> Users(a)openser.org >> http://openser.org/cgi-bin/mailman/listinfo/users > >_______________________________________________ >Users mailing list >Users(a)openser.org >http://openser.org/cgi-bin/mailman/listinfo/users >_______________________________________________ >Users mailing list >Users(a)openser.org >http://openser.org/cgi-bin/mailman/listinfo/users > = = = = = = = = = = = = = = = = = = = = 　　　　　　　　sukerry 　　　　　　　　sukerry(a)126.com 　　　　　　　　　　2007-03-29

1 0

[Serusers] avp_sprintf in ser 0.9.6?
by Stefan Sayer 28 Mar '07

28 Mar '07

Hello, is there any function which can combine several avp values, possibly with constant strings, in ser 0.9.6? I am looking for something like avp_sprintf("$dst_avp", "P-App-Param: val1=$avp1; val2=avp2\r\n") but the only function I found was avp_write which can take either string or avp. Thanks Stefan -- Stefan Sayer Media Services Development stefan.sayer(a)iptego.de www.iptego.de iptego GmbH Am Borsigturm 40 13507 Berlin Germany Amtsgericht Charlottenburg, HRB 101010 Geschaeftsfuehrer: Alexander Hoffmann

3 2

Re: [Users] Unauthorized Calls - PLEASE HELP!
by Mark Kent 28 Mar '07

28 Mar '07

Are you sure you deleted the Admin user, in the subscriber database? -mark

1 0

RE: [Users] Simple xcap-emulator for OpenSER
by Toni Barata 28 Mar '07

28 Mar '07

Hi Klaus, I have been using xcap-0.2.1 without problems until yesterday. Today I have upgrade to the xcap-0.5 but the following error occurs: PHP Parse error: parse error, unexpected T_CLASS in /var/www/xcap-root/config.php on line 19 I have php4 on my system and the db_mysql.php file is php3 version. Could this be the problem? Should I downgrade php4 to php3? Thanks, Toni -----Original Message----- From: users-bounces(a)openser.org [mailto:users-bounces@openser.org] On Behalf Of Klaus Darilion Sent: quarta-feira, 28 de Março de 2007 10:54 To: sukerry Cc: Klaus Darilion; Adrian Georgescu; users openser.org Subject: Re: [Users] Simple xcap-emulator for OpenSER there is nothing to compile. Read the Readme. you have to install PEAR and the modules mentioned in the READ. e.g. pear install Auth_HTTP pear install Log pear install DB regards klaus sukerry wrote: > Adrian Georgescu, > > > Thanks for your great job! > > However , when I compile php, an error says that Log.php can not be found! > > Thanks > > sukerry > > > > ======= 2007-03-28 00:56:33======= > >> Hello, >> >> We wrote a simple xcap emulator to be able to manage the XCAP >> documents used by OpenSER presence agent, by using PHP scripts in >> combination with Apache web server. >> >> I have tested it against OpenSER with MySQL and Eyebeam for Apple. >> Klaus Darilion has tested it against Postgress and Eyebeam for Windows. >> >> The software can be downloaded from: >> >> http://download.dns-hosting.info/XCAP/xcap-0.5.tar.gz >> >> Regards, >> Adrian >> >> >> _______________________________________________ >> Users mailing list >> Users(a)openser.org >> http://openser.org/cgi-bin/mailman/listinfo/users >> > > > 　　　　　　　　sukerry > 　　　　　　　　sukerry(a)126.com > 　　　　　　　　　　2007-03-28 > > > > ------------------------------------------------------------------------ > > _______________________________________________ > Users mailing list > Users(a)openser.org > http://openser.org/cgi-bin/mailman/listinfo/users _______________________________________________ Users mailing list Users(a)openser.org http://openser.org/cgi-bin/mailman/listinfo/users

2 1

[Serusers] Status of Ottendorf and Presence
by Steve Blair 28 Mar '07

28 Mar '07

Would someone be able to tell me the status of the Ottendorf release? In addition to knowing when the stable release will be available I am also interested in when presence support will be available. Thanks,Steve

5 5

[Serusers] msilo module problem
by POON Ben 28 Mar '07

28 Mar '07

Hi all, I am trying to use the msilo module. On the website it says the dependency is only a db module and the tm module. Both of which are included in my ser.cfg file before the loadmodule for the msilo module. Can someone please help me find out what is wrong? Thanks. However, when I try to start ser, it gives me this: ************************************************************************ ****************** bash# ser -D -E 0(29857) parse error (166,17-18): unknown command, missing loadmodule? 0(29857) parse error (196,22-23): unknown command, missing loadmodule? 0(29857) parse error (243,20-21): unknown command, missing loadmodule? ERROR: bad config file (3 errors) Segmentation Fault (core dumped) ************************************************************************ ******************* I've checked the lines 166, 196, and 243, they all correspond to lines where I use m_dump and m_store. The config file is basically a copy of the one provided at http://www.iptel.org/ser/doc/modules/msilo Are there other dependencies not listed on the module page? I don't need SEMS or anything like that do I? Thank you very much, Ben

2 3

[Users] SIP Registrartions
by raviprakash sunkara 28 Mar '07

28 Mar '07

Hello Users , I have one OpenSER server , this can handle the Both Sip Registrar , location server, proxy server, But I need OpenSER only proxy that , When UAC send the Registrartion to OpenSER , and OpenSER send to Vendor Proxy ( Cisco Proxy server ). And other one I have 2 openSER , first one Registrar server say OP1 and other is OP2 UAC( register) -------->OP2-----------> OP1( here it have to save ) -- Thanks and Regards Ravi Prakash Sunkara ravi.sunkara(a)hyperion-tech.com M:+91 9985077535 www.hyperion-tech.com Client and Parent company :- www.august-networks.com

2 1

[Serusers] global contact list
by Barta János 28 Mar '07

28 Mar '07

Hello! I have a little problem with the (global) contact list subscription of the presence, please help me. I installed the presence server (0.10.99-dev35-pa-4.1), and it works without any problems. But I can not use the "Subscribe to contact list" of the eyeBeam. (The user subscribe list works fine.) I typed the next content into this field (of the eyeBeam): sip:bartaj-list@test.intra and my config file contains: sip:/var/xcap-root/rls-services/global# cat ./index <?xml version="1.0" encoding="UTF-8"?> <rls-services> <service uri="sip:bartaj-list@test.intra"> <list name="Human resources"> <entry uri="sip:test1@test.intra"> <display-name>bartaj</display-name> </entry> <entry uri="sip:test2@test.intra"> <display-name>12345</display-name> </entry> </list> <packages> <package>presence</package> </packages> </service> </rls-services> But I can see only the user subscribe list, and can't see the global one. Why? Can anybody help me? Thx, Jani _________________________________________________________________ Vásároljon kényelmesen! Több 10.000 ajánlattal, kedvező árakkal várjuk. http://cthandler.adverticum.net/?cturl=http%3A%2F%2Fwww.vasarlas.origo.hu%3…

2 1

[Users] Radius
by jidn jidn 28 Mar '07

28 Mar '07

Hi list, I need to know if open ser have a module, that uses radius, for connect with Alepo Because I have Alepo for billing. Thanks, Pablo __________________________________________________ Preguntá. Respondé. Descubrí. Todo lo que querías saber, y lo que ni imaginabas, está en Yahoo! Respuestas (Beta). ¡Probalo ya! http://www.yahoo.com.ar/respuestas

1 0

Re: [Users] Simple xcap-emulator for OpenSER
by sukerry 28 Mar '07

28 Mar '07

Adrian Georgescu, Thanks for your great job! However , when I compile php, an error says that Log.php can not be found! Thanks sukerry ======= 2007-03-28 00:56:33======= >Hello, > >We wrote a simple xcap emulator to be able to manage the XCAP >documents used by OpenSER presence agent, by using PHP scripts in >combination with Apache web server. > >I have tested it against OpenSER with MySQL and Eyebeam for Apple. >Klaus Darilion has tested it against Postgress and Eyebeam for Windows. > >The software can be downloaded from: > >http://download.dns-hosting.info/XCAP/xcap-0.5.tar.gz > >Regards, >Adrian > > >_______________________________________________ >Users mailing list >Users(a)openser.org >http://openser.org/cgi-bin/mailman/listinfo/users > 　　　　　　　　sukerry 　　　　　　　　sukerry(a)126.com 　　　　　　　　　　2007-03-28

2 1

[Users] Content-type in PUBLISH request
by jh＠tutpro.com 28 Mar '07

28 Mar '07

i started to experiment with sending PUBLISH requests using pua_mi module. if i understood correctly from RFC 3903, PUBLISH request should contain a content-type header, such as Content-Type: application/pidf+xml PUBLISH request sent via pua_mi does not contain any content-type header. should one be added so that the receiver of PUBLISH request could know how to decode the body? another question related to this is, what event packages does openser presence server support? i assume that it supports "presence" event package (where content type usually is pidf+xml), but how about "message-summary" event package (RFC 3842) that could be used to publish message waiting events? -- juha

4 7

[Users] OpenSER 1.2 support for sip:wizard
by SipWise Support 28 Mar '07

28 Mar '07

Hi all, We'd like to announce that sip:wizard (http://www.sipwise.com/wizard), the OpenSER configuration generator, now also supports OpenSER 1.2. Cheers, Your sip:wise Team

2 1

[Users] out of memory
by Papadopoulos Georgios 28 Mar '07

28 Mar '07

Hello, Lately our OpenSER 1.1.1 is running out of memory and I get the following message 4(25190) get_hdr_field: out of memory The result is that it stops processing any incoming request. This is a production system and of course it causes a great deal of frustration. The last time this happened I got the following statistics before restarting > ./openserctl fifo get_statistics Total statistics = 37 Total modules = 5 Module name = core; statistics=8 core:rcv_requests = 3259334 core:rcv_replies = 8816 core:fwd_requests = 736 core:fwd_replies = 137 core:drop_requests = 743 core:drop_replies = 0 core:err_requests = 0 core:err_replies = 43 Module name = shmem; statistics=6 shmem:total_size = 268435456 shmem:used_size = 1675864 shmem:real_used_size = 1835104 shmem:max_used_size = 4399048 shmem:free_size = 266600352 shmem:fragments = 17710 Module name = sl; statistics=9 sl:1xx_replies = 0 sl:2xx_replies = 1690410 sl:3xx_replies = 43 sl:4xx_replies = 334827 sl:5xx_replies = 1185629 sl:6xx_replies = 0 sl:sent_replies = 3210909 sl:sent_err_replies = 0 sl:received_ACKs = 743 Module name = tm; statistics=11 tm:received_replies = 8636 tm:relayed_replies = 7096 tm:local_replies = 1718 tm:UAS_transactions = 7003 tm:UAC_transactions = 94 tm:2xx_transactions = 1528 tm:3xx_transactions = 3 tm:4xx_transactions = 5129 tm:5xx_transactions = 468 tm:6xx_transactions = 0 tm:inuse_transactions = 0 Module name = usrloc; statistics=3 usrloc:location-users = 0 usrloc:location-contacts = 0 usrloc:location-expires = 7282 I am not sure how to read these numbers but I see a big "free_size" and still OpenSER is out of memory. Any suggestions? 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.

2 1

[Users] why b2bua always relay 403
by liu york 28 Mar '07

28 Mar '07

Dear all I use astersik b2bua and radius for auth and prepaid on pstn call,there is a big problem is that any responese from PSTN GW,for example 406,503...,the bubua always relay 403 to sip client.So i cant make the status clearly when pstn call,what's wrong with my b2bua,any cfg of bubua for me? many many thx.

2 1

[Users] Openser Not Send Ack to Callee?
by 杨冬 28 Mar '07

28 Mar '07

hi, all: I'm new to here and just installed an instance of openser-1.2.0-notls version under CentOS 4.3 platform. Also I've added mysql db support and it seemed all is working well. But when I made a common call through openser, I found a problem that the openser didn't send ACK message to the callee. The flow is as follows: caller ---INVITE--> openser openser ---INVITE--> callee openser <--180-------- callee caller <----180------ openser openser <----200------- callee caller <----200------ openser caller ------ACK----> openser At this time when the caller send ACK to openser, openser didn't send ACK to the callee. So after 30 seconds, the callee released the call due to time out. Does anyone know what's the problem? Any help will be appreciate!

2 2

[Serusers] Problems with ACK
by Ricardo Martinez 27 Mar '07

27 Mar '07

Hello List. I have a problem with an ACK message for a CANCEL. I'm just wondering if anyone knows what could be happening here. It seems that SER can't route or "understand" this ACK ACK sip:0299005622408196@sipvoiss.desa.redvoiss.net SIP/2.0. v: SIP/2.0/UDP 192.168.1.100:5060;branch=z9hG4bK2861608023. f: "5502203289" <sip:5502203289@sipvoiss.desa.redvoiss.net>;tag=1349608987. t: <sip:0299005622408196@sipvoiss.desa.redvoiss.net>;tag=f146818fa4. i: 5c83a04822964085e07aabd210e9d72f(a)192.168.1.100. CSeq: 4 ACK. l: 0. Could be something with the COMPACT form ??? This is the log from the debug : Mar 23 12:18:10 sipvoiss ser[5430]: t_lookup_request: start searching: hash=52251, isACK=1 Mar 23 12:18:10 sipvoiss ser[5430]: DEBUG: RFC3261 transaction matching failed Mar 23 12:18:10 sipvoiss ser[5430]: DEBUG: t_lookup_request: no transaction found Mar 23 12:18:10 sipvoiss ser[5430]: SER: forwarding ACK statelessly Mar 23 12:18:10 sipvoiss ser[5430]: DEBUG: mk_proxy: doing DNS lookup... Mar 23 12:18:10 sipvoiss ser[5430]: get_record: lookup(_sip._udp.sipvoiss.desa.redvoiss.net, 33) failed Mar 23 12:18:10 sipvoiss ser[5430]: sip_resolvehost: no SRV record found for sipvoiss.desa.redvoiss.net, trying 'normal' lookup... Mar 23 12:18:10 sipvoiss ser[5430]: check_via_address(10.0.0.248, 192.168.1.100, 0) Mar 23 12:18:10 sipvoiss ser[5430]: Sending: ACK sip:0299005622408196@sipvoiss.desa.redvoiss.net SIP/2.0^M Max-Forwards: 10^M Record-Route: <sip:10.0.0.246;ftag=2639303304;lr=on>^M Via: SIP/2.0/UDP 10.0.0.246;branch=0^M v: SIP/2.0/UDP 192.168.1.100:5060;received=10.0.0.248;branch=z9hG4bK365542204^M f: "5502203289" <sip:5502203289@sipvoiss.desa.redvoiss.net>;tag=2639303304^M t: <sip:0299005622408196@sipvoiss.desa.redvoiss.net>;tag=2746a580a4^M i: 81983e61d980fd3ef0046dafe9518284(a)192.168.1.100^M CSeq: 10 ACK^M l: 0^M ^M . Mar 23 12:18:10 sipvoiss ser[5430]: orig. len=338, new_len=477, proto=1 Mar 23 12:18:10 sipvoiss ser[5430]: DEBUG:destroy_avp_list: destroying list (nil) Mar 23 12:18:10 sipvoiss ser[5430]: receive_msg: cleaning up What does it means : "RFC3261 transaction matching failed" and why ??? The weird situation happend when almost the same message arrives without the Compact Form : V102 ACK sip:0299005622408196@sipvoiss.desa.redvoiss.net SIP/2.0. Via: SIP/2.0/UDP 10.0.0.237:5060;branch=z9hG4bK2364391837. From: "5502203289" <sip:5502203289@sipvoiss.desa.redvoiss.net>;tag=827237367. To: <sip:0299005622408196@sipvoiss.desa.redvoiss.net>;tag=6b466391a4. Call-ID: 43b2cc325b7fbe9f8790e4cee01dc4b3(a)10.0.0.237. CSeq: 2 ACK. Content-Length: 0. This message works ok!. .... ... Mar 23 16:30:06 sipvoiss ser[5974]: DEBUG: RFC3261 transaction matched, tid=424819551 Mar 23 16:30:06 sipvoiss ser[5974]: DEBUG: t_lookup_request: transaction found (T=0x404ce3e8) Mar 23 16:30:06 sipvoiss ser[5974]: DEBUG: cleanup_uac_timers: RETR/FR timers reset Mar 23 16:30:06 sipvoiss ser[5974]: DEBUG: add_to_tail_of_timer[2]: 0x404ce430 Mar 23 16:30:06 sipvoiss ser[5974]: DEBUG:destroy_avp_list: destroying list (nil) Mar 23 16:30:06 sipvoiss ser[5974]: receive_msg: cleaning up Can someone give me a hand here? Thanks in advance Regards, Ricardo Martinez-

3 4

[Serusers] New search-page
by Marcin Pazdro 27 Mar '07

27 Mar '07

Hi all, I'm going to improve the documentation search page (or rather to create new search engine). Here: http://www.iptel.org/ser_documentation_dynamic_search_page_functional_speci… I have placed a functional specification that describes main guidelines of new search page. I would like to get some feedback from you. Please let me know if you have some comments, tips or questions. pazdro :)

3 4

Re: [Users] register more than one username by IP phone
by Klaus Darilion 27 Mar '07

27 Mar '07

forgotten to Cc the list ... Klaus Darilion wrote: > I think what you need are aliases. An alias maps from one SIP URI to > another. > > e.g. sip:kd@domain.com --> sip:klaus.darilion@domain.com > sip:+4315056416@domain.com --> sip:klaus.darilion@domain.com. > > Thus, if openser receives a request, you first lookup the alias and then > lookup the location table. You can either use the aliases table and use > lookup("aliases") or use the ALIAS_DB module. > > regards > klaus > > Bodin Bruno wrote: >> Klaus Darilion a écrit : >>> The only identifier which is REGISTERed is the current location of >>> the SIP client (ipaddress:port). This gets mapped to the SIP AoR (the >>> user's SIP address). >>> >>> A user can use several clients concurrently. Then this user will show >>> up multiple times in the location table - one entry for each SIP client. >>> >>> Hope this helps - I still don't understand what you want to achieve. >>> >>> regards >>> klaus >>> >>> Bodin Bruno wrote: >>>> Hi, >>>> Is it possible to register two (or more) identifiers by user, such >>>> as phone number, username or service ? >>>> Thank >>>> >>>> _______________________________________________ >>>> Users mailing list >>>> Users(a)openser.org >>>> http://openser.org/cgi-bin/mailman/listinfo/users >> Hi, >> In some steps, >> >> what I do : >> >> step 1. Softphone clients are registered in openser with >> authentification (digest etc....) >> step 2. Openser use radius to check them (with ldap) >> step 3. Openser do save("location") to store softphone address. >> >> What I need : >> >> after step 3, authenticate username, and phone number of client are >> usable to call them. >> >> What I don't need : >> >> currently, the username used to call a softphone is the only choice of >> this user and this choice isn't limited. >> >> I'm sorry for my poor english, i'm french student. >> >> thank for your help >> >> >> >> >

3 2

[Serusers] Jabber w/ Ser
by SER LIST 27 Mar '07

27 Mar '07

Hello, has anyone successfuly worked with Jabber module? Especially forwarding messages to Hotmail, yahoo, etc. I am having issues and wanted to know whether there are issues in implementation of jaber module or not?Thanks in advance _________________________________________________________________ Your Space. Your Friends. Your Stories. Share your world with Windows Live Spaces. http://spaces.live.com/?mkt=en-ca

1 0

[Users] Openser on Sun Ultrasparc T1 Processors - Mismatch architecture detection
by Sergio Gutierrez 27 Mar '07

27 Mar '07

Hi Henning. I tested the compilation and it does not detect the architecture. I think that maybe is because of uname -p outputs sparc, and uname -m outputs sun4v. Maybe, would it be possible to include the fix to this condition at the later if (line 83 at Makefile.defs) # fix sparc -> sparc64 ifeq ($(ARCH),sparc) ifeq ($(shell uname -m),sun4u) ARCH := sparc64 endif endif Kind regards On 3/27/07, Henning Westerholt <henning.westerholt(a)1und1.de> wrote: > > On Tuesday 27 March 2007 17:12, you wrote: > > Hi Henning. > > > > The patch applies OK. > > Hi Sergio, thank you. > And is the right architecture detected, if you do a fresh compile with > this > patch? > > Best regards, > > Henning >

1 0

Re: [Serusers] re: CONTACT field malformed in a 302 reply
by Jiri Kuthan 27 Mar '07

27 Mar '07

Contact from SER is NOT malformed. It is 100% compliant to the RFC3261 spec (see sections 20.10 and 25 of RFC 3261). in the grammar, contact expands to name-addr|addr-spec, with addr-spec being URI. Exapmles in the addr-spec for also appear throughout the spec. Thus I suggest that the softswitch vendor makes himself familiar with this document. As a workaround you may wish trying some manual tricks to form a reply which will make the UAC equipment happy (append_to_reply). -jiri p.s. interestingly, gl_redirect must be your own feature, so if you developed some extra SER code updating the way of generating Contacts in 3xx should not be a big deal. I just occur to think that doing it in public SER doesn't make much sense, because if there are multiple ways to do things in SIP, whichever you choose, you will find someone who is silly enough only to accept the opposite one :-) At 20:57 26/03/2007, Jignesh Gandhi wrote: >Hello, > >I am using SER as a redirect server. >Recently I came across an issue where the 302 sent back by SER is >not liked by a soft switch. Particularly , the format of the CONTACT >field according to the softswitch.. > >Here is an excerpt of the 302 reply send back ... > >Session Initiation Protocol > Status-Line: SIP/2.0 302 MovedTemporarily > Status-Code: 302 > Resent Packet: True > Suspected resend of frame: 73 > Message Header > To: <<mailto:sip:12345@172.20.20.46>sip:12345@172.20.20.46>;tag=b27e1a1d33761e85846fc98f5f3a7e58.dfa5 > SIP to address: <mailto:sip:12345@172.20.20.46>sip:12345@172.20.20.46 > SIP tag: b27e1a1d33761e85846fc98f5f3a7e58.dfa5 > From: <http://172.20.20.46>172.20.20.46<<mailto:sip:12345@172.20.20.46>sip:12345@172.20.20.46>;tag=161dda6e > SIP Display info: <http://172.20.20.46>172.20.20.46 > SIP from address: <mailto:sip:12345@172.20.20.46>sip:12345@172.20.20.46 > SIP tag: 161dda6e > Via: SIP/2.0/UDP <http://10.99.99.140:9585>10.99.99.140:9585;branch=z9hG4bK-d87543-730866470-1--d87543-;rport=9585 > Call-ID: 95239a63f0347c53 > CSeq: 1 INVITE > Contact: sip:12345@172.20.20.37:5060 > Server: Sip EXpress router (0.8.14 (i386/linux)) > Content-Length: 0 > Warning: 392 <http://172.20.20.46:5060>172.20.20.46:5060 "Noisy feedback tells: pid=9550 req_src_ip=<http://10.99.99.140>10.99.99.140 req_src_port=9585 in_uri=<mailto:sip:12345@172.20.20.46>sip:12345@172.20.20.46 out_uri=sip:12345@172.20.20.37:5060 via_cnt==1 > >the softswitch is wanting the contact field with <sip:xxxx@xxx.xxx.xxx.xxx:5060> like a FROM or TO URI. > >Here is ser.cfg part that does the sl_send_reply(); > > # do a stateless redirect, if return code is correct > if (method=="INVITE") > { > xlog("L_INFO", "SourceIP <%is> \n"); > xlog("L_INFO", "From-uri<%fu>, r-uri <%ru> \n"); > if (!gl_redirect()) > { > sl_send_reply("480", "TemporarilyUnavailable"); > xlog("L_WARN", "Sending a 480 response with r-uri <%ru>\n"); > break; > } > else > { > sl_send_reply("302", "MovedTemporarily"); > xlog("L_DBG", "Sending a 302 response with r-uri <%ru>\n"); > break; > } > }; > >Any help is appreciated. > > >thanks, >-- >Jignesh Gandhi ><mailto:jigpgandhi@gmail.com>jigpgandhi(a)gmail.com >_______________________________________________ >Serusers mailing list >Serusers(a)lists.iptel.org >http://lists.iptel.org/mailman/listinfo/serusers -- Jiri Kuthan http://iptel.org/~jiri/

1 0

[Users] Openser on Sun Ultrasparc T1 Processors - Mismatch architecture detection
by Sergio Gutierrez 27 Mar '07

27 Mar '07

Hi everybody. I think that there is something missing on Makefile.defs. Sun Machines using the new line Processors (UltraSparc T1) are not correctly detected as a Sparc 64 bit machine. I think that architecture detection should include "sun4v" (uname -m output on a Sun Fire T1000 or T2000) as equivalent to Sun4u. Thanks. Sergio Gutiérrez.

2 3

[Users] fifo,fifo_mode commands in 1.2.0-tls
by Steve Blair 27 Mar '07

27 Mar '07

I'm upgrading a 1.0 system to 1.2.0-tls and I get a few config file errors when trying to start the proxy using the previous openser.cfg file. It seems the fifo, fifo_mode and fifo_db_url commands have changed but I can only find a change log reference for fifo_mode. What are the correct replacements for these commands? Thanks,Steve

3 2

Re: [Users] Not able to access avp variables in reply route
by Asterisk Expert 27 Mar '07

27 Mar '07

On 3/26/07, Klaus Darilion <klaus.mailinglists(a)pernau.at> wrote: > > > > Asterisk Expert wrote: > > So you mean it is not possible to access values set from one > > dialog(INVITE-200 OK) in (BYE-200OK) ? > > You can use avp_db_query to store a certain value into a table during > INVITE and fetch it back during BYE. Of course you need a key which is > identical during the dialog - e.g. callid+fromtag+totag. But totag will be null before relaying invite request, isn't it? Currently I did it with just call id. Let me know if it will create any problem. regards > klaus > > > Is there any alternative? I must have to use custom CDR not db or > radius. > > > > On 3/26/07, Klaus Darilion <klaus.mailinglists(a)pernau.at> wrote: > >> > >> > >> > >> Asterisk Expert wrote: > >> > I thought one call is one transaction isn't it? > >> > >> No. > >> > >> A transaction is a request till the final response, e.g. INVITE-200 OK. > >> or OPTIONS-200 Ok. > >> > >> In SIP terminology a call is named "dialog". A dilaog consists of > >> multiple transaction. The first transaction is the "dialog creating > >> transaction" (e.g. INVITE) and the last transaction in this dialog is > >> the "dialog terminating transcation" e.g. BYE. > >> > >> Thus, INVITE and BYE are seperate transactions which belong to the same > >> dialog. > >> > >> Openser is transaction statefull, but not dialog statefull. > >> > >> regards > >> klaus > >> > >> > > >> > On 3/26/07, Klaus Darilion <klaus.mailinglists(a)pernau.at> wrote: > >> >> > >> >> I guess you are trying to use an AVP created during INVITE in the > BYE > >> >> transaction. This is not possible as the BYE is a different > >> transaction > >> >> and AVP lifetime is limited to a single transaction. > >> >> > >> >> regards > >> >> klaus > >> >> > >> >> Asterisk Expert wrote: > >> >> > Hello, > >> >> > I'm trying to implement custom CDR using OpenSER. What I do is, > >> >> insert a > >> >> > record in cdr table on invite request. I get the id of the > inserted > >> row > >> >> > using LAST_INSERT_ID() function of mysql in avp_db_query and > >> store in > >> >> avp > >> >> > variable rowid. I set connect time in reply route when I receive > 200 > >> OK > >> >> for > >> >> > Invite request. When I get 200 OK for BYE request, I update the > cdr > >> >> record > >> >> > and store connect time, disconnect time, duration, etc. But at > this > >> >> > place(reply route) I get the null rowid so as connect time. > >> >> According to > >> >> tm > >> >> > module's onreply_avp_mode parameter, I should be able to see the > >> values > >> >> set > >> >> > from request route in reply route if I set that parameter to 1 > >> but it > >> >> > has no > >> >> > effect. I can not use either avp variables or script variables as > >> >> > transaction variables to record custom cdr. Can anyone guide me > >> >> > implementing > >> >> > this scenario or tell me what I've done wrong? > >> >> > > >> >> > > >> >> > > >> >> > >> > ------------------------------------------------------------------------ > >> >> > > >> >> > _______________________________________________ > >> >> > Users mailing list > >> >> > Users(a)openser.org > >> >> > http://openser.org/cgi-bin/mailman/listinfo/users > >> >> > >> > > >> > > >> > > >> > > > > > > > -- Regards Ruchir Brahmbhatt

2 1

RE: [Users] load testing presence server
by Toni Barata 27 Mar '07

27 Mar '07

Hi Daniel, In a scenario in witch we have a winfo and presence Subscribe with a 70 sessions per second after a wile (3906 sessions in last test) the openser crashes. Can you take a look in the attached logs from /var/log/openser.log and from core dump (they are on the same attached file)? Thanks, Toni -----Original Message----- From: Daniel-Constantin Mierla [mailto:daniel@voice-system.ro] Sent: terça-feira, 27 de Março de 2007 10:12 To: Toni Barata Cc: users(a)openser.org Subject: Re: [Users] load testing presence server Hello, On 03/26/07 19:12, Toni Barata wrote: > Hi Daniel, > > Increasing the children from 4 to 16 did turn into same results (I was already using debug=3 and fork=yes). > > But setting debug=0 did real turn in much better results. > looks like lot of syslog messages are printed. Can you check if your syslog is set asynchronous for openser? Cheers, Daniel > Thanks a lot, > Toni > > -----Original Message----- > From: Daniel-Constantin Mierla [mailto:daniel@voice-system.ro] > Sent: segunda-feira, 26 de Março de 2007 16:53 > To: Toni Barata > Cc: users(a)openser.org > Subject: Re: [Users] load testing presence server > > Hello, > > if you use exactly the same config, then turn debug to a lower level > (e.g., 3), set fork=yes and children to 16 for better results. > > Cheers, > Daniel > > > On 03/26/07 18:48, Toni Barata wrote: > >> Hi Anka, >> >> >> >> In a scenario using Openser as a Presence Sever (using the config file >> example located in >> http://openser.org/dokuwiki/doku.php/presence:configuration-file), the >> execution of load tests (with sipp) with Subscribe Presence WInfo had >> as result a maximum of 20 sessions per second (We are using a Intel(R) >> Xeon(TM) CPU 3.00GHz with 2GB RAM), with lots of retransmissions if we >> increase to values bigger than 20 (Openser dos not crash). Is there >> any configurable parameter in the Presence module that allows >> increasing this value? >> >> >> >> Best regards, >> >> Toni >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Users mailing list >> Users(a)openser.org >> http://openser.org/cgi-bin/mailman/listinfo/users >> >> > >

1 0

RE: [Users] load testing presence server
by Toni Barata 27 Mar '07

27 Mar '07

Hi Ovidiu, Thanks for the tip. But using the asynchronous mode it was not enough to increase the presence server performance if debug parameter is >= 3. Best Regards, Toni -----Original Message----- From: Ovidiu Sas [mailto:sip.nslu@gmail.com] Sent: segunda-feira, 26 de Março de 2007 22:24 To: Toni Barata Cc: daniel(a)voice-system.ro; users(a)openser.org Subject: Re: [Users] load testing presence server Hi Toni, Maybe this will help you: http://www.voice-system.ro/docs/ser-syslog/ar01s06.html Check the Note at the end of the page: NOTE: The '-' in front of "/var/log/ser.log" is to omit synchronizing the log file after every log message. If you choose to configure "syslog" in synchronous mode you must be aware that it has big impact over performances when the signaling traffic is high. Regards, Ovidiu Sas On 3/26/07, Toni Barata <toni-r-barata(a)ptinovacao.pt> wrote: > Hi Daniel, > > Increasing the children from 4 to 16 did turn into same results (I was already using debug=3 and fork=yes). > > But setting debug=0 did real turn in much better results. > > Thanks a lot, > Toni > > -----Original Message----- > From: Daniel-Constantin Mierla [mailto:daniel@voice-system.ro] > Sent: segunda-feira, 26 de Março de 2007 16:53 > To: Toni Barata > Cc: users(a)openser.org > Subject: Re: [Users] load testing presence server > > Hello, > > if you use exactly the same config, then turn debug to a lower level > (e.g., 3), set fork=yes and children to 16 for better results. > > Cheers, > Daniel > > > On 03/26/07 18:48, Toni Barata wrote: > > > > Hi Anka, > > > > > > > > In a scenario using Openser as a Presence Sever (using the config file > > example located in > > http://openser.org/dokuwiki/doku.php/presence:configuration-file), the > > execution of load tests (with sipp) with Subscribe Presence WInfo had > > as result a maximum of 20 sessions per second (We are using a Intel(R) > > Xeon(TM) CPU 3.00GHz with 2GB RAM), with lots of retransmissions if we > > increase to values bigger than 20 (Openser dos not crash). Is there > > any configurable parameter in the Presence module that allows > > increasing this value? > > > > > > > > Best regards, > > > > Toni > > > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > Users mailing list > > Users(a)openser.org > > http://openser.org/cgi-bin/mailman/listinfo/users > > > > _______________________________________________ > Users mailing list > Users(a)openser.org > http://openser.org/cgi-bin/mailman/listinfo/users >

1 0

[Users] register more than one username by IP phone
by Bodin Bruno 27 Mar '07

27 Mar '07

Hi, Is it possible to register two (or more) identifiers by user, such as phone number, username or service ? Thank

4 6

[Users] Contact header modification
by Michel Bensoussan 27 Mar '07

27 Mar '07

Hello. Is there a way to modify the contact header? For example: REGISTER REGISTER UA -----------------------------------------------> openser ----------------------------------------------------> Registrar IP:1.0.0.1 contact: ua(a)1.0.0.1 IP:1.0.0.2 contact: ua(a)1.0.0.2 The idea is to ensure that incoming call (INVITE) will path through the openser. Another setup is two interfaces, one public and one internal. Is it possible with openser? REGISTER REGISTER UA -----------------------------------------------> openser ----------------------------------------------------> Registrar IP:1.0.0.1 contact: ua(a)1.0.0.1 IP:1.0.0.2 IP:10.2.1.25 contact: ua(a)10.2.1.25 Thanks. Regards, Michel.

2 2

[Serusers] Record Routing
by KUMAR 27 Mar '07

27 Mar '07

I am using SER 0.9.6 along with MS RTC Client API for the client application. When I used the line: if(method!=REGISTER){ record_route(); } It caused in a one way communication only in case of audio as well as in case of in case of instant messaging, a new communication session had to be established for each message. But when i removed the record_route() and used sth like: if(method==ACK){ t_relay(); } When my code included both the above code snippets, it never reached the later: if (method==ACK)... part. Can anyone please tell me why when record_route() was switched on, the control never reached the later part. Thank you kumar

2 1

RE: [Users] Problem configuring the openSER with the DISC
by priyanka.bhargava＠wipro.com 27 Mar '07

27 Mar '07

Hi, I have still not reached the point of authentication, the failure is happening at establishment on the TCP connection between openSER and Diameter Client. Thanks, Priyanka ________________________________ From: raviprakash sunkara [mailto:sunkara.raviprakash.feb14@gmail.com] Sent: Tuesday, March 27, 2007 4:03 PM To: Priyanka Bhargava (WT01 - IP-Multimedia Carrier & Ent Networks) Subject: Re: [Users] Problem configuring the openSER with the DISC Hello Can u check the port forwoarding of diameter clinet and server, if there are in remote. In diameter server , client file is there, in that u need to give the openser username(a)domain.openSER and Password and nas ( n.w access server ) file in this U server has to know the DC and same in DC server file will this need to tell the DS. I guess, Because , Radius and Diameter are Same purpose using in openSER and other AAA purpose. But in My experience Radius is Best, On 3/27/07, priyanka.bhargava(a)wipro.com < priyanka.bhargava(a)wipro.com <mailto:priyanka.bhargava@wipro.com> > wrote: Hi Ravi, Thanks for your quick response. I'm actually connecting openSER with the diameter client. But the client is not accepting the connection. The configuration between the diameter client and server are already done. And they are communicating properly the only problem is the communication between the Diameter Client and the openSER. Thanks, Priyanka ________________________________ From: raviprakash sunkara [mailto:sunkara.raviprakash.feb14@gmail.com] Sent: Tuesday, March 27, 2007 2:16 PM To: Priyanka Bhargava (WT01 - IP-Multimedia Carrier & Ent Networks) Cc: users(a)openser.org Subject: Re: [Users] Problem configuring the openSER with the DISC Hello Priyanka, Diameter and radius both are same purpose. DialMeter Server never communicate with OpenSER, Vice versa, So Need the DiaMeter client, Which play the main role to Both openSER or Diameter, U problem in Diameter Clinet and server Configuration, -UA -------->OpenSER-->DiameterClient ---> Diameter Server. in DiC u should configured the authentation, where the Server is located. I'm Using the Radius for AAA, Thanks & Regards Sunkara Ravi Prakash Hyd..... On 3/27/07, priyanka.bhargava(a)wipro.com < priyanka.bhargava(a)wipro.com> wrote: Hi All, I'm trying use to Diameter Server Client (DISC) for the authentication purpose (using the auth_diameter module). But I'm facing issues while creating a connection between openSER and DISC. The diameter client does not accept the connection from the openSER. Please let me know if somebody has tried this out and can pass me the config files and the code changes if any. Thanks, Priyanka The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com _______________________________________________ Users mailing list Users(a)openser.org http://openser.org/cgi-bin/mailman/listinfo/users -- Thanks and Regards Ravi Prakash Sunkara ravi.sunkara(a)hyperion-tech.com M:+91 9985077535 www.hyperion-tech.com Client and Parent company :- www.august-networks.com The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com -- Thanks and Regards Ravi Prakash Sunkara ravi.sunkara(a)hyperion-tech.com M:+91 9985077535 www.hyperion-tech.com Client and Parent company :- www.august-networks.com The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com

1 0

[Users] Invalid Table Version
by Martin Klisch 27 Mar '07

27 Mar '07

Hello, after upgrading our MySQL 4.0.x to 5 and compiling the openser(1.1.1)-mysql modul with the new mysql libraries i always get this error: [ID 272136 local1.error] table_version(): Invalid type (2) or nul (0) version columns for subscriber The tableversion is the right one and i can access the openser tables with the openser-user via regular mysql console client. now i tried it with mysql 4.1 - it's the same problem. anyone has an idea, what the problem could be?

2 3

RE: [Users] PRESENCE module issues
by Geir O. Jensen 27 Mar '07

27 Mar '07

Well, I did what you said... Grabbed the SVN (today, Tuesday 27th), purged the old db, modules, binaries and libraries ... Recompiled, ran openser_mysql.sh create and now I get this error; PRESENCE:mod_init: Wrong version v1 for table <presentity>, need v0 ... :-/ Now what - Geir > -----Original Message----- > From: Anca Vamanu [mailto:anca@voice-system.ro] > Sent: Monday, March 26, 2007 7:01 PM > To: Geir O. Jensen > Subject: Re: [Users] PRESENCE module issues > > Hello, > > Don't worry. It will for sure be up and running by then. > > I was not talking about the offical release, but the SVN > version of OpenSer1.2. > To download it use: > > # svn co > https://openser.svn.sourceforge.net/svnroot/openser/branches/1 > .2 openser More information at: > http://www.openser.org/mos/view/Download/ > > It must work now :) . > > Best regards, > Anca > > > > Geir O. Jensen wrote: > > >Okay, I downloaded the 1.2.0 tarball on the 19th of March. Was it > >changed after that date? The date stamp on the > >http://www.openser.org/pub/openser/1.2.0/src/ server location says > >March 12th... > > > >Hopefully I'll be able to do this within a few days... Easter is > >looming and things slow down around here then :D > > > >Thanks for your help so far! > > > >- Geir > > > > > > > >>-----Original Message----- > >>From: Anca Vamanu [mailto:anca@voice-system.ro] > >>Sent: Monday, March 26, 2007 10:17 AM > >>To: G.O. Jensen > >>Cc: daniel(a)voice-system.ro > >>Subject: Re: [Users] PRESENCE module issues > >> > >>Hello, > >> > >>I was in fact refering to the newst version of OpenSer 1.2.0. > >>It has also been updated. > >>You can also take the svn version- it will work with the > modules from > >>1.2.0, but you have to make a change in the > >>database- adding 2 new columns in active_watcher_table > >>- so you should run the database script again. It has a transport > >>issue fixed which is still under testing. > >> > >>Best regards, > >> > >>Anca Vamanu > >> > >>G.O. Jensen wrote: > >> > >> > >> > >>>Hm, righto. Well, I used the "official" downloadable tarball from > >>>openser.org. Maybe they should rush out a 1.2.1 patch asap then :D > >>> > >>>So, do I need to grab all modules and OpenSER core from > SVN too, or > >>>while the "updated" presence module work with the "stable" 1.2.0 > >>>OpenSER release? > >>> > >>>Anca Vamanu said: > >>> > >>> > >>> > >>> > >>>>Hello, > >>>> > >>>>I found the problem, much simpler that we might have > >>>> > >>>> > >>thought. You use > >> > >> > >>>>an old version, at least a week old. There was a bug there that I > >>>>fixed last week. > >>>>You should take the latest version on svn and it should work. > >>>> > >>>>Best regards, > >>>> > >>>>Anca Vamanu > >>>> > >>>> > >>>>G.O. Jensen wrote: > >>>> > >>>> > >>>> > >>>> > >>>> > >>>>>Hey, I really want to get this working so all the effort I > >>>>> > >>>>> > >>can pour > >> > >> > >>>>>into it :D I will do more testing over the weekend > though - I have > >>>>>two servers so I can see if the problems crops up on both. > >>>>> > >>>>>The clients use are eyeBeam 1.5 (Windows) and Gaim > 2.0beta (Linux). > >>>>>OpenSER crashes when I register the eyeBeam client and the > >>>>> > >>>>> > >>presence > >> > >> > >>>>>exchange starts. Fork is indeed set to yes in my Config > >>>>> > >>>>> > >>(which I can > >> > >> > >>>>>get you a copy of over the weekend aswell to help > reproduce it at > >>>>>your > >>>>>end...) > >>>>> > >>>>>(I'm at home now so I can't access all data easily...) > >>>>> > >>>>>Thanks, > >>>>>G.O. Jensen > >>>>>UNINETT > >>>>> > >>>>>Anca Vamanu said: > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>>>Thanks for your effort. > >>>>>>Unfortunatelly the backtrace is not revealing at all. It seems > >>>>>>compulsory to reproduce your scenario to be able to fix > >>>>>> > >>>>>> > >>this. And I > >> > >> > >>>>>>just can't manage to do this. > >>>>>>What clients are you using? > >>>>>>Is fork yes or no in your configuration? > >>>>>> > >>>>>>Many thanks. > >>>>>> > >>>>>>G.O. Jensen wrote: > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>>>Anca-Maria Vamanu said: > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>>>I can't reproduce what you got there and I can't figure > >>>>>>>> > >>>>>>>> > >>out from > >> > >> > >>>>>>>>the log what goes wrong. > >>>>>>>>Could you please send be the backtrace of the generated core. > >>>>>>>>Use: gdb openser core > >>>>>>>> >bt > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>Sure can do... this error was reproducible for me (I > tried 3 or 4 > >>>>>>>times...) > >>>>>>> > >>>>>>>Main routing script does a if method= then handle_() > >>>>>>> > >>>>>>> > >>thingy... and > >> > >> > >>>>>>>then returns. > >>>>>>> > >>>>>>>root@test-sip:/# gdb openser core GNU gdb 6.4-debian Copyright > >>>>>>>2005 Free Software Foundation, Inc. > >>>>>>>GDB is free software, covered by the GNU General > Public License, > >>>>>>>and you are welcome to change it and/or distribute > copies of it > >>>>>>>under certain conditions. > >>>>>>>Type "show copying" to see the conditions. > >>>>>>>There is absolutely no warranty for GDB. Type "show > >>>>>>> > >>>>>>> > >>warranty" for > >> > >> > >>>>>>>details. > >>>>>>>This GDB was configured as "i486-linux-gnu"...Using host > >>>>>>>libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". > >>>>>>> > >>>>>>>Core was generated by `/usr/local/sbin/openser -P > >>>>>>>/var/run/openser.pid -m > >>>>>>>32 -u root -g root'. > >>>>>>>Program terminated with signal 11, Segmentation fault. > >>>>>>> > >>>>>>>warning: Can't read pathname for load map: Input/output error. > >>>>>>>Reading symbols from /lib/tls/i686/cmov/libdl.so.2...done. > >>>>>>>Loaded symbols for /lib/tls/i686/cmov/libdl.so.2 > Reading symbols > >>>>>>> > >>>>>>> > >>>>>>>from /lib/tls/i686/cmov/libresolv.so.2...done. > >>>>>> > >>>>>> > >>>>>>>Loaded symbols for /lib/tls/i686/cmov/libresolv.so.2 Reading > >>>>>>>symbols from /usr/lib/i686/cmov/libssl.so.0.9.8...done. > >>>>>>>Loaded symbols for /usr/lib/i686/cmov/libssl.so.0.9.8 > >>>>>>>Reading symbols from > >>>>>>> > >>>>>>> > >>/usr/lib/i686/cmov/libcrypto.so.0.9.8...done. > >> > >> > >>>>>>>Loaded symbols for /usr/lib/i686/cmov/libcrypto.so.0.9.8 > >>>>>>>Reading symbols from /lib/tls/i686/cmov/libc.so.6...done. > >>>>>>>Loaded symbols for /lib/tls/i686/cmov/libc.so.6 Reading symbols > >>>>>>> > >>>>>>> > >>>>>>>from /lib/ld-linux.so.2...done. > >>>>>> > >>>>>> > >>>>>>>Loaded symbols for /lib/ld-linux.so.2 Reading symbols from > >>>>>>>/usr/lib/libz.so.1...done. > >>>>>>>Loaded symbols for /usr/lib/libz.so.1 Reading symbols from > >>>>>>>/usr/local/lib/openser/modules/mysql.so...done. > >>>>>>>Loaded symbols for /usr/local/lib/openser/modules/mysql.so > >>>>>>>Reading symbols from /lib/tls/i686/cmov/libm.so.6...done. > >>>>>>>Loaded symbols for /lib/tls/i686/cmov/libm.so.6 Reading symbols > >>>>>>> > >>>>>>> > >>>>>>>from /usr/lib/libmysqlclient.so.14...done. > >>>>>> > >>>>>> > >>>>>>>Loaded symbols for /usr/lib/libmysqlclient.so.14 > Reading symbols > >>>>>>> > >>>>>>> > >>>>>>>from /lib/tls/i686/cmov/libcrypt.so.1...done. > >>>>>> > >>>>>> > >>>>>>>Loaded symbols for /lib/tls/i686/cmov/libcrypt.so.1 > >>>>>>> > >>>>>>> > >>Reading symbols > >> > >> > >>>>>>>from /lib/tls/i686/cmov/libnsl.so.1...done. > >>>>>> > >>>>>> > >>>>>>>Loaded symbols for /lib/tls/i686/cmov/libnsl.so.1 > >>>>>>> > >>>>>>> > >>Reading symbols > >> > >> > >>>>>>>from /usr/local/lib/openser/modules/sl.so...done. > >>>>>> > >>>>>> > >>>>>>>Loaded symbols for /usr/local/lib/openser/modules/sl.so > >>>>>>>Reading symbols from > /usr/local/lib/openser/modules/tm.so...done. > >>>>>>>Loaded symbols for /usr/local/lib/openser/modules/tm.so > >>>>>>>Reading symbols from > /usr/local/lib/openser/modules/rr.so...done. > >>>>>>>Loaded symbols for /usr/local/lib/openser/modules/rr.so > >>>>>>>Reading symbols from > >>>>>>> > >>>>>>> > >>/usr/local/lib/openser/modules/maxfwd.so...done. > >> > >> > >>>>>>>Loaded symbols for /usr/local/lib/openser/modules/maxfwd.so > >>>>>>>Reading symbols from > >>>>>>> > >>>>>>> > >>/usr/local/lib/openser/modules/usrloc.so...done. > >> > >> > >>>>>>>Loaded symbols for /usr/local/lib/openser/modules/usrloc.so > >>>>>>>Reading symbols from > >>>>>>>/usr/local/lib/openser/modules/registrar.so...done. > >>>>>>>Loaded symbols for /usr/local/lib/openser/modules/registrar.so > >>>>>>>Reading symbols from > >>>>>>> > >>>>>>> > >>/usr/local/lib/openser/modules/textops.so...done. > >> > >> > >>>>>>>Loaded symbols for /usr/local/lib/openser/modules/textops.so > >>>>>>>Reading symbols from > >>>>>>> > >>>>>>> > >>/usr/local/lib/openser/modules/xlog.so...done. > >> > >> > >>>>>>>Loaded symbols for /usr/local/lib/openser/modules/xlog.so > >>>>>>>Reading symbols from > >>>>>>> > >>>>>>> > >>/usr/local/lib/openser/modules/enum.so...done. > >> > >> > >>>>>>>Loaded symbols for /usr/local/lib/openser/modules/enum.so > >>>>>>>Reading symbols from > >>>>>>> > >>>>>>> > >>/usr/local/lib/openser/modules/uri_db.so...done. > >> > >> > >>>>>>>Loaded symbols for /usr/local/lib/openser/modules/uri_db.so > >>>>>>>Reading symbols from > >>>>>>> > >>>>>>> > >>/usr/local/lib/openser/modules/options.so...done. > >> > >> > >>>>>>>Loaded symbols for /usr/local/lib/openser/modules/options.so > >>>>>>>Reading symbols from > >>>>>>> > >>>>>>> > >>/usr/local/lib/openser/modules/auth.so...done. > >> > >> > >>>>>>>Loaded symbols for /usr/local/lib/openser/modules/auth.so > >>>>>>>Reading symbols from > >>>>>>> > >>>>>>> > >>/usr/local/lib/openser/modules/auth_db.so...done. > >> > >> > >>>>>>>Loaded symbols for /usr/local/lib/openser/modules/auth_db.so > >>>>>>>Reading symbols from > >>>>>>> > >>>>>>> > >>/usr/local/lib/openser/modules/avpops.so...done. > >> > >> > >>>>>>>Loaded symbols for /usr/local/lib/openser/modules/avpops.so > >>>>>>>Reading symbols from > >>>>>>> > >>>>>>> > >>/usr/local/lib/openser/modules/mi_fifo.so...done. > >> > >> > >>>>>>>Loaded symbols for /usr/local/lib/openser/modules/mi_fifo.so > >>>>>>>Reading symbols from > >>>>>>> > >>>>>>> > >>/usr/local/lib/openser/modules/presence.so...done. > >> > >> > >>>>>>>Loaded symbols for /usr/local/lib/openser/modules/presence.so > >>>>>>>Reading symbols from /usr/lib/libxml2.so.2...done. > >>>>>>>Loaded symbols for /usr/lib/libxml2.so.2 Reading symbols from > >>>>>>>/lib/tls/i686/cmov/libnss_compat.so.2...done. > >>>>>>>Loaded symbols for /lib/tls/i686/cmov/libnss_compat.so.2 > >>>>>>>Reading symbols from /lib/tls/i686/cmov/libnss_nis.so.2...done. > >>>>>>>Loaded symbols for /lib/tls/i686/cmov/libnss_nis.so.2 > >>>>>>>Reading symbols from > /lib/tls/i686/cmov/libnss_files.so.2...done. > >>>>>>>Loaded symbols for /lib/tls/i686/cmov/libnss_files.so.2 > >>>>>>>#0 0x080b7eed in fm_free (qm=0x8170b40, p=0xb7a8ffdf) at > >>>>>>>mem/f_malloc.c:130 > >>>>>>>130 frag->u.nxt_free=*f; > >>>>>>>(gdb) bt > >>>>>>>#0 0x080b7eed in fm_free (qm=0x8170b40, p=0xb7a8ffdf) at > >>>>>>>mem/f_malloc.c:130 > >>>>>>>#1 0xb7a8ce8f in handle_subscribe (msg=0x8186ca8, str1=0x0, > >>>>>>>str2=0x0) > >>>>>>> at subscribe.c:1099 > >>>>>>>#2 0x08052d56 in do_action (a=0x8178f48, msg=0x8186ca8) at > >>>>>>>action.c:883 > >>>>>>>#3 0x08051faa in run_action_list (a=0x8178e68, > msg=0x8186ca8) at > >>>>>>>action.c:131 > >>>>>>>#4 0x08054423 in do_action (a=0x81790d8, msg=0x8186ca8) at > >>>>>>>action.c:801 > >>>>>>>#5 0x08051faa in run_action_list (a=0x8178ba0, > msg=0x8186ca8) at > >>>>>>>action.c:131 > >>>>>>>#6 0x08054423 in do_action (a=0x817bc88, msg=0x8186ca8) at > >>>>>>>action.c:801 > >>>>>>>#7 0x08051faa in run_action_list (a=0x81770c8, > msg=0x8186ca8) at > >>>>>>>action.c:131 > >>>>>>>#8 0x080552c5 in run_top_route (a=0x81770c8, msg=0x0) at > >>>>>>>action.c:111 > >>>>>>>#9 0x08082769 in receive_msg ( > >>>>>>> buf=0x8140180 "SUBSCRIBE sip:oak@test-sip.uninett.no > >>>>>>> > >>>>>>> > >>SIP/2.0\r\nVia: > >> > >> > >>>>>>>SIP/2.0/UDP > >>>>>>>158.38.62.97:16472;branch=z9hG4bK-d87543-2b2f3c5a00212916 > >>>>>>> > >>>>>>> > >>-1--d87543-;rport\r\nMax-Forwards: > >> > >> > >>>>>>>69\r\nContact: <sip:gojensen@158.38.62.97:16472>"..., > >>>>>>> len=635, rcv_info=0xbfae1328) at receive.c:156 #10 > >>>>>>> > >>>>>>> > >>0x080b112a in > >> > >> > >>>>>>>udp_rcv_loop () at udp_server.c:465 > >>>>>>>#11 0x08070a08 in main_loop () at main.c:834 > >>>>>>>#12 0x08072045 in main (argc=9, argv=0xbfae14e4) at main.c:1399 > >>>>>>> > >>>>>>>// geir.o.jensen(a)uninett.no > >>>>>>> UNINETT AS, NO-7465 Trondheim, NORWAY > >>>>>>> Fax: +47 73 55 79 01, Phn: +47 73 55 79 00 > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>// geir.o.jensen(a)uninett.no > >>>>> UNINETT AS, NO-7465 Trondheim, NORWAY > >>>>> Fax: +47 73 55 79 01, Phn: +47 73 55 79 00 > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>> > >>>> > >>>> > >>>> > >>>// geir.o.jensen(a)uninett.no > >>> UNINETT AS, NO-7465 Trondheim, NORWAY > >>> Fax: +47 73 55 79 01, Phn: +47 73 55 79 00 > >>> > >>> > >>> > >>> > >> > >> > > > > > > > >

3 3

RE: [Users] load testing presence server
by Toni Barata 27 Mar '07

27 Mar '07

Hi Daniel, Increasing the children from 4 to 16 did turn into same results (I was already using debug=3 and fork=yes). But setting debug=0 did real turn in much better results. Thanks a lot, Toni -----Original Message----- From: Daniel-Constantin Mierla [mailto:daniel@voice-system.ro] Sent: segunda-feira, 26 de Março de 2007 16:53 To: Toni Barata Cc: users(a)openser.org Subject: Re: [Users] load testing presence server Hello, if you use exactly the same config, then turn debug to a lower level (e.g., 3), set fork=yes and children to 16 for better results. Cheers, Daniel On 03/26/07 18:48, Toni Barata wrote: > > Hi Anka, > > > > In a scenario using Openser as a Presence Sever (using the config file > example located in > http://openser.org/dokuwiki/doku.php/presence:configuration-file), the > execution of load tests (with sipp) with Subscribe Presence WInfo had > as result a maximum of 20 sessions per second (We are using a Intel(R) > Xeon(TM) CPU 3.00GHz with 2GB RAM), with lots of retransmissions if we > increase to values bigger than 20 (Openser dos not crash). Is there > any configurable parameter in the Presence module that allows > increasing this value? > > > > Best regards, > > Toni > > ------------------------------------------------------------------------ > > _______________________________________________ > Users mailing list > Users(a)openser.org > http://openser.org/cgi-bin/mailman/listinfo/users >

3 2

[Users] Re: memory issues
by Papadopoulos Georgios 27 Mar '07

27 Mar '07

Hi Daniel, Does this problem affect 1.1.1 or only 1.2? Is there a patch to use for 1.1.1? thank you George -------------------------------------------------------------------------------- Hello Ovidiu, On 03/23/07 17:04, Ovidiu Sas wrote: > Hi Daniel, > > Can we backport this one to 1.2? already done, two minutes after the commit in trunk. Cheers, Daniel > > > Regards, > Ovidiu Sas > > On 3/22/07, Daniel-Constantin Mierla <daniel at voice-system.ro <http://openser.org/cgi-bin/mailman/listinfo/users> > wrote: >> Hello, >> >> the supposed fragmentation turned out to be a mem leak in pkg. Please >> take the latest SVN version and try again to see if you got same >> results. >> >> Thanks, >> Daniel >> >> On 03/19/07 18:52, Christian Schlatter wrote: >> > ... >> >>> The memory statistics indeed show a high number of memory fragments: >> >>> >> >>> before 'out of memory': >> >>> >> >>> shmem:total_size = 536870912 >> >>> shmem:used_size = 59607040 >> >>> shmem:real_used_size = 60106488 >> >>> shmem:max_used_size = 68261536 >> >>> shmem:free_size = 476764424 >> >>> shmem:fragments = 9897 >> >>> >> >>> after 'out of memory' (about 8000 calls per process): >> >>> >> >>> shmem:total_size = 536870912 >> >>> shmem:used_size = 4171160 >> >>> shmem:real_used_size = 4670744 >> >>> shmem:max_used_size = 68261536 >> >>> shmem:free_size = 532200168 >> >>> shmem:fragments = 57902 >> >>> >> >>>> >> >>>> You can try to compile openser with -DQM_JOIN_FREE (add it in DEFS >> >>>> variable of Makefile.defs) and test again. Free fragments should be >> >>>> merged and fragmentation should not occur -- processing will be >> >>>> slower. We will try for next release to provide a better solution >> >>>> for that. >> >>> >> >>> Compiling openser with -DQM_JOIN_FREE did not help. I'm not sure how >> >>> big of a problem this fragmentation issue is. >> >> What is the number of fragments with QM_JOIN_FREE after flooding? >> > >> > The numbers included above are with QM_JOIN_FREE enabled. >> > >> >>> Do you think it would make sense to restart our production openser >> >>> instances from time to time just to make sure they're not running >> >>> into this memory fragmentation limits? >> >> The issue will occur only when the call rate reaches the limits of >> >> the proxy's memory. Otherwise the chunks are reused. Transactions and >> >> avps are rounded up to be sure there will be minimized the number of >> >> different sizes for memory chunks. It wasn't reported too often, >> >> maybe that's why no big attention was paid to it. This memory system >> >> is in place since the beginning of ser. Alternative is to use sysv >> >> shared memory, but is much slower, along with libc private memory >> >> manager. >> > >> > I've done some more testing and the same out-of-memory stuff happens >> > when I run sipp with 10 calls per second only. I tested with >> > 'children=1' and I only could get through about 8200 calls (again >> > those 8000 calls / process). And this is with QM_JOIN_FREE enabled. >> > >> > Memory statistics: >> > >> > before: >> > shmem:total_size = 536870912 >> > shmem:used_size = 2311976 >> > shmem:real_used_size = 2335720 >> > shmem:max_used_size = 2465816 >> > shmem:free_size = 534535192 >> > shmem:fragments = 183 >> > >> > after: >> > shmem:total_size = 536870912 >> > shmem:used_size = 1853472 >> > shmem:real_used_size = 1877224 >> > shmem:max_used_size = 2465816 >> > shmem:free_size = 534993688 >> > shmem:fragments = 547 >> > >> > So I'm not sure if this is really a fragmentation issue. 10 cps surely >> > doesn't reach the proxy's memory. >> > >> > Thoughts? >> > >> > Christian >> > >> > >> > >> >> Cheers, >> >> Daniel >> >> >> >>> >> >>> thanks, >> >>> Christian >> >>> >> >>>> >> >>>> Cheers, >> >>>> Daniel >> >>>> >> >>>> On 03/18/07 01:21, Christian Schlatter wrote: >> >>>>> Christian Schlatter wrote: >> >>>>> ... >> >>>>>> >> >>>>>> I always had 768MB shared memory configured though, so I still >> >>>>>> can't explain the memory allocation errors I got. Some more test >> >>>>>> runs revealed that I only get these errors when using a more >> >>>>>> production oriented config that loads more modules than the one >> >>>>>> posted in my earlier email. I now try to figure out what exactly >> >>>>>> causes these memory allocation errors that happen reproducibly >> >>>>>> after about 220s at 400 cps. >> >>>>> >> >>>>> I think I found the cause for the memory allocation errors. As >> >>>>> soon as I include an AVP write operation in the routing script, I >> >>>>> get 'out of memory' messages after a certain number of calls >> >>>>> generated with sipp. >> >>>>> >> >>>>> The routing script to reproduce this behavior looks like (full >> >>>>> config available at >> >>>>> http://www.unc.edu/~cschlatt/openser/openser.cfg <http://www.unc.edu/~cschlatt/openser/openser.cfg> ): >> >>>>> >> >>>>> route{ >> >>>>> $avp(s:ct) = $ct; # commenting this line solves >> >>>>> # the memory problem >> >>>>> >> >>>>> if (!method=="REGISTER") record_route(); >> >>>>> if (loose_route()) route(1); >> >>>>> >> >>>>> if (uri==myself) rewritehost("xx.xx.xx.xx"); >> >>>>> route(1); >> >>>>> } >> >>>>> >> >>>>> route[1] { >> >>>>> if (!t_relay()) sl_reply_error(); >> >>>>> exit; >> >>>>> } >> >>>>> >> >>>>> An example log file showing the 'out of memory' messages is >> >>>>> available at http://www.unc.edu/~cschlatt/openser/openser.log <http://www.unc.edu/~cschlatt/openser/openser.log> . >> >>>>> >> >>>>> Some observations: >> >>>>> >> >>>>> - The 'out of memory' messages always appear after about 8000 test >> >>>>> calls per worker process. One call consists of two SIP >> >>>>> transactions and six end-to-end SIP messages. An openser with 8 >> >>>>> children handles about 64'000 calls, whereas 4 children only >> >>>>> handle about 32'000 calls. The sipp call rate doesn't matter, only >> >>>>> number of calls. >> >>>>> >> >>>>> - The 8000 calls per worker process are independent from the >> >>>>> amount of shared memory available. Running openser with -m 128 or >> >>>>> -m 768 does not make a difference. >> >>>>> >> >>>>> - The more AVP writes are done in the script, the less calls go >> >>>>> through. It looks like each AVP write is leaking memory (unnoticed >> >>>>> by the memory statistics). >> >>>>> >> >>>>> - The fifo memory statistics do not reflect the 'out of memory' >> >>>>> syslog messages. Even if openser does not route a single SIP >> >>>>> message because of memory issues, the statistics still show a lot >> >>>>> of 'free' memory. >> >>>>> >> >>>>> >> >>>>> All tests were done with openser SVN 1.2 branch on Ubuntu dapper >> >>>>> x86. I think the same is true for 1.1 version but I haven't tested >> >>>>> that yet. >> >>>>> >> >>>>> >> >>>>> Christian >> >>>>> >> >>> >> >>> >> > >> > >> > _______________________________________________ >> > Users mailing list >> > Users at openser.org <http://openser.org/cgi-bin/mailman/listinfo/users> >> > http://openser.org/cgi-bin/mailman/listinfo/users <http://openser.org/cgi-bin/mailman/listinfo/users> >> > >> >> _______________________________________________ >> Users mailing list >> Users at openser.org <http://openser.org/cgi-bin/mailman/listinfo/users> >> http://openser.org/cgi-bin/mailman/listinfo/users <http://openser.org/cgi-bin/mailman/listinfo/users> >> > Γιώργος Παπαδόπουλος Altec Telecoms R&D Department Πάτμου 14, 151 23 Μαρούσι τηλ.: +30 211 687 2933 fax.: +30 211 687 2911 e-mail: geop(a)altectelecoms.gr 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.

2 1

[Users] pua_usrloc and expire time
by H Quintana 27 Mar '07

27 Mar '07

Hello, I'm using the pua_usrloc for IP phones with no presence options. When I restart the IP phone, the first REGISTER makes the module to send the PUBLISH message and the presentity is stored in the table with the proper expiration time. For the next REGISTER, it seems the module is using the old "expires" time instead taking the new value because the presentity expires some seconds after that. For further registrations, it's happening the same because the status is always offline after the second REGISTER. It doesn't matter the db_mode used for the usrloc module. Any suggestions? Thanks for your help, Humberto Quintana ____________________________________________________________________________________ Expecting? Get great news right away with email Auto-Check. Try the Yahoo! Mail Beta. http://advision.webevents.yahoo.com/mailbeta/newmail_tools.html

2 1

[Users] I need save("location") but with some change ...
by Bodin Bruno 27 Mar '07

27 Mar '07

Hello, I currently use this code : if (is_method("REGISTER")) { if (!radius_www_authorize("mydomain")) { www_challenge("mydomain", "0"); exit; }; xlog("new user : $au"); save("location")) ; exit; }; But save function add a new item in location table with these param : Username, domain, contact ....user_agent, socket, methods. Username use by register module isn't Authentification's username how can I change it ? Is it possible to add more location for a user ? ( Like username and numer phone ) Thank for your help.

3 2

[Users] Watchers table not being updated
by Sebastian Murray-Roberts 27 Mar '07

27 Mar '07

Hi, I'm trying to set up OpenSER as a presence server without using force_active (ie to allow authorization). I have two x-lite clients which register with OpenSER and can subscribe to each other. I get a prompt on each client asking whether to authorize the other, but if I click yes no presence info is displayed. If I restart either of the x-lites the authorization message appears again. I know this is because the subs_status field of the watchers table is not being changed from "pending" to "active". If I run a packet capture when starting up x-lite, it sends the 200 OK to the notify provided by OpenSER, but when I click "allow" in the authorization box, nothing is sent to OpenSER. Has anyone got presence working with x-lite without using force_active? If so, is there anything I'm missing? My config file is as follows: debug=7 # debug level (cmd line: -dddddddddd) fork=no log_stderror=yes check_via=no # (cmd. line: -v) dns=no # (cmd. line: -r) rev_dns=no # (cmd. line: -R) listen=udp:192.168.1.107:5060 children=4 mpath="/usr/local/lib/openser/modules/" loadmodule "mysql.so" loadmodule "sl.so" loadmodule "usrloc.so" loadmodule "registrar.so" loadmodule "maxfwd.so " loadmodule "textops.so" loadmodule "tm.so" loadmodule "rr.so" loadmodule "presence.so" loadmodule "avpops.so" loadmodule "mi_fifo.so" modparam("mi_fifo", "fifo_name", "/tmp/openser_fifo") modparam("usrloc", "db_mode", 3) modparam("rr", "enable_full_lr", 1) modparam("presence|^usrloc$", "db_url"," mysql://user:pass@localhost /openser") modparam("presence", "force_active", 0) modparam("presence", "max_expires", 3600) modparam("presence", "server_address", "sip: 192.168.1.107:5060") route{ if (!mf_process_maxfwd_header("10")) { sl_send_reply("483","Too Many Hops"); exit; }; if (msg:len >= 2048 ) { sl_send_reply("513", "Message too big"); exit; }; if (!is_method("REGISTER")) record_route(); if (loose_route()) { route(1); exit; }; if (!uri==myself) { route(1); exit; }; if (uri==myself) { if (method=="REGISTER") { save("location"); exit; }; if (!lookup("location")) { sl_send_reply("404", "Not Found"); exit; }; }; if( is_method("PUBLISH|SUBSCRIBE")) { route(2); exit; }; route(1); } route[1] { if (!t_relay()) { sl_reply_error(); }; exit; } route[2] { sl_send_reply("100","trying"); if (!t_newtran()) { sl_reply_error(); exit; }; if(is_method("PUBLISH")) { handle_publish(); t_release(); } else if( is_method("SUBSCRIBE")) { handle_subscribe(); t_release(); }; exit; } Thanks in advance, Sebastian -- Sebastian Murray-Roberts (B.Sc Hons) Server Developer Yeigo Communications http://www.yeigo.com Tel: +27 21 409 7807 Fax: +27 21 409 7050 Mobile: +27 72 183 5998 CONFIDENTIALITY NOTICE: E-MAIL This e-mail is confidential. If you receive it by mistake, please delete it and notify the sender immediately. If you are not the intended recipient, you may not use, disclose, distribute, copy or publish any information contained herein.

2 1

[Serusers] re: CONTACT field malformed in a 302 reply
by Jignesh Gandhi 27 Mar '07

27 Mar '07

Hello, I am using SER as a redirect server. Recently I came across an issue where the 302 sent back by SER is not liked by a soft switch. Particularly , the format of the CONTACT field according to the softswitch.. Here is an excerpt of the 302 reply send back ... Session Initiation Protocol Status-Line: SIP/2.0 302 MovedTemporarily Status-Code: 302 Resent Packet: True Suspected resend of frame: 73 Message Header To: <sip:12345@172.20.20.46>;tag= b27e1a1d33761e85846fc98f5f3a7e58.dfa5 SIP to address: sip:12345@172.20.20.46 SIP tag: b27e1a1d33761e85846fc98f5f3a7e58.dfa5 From: 172.20.20.46<sip:12345@172.20.20.46>;tag=161dda6e SIP Display info: 172.20.20.46 SIP from address: sip:12345@172.20.20.46 SIP tag: 161dda6e Via: SIP/2.0/UDP 10.99.99.140:9585 ;branch=z9hG4bK-d87543-730866470-1--d87543-;rport=9585 Call-ID: 95239a63f0347c53 CSeq: 1 INVITE * Contact: sip:12345@172.20.20.37:5060 * Server: Sip EXpress router (0.8.14 (i386/linux)) Content-Length: 0 Warning: 392 172.20.20.46:5060 "Noisy feedback tells: pid=9550 req_src_ip=10.99.99.140 req_src_port=9585 in_uri=sip:12345@172.20.20.46out_uri= sip:12345@172.20.20.37:5060 via_cnt==1 the softswitch is wanting the contact field with <sip:xxxx@xxx.xxx.xxx.xxx:5060> like a FROM or TO URI. Here is ser.cfg part that does the sl_send_reply(); # do a stateless redirect, if return code is correct if (method=="INVITE") { xlog("L_INFO", "SourceIP <%is> \n"); xlog("L_INFO", "From-uri<%fu>, r-uri <%ru> \n"); if (!gl_redirect()) { sl_send_reply("480", "TemporarilyUnavailable"); xlog("L_WARN", "Sending a 480 response with r-uri <%ru>\n"); break; } else { sl_send_reply("302", "MovedTemporarily"); xlog("L_DBG", "Sending a 302 response with r-uri <%ru>\n"); break; } }; Any help is appreciated.** thanks, -- Jignesh Gandhi jigpgandhi(a)gmail.com

3 2

Re: [Serusers] SER - Config files
by samuel 27 Mar '07

27 Mar '07

First of all, please CC to the list!!! it->refers to the routing script you are using that by default is ser.cfg. You can change it starting ser with -f parameter and placing after the config file. I recomend you to look into iptel.org and get the general overview of the project. samuel. 2007/3/26, Goh, Tee-Yong <gohty(a)m1.com.sg>: > > > > Hi Samuel, > > Thank you for your support. > Therefore, you have mentioned that ser.cfg is just an example and do not > need to modify. However, as you have mentioned "You would definetely need to > modify it to make SER behave as your requirements dictates", what does "it" > are you refering to? The files in the SER or just ser.cfg? > > Please advice. > > Thank you. > > Regards, > Howard > > > -----Original Message----- > From: samuel [mailto:samu60@gmail.com] > Sent: Monday, March 26, 2007 5:10 PM > To: Goh, Tee-Yong > Cc: serusers(a)iptel.org > Subject: Re: [Serusers] SER - Config files > > > ser.cfg is, usually, the routing script that dictates how SER behaves > on receiving SIP requests and responses. > It's just an example that should work wihtout modificaction and is > meant as a starting point to get into SER. You would definetely need > to modify it to make SER behave as your requirements dictates. > > look for more information in iptel.org and google... > > Good Luck! > > sam > > 2007/3/25, Goh, Tee-Yong <gohty(a)m1.com.sg>: > > > > > > > > Hi all, > > > > May i seek your expertise advice. I have found the config file name > > "ser.cfg" and "ser.cfg~" in the SER-0.9.6. > > However, i do not know what are they used for? Can i make any modification > > to them? > > > > Please advice. > > > > Thank you. > > > > Regards, > > Howard > > > > ________________________________ > > This email (including any attachment) is subject to the following > > disclaimer: > > > http://m1.com.sg/M1/misc/disclaimer________________________________ > > > > _______________________________________________ > > Serusers mailing list > > Serusers(a)lists.iptel.org > > http://lists.iptel.org/mailman/listinfo/serusers > > > > > > ________________________________ > This email (including any attachment) is subject to the following > disclaimer: > http://m1.com.sg/M1/misc/disclaimer________________________________ >

1 0

[Users] Openser Compilation problem using Optimized GCC
by Sergio Gutierrez 27 Mar '07

27 Mar '07

Hello everybody. I discovered another issue when compiling openser on Solaris 10 running on Sparc. If I use standard gcc version 3.4.3, it compiles and runs Ok when it is compiled on 32 bits (Standard compilation without special command line options). But If I use the GCC edition for SPARC Systems (GCCFS) by Sun Microsytems (which is based on GCC 4.0.3 and is an optimized edition for Solaris on SPARC), openser fails to start complaining about table versions. Below appears the log output, and the backtrace of the generated core file: WARNING: no fork mode 0(1120) fm_malloc_init: F_OPTIMIZE=16384, /ROUNDTO=2048 0(1120) fm_malloc_init: F_HASH_SIZE=2067, fm_block size=16560 0(1120) fm_malloc_init(fc800000, 33554432), start=fc800000 0(1120) shm_mem_init: success 0(0) core dump limits set to 0 0(0) DEBUG:add_avp_galias: registering <serial_branch> for avp id <16725044> 0(0) INFO: statistics manager successfully initialized 0(0) DEBUG: init_mod: sl 0(0) StateLess module - initializing 0(0) DEBUG: MD5 calculated: 224bba3fcb82b3a99110f369fb8df55a 0(0) DEBUG: register_stats: sl 0(0) DEBUG: init_mod: usrloc 0(0) usrloc - initializing 0(0) INFO:ul_init_locks: locks array size 4096 0(0) unixsock_register_cmd: New command (ul_rm) registered 0(0) unixsock_register_cmd: New command (ul_rm_contact) registered 0(0) unixsock_register_cmd: New command (ul_dump) registered 0(0) unixsock_register_cmd: New command (ul_flush) registered 0(0) unixsock_register_cmd: New command (ul_add) registered 0(0) unixsock_register_cmd: New command (ul_show_contact) registered 0(0) find_mod_export: found <db_use_table> in module mysql [/toip2/lib/openser/modules/] 0(0) find_mod_export: found <db_init> in module mysql [/toip2/lib/openser/modules/] 0(0) find_mod_export: found <db_close> in module mysql [/toip2/lib/openser/modules/] 0(0) find_mod_export: found <db_query> in module mysql [/toip2/lib/openser/modules/] 0(0) find_mod_export: found <db_fetch_result> in module mysql [/toip2/lib/openser/modules/] 0(0) find_mod_export: found <db_raw_query> in module mysql [/toip2/lib/openser/modules/] 0(0) find_mod_export: found <db_free_result> in module mysql [/toip2/lib/openser/modules/] 0(0) find_mod_export: found <db_insert> in module mysql [/toip2/lib/openser/modules/] 0(0) find_mod_export: found <db_delete> in module mysql [/toip2/lib/openser/modules/] 0(0) find_mod_export: found <db_update> in module mysql [/toip2/lib/openser/modules/] 0(0) find_mod_export: found <db_replace> in module mysql [/toip2/lib/openser/modules/] 0(0) DEBUG: register_stats: usrloc 0(0) DEBUG: register_mi: usrloc 0(0) DEBUG: init_mod: registrar 0(0) registrar - initializing 0(0) find_cmd_export_t: found <load_sl>(0) in module sl [/toip2/lib/openser/modules/] 0(0) find_cmd_export_t: found <ul_bind_usrloc>(1) in module usrloc [/toip2/lib/openser/modules/] 0(0) DEBUG: register_stats: registrar 0(0) DEBUG: init_mod: tm 0(0) TM - initializing... 0(0) Call-ID initialization: '47395976' 0(0) unixsock_register_cmd: New command (t_uac_dlg) registered 0(0) unixsock_register_cmd: New command (t_uac_cancel) registered 0(0) unixsock_register_cmd: New command (t_hash) registered 0(0) unixsock_register_cmd: New command (t_reply) registered 0(0) DEBUG: lock_initialize: lock initialization started 0(0) Warning: uac does not spread across the whole hash table 0(0) DEBUG: MD5 calculated: b5fd95724ef23fee9ce49ee6c27239d6 0(0) DEBUG: MD5 calculated: d0730e359e0208514db6efb58e0ac8b9 0(0) DEBUG: register_stats: tm 0(0) DEBUG: register_mi: tm 0(0) DEBUG: init_mod: mysql 0(0) mysql: MySQL client version is 5.0.37 0(0) DEBUG: init_mod: auth 0(0) AUTH module - initializing 0(0) find_cmd_export_t: found <load_sl>(0) in module sl [/toip2/lib/openser/modules/] 0(0) xl_parse_name: name [s:rpid] index [0] 0(0) xl_parse_vname: avp [s:rpid] 0(0) DEBUG: init_mod: auth_db 0(0) AUTH_DB module - initializing 0(0) find_mod_export: found <db_use_table> in module mysql [/toip2/lib/openser/modules/] 0(0) find_mod_export: found <db_init> in module mysql [/toip2/lib/openser/modules/] 0(0) find_mod_export: found <db_close> in module mysql [/toip2/lib/openser/modules/] 0(0) find_mod_export: found <db_query> in module mysql [/toip2/lib/openser/modules/] 0(0) find_mod_export: found <db_fetch_result> in module mysql [/toip2/lib/openser/modules/] 0(0) find_mod_export: found <db_raw_query> in module mysql [/toip2/lib/openser/modules/] 0(0) find_mod_export: found <db_free_result> in module mysql [/toip2/lib/openser/modules/] 0(0) find_mod_export: found <db_insert> in module mysql [/toip2/lib/openser/modules/] 0(0) find_mod_export: found <db_delete> in module mysql [/toip2/lib/openser/modules/] 0(0) find_mod_export: found <db_update> in module mysql [/toip2/lib/openser/modules/] 0(0) find_mod_export: found <db_replace> in module mysql [/toip2/lib/openser/modules/] 0(0) find_cmd_export_t: found <bind_auth>(0) in module auth [/toip2/lib/openser/modules/] 0(0) find_cmd_export_t: found <load_sl>(0) in module sl [/toip2/lib/openser/modules/] 0(0) DEBUG: init_mod: auth_radius 0(0) auth_radius - Initializing 0(0) auth_radius: No `Cisco' vendor in Radius dictionary 0(0) find_cmd_export_t: found <bind_auth>(0) in module auth [/toip2/lib/openser/modules/] 0(0) DEBUG: init_mod: acc 0(0) ACC - initializing 0(0) find_cmd_export_t: found <load_tm>(0) in module tm [/toip2/lib/openser/modules/] 0(0) xl_parse_name: name [Via] index [-2] 0(0) INFO:xl_parse_name: using hdr type (1) instead of <Via> 0(0) fixing radius_www_authorize, line 63 0(0) fixing www_challenge, line 65 0(0) fixing save, line 69 0(0) db_init: Connection 'mysql://openser:openserrw@localhost/openser' not found in pool 0(0) new_connection: Opening MySQL connection: mysql://openser:openserrw@localhost/openser 0(0) new_connection: Connection type is Localhost via UNIX socket 0(0) new_connection: Protocol version is 10 0(0) new_connection: Server version is 5.0.37-log 0(0) table_version(): Invalid type (2) or nul (0) version columns for location 0(0) register_udomain(): Error while querying table version 0(0) pool_remove: Removing connection from the pool 0(0) domain_fixup(): Error while registering domain 0(0) ERROR: fix_actions: fixing failed (code=-1) at cfg line 69 0(0) ERROR: fix_expr : fix_actions error ERROR: error -1 while trying to fix configuration Segmentation Fault (core dumped) # GDB backtrace (gdb) bt #0 0x000305a8 in process_count () #1 0x00030518 in kill_all_children () #2 0x00033ab8 in main () Is there any incompatibility when using GCC 4.X to compile openser? Thanks in advance for your help. Sergio Gutiérrez

1 0

[Users] "client did not present a certificate"(OpenSER 1.2 + EyeBeam 1.5 + TLS) !! need help!!
by yanlin 27 Mar '07

27 Mar '07

Hi, all, i have been trying to test TLS support on OpenSER with EyeBeam client, but in no vain. OpenSER keep complaining that "client did not present a certificate". really need help! thanks in advance. here is some info of my environment: 1) OpenSER 1.2 and EyeBeam 1.5 2) run "openserctl tls rootCA", create "cacert.pem" under /etc/openser/tls/rootCA/. 3) run "openserctl tls userCERT", create "user-calist.pem user-cert.pem user-cert_req.pem user-privkey.pem" under /etc/openser/tls/user/. 4) i have set openser.cfg as follow: disable_tls = 0 listen = tls:172.22.14.61:5061 tls_verify_client = 0 tls_require_client_certificate = 0 tls_method = TLSv1 tls_certificate = /etc/openser/tls/user/user-cert.pem" tls_private_key = "/etc/openser/tls/user/user-privkey.pem" tls_ca_list = "/etc/openser/tls/user/user-calist.pem" 5) copy "/etc/openser/tls/rootCA/cacert.pem" created at step 2) to EyeBeam clinet machine, which was a Windows XP machine, run "certmrg.msc" there, import this certificate to WindowXP "root certificate store". when run ... error occur. OpenSER complaint that "client did not present a certificate", and EyeBeam receive a "503 certificate name mismath". Any advise will be very appreciate !! yan lin yanlin(a)fortinet.com 2007-3-26

3 3

[Serusers] New search-page
by Marcin Pazdro 26 Mar '07

26 Mar '07

Hi all, I'm going to improve the documentation search page (or rather to create new search engine). Here: http://www.iptel.org/ser_documentation_dynamic_search_page_functional_speci… I have placed a functional specification that describes main guidelines of new search page. I would like to get some feedback from you. Please let me know if you have some comments, tips or questions. pazdro :)

2 1

[Users] Openser fails when compiled on Solaris 64bit
by Sergio Gutierrez 26 Mar '07

26 Mar '07

Hi I am trying to run Openser compiled on 64 bits on a SPARC Machine running Solaris 10. When I create a simple configuration file for testing radius integration, Openser starts to consume the whole memory reservation (-m parameter) and fails with segmentation fault error. after several tests, I have found that the error is caused by save() function (registrar module). This is the main route my configuration file: route { if(method=="REGISTER") { if(!radius_www_authorize("")) { www_challenge("", "0"); return; }; if(!save("location")) { sl_reply_error(); }; return; } else { } } Thanks in advance for your help. Sergio G.

2 1

[Users] load testing presence server
by Toni Barata 26 Mar '07

26 Mar '07

Hi Anka, In a scenario using Openser as a Presence Sever (using the config file example located in http://openser.org/dokuwiki/doku.php/presence:configuration-file), the execution of load tests (with sipp) with Subscribe Presence WInfo had as result a maximum of 20 sessions per second (We are using a Intel(R) Xeon(TM) CPU 3.00GHz with 2GB RAM), with lots of retransmissions if we increase to values bigger than 20 (Openser dos not crash). Is there any configurable parameter in the Presence module that allows increasing this value? Best regards, Toni

2 1

[Users] Not able to access avp variables in reply route
by Asterisk Expert 26 Mar '07

26 Mar '07

Hello, I'm trying to implement custom CDR using OpenSER. What I do is, insert a record in cdr table on invite request. I get the id of the inserted row using LAST_INSERT_ID() function of mysql in avp_db_query and store in avp variable rowid. I set connect time in reply route when I receive 200 OK for Invite request. When I get 200 OK for BYE request, I update the cdr record and store connect time, disconnect time, duration, etc. But at this place(reply route) I get the null rowid so as connect time. According to tm module's onreply_avp_mode parameter, I should be able to see the values set from request route in reply route if I set that parameter to 1 but it has no effect. I can not use either avp variables or script variables as transaction variables to record custom cdr. Can anyone guide me implementing this scenario or tell me what I've done wrong? -- Regards Ruchir Brahmbhatt Ecosmob Technologies

2 3

[Users] openserctl alias show ???
by Daryl Sanders 26 Mar '07

26 Mar '07

How can I view a list of aliases via openserctl? I tried "openserctl alias show", however this seems to return a list of registered UA's not aliases. - Daryl

4 5

[Users] Can not access script variables in openser 1.2.0
by Asterisk Expert 26 Mar '07

26 Mar '07

Hello, Sorry last mail sent accidentally. I've initialized some SCRIPT VARIABLES in request route. I modify the values of some of these SCRIPT VARIABLES in reply route. But I'm not able to get value of some of those variables in either request or reply route. Any idea? -- Regards Ruchir Brahmbhatt

2 2

[Serusers] Changing expires in 200 OK for Register
by Baljeet Gill 26 Mar '07

26 Mar '07

Hi All, Is there a way to change the "expires" value in the 200 response (sent by SER) for REGISTER? Thanks, Baljeet To access the latest news from CSR copy this link into a web browser: http://www.csr.com/email_sig.php To get further information regarding CSR, please visit our Investor Relations page at http://ir.csr.com/csr/about/overview

2 1

[Users] rewritehost
by Kro Kamil 26 Mar '07

26 Mar '07

hello, suppose that i am calling xxxxx(a)10.0.0.9 and i want to send this call to 10.0.0.10. is there any difference between rewritehost(10.0.0.10); and $ruri=sip:xxxxx@10.0.0.10; thanks _________________________________________________________________ Live.com'u deneyin: çevrimiçi dünyanızı bir araya getirin; haberler, spor, hava durumu ve çok daha fazlası. http://www.live.com/getstarted

2 1

[Serusers] FIFO file
by Meidiana Ten 26 Mar '07

26 Mar '07

Hi, I'd like to know if we had 2 SER config file (home proxy and voicemail server) in same machine, do I have to setup different fifo file? For example, SER home proxy has fifo file /tmp/ser_fifo so what fifo I have to use for SER voicemail server? And how do I create the other fifo file? Thanx Regards, Meidiana --------------------------------- Don't be flakey. Get Yahoo! Mail for Mobile and always stay connected to friends.

5 4

[Users] No audio when openSER is forworded to Asterisk server in the Same LAN network.
by raviprakash sunkara 26 Mar '07

26 Mar '07

Hello Users . For last 2 days onwards i'm fighting with this promlem, In integrating with Asterisk and openSER, No audio when openSER is forworded to Asterisk server in the Same LAN network. OpenSER and Asterisk are in the Same LAN network. With NAT , i forward the the port to 192.168.2.11 of openSER sip port and rtp port. With out NAT is Working Fine , openSER ip is 192.168.2.11 Asterisk is in 192.168.2.75 alias=sip.hyperion-tech.com if ( method =="INVITE") { if(uri=~"sip:1234567@sip.hyperion-tech.com || uri=~" sip:12345678@sip.hyperion-tech.com") { route(12); }; }; route[12] { rewrtitehostport("192.168.2.75:5060"); # ASTERISK SERVER if(!t_relay()) { sl_send_error(); exit; }; } -- Thanks and Regards Ravi Prakash Sunkara ravi.sunkara(a)hyperion-tech.com M:+91 9985077535 www.hyperion-tech.com Client and Parent company :- www.august-networks.com

1 0

Re: [Users] Not able to access avp variables in reply route
by Asterisk Expert 26 Mar '07

26 Mar '07

Yes I know radius accounting will work but I have to do it without radius. So I'm doing it manually using avp_db_query. On 3/26/07, raviprakash sunkara <sunkara.raviprakash.feb14(a)gmail.com> wrote: > > Hi > > U can use the Radius for account > > with Acc of radius some avp functions are there > > u means > like this > onroute_reply[] > { > if( status==200) > { > i f ( method == "invite" ) > accouting start of avp module > if methosd == bye) > acctoung stop of avp module > } > } > > > On 3/26/07, Asterisk Expert < asterisk.expert(a)gmail.com> wrote: > > > Hello, > > I'm trying to implement custom CDR using OpenSER. What I do is, insert a > > record in cdr table on invite request. I get the id of the inserted row > > using LAST_INSERT_ID() function of mysql in avp_db_query and store in avp > > variable rowid. I set connect time in reply route when I receive 200 OK for > > Invite request. When I get 200 OK for BYE request, I update the cdr record > > and store connect time, disconnect time, duration, etc. But at this > > place(reply route) I get the null rowid so as connect time. According to tm > > module's onreply_avp_mode parameter, I should be able to see the values set > > from request route in reply route if I set that parameter to 1 but it has no > > effect. I can not use either avp variables or script variables as > > transaction variables to record custom cdr. Can anyone guide me implementing > > this scenario or tell me what I've done wrong? > > -- > > Regards > > Ruchir Brahmbhatt > > Ecosmob Technologies > > > > _______________________________________________ > > Users mailing list > > Users(a)openser.org > > http://openser.org/cgi-bin/mailman/listinfo/users > > > > > > > -- > Thanks and Regards > Ravi Prakash Sunkara > ravi.sunkara(a)hyperion-tech.com > M:+91 9985077535 > www.hyperion-tech.com > Client and Parent company :- www.august-networks.com -- Regards Asterisk Expert

1 0

[Users] No audio when openSER is forwarded to Asterisk server in the Same LAN network.
by raviprakash sunkara 26 Mar '07

26 Mar '07

Hello Users . For last 2 days onwards i'm fighting with this promlem, In integrating with Asterisk and openSER, No audio when openSER is forworded to Asterisk server in the Same LAN network. OpenSER and Asterisk are in the Same LAN network. With NAT , i forward the the port to 192.168.2.11 of openSER sip port and rtp port. With out NAT is Working Fine , openSER ip is 192.168.2.11 Asterisk is in 192.168.2.75 alias=sip.hyperion-tech.com if ( method =="INVITE") { if(uri=~"sip:1234567@sip.hyperion-tech.com || uri=~" sip:12345678@sip.hyperion-tech.com") { route(12); }; }; route[12] { rewrtitehostport("192.168.2.75:5060"); # ASTERISK SERVER if(!t_relay()) { sl_send_error(); exit; }; } -- Thanks and Regards Ravi Prakash Sunkara ravi.sunkara(a)hyperion-tech.com M:+91 9985077535 www.hyperion-tech.com Client and Parent company :- www.august-networks.com

1 0

[Users] VOIP Patent Bomb Goes Off In U.S.
by michael papet 26 Mar '07

26 Mar '07

For those of you that haven't heard, here's a nice rundown on Verizon's patent enforcement activities. http://ipurbia.com/2007/03/verizon-patent-analysis.html This news makes me sad.

2 1

[Users] Openser not starting
by Knight Tiger 26 Mar '07

26 Mar '07

Hi I ran [root@openser ~]# openser start Listening on udp: A.B.C.D [A.B.C.D]:5060 udp: 127.0.0.1 [127.0.0.1]:5060 tcp: A.B.C.D [A.B.C.D]:5060 tcp: 127.0.0.1 [127.0.0.1]:5060 Aliases: tcp: localhost.my.domain:5060 tcp: localhost:5060 tcp: dhcpwl009.testdomain.com:5060 udp: localhost.my.domain:5060 udp: localhost:5060 udp: dhcpwl009.testdomain.com:5060 but I dont see any process running with the ps command So I checked the config files using -c [root@openser ~]# openser -c Listening on udp: A.B.C.D [A.B.C.D]:5060 udp: 127.0.0.1 [127.0.0.1]:5060 tcp: A.B.C.D [A.B.C.D]:5060 tcp: 127.0.0.1 [127.0.0.1]:5060 Aliases: tcp: localhost.my.domain:5060 tcp: localhost:5060 tcp: dhcpwl009.testdomain.com:5060 udp: localhost.my.domain:5060 udp: localhost:5060 udp: dhcpwl009.testdomain.com:5060 config file ok, exiting... 0(16175) INFO:mi_fifo:mi_destroy:memory for the child's mi_fifo_pid was not allocated -> nothing to destroy [root@openser ~]# So the config files are okay but then openser does not start. So I tried root@openser % openserctl moni [cycle #: 1; if constant make sure server lives] and the process does not die.. I had to manually kill the process. I checked the subscriber table on the database and it was corect. I had registered a few users and it reflected them. The Postgres database is running. What am I doing wrong ? Any help would be appreciated. Thanks Knight

2 1

[Users] OpenSER as a Load Balancer for Asterisk and RE-INVITEs
by Edoardo Serra 25 Mar '07

25 Mar '07

Hi all, I have an OpenSER acting as a registrar server and as a load balancer (with dispatcher module) for a cluster of PSTN Gateways based on Asterisk. When an inbound call is coming from the PSTN, Asterisks dial SIP/user@openser and the call is properly forwarded to the correct user in OpenSER location table But, if the user wants, for example, to put the call On-Hold, its user agent sends a RE-INVITE to OpenSER. My problem is that OpenSER (correctly) dispatch the call to a random Asterisk GW, and, if it's not the GW which is handling the call, On-Hold does not work and another call is originated. Tnx in advance for help Edoardo My openser.cfg follows # $Id: ser.cfg,v 1.21.4.1 2003/11/10 15:35:15 andrei Exp $ # ----------- global configuration parameters ------------------------ check_via=yes # (cmd. line: -v) dns=no # (cmd. line: -r) rev_dns=no # (cmd. line: -R) fifo="/tmp/ser_fifo" #uid=nobody #gid=nobody # ------------------ module loading ---------------------------------- loadmodule "/usr/lib/openser/modules/sl.so" loadmodule "/usr/lib/openser/modules/tm.so" loadmodule "/usr/lib/openser/modules/rr.so" loadmodule "/usr/lib/openser/modules/maxfwd.so" loadmodule "/usr/lib/openser/modules/usrloc.so" loadmodule "/usr/lib/openser/modules/registrar.so" loadmodule "/usr/lib/openser/modules/nathelper.so" loadmodule "/usr/lib/openser/modules/textops.so" loadmodule "/usr/lib/openser/modules/exec.so" loadmodule "/usr/lib/openser/modules/uri.so" loadmodule "/usr/lib/openser/modules/uri_db.so" loadmodule "/usr/lib/openser/modules/dispatcher.so" loadmodule "/usr/lib/openser/modules/mysql.so" loadmodule "/usr/lib/openser/modules/auth.so" loadmodule "/usr/lib/openser/modules/auth_db.so" modparam("usrloc", "db_mode", 2) modparam("usrloc", "db_url", "mysql://user:pass@192.168.252.5/openser") modparam("usrloc", "timer_interval", 120) modparam("auth_db", "calculate_ha1", 0) modparam("auth_db", "db_url", "mysql://user:pass@192.168.252.5/db") modparam("uri_db", "db_url", "mysql://user:pass@192.168.252.5/openser") modparam("rr", "enable_full_lr", 1) modparam("registrar", "nat_flag", 6) modparam("registrar", "max_expires", 3600) modparam("registrar", "min_expires", 60) modparam("registrar", "append_branches", 0) modparam("registrar", "desc_time_order", 1) modparam("nathelper", "natping_interval", 20) # Ping interval 20 s modparam("nathelper", "ping_nated_only", 1) # Ping only clients behind NAT modparam("dispatcher", "force_dst", 1) # ------------------------- request routing logic ------------------- # main routing logic route{ if (!mf_process_maxfwd_header("10")) { sl_send_reply("483","Too Many Hops"); exit; }; if ( msg:len > max_len ) { sl_send_reply("513", "Message too big"); exit; }; if ( (method=="OPTIONS") || (method=="SUBSCRIBE") || (method=="NOTIFY") ) { sl_send_reply("405", "Method Not Allowed"); exit; } if (!method=="REGISTER") { record_route(); }; if ((src_ip==ip.of.asterisk.1) || (src_ip==ip.of.asterisk.1)) { if (!lookup("location")) { sl_send_reply("486", "Busy here"); exit; }; if (!t_relay()) { sl_reply_error(); }; exit; }; if (nat_uac_test("3")) { if ((method=="REGISTER") || (method=="INVITE") || (method=="OPTIONS")) { fix_nated_contact(); force_rport(); setflag(6); # Mark as NATed } } if (method=="REGISTER") { if (!proxy_authorize("exorsa", "openser_view")) { proxy_challenge("exorsa", "0"); exit; } if (!check_to()) { sl_send_reply("403", "Digest username and URI username do NOT match! Stay away!"); exit; } save("location"); exit; }; if (method=="INVITE") { if (!proxy_authorize("exorsa", "openser_view")) { proxy_challenge("exorsa", "0"); exit; } if (!check_from()) { sl_send_reply("403", "Digest username and URI username do NOT match! Stay away!"); exit; } } # loose-route processing if (loose_route()) { # mark routing logic in request append_hf("P-hint: rr-enforced\r\n"); route(1); exit; }; if (!uri==myself) { # mark routing logic in request append_hf("P-hint: outbound\r\n"); route(1); exit; }; append_hf("P-hint: usrloc applied\r\n"); route(1); } route[1] { # !! Nathelper if (uri=~"[@:](192\.168\.|10\.|172\.(1[6-9]|2[0-9]|3[0-1])\.)" && !search("^Route:")){ sl_send_reply("479", "We don't forward to private IP addresses"); exit; }; # NAT processing of replies; apply to all transactions (for example, # re-INVITEs from public to private UA are hard to identify as # NATed at the moment of request processing); look at replies t_on_reply("1"); if ((src_ip!=ip.of.asterisk.1) && (src_ip!=ip.of.asterisk.2)) { ds_select_dst("1", "0"); } if (!t_relay()) { sl_reply_error(); }; } # !! Nathelper onreply_route[1] { # NATed transaction ? if (isflagset(6) && status =~ "(183)|2[0-9][0-9]") { fix_nated_contact(); # otherwise, is it a transaction behind a NAT and we did not # know at time of request processing ? (RFC1918 contacts) } else if (nat_uac_test("1")) { fix_nated_contact(); }; }

2 2

[Users] roadmap web page
by Ovidiu Sas 24 Mar '07

24 Mar '07

Hi, Now that openser 1.2 was released, it is time to update the roadmap :) http://www.openser.org/mos/view/Roadmap/ Regards, Ovidiu Sas

1 0

[Users] Re: Openser not starting (Knight Tiger)
by vallimamod abdullah 24 Mar '07

24 Mar '07

Hello Knight, On 3/24/07, "Knight Tiger" <caugar(a)gmail.com> wrote on behalf of users-request(a)openser.org <users-request(a)openser.org>: > [...] > So the config files are okay but then openser does not start. > [...] Have you had a look on the logs ? There are sometimes config errors that are not detected during the check but only at startup. So you can try with: debug=9 fork=no log_stderror=yes in your config and run openser directly (i.e. not via the init script) to get verbose output to the console. -- Regards, -vma .

1 0

[Users] Can not access script variables
by Asterisk Expert 24 Mar '07

24 Mar '07

Hello, I've initialized some script variables in request route. I modify the values of some of these SCRIPT VARIABLES -- Regards Asterisk Expert

1 0

[Users] Comparable regex function in openser
by CARTWRIGHT, CORY C (ATTSNET) 23 Mar '07

23 Mar '07

Hello all, I am attempting to add a line to the SDP of a reply using subst. In perl I can do it like this. $test1 =~ s/(.+)\sRTP\/AVP\s18\s(.+)/$1 RTP\/AVP 18 $2\na=fmtp:18 annexb=no\n/g; This ensures I have the whole "m=audio 28104 RTP/AVP 18 101 19" string in the replacement I started with this: subst('/(.*) RTP\/AVP 18 (.*)/\1 RTP\/AVP 18 \2\r\na=fmtp:18 annexb=no\r\n/g'); As most of you probably can see this does not work. Does anyone know if this is possible? Thanks. This e-mail and any files transmitted with it are the property of AT&T Connecticut, are confidential, and are intended solely for the use of the individuals or entities to whom it is addressed. If you are not a named recipient, or otherwise have reason to believe that you have received this message in error, please notify the sender at phone 203-420-7225, and delete this message immediately from your computer. Any other use, retention, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited.

2 3

[Users] OpenSER 1.2 and NAT
by Andreas Granig 23 Mar '07

23 Mar '07

Hi, When migrating my config from 1.1 to 1.2, far-end NAT traversal doesn't work anymore. Here is what I do: modparam("usrloc", "nat_bflag", 6) ... # register handling: if(!search("^Contact:[ ]*\*") && nat_uac_test("19")) { xlog("L_INFO", "NATed REGISTER\n"); fix_nated_register(); setbflag(6); } if(!save("location")) { # error handling ... } The log message is printed, so NAT is detected. The received-column in the DB also shows the correct NAT-address, but the flag-column is always 0. Any advice? Regards, Andreas This e-mail is confidential and may well also be legally privileged. If you have received it in error, you are on notice of its status. Please notify us immediately by reply e-mail and then delete this message from your system. Please do not copy it or use it for any purposes, or disclose its contents to any other person: to do so could be a breach of confidence. Thank you for your cooperation. Information pursuant to paragraph 14 Austrian Companies Code: UPC Austria GmbH; Registered Office: Wolfganggasse 58-60, 1120 Vienna Company Register Number: FN 189858d at the Commercial Court of Vienna

2 3

[Users] Openser 1.2.0 and exec_dset
by Tobias Lindgren 23 Mar '07

23 Mar '07

Hi all, I'm using exec_dset to run a script which takes the Request-URI and returns a new Request-URI based on the number dialed. In ser.cfg I'm doing this: if (exec_dset("lookup.sh \"$$SIP_RURI\"")) { # Route call } else { # Reply with a cause } Recently a customer started to use SIP-X, and his INVITES with Request-URIs looks like this: sip:1001@192.168.0.1:5060;sipx-noroute=Voicemail Ser responds with "500 Server Internal Error" to these INVITEs, which is due to that my script fails. If I run OpenSER in the foreground with debugging I can see this: 0(20509) exec:w_exec_dset: executing [lookup.php "$SIP_RURI"] 0(20509) exec_str: rtrim sh: line 1: sipx-noroute=Voicemail: command not found How do I correctly escape the SIP_RURI in my openser.cfg to prevent my script from failing? Or is the RURI to long or something? If I run my script from commandline with the request uri, everything is fine. Br, /Tobias

2 6

[Users] PRESENCE module issues
by Geir O. Jensen 23 Mar '07

23 Mar '07

Setup; OpenSER 1.2.0 Fresh install (no SERWEB, all the rest) running on MySQL 5.0.22 (Ubuntu 6.06) Two subscribers that publish status, but neither can see status of the other... They are both in the presentity table and listed in the watchers/active_watchers table. When I change status in the client the following occurs on the server; PRESENCE:update_presentity: querying presentity PRESENCE:get_subs_dialog:querying database table = active_watchers PRESENCE: get_subs_dialog:The query for subscribtion for [user]= gojensen,[domain]= test-sip.uninett.no for [event]= presence returned no result PRESENCE:query_db_notify: Could not get subs_dialog from database PRESENCE:update_presentity: Could not send Notify PRESENCE: handle_publish: sip-etag: [SIP-ETag: a.1174552555.9851.2^M /31] I looked through the archives and google very quickly and found something about wrong record sizes and types (for postgresql)... However neither seems to apply in my case. Has anyone got PRESENCE module working, or more importantly, does anyone know how to solve the above issue? // sip:gojensen@uninett.no | h323: 004710012 pstn: +47 73 55 79 23 | fax: +47 73 55 79 01

4 6

Re: [Users] OpenSER crashes when attempting to use null avp variable
by Daniel-Constantin Mierla 23 Mar '07

23 Mar '07

Hello, On 03/23/07 13:59, Asterisk Expert wrote: > Hello Daniel, > I just figured out. I forgot to set db url for avpops :)) > But in this case openser should not start and give error. not? does now, thanks for reporting (just committed on svn). > Instead it started and when executed mysql query, it crashed. > I have one more query. I read that if we set onreply_avp_mode=1 in tm > module, we can access avp variables in reply routes. I have done the > same. I set some avp value in request route and update mysql db based > on that value in reply route but I'm getting null :( > What do you think will be the problem? I will check it. Cheers, Daniel > > > On 3/23/07, *Daniel-Constantin Mierla* <daniel(a)voice-system.ro > <mailto:daniel@voice-system.ro> > wrote: > > Hello, > > i tried to reproduce, but I got no same result. If the avp is > null, the > returned values is false in comparisons. > > Could you send log messages and backtrace? > > Cheers, > Daniel > > > On 03/23/07 10:37, Asterisk Expert wrote: > > Hello, > > I'm using openser 1.2.0 . I have following section in my > openser.cfg. > > > > avp_db_query("SELECT active, accountcode FROM openser_ip_auth WHERE > > ip_addr='$src_ip'","$avp(s:active);$avp(s:accountcode)"); > > xlog("L_INFO", "\n$avp(s:active):::$avp(s:accountcode)\n"); > > if (!avp_check("$avp(s:active)","eq/1/I")) > > { > > xlog("L_ERR", "$si [$Tf]: $rm $fu -> $ru: REGISTER: bad > > credentials, ask for credentials\n"); > > > > #authentication failed > > www_challenge("", "0"); > > setflag(1); > > return; > > } > > Basically I'm doing IP based authentication. I have used the similar > > method in version 1.1 but openser 1.2.0 crashes if the query in > > avp_db_query returns no rows which keeps those two avp variables > null. > > Is this a bug or I'm doing something wrong? > > I also tried "==" operator for comparison but it crashes whenever it > > is trying to access one of those two variables. > > -- > > Regards > > Ruchir Brahmbhatt > > Ecosmob Technologies > > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > Users mailing list > > Users(a)openser.org <mailto:Users@openser.org> > > http://openser.org/cgi-bin/mailman/listinfo/users > > > > > > > -- > Regards > Ruchir Brahmbhatt

2 2

[Users] memory issues
by Christian Schlatter 23 Mar '07

23 Mar '07

I'm doing sipp performance measurements with openser 1.2 and I was surprised on how much memory the openser processes do allocate when confronted with a high call-per-second load. I observed the following behavior: One sipp instance creates SIP requests that get routed through openser and forwarded to another sipp instance running in UAS mode. The sipp scenario looks like INVITE ----------> 100 <---------- 180 <---------- 200 <---------- ACK ----------> Pause [ 10.0s] BYE ----------> 200 <---------- Nothing special here. The openser instance record routes the SIP requests and forwards them in transaction stateful mode (t_relay) to the sipp UAS instance. The routing script looks like: route{ if (!method=="REGISTER") record_route(); if (loose_route()) route(1); if (uri==myself) rewritehost("xx.xx.xx.xx"); route(1); } route[1] { if (!t_relay()) sl_reply_error(); exit; } ( xx.xx.xx.xx is the IP of sipp UAS) Running sipp with a call rate of 500 cps results in 45 MB of memory allocation per openser process after a few seconds. What could cause this behavior, message queuing maybe? But then again having a message queue of 40+ MB seems to be unrealistic. And the memory consumption goes up the longer the test runs until openser dies because of out-of-memory. I observed the same behavior with openser 1.1 and 1.2. Is this a memory leak or did I miss some settings? And what's the best method to debug memory issues with openser? thanks in advance, Christian

4 13

[Users] No Audio when integrating openSER and Asterisk , in NAT
by raviprakash sunkara 23 Mar '07

23 Mar '07

Hello Users openSER is sip proxy and registrar , Asterisk is as PBX, Conference and Voicemail servers, openSER and Asterisk are in the Same N/w Where As the UAC are in Behind the NAT, When Astetrisk is not integrated , UAC are in Behind the NAT is working, openSER is 192.168.2.5 Asterisk is 192.168.2.6 I'm just use rewritehost to asterisk server, UAC ----> openSER - - - -> Asterisk (voicemail sserver ). Please help me -- Thanks and Regards Ravi Prakash Sunkara ravi.sunkara(a)hyperion-tech.com M:+91 9985077535 www.hyperion-tech.com Client and Parent company :- www.august-networks.com

1 0

[Users] OpenSER crashes when attempting to use null avp variable
by Asterisk Expert 23 Mar '07

23 Mar '07

Hello, I'm using openser 1.2.0. I have following section in my openser.cfg. avp_db_query("SELECT active, accountcode FROM openser_ip_auth WHERE ip_addr='$src_ip'","$avp(s:active);$avp(s:accountcode)"); xlog("L_INFO", "\n$avp(s:active):::$avp(s:accountcode)\n"); if (!avp_check("$avp(s:active)","eq/1/I")) { xlog("L_ERR", "$si [$Tf]: $rm $fu -> $ru: REGISTER: bad credentials, ask for credentials\n"); #authentication failed www_challenge("", "0"); setflag(1); return; } Basically I'm doing IP based authentication. I have used the similar method in version 1.1 but openser 1.2.0 crashes if the query in avp_db_query returns no rows which keeps those two avp variables null. Is this a bug or I'm doing something wrong? I also tried "==" operator for comparison but it crashes whenever it is trying to access one of those two variables. -- Regards Ruchir Brahmbhatt Ecosmob Technologies

2 1

[Users] are there sites that use OpenSER server?
by 김형선 23 Mar '07

23 Mar '07

Hello. Are there sites that use OpenSER server? Like 'iptel.org' (don't care commercial site or not) thanks. 새로운 기부문화의 씨앗, 해피빈

4 3

[Serusers] (no subject)
by KUMAR 23 Mar '07

23 Mar '07

thank you, that was helpful. kumar

1 0

[Serusers] Sip Softphone
by Jai Rangi 23 Mar '07

23 Mar '07

Hello, We are looking for a sip based softphone that can be customized according to our need. Something like Skype, so that use have to enter only username and password. If it can be open source that will be great. If not we can also pay some one who can do that for us. Please let me know if any one can do this or suggest me where to find that. Thank you, -JP

4 3

[Users] openser1.2.0+diameter
by 赵俊杰 23 Mar '07

23 Mar '07

Hello,ereryone I want to use diameter for sip accounting under ipv6.But I don't know how to configure it .Who can give me some suggestion? Thank you very much.My sip server is openser 1.2.0. Zhao Junjie 2007-03-22

2 1

[Serusers] groups
by KUMAR 23 Mar '07

23 Mar '07

yes, i was talking about the 'group' module. I still see it in 0.9.6. Moreover, there's even a table 'grp' in the ser database. Even if it has been removed now, i would like to know what it is/was used for. thank you kumar

2 1

[Serusers] Groups
by KUMAR 23 Mar '07

23 Mar '07

can you please tell me or point me to a link as to what are groups used for in SER. thank you kumar

2 1

[Serusers] INFO: Prague User Group Meetings Presentations Now Available
by Greger V. Teigre 23 Mar '07

23 Mar '07

To all of you who participated in the Prague User Group meetings on Monday and Wednesday: It was great to meet you, get a face behind the the name, and thanks for all the good discussions we had! There were people I didn't have the chance to talk to, I'm sure we get the opportunity another time :-) To those of you who did not have the possibility to attend: The presentations from Monday can be found on iptel.org in PDF format, together with a brief summary. http://www.iptel.org/ser/usergroup/prague/summary The Wednesday meeting was available as an mp3 stream and many people listened in and participated on IRC. http://www.iptel.org/ser_workshop The full workshop will soon be made available, as well as a summary of the conclusions and most important topic. A separate announcement will be made when available. g-)

2 1

[Serusers] SIP Accounting Module problem
by POON Ben 23 Mar '07

23 Mar '07

Hi folks, I'm trying to get my accounting services working, but am having trouble doing so... I am using the sample ser.cfg file, and am having a problem loading the acc.so module. In the ser.cfg file, I try added the line: loadmodule "/usr/sfw/lib/ser/modules/acc.so" to the bottom of the loadmodule section. I haven't done any modparam or scripting yet, even so, when I restart the ser service, I get: Starting SER : cat: cannot open /var/run/ser.pid. If I comment or remove the loadmodule line, ser will load again. Is there anything else I need to add or configure before loading this module? I went to /usr/sfw/lib/ser/modules to make sure acc.so is there, and it is. Any help is greatly appreciated. Thank you very much. Ben

3 7

[Users] OpenSER not sending responses to IP in via header
by Tim Madorma 23 Mar '07

23 Mar '07

Hi, I have an OpenSER behind a BIG IP load balancer. The scenario is as follows: 1) The UAC will initiate the call with an INVITE that has the REQ URI set to the IP of the BIG IP. 2) The OpenSER has an alias configured for the IP address of the BIG IP so it receives the incoming INVITE, but when it sends a 100 response, it does not send it to the UAC address that is specified in the VIA header, rather it sends it to the source IP (which is the IP of the BIG IP load balancer). This is undesirable. 3) After the UAS receives the proxied INVITE, it responds with a 100, then answers with a 200. 4) When the OpenSER receives the 100, it forwards this back to the BIG IP load balancer! First, I am surprised that it fowards a 100 at all, and second it is undesirable to send any responses to the BIG IP load balancer since the via header indicates the IP of the UAC. 5) When the OpenSER receives the 200, it forwards it back to the BIG IP also.. again, I don't know why it isn't sending to the IP address of the via - which is that of the UAC. Any suggestions would be most helpful. Here are my related openser.cfg settings: # LOCAL IP ADDRESS AND PORTS listen=65.185.232.62:5061 listen=65.185.232.62:5062 listen=65.185.232.62:5063 # IP ADDRESS AND PORTS OF THE BIG IP LOAD BALANCER alias=65.185.233.104:5061 alias=65.185.233.104:5062 alias=65.185.233.104:5063 thanks, Tim

3 3

[Serusers] group info
by KUMAR 23 Mar '07

23 Mar '07

Hi, I want to store the buddylist from the client application on the SER. How do i go about it. I guess, i can do it using the groups but cant' really find any resources to do the studying part. Can you please point me as to where i can find the information regarding this.?? thank you kumar

2 1

[Users] OpenSER sometimes forwarding 100 response
by Tim Madorma 23 Mar '07

23 Mar '07

Hi, I'm using version 1.2 of OpenSER. After proxying an INVITE from a UAC to a UAS, the UAS replies with a 100 Trying. *Sometimes* the OpenSER forwards this 100 Trying to the UAC. Any idea how to disable this? I think this can be done using onreply_route, but it seems that a received 100 should not be forwarded by default. thanks, Tim

2 1

[Users] reason of interlocking with Asterisk server
by 김형선 23 Mar '07

23 Mar '07

Hello. I think that some sites use OpenSER with Asterisk server. But Why? (for accounting? or supplementary service?) Aren't they same? In conceptionally, OpenSER is central VoIP server, and Asterisk is IP-PBX for apart site. right? What is the structure of service being applied, in generally? OpenSER, Asterisk,... What is the role of them? thank you. 새로운 기부문화의 씨앗, 해피빈

2 1

[Users] Openser + postgres not starting
by Knight Tiger 23 Mar '07

23 Mar '07

Hi I have installed Openser v 1.2 no tls. I have Postgres version 8.0.7. I tried openser start [root@openser /usr/local/lib]# openser start ERROR: bad config file (1 errors) [root@openser /usr/local/lib]# openser -c 0(29611) ERROR: load_module: could not open module </usr/local/lib/openser/modules/postgres.so>: /usr/local/lib/openser/modules/postgres.so: Undefined symbol "PQescapeStringConn" 0(29611) parse error (41,13-14): failed to load module ERROR: bad config file (1 errors) 0(29611) INFO:mi_fifo:mi_destroy:memory for the child's mi_fifo_pid was not allocated -> nothing to destroy I then ran openserctl moni cycle #1, if constant make sure server lives My openser.cfg file # ----------- global configuration parameters ------------------------ debug=3 # debug level (cmd line: -dddddddddd) fork=yes log_stderror=no # (cmd line: -E) children=4 # Uncomment these lines to enter debugging mode #fork=no #log_stderror=yes # port=5060 # uncomment the following lines for TLS support #disable_tls = 0 #listen = tls:your_IP:5061 #tls_verify_server = 1 #tls_verify_client = 1 #tls_require_client_certificate = 0 #tls_method = TLSv1 #tls_certificate = "/usr/local/etc/openser/tls/user/user-cert.pem" #tls_private_key = "/usr/local/etc/openser/tls/user/user-privkey.pem" #tls_ca_list = "/usr/local/etc/openser/tls/user/user-calist.pem" # ------------------ module loading ---------------------------------- #set module path mpath="/usr/local/lib/openser/modules/" # Uncomment this if you want to use SQL database #loadmodule "mysql.so" loadmodule "postgres.so" loadmodule "sl.so" loadmodule "tm.so" loadmodule "rr.so" loadmodule "maxfwd.so" loadmodule "usrloc.so" loadmodule "registrar.so" loadmodule "textops.so" loadmodule "mi_fifo.so" # Uncomment this if you want digest authentication # mysql.so must be loaded ! #loadmodule "auth.so" #loadmodule "auth_db.so" # ----------------- setting module-specific parameters --------------- # -- mi_fifo params -- modparam("mi_fifo", "fifo_name", "/tmp/openser_fifo") # -- usrloc params -- modparam("usrloc", "db_mode", 0) # Uncomment this if you want to use SQL database # for persistent storage and comment the previous line modparam("usrloc", "db_mode", 2) # -- auth params -- # Uncomment if you are using auth module # #modparam("auth_db", "calculate_ha1", yes) # # If you set "calculate_ha1" parameter to yes (which true in this config), # uncomment also the following parameter) # #modparam("auth_db", "password_column", "password") # -- rr params -- # add value to ;lr param to make some broken UAs happy modparam("rr", "enable_full_lr", 1) ...... .... I checked for the PQescapeStringConn and found this www.mail-archive.com/devel@openser.org.msg05182.html but I could not make anything out of it I dont want authentication just yet. Can anyone tell me what is wrong ? Thanks in advance Caugar

3 3

[Users] an example of xcap_table entry?
by jh＠tutpro.com 22 Mar '07

22 Mar '07

is there somewhere an example off xcap_table entry that would show who is allowed to subscribe the presence of an AoR? -- juha

3 2

[Users] OpenSER performance tests
by Bogdan-Andrei Iancu 22 Mar '07

22 Mar '07

Hi everybody, based on the newly 1.2.0 OpenSER release, we ran some tests in order to give some realistic numbers about the performances of OpenSER. I think it is a very useful information for our community or other interested people. For more, please refer to the news bulletin: http://www.openser.org/mos/view/News/NewsItem/OpenSER-1.2.0---Perfomance-Te… or directly to the tests results web page: http://www.openser.org/docs/openser-performance-tests/ regards, bogdan

6 11

[Serusers] ACK for non-2XX not record-routed
by Emmanuel Hislen 22 Mar '07

22 Mar '07

Hi, I've been using SER (0.9.6) as a Proxy doing Loose Routing between 2 endpoints. If I place a call I can see how the ACK for the 2XX response to the INVITE is properly handled (Route header removed, Record-Route inserted). Now with the call still up, I do a re-INVITE which is rejected with a 415. The re-INVITE request sent by UAC contained a Route header, as it was an in-dialog request in a record-routed dialog. Now as per RFC3261 section 17.1.1.3: If the INVITE request whose response is being acknowledged had Route header fields, those header fields MUST appear in the ACK. This is to ensure that the ACK can be routed properly through any downstream stateless proxies. My UAC complied with the above, but SER seemed to choke on this: whereas the ACK for 2XX was successfully routed by SER in the original INVITE, the ACK for non-2XX (looking exactly the same: same Request URI, same IP destination, same Route header, ... different Via branch of course) is not handled properly: yes the ACK reaches UAS but it still has the Route header in it, and no Record-Route was added. And I'm guessing that if there had been another proxy in the Route Set on the way to the UAS it would have been bypassed. SER traces for ACK-2XX: > 0(13574) ===> Loose Routing logic... > 0(13574) parse_headers: flags=-1 > 0(13574) DEBUG: t_newtran: msg id=89 , global msg id=88 , T on entrance=0xffffffff > 0(13574) parse_headers: flags=-1 > 0(13574) parse_headers: flags=60 > 0(13574) t_lookup_request: start searching: hash=41794, isACK=1 > 0(13574) parse_headers: flags=28 > 0(13574) DEBUG: t_lookup_request: e2e proxy ACK found > 0(13574) parse_headers: flags=4 > 0(13574) DEBUG: totag for e2e ACK found: 0 > 0(13574) SER: forwarding ACK statelessly SER traces for ACK-non-2XX: > 0(13574) ===> Loose Routing logic... > 0(13574) parse_headers: flags=-1 > 0(13574) DEBUG: t_newtran: msg id=92 , global msg id=91 , T on entrance=0xffffffff > 0(13574) parse_headers: flags=-1 > 0(13574) parse_headers: flags=60 > 0(13574) t_lookup_request: start searching: hash=41807, isACK=1 > 0(13574) DEBUG: RFC3261 transaction matched, tid=007d7195499e33a1 > 0(13574) DEBUG: t_lookup_request: transaction found (T=0xb616ae48) > 0(13574) DEBUG: cleanup_uac_timers: RETR/FR timers reset > 0(13574) DEBUG: add_to_tail_of_timer[2]: 0xb616ae90 > 0(13574) DEBUG:destroy_avp_list: destroying list (nil) > 0(13574) receive_msg: cleaning up This doesn't seem right, am I missing something here? Thanks, Emmanuel.

3 5

Re: [Users] To: header in e.164 format - adding a plus
by Daryl Sanders 22 Mar '07

22 Mar '07

I'd love to use uac_replace_to(), but to my knowledge it does not exist. I read through the UAC module docs and there is no mention of it. Any other posibilities? If I were to use subst(), can it be applied it in such a way that it does not cause problems with the dialog? - Daryl On 3/21/07, Alan Crosswell <alan(a)columbia.edu> wrote: > Let me guess -- Level 3? They're the only ones that make that bogus > requirement AFAIK. And, the subst() is of course wrong, you need to do > uac_replace_to() or break the dialog otherwise.... > /a > > Daryl Sanders wrote: > > One of my providers requires the To: header to be in e.164 format with > > a "+" in front of it. Since there is no uac_replace_to() function yet, > > what are my options for adding this plus symbol? > > > > Before anyone suggests it... I cannot just use another provider. I > > must find a solution to add the plus symbol. > > > > Thanks, > > Daryl > > > > _______________________________________________ > > Users mailing list > > Users(a)openser.org > > http://openser.org/cgi-bin/mailman/listinfo/users >

3 3

[Users] SUBSCRIBE/NOTIFY problem
by Vadim Berezniker 22 Mar '07

22 Mar '07

The setup is: Polycom 601 => OpenSER => Asterisk The SUBSCRIBE from the phone reaches asterisk just fine and the OK is returned properly to the phone. The NOTIFY messages don't get to the phone, however. SER sends it to the requested URI (which is phone@ser), which ends up being relayed back to Asterisk.

1 1

[Users] parameter of route(n)
by jh＠tutpro.com 22 Mar '07

22 Mar '07

is it so that currently parameter n of call route(n) needs to be an integer constant, i.e., that use of a pseudo variable is not possible? -- juha

4 8

[Users] dispatcher, failure route and force_send_socket problem
by Klaus Darilion 22 Mar '07

22 Mar '07

Hi! Once again I have a problem with force_send_socket and branches in failure route. Scenario: normal route block --> call SIP client after timeout --> failure route in failure route send to gateway via dispatcher module The gateway accepts signaling only from a certain port, thus I have to use force_send_socket. The problem is, that if I call force_send_socket() in failure route, it sets the send_Socket for branches[0]. Thus if I call force_Send_socket before ds_select_domain it sets branches[0], but the sendsocket is not copied into the new branch when ds_select_domain internally calls append_branch. With version 1.1 I can use the ugly workaround to manually call append_branch too, as this copies another branch and also copies the sendsocket. Then I have 2 new branches where branches[1] gets dropped by teh firewall (wrong sendseocket) but branches[2] succeeds. But with version 1.2 the sendsocket is never copied from branches[0] and I can't set it manually for a certain branch. Are there any workarounds (for version 1.1. and 1.2) thanks klaus version 1.1: -- Klaus Darilion nic.at

1 1

[Users] [user] openser TLS and eyebeam
by Bodin Bruno 22 Mar '07

22 Mar '07

I made certificat, I add user folder to openser ser config (with lines it must) and I add certificat in Internet explorer for client. But eyebeam say certificat failed. Anyone have experience with eyebeam and tls ? thank.

2 1

[Users] OpenSer Asterisk
by Michael Chan 22 Mar '07

22 Mar '07

Hi, OpenSer Support, I read the OpenSer and Asterisk real time intergation and follow the config instruction but still no result that we can make PSTN call through Asterisk without using the name and PW of OpenSer on the UA Sip Client (X-lite). On the Asterisk side, we assigned a user name and PW to OpenSer, but not sure where we can create script on OpenSer side that allow all calls to Asterisk without using the shared secret name and PW of OpenSer. Please any help will be grateful. MC -------------------------------------------------------------------------------- I am using the free version of SPAMfighter for private users. It has removed 234 spam emails to date. Paying users do not have this message in their emails. Try SPAMfighter for free now!

2 1

RE: [Serusers] re: composing SIP messages
by Goh, Tee-Yong 22 Mar '07

22 Mar '07

Hi Greger, Thank you for sharing the information. May i know which part of the program in the SER can i find FIFO? Please advice. Thanks. Regards, Howard -----Original Message----- From: serusers-bounces(a)lists.iptel.org [mailto:serusers-bounces@lists.iptel.org]On Behalf Of Greger V. Teigre Sent: Thursday, March 22, 2007 3:10 PM To: Jignesh Gandhi Cc: serusers(a)lists.iptel.org Subject: Re: [Serusers] re: composing SIP messages No, but there is a FIFO interface that allows inserting messages into SER. For anything but trivial cases, you will probably want to do it from SEMS. g-) Jignesh Gandhi wrote: Is there a way to compose SIP messages such as INVITE from scratch using SER ? I am new to SER... So any help would be appreciated thanks, -- Jignesh Gandhi jigpgandhi(a)gmail.com _____ _______________________________________________ Serusers mailing list Serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers This email (including any attachment) is subject to the following disclaimer: http://m1.com.sg/M1/misc/disclaimer

1 0

[Serusers] re: composing SIP messages
by Jignesh Gandhi 22 Mar '07

22 Mar '07

Is there a way to compose SIP messages such as INVITE from scratch using SER ? I am new to SER... So any help would be appreciated thanks, -- Jignesh Gandhi jigpgandhi(a)gmail.com

2 1

[Users] Compiling Openser for best performance on Solaris SPARC
by Sergio Gutierrez 21 Mar '07

21 Mar '07

Hi. Currently I am installing Openser 1.2.0 on a Sun Fire T2000 running Solaris 10. Although I used an optimized version of GCC for SPARC Systems, and used the recommended settings to generate accurate code for my Processor (UltraSPARC T1), the results of the performance tests are just 50% of the presented ones on the web page. My setup is the following: Proxy and UAS: Sun Fire T2000, 8 GB RAM, 1 UltraSPARC T1 1.2 GHZ 6 Core. UAC's: Two domain of a Sun Fire 12K, 4 GB RAM, 4 UlraSPARC III+ 900 Mhz Software versions listed as on the webpage. openser -V output: version: openser 1.2.0-notls (sparc/solaris) flags: STATS: Off, USE_IPV6, USE_TCP, DISABLE_NAGLE, USE_MCAST, SHM_MEM, SHM_MMAP, PKG_MALLOC, F_MALLOC, FAST_LOCK-ADAPTIVE_WAIT-NOSMP ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535 poll method support: poll, select, /dev/poll. svnrevision: unknown @(#) $Id: main.c 1827 2007-03-12 15:22:53Z bogdan_iancu $ main.c compiled on 21:43:51 Mar 19 2007 with gcc 4.0.3 I would thank any idea about how could I improve the performnace of my setup. I think that because of the hardware specifications, the result should be at least equal than listed. Thanks in advance. Kind regards. Sergio Gutiérrez.

2 7

[Serusers] Acc not writing to MySQL
by POON Ben 21 Mar '07

21 Mar '07

Hi all, I am having a lot of trouble making the acc module work... I've googled and tried a lot of sample config but am still having no luck. Can someone please help me to get accounting on my server? Below is my ser.cfg file. It's basically the sample one with some editing. The auth stuff work really nicely :) Everything seems to load fine when I do a "ser -D -E" However, I noticed that nothing is ever entered into the acc table in the ser database. I am running ser 0.9.6 with mysql 5.0.37. Thank you so much! Ben # # $Id: ser.cfg,v 1.25.2.1 2005/02/18 14:30:44 andrei Exp $ # # simple quick-start config script # # ----------- global configuration parameters ------------------------ #debug=3 # debug level (cmd line: -dddddddddd) fork=yes #log_stderror=no # (cmd line: -E) listen=1.1.1.1 listen=127.0.0.1 # hostname matching an alias will satisfy the condition uri==myself". alias="localhost" alias=1.1.1.1 /* Uncomment these lines to enter debugging mode fork=no log_stderror=yes */ check_via=no # (cmd. line: -v) dns=no # (cmd. line: -r) rev_dns=no # (cmd. line: -R) #port=5060 #children=4 fifo="/tmp/ser_fifo" fifo_db_url="mysql://admin:heslo@localhost/ser" # ------------------ module loading ---------------------------------- # Uncomment this if you want to use SQL database loadmodule "/usr/local/lib/ser/modules/mysql.so" loadmodule "/usr/local/lib/ser/modules/sl.so" loadmodule "/usr/local/lib/ser/modules/tm.so" loadmodule "/usr/local/lib/ser/modules/rr.so" loadmodule "/usr/local/lib/ser/modules/maxfwd.so" loadmodule "/usr/local/lib/ser/modules/usrloc.so" loadmodule "/usr/local/lib/ser/modules/registrar.so" loadmodule "/usr/local/lib/ser/modules/textops.so" loadmodule "/usr/local/lib/ser/modules/acc.so" # Uncomment this if you want digest authentication # mysql.so must be loaded ! loadmodule "/usr/local/lib/ser/modules/auth.so" loadmodule "/usr/local/lib/ser/modules/auth_db.so" # ----------------- setting module-specific parameters --------------- # -- usrloc params -- #modparam("usrloc", "db_mode", 0) # Uncomment this if you want to use SQL database # for persistent storage and comment the previous line modparam("usrloc", "db_mode", 2) # -- auth params -- # Uncomment if you are using auth module # modparam("auth_db", "calculate_ha1", yes) # # If you set "calculate_ha1" parameter to yes (which true in this config), # uncomment also the following parameter) # modparam("auth_db", "password_column", "password") # -- rr params -- # add value to ;lr param to make some broken UAs happy modparam("rr", "enable_full_lr", 1) # -- acc params -- # set the reporting log level modparam("acc", "log_level", 1) # number of flag, which will be used for accounting; if a message is # labeled with this flag, its completion status will be reported modparam("acc", "log_flag", 1) modparam("acc", "log_missed_flag", 2) # ------------------------- request routing logic ------------------- # main routing logic route{ # initial sanity checks -- messages with # max_forwards==0, or excessively long requests if (!mf_process_maxfwd_header("10")) { sl_send_reply("483","Too Many Hops"); break; }; if (msg:len >= 2048 ) { sl_send_reply("513", "Message too big"); break; }; # we record-route all messages -- to make sure that # subsequent messages will go through our proxy; that's # particularly good if upstream and downstream entities # use different transport protocol if (!method=="REGISTER") record_route(); # subsequent messages withing a dialog should take the # path determined by record-routing if (loose_route()) { # mark routing logic in request append_hf("P-hint: rr-enforced\r\n"); route(1); break; }; if (!uri==myself) { # mark routing logic in request append_hf("P-hint: outbound\r\n"); route(1); break; }; # if the request is for other domain use UsrLoc # (in case, it does not work, use the following command # with proper names and addresses in it) if (uri==myself) { if (method=="REGISTER") { # Uncomment this if you want to use digest authentication if (!www_authorize("localhost", "subscriber")) { www_challenge("localhost", "0"); break; }; save("location"); break; }; lookup("aliases"); if (!uri==myself) { append_hf("P-hint: outbound alias\r\n"); route(1); break; }; # native SIP destinations are handled using our USRLOC DB if (!lookup("location")) { sl_send_reply("404", "Not Found"); break; }; }; # Report missed calls setflag(2); append_hf("P-hint: usrloc applied\r\n"); route(1); } route[1] { # Set accounting flag setflag(1); # send it out now; use stateful forwarding as it works reliably # even for UDP2TCP if (!t_relay()) { sl_reply_error(); }; }

1 0

[Users] To: header in e.164 format - adding a plus
by Daryl Sanders 21 Mar '07

21 Mar '07

One of my providers requires the To: header to be in e.164 format with a "+" in front of it. Since there is no uac_replace_to() function yet, what are my options for adding this plus symbol? Before anyone suggests it... I cannot just use another provider. I must find a solution to add the plus symbol. Thanks, Daryl

3 2

[Users] Fresh OpenSER 1.2.0 Openserctl can only add 1 user?!
by Geir O. Jensen 21 Mar '07

21 Mar '07

I have two server, one in production and one for testing. Trying to debug something else entirely I upgraded the production server from 1.1.0 to 1.2.0 yesterday. Everything seems to work fine on it. So I wiped my testbed and compiled OpenSER 1.2.0 on the testing system, installed the mysql db and started it up. Worked fine. I then began adding testaccounts on the testsystem, - first user ok... - second user, not so ok... # openserctl add test test gojensen(a)uninett.no MySql password for user 'xxx@localhost': ERROR 1062 (23000) at line 1: Duplicate entry '' for key 3 ERROR: introducing the new user 'test' to the database failed Of course, I couldn't add a third or fourth either, so I'm basically stuck with one user and the admin account. Any idea where to start debugging this?! (As a note, I added 3 test accounts on the production server with no problems... Their config files are basically identical - the testing server only adds the presence module...) // sip:gojensen@uninett.no | h323: 004710012 pstn: +47 73 55 79 23 | fax: +47 73 55 79 01

2 2

[Users] Wesip C2C
by Helmut Kuper 21 Mar '07

21 Mar '07

Hello, after upgrading to wesip 0.1.3 I'm not able anymore to start c2c application. in WeSIP's logfile I can find this exception: 2007-03-21 18:11:52 StandardManager[/click2call-08_11_06]: Seeding random number generator class java.security.SecureRandom 2007-03-21 18:11:52 StandardManager[/click2call-08_11_06]: Seeding of random number generator has been completed 2007-03-21 18:11:52 HTMLManager: ManagerServlet.install[/click2call-08_11_06] java.lang.NoClassDefFoundError: com/voztele/wesip/apps/click2call/C2CDefaultServlet at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(Unknown Source) at java.security.SecureClassLoader.defineClass(Unknown Source) at java.net.URLClassLoader.defineClass(Unknown Source) at java.net.URLClassLoader.access$100(Unknown Source) at java.net.URLClassLoader$1.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1379) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1307) at com.voztele.sipservlet.core.StandardSipWrapper.loadServlet(StandardSipWrapper.java:753) at com.voztele.sipservlet.core.StandardSipWrapper.load(StandardSipWrapper.java:701) at org.apache.catalina.core.StandardHttpContext.loadOnStartup(StandardHttpContext.java:3382) at org.apache.catalina.core.StandardHttpContext.start(StandardHttpContext.java:3605) at com.voztele.sipservlet.core.ConvergedContext.start(ConvergedContext.java:259) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:773) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:759) at org.apache.catalina.core.StandardHttpHost.addChild(StandardHttpHost.java:552) at com.voztele.sipservlet.core.ConvergedHost.addChild(ConvergedHost.java:157) at com.voztele.sipservlet.core.ConvergedHostDeployer.install(ConvergedHostDeployer.java:264) at com.voztele.sipservlet.core.ConvergedHost.install(ConvergedHost.java:170) at org.apache.catalina.servlets.ManagerServlet.install(ManagerServlet.java:663) at org.apache.catalina.servlets.HTMLManagerServlet.install(HTMLManagerServlet.java:265) at org.apache.catalina.servlets.HTMLManagerServlet.doPost(HTMLManagerServlet.java:245) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:200) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:146) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:206) #################################################################################### When I cwitch back to wesip 0.1.2 C2C is loading and starting fine. I use click2call-08_11_06 When I search for the missed class C2CDefaultServlet I get this: hk@vm-en-test0:~/wesip/wesip$ find . -name "C2CDefaultServlet*" ./wesipapps/click2call-08_11_06/WEB-INF/classes/com/voztele/wesip/apps/click2call/C2CDefaultServlet.class So it#s there, but wesip doesn#t find it. Wher do I have to tell weSIP the location of that class ? regards helmut

1 0

Re: [Users] NAT Problem with OpenSER behind load balancer
by Daniel-Constantin Mierla 21 Mar '07

21 Mar '07

You should keep cc-ing mailing lists, so people coming after a while, with same issue, will be reading mail thread and see that the given solution was right. Thanks, Daniel On 03/20/07 21:42, Tim Madorma wrote: > Got it. thanks so much! > > Tim > > On 3/20/07, Daniel-Constantin Mierla <daniel(a)voice-system.ro> wrote: >> Hello, >> >> On 03/20/07 17:39, Tim Madorma wrote: >> > Hi, >> > >> > I have put the OpenSER version 1.2 behind a BIG IP load balancer which >> > provides a static private IP address (10.1.1.20) via NAT to the >> > OpenSER. In our application, the clients will send to one of the three >> > public addresses that are defined as aliases: >> > >> > alias="65.185.232.62:5061" >> > alias="65.185.232.62:5062" >> > alias="65.185.232.62:5063" >> you have to remove quotes around the value of alias parameters. As it is >> now, the value between quotes is considered to be hostname. >> alias=65.185.232.62:5061 >> alias=65.185.232.62:5062 >> alias=65.185.232.62:5063 >> >> Same case as it was reported by Juha, today with loose routing ... >> >> Cheers, >> Daniel >> >> > >> > An incoming OPTIONS message is received with the host in the REQ URI >> > set to 65.185.232.62:5063 is received and when it hits this section of >> > openser.cfg: >> > >> > if (!uri==myself) { >> > # mark routing logic in request >> > append_hf("P-hint: outbound\r\n"); >> > route(1); >> > }; >> > >> > it executes within the if conditional and tries to route the OPTIONS >> > message. I am wondering why uri does not match myself. The debug >> > output from the log is as follows (it seems that the alias assignments >> > are not working): >> > >> > >> > Mar 19 16:41:11 homer openser[2267]: [ID 487083 local0.debug] >> > grep_sock_info - checking if host==us: 13==9 && [65.185.232.62] == [1 >> > 0.1.1.20] >> > Mar 19 16:41:11 homer openser[2267]: [ID 375670 local0.debug] >> > grep_sock_info - checking if port 5061 matches port 5063 >> > Mar 19 16:41:11 homer openser[2267]: [ID 487083 local0.debug] >> > grep_sock_info - checking if host==us: 13==9 && [65.185.232.62] == [1 >> > 0.1.1.20] >> > Mar 19 16:41:11 homer openser[2267]: [ID 375670 local0.debug] >> > grep_sock_info - checking if port 5062 matches port 5063 >> > Mar 19 16:41:11 homer openser[2267]: [ID 487083 local0.debug] >> > grep_sock_info - checking if host==us: 13==9 && [65.185.232.62] == [1 >> > 0.1.1.20] >> > Mar 19 16:41:11 homer openser[2267]: [ID 375670 local0.debug] >> > grep_sock_info - checking if port 5063 matches port 5063 >> > Mar 19 16:41:11 homer openser[2267]: [ID 140248 local0.debug] >> > DEBUG:check_self: host != me >> > >> > >> > Any suggestions? I have not tried this in any other version. Is this a >> > possible bug in 1.2? >> > >> > thanks, >> > Tim >> > >> > _______________________________________________ >> > Users mailing list >> > Users(a)openser.org >> > http://openser.org/cgi-bin/mailman/listinfo/users >> > >> >

3 3

[Users] ENC: Presence Module - Eyebeam 1.5
by Hildebrando Trannin 21 Mar '07

21 Mar '07

Hi all, I configured the presence module in OpenSER v1.2 and it looks like ok. But when tested with EyeBeam 1.5 (buil 30037) it doesn't work. I used the WireShark to see the SIP messages and observed that in NOTIFY messages there aren't PIDF document, neither message body. Furthermore, OpenSER didn't parse xml BODY from PRESENTITY table when try to build notify. The PIDF document that EyeBeam creates and the error that OpenSER gave me when try to parser this document are below. Can someone help me with this problem? Is it a bug from OpenSER? Regards, Hildebrando PIDF Document <?xml version="1.0" encoding="UTF-8" standalone="no" ?> <pr:presence xmlns:pr="urn:ietf:params:xml:ns:pidf" entity="sip:hildebrando@voip.maritaca" xmlns:caps="urn:ietf:params:xml:ns:pidf:caps" xmlns:cipid="urn:ietf:params:xml:ns:pidf:cipid" xmlns:counterpath="www.counterpath.com/presence/ext" xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model" xmlns:rpid="urn:ietf:params:xml:ns:pidf:rpid"> <pr:tuple id="se43ac217"> <pr:status> <pr:basic>open</pr:basic> </pr:status> <pr:note>Busy</pr:note> <rpid:user-input last-input="2007-03-19T19:21:49Z">active</rpid:user-input> <pr:timestamp>2007-03-19T19:21:49Z</pr:timestamp> </pr:tuple> <dm:person id="p0d4e4429"> <rpid:activities> <rpid:busy/> </rpid:activities> <dm:note>Busy</dm:note> </dm:person> </pr:presence> OpenSER Error 2(6498) Chegou um PUBLISH de (hildebrando) para (sip:hildebrando@voip.maritaca) 2(6498) PRESENCE:update_presentity: querying presentity 2(6498) PRESENCE:get_subs_dialog:querying database table = active_watchers 2(6498) PRESENCE:get_p_notify_body: querying presentity 2(6498) PRESENCE:agregate_xmls: ERROR while parsing xml body message 2(6498) PRESENCE:notify:dialog informations: 2(6498) [p_user]= hildebrando [p_domain]= voip.maritaca [w_user]= gustavo [w_domain]= voip.maritaca 2(6498) [event]= presence [staus]= active [expires]= 3340 2(6498) [to_tag]= 10.6503.1174328485.15 [from_tag]= 80746145

3 5

[Users] xmpp module
by Sebastian Murray-Roberts 21 Mar '07

21 Mar '07

Hi, I just have a question about the new xmpp module. I have set up an OpenSER box as a presence server using the presence module, and everything is working fine, messaging and presence. Now I would like to allow those users to communicate with users logged into a jabber server. My first question is can presence information be exchanged between OpenSER and the jabber server? If so, how is this achieved since the xmpp module only has an xmpp_send_message() method. Also, just to make sure I understand how the module works, would this be a correct summary of the module's functionality for a SIP to Jabber message with a response: User A registers with OpenSER. User B registers with jabber server (OpenFire) User A sends a message to sip:User B*<jabber_domain>@<gateway_domain> with from details : sip:User A*<openser_domain>@<gateway_domain> OpenSER forwards the request to the gateway Gateway translates the message and sends it to the jabber server Jabber server delivers message to User B Jabber server sends response to gateway with to details: User A*<openser_domain>@<gateway_domain> Gateway forwards response to sip:User A@<openser_domain> Is that more or less correct, or am I off the mark? Finally, if that is the case, would User A need to be registered on the jabber server already? I've never worked with presence before, so I'm still trying to get to grips with it. Any comments/insights are much appreciated. Many thanks, Sebastian -- Sebastian Murray-Roberts (B.Sc Hons) Server Developer Yeigo Communications http://www.yeigo.com Tel: +27 21 409 7807 Fax: +27 21 409 7050 Mobile: +27 72 183 5998 CONFIDENTIALITY NOTICE: E-MAIL This e-mail is confidential. If you receive it by mistake, please delete it and notify the sender immediately. If you are not the intended recipient, you may not use, disclose, distribute, copy or publish any information contained herein.

2 1

[Users] Commercial SIP Server
by Michel Bensoussan 21 Mar '07

21 Mar '07

Hello Is there a way to know which commercial SIP servers are based on openser or ser? Or if a specific SIP server is based on openser or ser? Thanks. Regards, Michel.

3 5

答复: [Users] ERROR 1062 (23000): Duplicate entry
by 郭军 21 Mar '07

21 Mar '07

Why don't you use openserctl add ....to add new user? -----邮件原件----- 发件人: alper ozbilen [mailto:alperbilen@hotmail.com] 发送时间: 2007年3月21日 16:45 收件人: users(a)openser.org 主题: [Users] ERROR 1062 (23000): Duplicate entry Dear All, I can not insert a new subscriber from mysql console. When I look at subscireber table, ha1 & ha1b & and phplib_id fields looks null. So, i can only insert one new subscriber. When i attempt to insert second one, i get error written below: ERROR 1062 (23000): Duplicate entry '' for key 3 Note : My insert sentence like that: insert into subscriber (username, domain, password, email_address) values ("testuser","myfon.com","testpasswd","emailoftestuser(a)myfon.com"); I am confused about what i should to do to fix null statement of ha1 & ha2 & and phplib_id fields. on the other side, there is no probem to add new user through openserctl What was the problem? I will wait your kind suggestion. Regards, Alper Ozbilen _________________________________________________________________ Exercise your brain! Try Flexicon. http://games.msn.com/en/flexicon/default.htm?icid=flexicon_hmemailtaglinema… _______________________________________________ Users mailing list Users(a)openser.org http://openser.org/cgi-bin/mailman/listinfo/users

7 9

[Users] RHEL/Fedora equivalents of deb packages in RPM SPEC
by Alan Crosswell 21 Mar '07

21 Mar '07

The BuildPrereq lines in the RPM SPEC file for Fedora Core (openser.spec.fedora) supplied with 1.2.0 references debian names for the package (e.g. libxml2-dev -> libxml2-devel). Before I waste too much time finding the equivalent RHEL and/or Fedora Core packages that do the job, I thought I would ask her if anyone else has done so. If not, I'll make sure to submit patches for the SPECs once I figure them out. I am really looking to build on RHEL4 but clearly will need to grab some RPMs from Fedora Core.... Please no religious rants about Debian vs. RHEL vs. Fedora vs. SuSE and so on:-) /a

3 2

[Users] info-color of openserctl
by Andreas Granig 21 Mar '07

21 Mar '07

Hi, Could we please change the color of minfo from yellow to, say, orange in openserctl? It's impossible to read on a console with white background. Cheers, Andreas This e-mail is confidential and may well also be legally privileged. If you have received it in error, you are on notice of its status. Please notify us immediately by reply e-mail and then delete this message from your system. Please do not copy it or use it for any purposes, or disclose its contents to any other person: to do so could be a breach of confidence. Thank you for your cooperation. Information pursuant to paragraph 14 Austrian Companies Code: UPC Austria GmbH; Registered Office: Wolfganggasse 58-60, 1120 Vienna Company Register Number: FN 189858d at the Commercial Court of Vienna

2 1

[Users] domain module in 1.2
by Andreas Granig 21 Mar '07

21 Mar '07

Hi, In openser 1.1, when I use db_mode=0 (no caching) for domain module, I get this error: /usr/local/openser-1.1# ./sbin/openserctl domain show 500 command 'domain_dump' not available In openser 1.2, the first time I execute the command, I get nothing, the second time openserctl just hangs until I terminate it with ctrl-c: /usr/local/openser-1.2# ./sbin/openserctl domain show /usr/local/openser-1.2# ./sbin/openserctl domain show ./sbin/openserctl: line 83: /tmp/openser_fifo: Interrupted system call Terminated Same thing for "domain reload" btw. Cheers, Andreas This e-mail is confidential and may well also be legally privileged. If you have received it in error, you are on notice of its status. Please notify us immediately by reply e-mail and then delete this message from your system. Please do not copy it or use it for any purposes, or disclose its contents to any other person: to do so could be a breach of confidence. Thank you for your cooperation. Information pursuant to paragraph 14 Austrian Companies Code: UPC Austria GmbH; Registered Office: Wolfganggasse 58-60, 1120 Vienna Company Register Number: FN 189858d at the Commercial Court of Vienna

4 7

[Users] Only db_mode=0 works with dbtext loaction table in 1.2
by Daryl Sanders 21 Mar '07

21 Mar '07

When using db_mode=1,2 or 3 I get the following error when starting OpenSER 1.2 using dbtext as the usrloc DB. 1(23052) preload_udomain(): Error while doing db_query 1(23052) ERROR:ul:child_init(1): Error while preloading domain 'location' 1(23052) ERROR:init_mod_child: Error while initializing module usrloc, rank 1 I am wondering if their may be a problem with the columns in the location table file. I tried two different methods of creating the initial table files... 1.) sc.dbtext dbtext /usr/local/etc/openser/dbtext/ 2.) textdb.sh create /usr/local/etc/openser/dbtext/ The first method has problems with the version file that I tried to repair by trying to mimic the mysql table structure. The second method seems to work ok with the exception of the error I mentioned above when starting OpenSER. Any help would be greatly appreciated! Thanks, Daryl

4 10

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