sr-users

sr-users@lists.kamailio.org

1 participants
37563 discussions

Re: [Users] branch parameter in ACK set to zero?
by Bogdan-Andrei Iancu 31 May '07

31 May '07

Hi Tim, As I suspected, it is empty branch is triggered by a bogus SIP flow. The ACK generated by the caller device is bogus as the TO uri is different than the TO in INVITE. Also the caller device does use branch at all in VIA and forces openser to do pre-RFC3261 transaction matching with involves the TO uri. As the log show, the ACK does not match any transaction: DEBUG: t_lookup_request: start searching: hash=11223, isACK=1 DEBUG: proceeding to pre-RFC3261 transaction matching DEBUG: t_lookup_request: no transaction found So, the ACK is forwarded as stateless request - for this case, there is complicated alg for computing the branch param based on the branch params from the previous VIA headers. But the previous VIA is bogus (no branch at all) and openser finds itself in the impossibility to compute a branch for its VIA. regards, bogdan Tim Madorma wrote: > Hi Bogdan, > > Attached is the log and the openser.cfg file. > > thanks, > Tim > > On 5/30/07, Tim Madorma <tmadorma(a)gmail.com> wrote: >> Hi Bogdan, >> >> I have attached an html file that shows the call trace (note that the >> OpenSER is 65.185.232.62:5061in the flow). I will send the log file >> and openser.cfg in a separate email since it would put me over the 40K >> limit. >> >> thanks, >> Tim >> >> On 5/30/07, Bogdan-Andrei Iancu <bogdan(a)voice-system.ro> wrote: >> > Hi Tim, >> > >> > the VIA branch param must not be 0, indeed. Could you provide an >> network >> > trace for the entire call and the debug log for level 9? >> > >> > regards, >> > bogdan >> > >> > Tim Madorma wrote: >> > > Hi, >> > > >> > > In testing with OpenSER 1.2 I noticed that the branch parameter >> of the >> > > Via in the ACK to 200 OK has a value of zero. This does not seem >> > > right. From 16.6 of RFC-3261: >> > > >> > > The proxy MUST insert a Via header field value into the copy >> > > before the existing Via header field values. The >> construction >> > > of this value follows the same guidelines of Section >> 8.1.1.7. >> > > This implies that the proxy will compute its own branch >> > > parameter, which will be globally unique for that branch, >> and >> > > contain the requisite magic cookie. >> > > >> > > Please advise. >> > > >> > > thanks, >> > > Tim >> > > >> > > _______________________________________________ >> > > Users mailing list >> > > Users(a)openser.org >> > > http://openser.org/cgi-bin/mailman/listinfo/users >> > > >> > >> > >> >>

1 0

[Serusers] Ser in B2B UA Mode
by Gustavo Passos Tourinho 31 May '07

31 May '07

Hi, Can ser be used like a b2b ua? I mean, can it register in others proxies? Thank you. Regards, Gustavo

2 1

[Users] Replace destination URI (remove port 5062)
by Peter P GMX 31 May '07

31 May '07

I have set up an OpenSER to run on port 5062 instead of 5060. Attached to OpenSER I have 2 videoconferencing clients which communicate via SIP. What's working so far - internal client (registered on OpenSER) to another internal client (registered on OpenSER) - internal client (registered on OpenSER) to another external client - this all works with the OpenSER and other clients behind their NAT, as Mediaproxy is installed What is actually not working is - another external client connetcing to an internal client (registered on OpenSER) because I have to adress the the To:URI as sip.mydomain.com:5062. - Whenever an external INVITE comed in, it ends up with "message too big" because OpenSER is cycling through its routing plan until it adds that many via headers that the message increases 2kb. - what I see is that openser does not try to find the client on sip.mydomain.com, instead I feel that it tries to find the client on sip.mydomain.com:5062 as uri. - as my operating system (debian etch) cannot resolve this domain, this runs through the loop My question: - is the a way to modify the destinaton header ($tu) that the port is cut off (name@sip.mydomain.com:5062 ==> name(a)sip.mydomain.com)? Best regards peter

2 1

[Serusers] Call forward on no answer and busy failing
by Ranganath B 31 May '07

31 May '07

Hi, I could get the blind (unconditional) call forward option working with the configuration that is provided in the IPTEL website but using the same config file and the ideas provided I couldn't get the call forward on busy and no answer working. I get the following error in the /var/log/messages: May 16 15:49:52 localhost /usr/local/sbin/ser[17563]: ERROR: mk_proxy: could not resolve hostname: "ser.iptel.org" May 16 15:49:52 localhost /usr/local/sbin/ser[17563]: ERROR: uri2proxy: bad host name in URI <sip:1234@ser.iptel.org> May 16 15:49:52 localhost /usr/local/sbin/ser[17563]: ERROR: t_forward_nonack: failure to add branches May 16 15:49:52 localhost /usr/local/sbin/ser[17563]: ERROR: w_t_relay (failure mode): forwarding failed May 16 15:49:52 localhost /usr/local/sbin/ser[17563]: error: mediaproxy/sendMediaproxyCommand(): can't connect to MediaProxy May 16 15:49:52 localhost /usr/local/sbin/ser[17563]: ERROR: sl_reply_error used: I'm terribly sorry, server error occurred (1/SL) It would be of great help if anybody provide me input on how to resolve this issue or a configuration file using which I can get the call forward on busy and no response working. BTW, I am using the ser verison: 0.9.6. I have populated an entry for call forward no answer/busy in the mysql database for the table "usr_preferences". Thanks in advance. Regards, Ranganath B

3 4

[Users] what algorithm does radiusclient-ng+openser use?(md5 or)
by Jason Ma 30 May '07

30 May '07

Hi All, I'm configuring radius support on openser using radiusclient-ng-0.5.5.1.tar.gz,and the radius server is Lucent AAA server,everytime openser sent the request to AAA server,the AAA server could not parse the request,the logs on AAA server is as below.I noticed that the the server said it was "Unsupported algorithm",and the algorithm was null,I'm wandering what kind of algorithm does radiusclient-ng use?MD5 or HA1......... Please help ! Thanks in advance. ~~~~~~~~~~~~~~~~~~~~~~~ 2007/05/29 16:51:45.685 <engine.item.setup> Initializing Radius Item: 192.168.1.42:33345->0.0.0.0:1812(77) 0 <engine.item.setup> Using dictionary: draft-sterman-aaa-sip-01 0 <engine.item.setup> Request decode: User-Name = "21230001(a)192.168.1.42" Digest-Attributes = User-Name = "21230001" Digest-Attributes = Realm = "192.168.1.42" Digest-Attributes = Nonce = "465c49b766fa11f4a9db29977bf16857d3372780" Digest-Attributes = URI = "sip:192.168.1.42" Digest-Attributes = Method = "REGISTER" Digest-Response = "689a0f89cd73751f61b12d04f585a224" Service-Type = IAPP-Register Anonymous = v0-a208-3231323330303031 NAS-Port = 5060 NAS-IP-Address = 192.168.1.42 0 <engine.item.setup> User-Name parsed: Base-User-Name = "21230001", User-Realm = "192.168.1.42" 0 <engine.item.setup> Item setup complete 0 <engine.worker.1> <setup> ==> ReadUserFile.auth:readUserFile 0 <plugin.ReadUserFile.auth:readUserFile> searchValue = ' 21230001(a)192.168.1.42'. 0 <plugin.ReadUserFile.auth:readUserFile> Found entry: 21230001(a)192.168.1.42 0 <plugin.ReadUserFile.auth:readUserFile> Check items for found entry: User-Password = <hidden> Auth-Type = Local 0 <plugin.ReadUserFile.auth:readUserFile> Reply items for found entry: 0 <plugin.ReadUserFile.auth:readUserFile> SUCCESS -- Read User 21230001(a)192.168.1.42 0 <engine.worker.1> ReadUserFile.auth:readUserFile ==> AuthHttpDigest.auth:checkDigest by SUCCESS -- Read User 21230001(a)192.168.1.42 0 <plugin.AuthHttpDigest.auth:checkDigest> response = 689a0f89cd73751f61b12d04f585a224 0 <plugin.AuthHttpDigest.auth:checkDigest> realm = 192.168.1.42 0 <plugin.AuthHttpDigest.auth:checkDigest> nonce = 465c49b766fa11f4a9db29977bf16857d3372780 0 <plugin.AuthHttpDigest.auth:checkDigest> method = REGISTER 0 <plugin.AuthHttpDigest.auth:checkDigest> uri = sip:192.168.1.42 0 <plugin.AuthHttpDigest.auth:checkDigest> qop = 0 <plugin.AuthHttpDigest.auth:checkDigest> algorithm = 0 <plugin.AuthHttpDigest.auth:checkDigest> entityBodyHash = 0 <plugin.AuthHttpDigest.auth:checkDigest> cNonce = 0 <plugin.AuthHttpDigest.auth:checkDigest> nonceCount = 0 <plugin.AuthHttpDigest.auth:checkDigest> username = 21230001 0 <plugin.AuthHttpDigest.auth:checkDigest> ERROR -- Error generating HTTP digest: java.io.IOException: Unsupported algorithm: : java.io.IOException: Unsupported algorithm: 1 <engine.worker.1> AuthHttpDigest.auth:checkDigest ==> End-Of-Methods by ERROR -- Error generating HTTP digest: java.io.IOException: Unsupported algorithm: 1 <engine.worker.1> 21230001(a)192.168.1.42 login discarded due to Error generating HTTP digest: java.io.IOException: Unsupported algorithm: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

2 3

[Users] branch parameter in ACK set to zero?
by Tim Madorma 30 May '07

30 May '07

Hi, In testing with OpenSER 1.2 I noticed that the branch parameter of the Via in the ACK to 200 OK has a value of zero. This does not seem right. From 16.6 of RFC-3261: The proxy MUST insert a Via header field value into the copy before the existing Via header field values. The construction of this value follows the same guidelines of Section 8.1.1.7. This implies that the proxy will compute its own branch parameter, which will be globally unique for that branch, and contain the requisite magic cookie. Please advise. thanks, Tim

3 4

[Serusers] SER 2.0.0 RC 1 won't start on Fedora 6
by Umer Waqar 30 May '07

30 May '07

Hi, I downloaded the source and compiled SER 2.0.0 RC 1 as per instructions on http://www.iptel.org/ser_2_0_0_release_candidate_1 I get an error when try to check it with 'sercmd' and also can't see the ser process running Rgrds, Umer [root@umer ~]# /usr/local/sbin/ser Listening on udp: 192.168.1.103 [192.168.1.103]:5060 tcp: 192.168.1.103 [192.168.1.103]:5060 Aliases: tcp: phone03.tb.jasomi.com:5060 udp: phone03.tb.jasomi.com:5060 *: umer-sip.jasomi.com:* [root@umer ~]# /usr/local/sbin/sercmd ERROR: connect_unix_sock: connect(/tmp/ser_ctl): No such file or directory [2] [root@umer ~]# ps -A | grep ser 135 ? 00:00:00 kseriod 4931 ? 00:00:00 gam_server

2 1

[Serusers] SER as a boundary proxy - how to force routing?
by tzieleniewski 30 May '07

30 May '07

Hi, I have the following situation. I have one SER instance with public IP and LAN working as a boundary proxy. (its only role is to filter the traffic and authorize users) on the LAN side I have another SER instance with works as registrar and local sip proxy. How can I force the second proxy this in the LAN network to route the messages to the boundary proxy(no matter what transport is used). The best solution would be to route them only when the calls are made to the users which are localized outside the local LAN on the public NET. Thank You In advanced Cheers Tomasz

1 0

RE: [Users] BUG: qm_free ?
by Papadopoulos Georgios 30 May '07

30 May '07

No, I don't use t_newtran at all. Now I am trying to get this to happen again but no luck... Anyway, is it something to worry about or will the leaked transactions be cleaned up? Regards, George ps. I cannot connect to the SVN, is it down? > -----Original Message----- > From: Bogdan-Andrei Iancu [mailto:bogdan@voice-system.ro] > Sent: Wednesday, May 30, 2007 4:33 PM > To: Papadopoulos Georgios > Cc: Klaus Darilion; users(a)openser.org > Subject: Re: [Users] BUG: qm_free ? > > Perfect - thanks for testing - I applied the fix also on 1.2. > > regarding the Warning message: there were in 1.2 some fixes > related to detection of the transactions leak due scripting > issues. Probably 1.1 was not able to detect and report all cases. > > Do you use in your script t_newtran() function? typically, > when you use this function without terminating the > transaction (relay or reply in a stateful way), you will get > the warning. can you check this on your script? > > regards, > bogdan > > Papadopoulos Georgios wrote: > > Solved! Thank you! > > However, before applying the patch, I increased private > memory to 2MB > > and it did not crash. Then I set it back to 1MB, applied > the patch and > > it worked. > > > > Now I have a ton of these messages: > > WARNING: script writer didn't release transaction What does > it mean? > > This was not present in 1.1 and my config script has not changed > > (except for the necessary changes for the migration) > > > > Regards > > > > George > > > > > > > > > > > >> -----Original Message----- > >> From: Bogdan-Andrei Iancu [mailto:bogdan@voice-system.ro] > >> Sent: Wednesday, May 30, 2007 2:18 PM > >> To: Papadopoulos Georgios > >> Cc: Klaus Darilion; users(a)openser.org > >> Subject: Re: [Users] BUG: qm_free ? > >> > >> Hi George, > >> > >> I managed to find the bug without the backtrace. I applied > a fix for > >> development version (SVN trunk) and find attached a patch > for 1.2 - > >> could you please give it a try and see if it solves the bug? > >> > >> thanks and regards, > >> bogdan > >> > >> Papadopoulos Georgios wrote: > >> > >>> I cannot find a core file anywhere. Where should it be? I can > >>> reproduce the problem very easily, so please give me more > >>> > >> instructions > >> > >>> on how to get the coredump+backtrace that you need. > >>> > >>> thank you > >>> > >>> George > >>> > >>> > >>> > >>> > >>>> -----Original Message----- > >>>> From: Klaus Darilion [mailto:klaus.mailinglists@pernau.at] > >>>> Sent: Tuesday, May 29, 2007 8:34 PM > >>>> To: Papadopoulos Georgios > >>>> Cc: users(a)openser.org > >>>> Subject: Re: [Users] BUG: qm_free ? > >>>> > >>>> Maybe a bug? > >>>> > >>>> Can you provide a coredump+backtrace? I'm sure Bogdan or > >>>> > >> Daniel will > >> > >>>> take a look at it. > >>>> > >>>> regards > >>>> klaus > >>>> > >>>> Papadopoulos Georgios wrote: > >>>> > >>>> > >>>>> Hi Klaus, > >>>>> > >>>>> It crashes immediately, I have no time to do anything. I > >>>>> > >>>>> > >>>> tried again > >>>> > >>>> > >>>>> and I increased the log level. So now it is process 692. > >>>>> > >>>>> > >>>> Here is part > >>>> > >>>> > >>>>> of the output. I can send you the whole output if that helps. > >>>>> > >>>>> thank you > >>>>> > >>>>> George > >>>>> > >>>>> > >>>>> 16(692) DEBUG: timer routine:5,tl=0xb61abdc4 next=0xb61adfd8, > >>>>> timeout=3000000 > >>>>> 16(692) DEBUG: retransmission_handler : request resending > >>>>> (t=0xb61abc78, REGISTER ... ) > >>>>> 16(692) DEBUG:tm:set_timer: relative timeout is 3000000 > >>>>> 16(692) DEBUG: add_to_tail_of_timer[6]: 0xb61abdc4 (6000000) > >>>>> 16(692) DEBUG: retransmission_handler : done > >>>>> 16(692) DEBUG: timer routine:5,tl=0xb61adfd8 next=(nil), > >>>>> timeout=3000000 > >>>>> 16(692) DEBUG: retransmission_handler : request resending > >>>>> (t=0xb61ade8c, REGISTER ... ) > >>>>> 16(692) DEBUG:tm:set_timer: relative timeout is 3000000 > >>>>> 16(692) DEBUG: add_to_tail_of_timer[6]: 0xb61adfd8 (6000000) > >>>>> 16(692) DEBUG: retransmission_handler : done > >>>>> 16(692) DEBUG: timer routine:0,tl=0xb6182810 next=0xb61845ac, > >>>>> timeout=3 > >>>>> 16(692) DEBUG: final_response_handler:stop retr. and send CANCEL > >>>>> (0xb61826a8) > >>>>> 16(692) DEBUG:tm:t_should_relay_response: T_code=0, new_code=408 > >>>>> 16(692) DEBUG:tm:t_pick_branch: picked branch 0, code 408 > >>>>> 16(692) DEBUG:tm:t_should_relay_response: dns-failover > >>>>> > >>>>> > >>>> test: branch=0, > >>>> > >>>> > >>>>> last_recv=408, flags=0 > >>>>> 16(692) DEBUG:tm:t_should_relay_response: trying > >>>>> > >> DNS-based failover > >> > >>>>> 16(692) qm_malloc(0xb5f99000, 72) called from blacklists.c: > >>>>> add_rule_to_list(377) > >>>>> 16(692) qm_malloc(0xb5f99000, 72) returns address > 0xb6278238 frag. > >>>>> 0xb6278220 (size=72) on 1 -th hit > >>>>> 16(692) DBG:add_list_to_head: adding to bl dns > >>>>> > >> 0xb6278238,0xb6278238 > >> > >>>>> 16(692) DEBUG:tm:local_reply: branch=0, save=0, winner=0 > >>>>> 16(692) DEBUG:tm:local_reply: local transaction completed > >>>>> 16(692) DEBUG: add_to_tail_of_timer[2]: 0xb61826f0 (8) > >>>>> 16(692) DEBUG: final_response_handler : done > >>>>> 16(692) DEBUG: timer routine:0,tl=0xb61845ac next=0xb6186c6c, > >>>>> timeout=3 > >>>>> 16(692) DEBUG: timer routine:0,tl=0xb6186c6c next=0xb6188d98, > >>>>> timeout=3 > >>>>> 16(692) DEBUG: final_response_handler:stop retr. and send CANCEL > >>>>> (0xb6186b04) > >>>>> 16(692) DEBUG:tm:t_should_relay_response: T_code=0, new_code=408 > >>>>> 16(692) DEBUG:tm:t_pick_branch: picked branch 0, code 408 > >>>>> 16(692) DEBUG:tm:t_should_relay_response: dns-failover > >>>>> > >>>>> > >>>> test: branch=0, > >>>> > >>>> > >>>>> last_recv=408, flags=0 > >>>>> 16(692) DEBUG:tm:t_should_relay_response: trying > >>>>> > >> DNS-based failover > >> > >>>>> 16(692) qm_malloc(0xb5f99000, 72) called from blacklists.c: > >>>>> add_rule_to_list(377) > >>>>> 16(692) qm_malloc(0xb5f99000, 72) returns address > 0xb62782b0 frag. > >>>>> 0xb6278298 (size=72) on 1 -th hit > >>>>> 16(692) DBG:add_list_to_head: adding to bl dns > >>>>> > >> 0xb62782b0,0xb62782b0 > >> > >>>>> 16(692) qm_free(0x8151c40, 0xb62782b0), called from > blacklists.c: > >>>>> rm_dups(440) > >>>>> 16(692) BUG: qm_free: bad pointer 0xb62782b0 (out of memory > >>>>> > >>>>> > >>>> block!) - > >>>> > >>>> > >>>>> aborting > >>>>> > >>>>> > >>>>> > >>>>>> -----Original Message----- > >>>>>> From: Klaus Darilion [mailto:klaus.mailinglists@pernau.at] > >>>>>> Sent: Tuesday, May 29, 2007 5:48 PM > >>>>>> To: Papadopoulos Georgios > >>>>>> Cc: users(a)openser.org > >>>>>> Subject: Re: [Users] BUG: qm_free ? > >>>>>> > >>>>>> The bug was in process 32133 > >>>>>> > >>>>>> There are no log statements from this process. What what this > >>>>>> process? > >>>>>> (use "openserctl ps" to see the PIDs of the processes) > >>>>>> > >>>>>> regards > >>>>>> klaus > >>>>>> > >>>>>> Papadopoulos Georgios wrote: > >>>>>> > >>>>>> > >>>>>>> Hello all, > >>>>>>> > >>>>>>> I am having some trouble geting Openser 1.2 to work. It > >>>>>>> > >>>>>>> > >>>>>> crashes pretty > >>>>>> > >>>>>> > >>>>>>> much immediately. I have tried it successfully on a test > >>>>>>> > >>>>>>> > >>>>>> system but as > >>>>>> > >>>>>> > >>>>>>> soon as I start it in the production environment, it > >>>>>>> > >>>>>>> > >>>>>> crashes. Any ideas? > >>>>>> > >>>>>> > >>>>>>> > >>>>>>> Thank you for any help. > >>>>>>> > >>>>>>> George > >>>>>>> > >>>>>>> > >>>>>>> 0(0) INFO: statistics manager successfully initialized > >>>>>>> 0(0) StateLess module - initializing > >>>>>>> 0(0) TM - initializing... > >>>>>>> 0(0) Maxfwd module- initializing > >>>>>>> 0(0) INFO:ul_init_locks: locks array size 512 > >>>>>>> 0(0) TextOPS - initializing > >>>>>>> 0(0) AVPops - initializing > >>>>>>> 0(0) permissions - initializing > >>>>>>> 0(0) WARNING: File not found: > >>>>>>> > >>>>>>> > >>>>>> /root/openser/config/permissions.allow > >>>>>> > >>>>>> > >>>>>>> 0(0) Default allow file > >>>>>>> > >>>>>>> > >>>>>> (/root/openser/config/permissions.allow) not > >>>>>> > >>>>>> > >>>>>>> found => empty rule set > >>>>>>> 0(0) WARNING: File not found: > >>>>>>> > >>>>>>> > >>>> /root/openser/config/permissions.deny > >>>> > >>>> > >>>>>>> 0(0) Default deny file > >>>>>>> > >>>>>>> > >>>> (/root/openser/config/permissions.deny) not > >>>> > >>>> > >>>>>>> found => empty rule set > >>>>>>> 0(0) AUTH module - initializing > >>>>>>> 0(0) AUTH_DB module - initializing > >>>>>>> 0(0) ACC - initializing > >>>>>>> 0(0) INFO:xl_parse_name: using hdr type (4) instead of <From> > >>>>>>> 0(0) INFO:xl_parse_name: using hdr type (3) instead of <To> > >>>>>>> 0(0) INFO:textops:hname_fixup: using hdr type name <Nat-flag> > >>>>>>> 0(0) INFO:textops:hname_fixup: using hdr type (31) > instead of > >>>>>>> <Remote-Party-ID> > >>>>>>> 0(0) INFO: udp_init: SO_RCVBUF is initially 110592 > >>>>>>> 0(0) INFO: udp_init: SO_RCVBUF is finally 262142 > >>>>>>> 0(0) INFO: udp_init: SO_RCVBUF is initially 110592 > >>>>>>> 0(0) INFO: udp_init: SO_RCVBUF is finally 262142 > >>>>>>> 0(0) INFO: udp_init: SO_RCVBUF is initially 110592 > >>>>>>> 0(0) INFO: udp_init: SO_RCVBUF is finally 262142 > >>>>>>> 0(0) INFO: udp_init: SO_RCVBUF is initially 110592 > >>>>>>> 0(0) INFO: udp_init: SO_RCVBUF is finally 262142 > >>>>>>> 0(0) INFO: udp_init: SO_RCVBUF is initially 110592 > >>>>>>> 0(0) INFO: udp_init: SO_RCVBUF is finally 262142 > >>>>>>> 1(32087) INFO:mi_fifo:mi_child_init(1): extra fifo > >>>>>>> > >>>>>>> > >>>>>> listener processes > >>>>>> > >>>>>> > >>>>>>> created > >>>>>>> 2(32093) pre_auth(): Credentials received are not > >>>>>>> > >> filled properly > >> > >>>>>>> 1(32087) ERROR: parse_to_param: spitting out [<] in status 22 > >>>>>>> 1(32087) ERROR: parse_to: invalid To - unexpected end of > >>>>>>> > >>>>>>> > >>>>>> header in > >>>>>> > >>>>>> > >>>>>>> state 22 > >>>>>>> 1(32087) ERROR: get_hdr_field: bad to header > >>>>>>> 1(32087) ERROR: bad header field > >>>>>>> 1(32087) ERROR:maxfwd:is_maxfwd_present : parsing > >>>>>>> > >>>>>>> > >>>>>> MAX_FORWARD header > >>>>>> > >>>>>> > >>>>>>> failed! > >>>>>>> 1(32087) ERROR: parse_to_param: spitting out [<] in status 22 > >>>>>>> 1(32087) ERROR: parse_to: invalid To - unexpected end of > >>>>>>> > >>>>>>> > >>>>>> header in > >>>>>> > >>>>>> > >>>>>>> state 22 > >>>>>>> 1(32087) ERROR: get_hdr_field: bad to header > >>>>>>> 1(32087) ERROR: bad header field > >>>>>>> 1(32087) find_first_route: Error while parsing headers > >>>>>>> 1(32087) ERROR: parse_to_param: spitting out [<] in status 22 > >>>>>>> 1(32087) ERROR: parse_to: invalid To - unexpected end of > >>>>>>> > >>>>>>> > >>>>>> header in > >>>>>> > >>>>>> > >>>>>>> state 22 > >>>>>>> 1(32087) ERROR: get_hdr_field: bad to header > >>>>>>> 1(32087) ERROR: bad header field > >>>>>>> 1(32087) find_credentials(): Error while parsing headers > >>>>>>> 1(32087) pre_auth(): Error while looking for credentials > >>>>>>> 1(32087) ERROR: parse_to_param: spitting out [<] in status 22 > >>>>>>> 1(32087) ERROR: parse_to: invalid To - unexpected end of > >>>>>>> > >>>>>>> > >>>>>> header in > >>>>>> > >>>>>> > >>>>>>> state 22 > >>>>>>> 1(32087) ERROR: get_hdr_field: bad to header > >>>>>>> 1(32087) ERROR: bad header field > >>>>>>> 1(32087) ERROR: parse_to_param: spitting out [<] in status 22 > >>>>>>> 1(32087) ERROR: parse_to: invalid To - unexpected end of > >>>>>>> > >>>>>>> > >>>>>> header in > >>>>>> > >>>>>> > >>>>>>> state 22 > >>>>>>> 1(32087) ERROR: get_hdr_field: bad to header > >>>>>>> 1(32087) ERROR: bad header field > >>>>>>> 1(32087) ERROR: build_res_buf_from_sip_req: alas, > >>>>>>> > >> parse_headers > >> > >>>>>>> failed > >>>>>>> 1(32087) pre_auth(): Error while sending 400 reply > >>>>>>> INFO: started (pid: 32073) > >>>>>>> [root@ser1 sbin]# 1(32087) pre_auth(): Credentials > >>>>>>> > >>>>>>> > >>>>>> received are not > >>>>>> > >>>>>> > >>>>>>> filled properly > >>>>>>> 16(32133) BUG: qm_free: bad pointer 0xb648f38c (out of > >>>>>>> > >>>>>>> > >>>>>> memory block!) > >>>>>> > >>>>>> > >>>>>>> - aborting > >>>>>>> 1(32087) WARNING: script writer didn't release transaction > >>>>>>> 3(32096) WARNING: script writer didn't release transaction > >>>>>>> 1(32087) WARNING: script writer didn't release transaction > >>>>>>> 3(32096) WARNING: script writer didn't release transaction > >>>>>>> 3(32096) WARNING: script writer didn't release transaction > >>>>>>> 2(32093) WARNING: script writer didn't release transaction > >>>>>>> 3(32096) WARNING: script writer didn't release transaction > >>>>>>> 1(32087) WARNING: script writer didn't release transaction > >>>>>>> 2(32093) WARNING: script writer didn't release transaction > >>>>>>> 3(32096) WARNING: script writer didn't release transaction > >>>>>>> 1(32087) WARNING: script writer didn't release transaction > >>>>>>> 3(32096) WARNING: script writer didn't release transaction > >>>>>>> 2(32093) WARNING: script writer didn't release transaction > >>>>>>> 3(32096) WARNING: script writer didn't release transaction > >>>>>>> 2(32093) WARNING: script writer didn't release transaction > >>>>>>> 3(32096) WARNING: script writer didn't release transaction > >>>>>>> 2(32093) WARNING: script writer didn't release transaction > >>>>>>> 1(32087) WARNING: script writer didn't release transaction > >>>>>>> 1(32087) WARNING: script writer didn't release transaction > >>>>>>> 3(32096) WARNING: script writer didn't release transaction > >>>>>>> 1(32087) WARNING: script writer didn't release transaction > >>>>>>> 2(32093) WARNING: script writer didn't release transaction > >>>>>>> 1(32087) WARNING: script writer didn't release transaction > >>>>>>> 3(32096) WARNING: script writer didn't release transaction > >>>>>>> 3(32096) WARNING: script writer didn't release transaction > >>>>>>> 1(32087) WARNING: script writer didn't release transaction > >>>>>>> 3(32096) WARNING: script writer didn't release transaction > >>>>>>> 3(32096) ERROR: parse_via: invalid char <=> in state 201 > >>>>>>> 3(32096) error: parse_via_param > >>>>>>> 3(32096) ERROR: parse_via on: <SIP/2.0/UDP > >>>>>>> 87.202.97.60:59945;branc==z9hG4bK2e302aa9;rport > >>>>>>> From: <sip:gdt@sip.i-call.gr>;tag=as52e610af > >>>>>>> To: <sip:gdt@sip.i-call.gr> > >>>>>>> Call-ID: 1b7dabcf26487db47f520b5c7195958e(a)gdt.ath.cx > >>>>>>> <mailto:1b7dabcf26487db47f520b5c7195958e@gdt.ath.cx> > >>>>>>> CSeq: 4471 REGISTER > >>>>>>> User-Agent: Asterisk PBX > >>>>>>> Max-Forwards: 70 > >>>>>>> Expires: 120 > >>>>>>> Contact: <sip:s@87.202.97.60:59945> > >>>>>>> Event: registration > >>>>>>> Content-Length: 0 > >>>>>>> > >>>>>>> 3(32096) ERROR: parse_via parse error, parsed so > >>>>>>> > >>>>>>> > >>>> far:<SIP/2.0/UDP > >>>> > >>>> > >>>>>>> 87.202.97.60:59945;branc=> > >>>>>>> 3(32096) ERROR: get_hdr_field: bad via > >>>>>>> 3(32096) ERROR: bad header field > >>>>>>> 3(32096) ERROR: parse_msg: message=<REGISTER > sip:sip.i-call.gr > >>>>>>> SIP/2.0 > >>>>>>> Via: SIP/2.0/UDP > 87.202.97.60:59945;branc==z9hG4bK2e302aa9;rport > >>>>>>> From: <sip:gdt@sip.i-call.gr>;tag=as52e610af > >>>>>>> To: <sip:gdt@sip.i-call.gr> > >>>>>>> Call-ID: 1b7dabcf26487db47f520b5c7195958e(a)gdt.ath.cx > >>>>>>> CSeq: 4471 REGISTER > >>>>>>> User-Agent: Asterisk PBX > >>>>>>> Max-Forwards: 70 > >>>>>>> Expires: 120 > >>>>>>> Contact: <sip:s@87.202.97.60:59945> > >>>>>>> Event: registration > >>>>>>> Content-Length: 0 > >>>>>>> > >>>>>>> 3(32096) ERROR: receive_msg: parse_msg failed > >>>>>>> 3(32096) WARNING: script writer didn't release transaction > >>>>>>> 3(32096) WARNING: script writer didn't release transaction > >>>>>>> 1(32087) WARNING: script writer didn't release transaction > >>>>>>> 3(32096) WARNING: script writer didn't release transaction > >>>>>>> 1(32087) WARNING: script writer didn't release transaction > >>>>>>> 3(32096) WARNING: script writer didn't release transaction > >>>>>>> 2(32093) WARNING: script writer didn't release transaction > >>>>>>> 1(32087) WARNING: script writer didn't release transaction > >>>>>>> 2(32093) WARNING: script writer didn't release transaction > >>>>>>> 2(32093) WARNING: script writer didn't release transaction > >>>>>>> 0(32073) child process 32133 exited by a signal 6 > >>>>>>> 0(32073) core was generated > >>>>>>> 0(32073) INFO: terminating due to SIGCHLD > >>>>>>> 1(32087) INFO: signal 15 received > >>>>>>> 2(32093) INFO: signal 15 received > >>>>>>> 3(32096) INFO: signal 15 received > >>>>>>> 5(32102) INFO: signal 15 received > >>>>>>> 6(32103) INFO: signal 15 received > >>>>>>> 13(32123) INFO: signal 15 received > >>>>>>> 14(32127) INFO: signal 15 received > >>>>>>> 15(32130) INFO: signal 15 received > >>>>>>> 1(32087) 4(32099) 7(32104) INFO: signal 15 received > >>>>>>> 8(32109) INFO: signal 15 received > >>>>>>> 9(32112) INFO: signal 15 received > >>>>>>> 10(32115) INFO: signal 15 received > >>>>>>> 11(32118) INFO: signal 15 received > >>>>>>> 12(32121) INFO: signal 15 received > >>>>>>> INFO: signal 15 received > >>>>>>> INFO: signal 15 received > >>>>>>> 0(32073) INFO:mi_fifo:mi_destroy: seems that fifo child > >>>>>>> > >>>>>>> > >>>> is already > >>>> > >>>> > >>>>>>> dead! > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> 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 > >>>>>>> > >>>>>>> > >>> _______________________________________________ > >>> Users mailing list > >>> Users(a)openser.org > >>> http://openser.org/cgi-bin/mailman/listinfo/users > >>> > >>> > >>> > >> > > > > > >

2 1

RE: [Users] BUG: qm_free ?
by Papadopoulos Georgios 30 May '07

30 May '07

Solved! Thank you! However, before applying the patch, I increased private memory to 2MB and it did not crash. Then I set it back to 1MB, applied the patch and it worked. Now I have a ton of these messages: WARNING: script writer didn't release transaction What does it mean? This was not present in 1.1 and my config script has not changed (except for the necessary changes for the migration) Regards George > -----Original Message----- > From: Bogdan-Andrei Iancu [mailto:bogdan@voice-system.ro] > Sent: Wednesday, May 30, 2007 2:18 PM > To: Papadopoulos Georgios > Cc: Klaus Darilion; users(a)openser.org > Subject: Re: [Users] BUG: qm_free ? > > Hi George, > > I managed to find the bug without the backtrace. I applied a > fix for development version (SVN trunk) and find attached a > patch for 1.2 - could you please give it a try and see if it > solves the bug? > > thanks and regards, > bogdan > > Papadopoulos Georgios wrote: > > I cannot find a core file anywhere. Where should it be? I can > > reproduce the problem very easily, so please give me more > instructions > > on how to get the coredump+backtrace that you need. > > > > thank you > > > > George > > > > > > > >> -----Original Message----- > >> From: Klaus Darilion [mailto:klaus.mailinglists@pernau.at] > >> Sent: Tuesday, May 29, 2007 8:34 PM > >> To: Papadopoulos Georgios > >> Cc: users(a)openser.org > >> Subject: Re: [Users] BUG: qm_free ? > >> > >> Maybe a bug? > >> > >> Can you provide a coredump+backtrace? I'm sure Bogdan or > Daniel will > >> take a look at it. > >> > >> regards > >> klaus > >> > >> Papadopoulos Georgios wrote: > >> > >>> Hi Klaus, > >>> > >>> It crashes immediately, I have no time to do anything. I > >>> > >> tried again > >> > >>> and I increased the log level. So now it is process 692. > >>> > >> Here is part > >> > >>> of the output. I can send you the whole output if that helps. > >>> > >>> thank you > >>> > >>> George > >>> > >>> > >>> 16(692) DEBUG: timer routine:5,tl=0xb61abdc4 next=0xb61adfd8, > >>> timeout=3000000 > >>> 16(692) DEBUG: retransmission_handler : request resending > >>> (t=0xb61abc78, REGISTER ... ) > >>> 16(692) DEBUG:tm:set_timer: relative timeout is 3000000 > >>> 16(692) DEBUG: add_to_tail_of_timer[6]: 0xb61abdc4 (6000000) > >>> 16(692) DEBUG: retransmission_handler : done > >>> 16(692) DEBUG: timer routine:5,tl=0xb61adfd8 next=(nil), > >>> timeout=3000000 > >>> 16(692) DEBUG: retransmission_handler : request resending > >>> (t=0xb61ade8c, REGISTER ... ) > >>> 16(692) DEBUG:tm:set_timer: relative timeout is 3000000 > >>> 16(692) DEBUG: add_to_tail_of_timer[6]: 0xb61adfd8 (6000000) > >>> 16(692) DEBUG: retransmission_handler : done > >>> 16(692) DEBUG: timer routine:0,tl=0xb6182810 next=0xb61845ac, > >>> timeout=3 > >>> 16(692) DEBUG: final_response_handler:stop retr. and send CANCEL > >>> (0xb61826a8) > >>> 16(692) DEBUG:tm:t_should_relay_response: T_code=0, new_code=408 > >>> 16(692) DEBUG:tm:t_pick_branch: picked branch 0, code 408 > >>> 16(692) DEBUG:tm:t_should_relay_response: dns-failover > >>> > >> test: branch=0, > >> > >>> last_recv=408, flags=0 > >>> 16(692) DEBUG:tm:t_should_relay_response: trying > DNS-based failover > >>> 16(692) qm_malloc(0xb5f99000, 72) called from blacklists.c: > >>> add_rule_to_list(377) > >>> 16(692) qm_malloc(0xb5f99000, 72) returns address 0xb6278238 frag. > >>> 0xb6278220 (size=72) on 1 -th hit > >>> 16(692) DBG:add_list_to_head: adding to bl dns > 0xb6278238,0xb6278238 > >>> 16(692) DEBUG:tm:local_reply: branch=0, save=0, winner=0 > >>> 16(692) DEBUG:tm:local_reply: local transaction completed > >>> 16(692) DEBUG: add_to_tail_of_timer[2]: 0xb61826f0 (8) > >>> 16(692) DEBUG: final_response_handler : done > >>> 16(692) DEBUG: timer routine:0,tl=0xb61845ac next=0xb6186c6c, > >>> timeout=3 > >>> 16(692) DEBUG: timer routine:0,tl=0xb6186c6c next=0xb6188d98, > >>> timeout=3 > >>> 16(692) DEBUG: final_response_handler:stop retr. and send CANCEL > >>> (0xb6186b04) > >>> 16(692) DEBUG:tm:t_should_relay_response: T_code=0, new_code=408 > >>> 16(692) DEBUG:tm:t_pick_branch: picked branch 0, code 408 > >>> 16(692) DEBUG:tm:t_should_relay_response: dns-failover > >>> > >> test: branch=0, > >> > >>> last_recv=408, flags=0 > >>> 16(692) DEBUG:tm:t_should_relay_response: trying > DNS-based failover > >>> 16(692) qm_malloc(0xb5f99000, 72) called from blacklists.c: > >>> add_rule_to_list(377) > >>> 16(692) qm_malloc(0xb5f99000, 72) returns address 0xb62782b0 frag. > >>> 0xb6278298 (size=72) on 1 -th hit > >>> 16(692) DBG:add_list_to_head: adding to bl dns > 0xb62782b0,0xb62782b0 > >>> 16(692) qm_free(0x8151c40, 0xb62782b0), called from blacklists.c: > >>> rm_dups(440) > >>> 16(692) BUG: qm_free: bad pointer 0xb62782b0 (out of memory > >>> > >> block!) - > >> > >>> aborting > >>> > >>> > >>>> -----Original Message----- > >>>> From: Klaus Darilion [mailto:klaus.mailinglists@pernau.at] > >>>> Sent: Tuesday, May 29, 2007 5:48 PM > >>>> To: Papadopoulos Georgios > >>>> Cc: users(a)openser.org > >>>> Subject: Re: [Users] BUG: qm_free ? > >>>> > >>>> The bug was in process 32133 > >>>> > >>>> There are no log statements from this process. What what this > >>>> process? > >>>> (use "openserctl ps" to see the PIDs of the processes) > >>>> > >>>> regards > >>>> klaus > >>>> > >>>> Papadopoulos Georgios wrote: > >>>> > >>>>> Hello all, > >>>>> > >>>>> I am having some trouble geting Openser 1.2 to work. It > >>>>> > >>>> crashes pretty > >>>> > >>>>> much immediately. I have tried it successfully on a test > >>>>> > >>>> system but as > >>>> > >>>>> soon as I start it in the production environment, it > >>>>> > >>>> crashes. Any ideas? > >>>> > >>>>> > >>>>> Thank you for any help. > >>>>> > >>>>> George > >>>>> > >>>>> > >>>>> 0(0) INFO: statistics manager successfully initialized > >>>>> 0(0) StateLess module - initializing > >>>>> 0(0) TM - initializing... > >>>>> 0(0) Maxfwd module- initializing > >>>>> 0(0) INFO:ul_init_locks: locks array size 512 > >>>>> 0(0) TextOPS - initializing > >>>>> 0(0) AVPops - initializing > >>>>> 0(0) permissions - initializing > >>>>> 0(0) WARNING: File not found: > >>>>> > >>>> /root/openser/config/permissions.allow > >>>> > >>>>> 0(0) Default allow file > >>>>> > >>>> (/root/openser/config/permissions.allow) not > >>>> > >>>>> found => empty rule set > >>>>> 0(0) WARNING: File not found: > >>>>> > >> /root/openser/config/permissions.deny > >> > >>>>> 0(0) Default deny file > >>>>> > >> (/root/openser/config/permissions.deny) not > >> > >>>>> found => empty rule set > >>>>> 0(0) AUTH module - initializing > >>>>> 0(0) AUTH_DB module - initializing > >>>>> 0(0) ACC - initializing > >>>>> 0(0) INFO:xl_parse_name: using hdr type (4) instead of <From> > >>>>> 0(0) INFO:xl_parse_name: using hdr type (3) instead of <To> > >>>>> 0(0) INFO:textops:hname_fixup: using hdr type name <Nat-flag> > >>>>> 0(0) INFO:textops:hname_fixup: using hdr type (31) instead of > >>>>> <Remote-Party-ID> > >>>>> 0(0) INFO: udp_init: SO_RCVBUF is initially 110592 > >>>>> 0(0) INFO: udp_init: SO_RCVBUF is finally 262142 > >>>>> 0(0) INFO: udp_init: SO_RCVBUF is initially 110592 > >>>>> 0(0) INFO: udp_init: SO_RCVBUF is finally 262142 > >>>>> 0(0) INFO: udp_init: SO_RCVBUF is initially 110592 > >>>>> 0(0) INFO: udp_init: SO_RCVBUF is finally 262142 > >>>>> 0(0) INFO: udp_init: SO_RCVBUF is initially 110592 > >>>>> 0(0) INFO: udp_init: SO_RCVBUF is finally 262142 > >>>>> 0(0) INFO: udp_init: SO_RCVBUF is initially 110592 > >>>>> 0(0) INFO: udp_init: SO_RCVBUF is finally 262142 > >>>>> 1(32087) INFO:mi_fifo:mi_child_init(1): extra fifo > >>>>> > >>>> listener processes > >>>> > >>>>> created > >>>>> 2(32093) pre_auth(): Credentials received are not > filled properly > >>>>> 1(32087) ERROR: parse_to_param: spitting out [<] in status 22 > >>>>> 1(32087) ERROR: parse_to: invalid To - unexpected end of > >>>>> > >>>> header in > >>>> > >>>>> state 22 > >>>>> 1(32087) ERROR: get_hdr_field: bad to header > >>>>> 1(32087) ERROR: bad header field > >>>>> 1(32087) ERROR:maxfwd:is_maxfwd_present : parsing > >>>>> > >>>> MAX_FORWARD header > >>>> > >>>>> failed! > >>>>> 1(32087) ERROR: parse_to_param: spitting out [<] in status 22 > >>>>> 1(32087) ERROR: parse_to: invalid To - unexpected end of > >>>>> > >>>> header in > >>>> > >>>>> state 22 > >>>>> 1(32087) ERROR: get_hdr_field: bad to header > >>>>> 1(32087) ERROR: bad header field > >>>>> 1(32087) find_first_route: Error while parsing headers > >>>>> 1(32087) ERROR: parse_to_param: spitting out [<] in status 22 > >>>>> 1(32087) ERROR: parse_to: invalid To - unexpected end of > >>>>> > >>>> header in > >>>> > >>>>> state 22 > >>>>> 1(32087) ERROR: get_hdr_field: bad to header > >>>>> 1(32087) ERROR: bad header field > >>>>> 1(32087) find_credentials(): Error while parsing headers > >>>>> 1(32087) pre_auth(): Error while looking for credentials > >>>>> 1(32087) ERROR: parse_to_param: spitting out [<] in status 22 > >>>>> 1(32087) ERROR: parse_to: invalid To - unexpected end of > >>>>> > >>>> header in > >>>> > >>>>> state 22 > >>>>> 1(32087) ERROR: get_hdr_field: bad to header > >>>>> 1(32087) ERROR: bad header field > >>>>> 1(32087) ERROR: parse_to_param: spitting out [<] in status 22 > >>>>> 1(32087) ERROR: parse_to: invalid To - unexpected end of > >>>>> > >>>> header in > >>>> > >>>>> state 22 > >>>>> 1(32087) ERROR: get_hdr_field: bad to header > >>>>> 1(32087) ERROR: bad header field > >>>>> 1(32087) ERROR: build_res_buf_from_sip_req: alas, > parse_headers > >>>>> failed > >>>>> 1(32087) pre_auth(): Error while sending 400 reply > >>>>> INFO: started (pid: 32073) > >>>>> [root@ser1 sbin]# 1(32087) pre_auth(): Credentials > >>>>> > >>>> received are not > >>>> > >>>>> filled properly > >>>>> 16(32133) BUG: qm_free: bad pointer 0xb648f38c (out of > >>>>> > >>>> memory block!) > >>>> > >>>>> - aborting > >>>>> 1(32087) WARNING: script writer didn't release transaction > >>>>> 3(32096) WARNING: script writer didn't release transaction > >>>>> 1(32087) WARNING: script writer didn't release transaction > >>>>> 3(32096) WARNING: script writer didn't release transaction > >>>>> 3(32096) WARNING: script writer didn't release transaction > >>>>> 2(32093) WARNING: script writer didn't release transaction > >>>>> 3(32096) WARNING: script writer didn't release transaction > >>>>> 1(32087) WARNING: script writer didn't release transaction > >>>>> 2(32093) WARNING: script writer didn't release transaction > >>>>> 3(32096) WARNING: script writer didn't release transaction > >>>>> 1(32087) WARNING: script writer didn't release transaction > >>>>> 3(32096) WARNING: script writer didn't release transaction > >>>>> 2(32093) WARNING: script writer didn't release transaction > >>>>> 3(32096) WARNING: script writer didn't release transaction > >>>>> 2(32093) WARNING: script writer didn't release transaction > >>>>> 3(32096) WARNING: script writer didn't release transaction > >>>>> 2(32093) WARNING: script writer didn't release transaction > >>>>> 1(32087) WARNING: script writer didn't release transaction > >>>>> 1(32087) WARNING: script writer didn't release transaction > >>>>> 3(32096) WARNING: script writer didn't release transaction > >>>>> 1(32087) WARNING: script writer didn't release transaction > >>>>> 2(32093) WARNING: script writer didn't release transaction > >>>>> 1(32087) WARNING: script writer didn't release transaction > >>>>> 3(32096) WARNING: script writer didn't release transaction > >>>>> 3(32096) WARNING: script writer didn't release transaction > >>>>> 1(32087) WARNING: script writer didn't release transaction > >>>>> 3(32096) WARNING: script writer didn't release transaction > >>>>> 3(32096) ERROR: parse_via: invalid char <=> in state 201 > >>>>> 3(32096) error: parse_via_param > >>>>> 3(32096) ERROR: parse_via on: <SIP/2.0/UDP > >>>>> 87.202.97.60:59945;branc==z9hG4bK2e302aa9;rport > >>>>> From: <sip:gdt@sip.i-call.gr>;tag=as52e610af > >>>>> To: <sip:gdt@sip.i-call.gr> > >>>>> Call-ID: 1b7dabcf26487db47f520b5c7195958e(a)gdt.ath.cx > >>>>> <mailto:1b7dabcf26487db47f520b5c7195958e@gdt.ath.cx> > >>>>> CSeq: 4471 REGISTER > >>>>> User-Agent: Asterisk PBX > >>>>> Max-Forwards: 70 > >>>>> Expires: 120 > >>>>> Contact: <sip:s@87.202.97.60:59945> > >>>>> Event: registration > >>>>> Content-Length: 0 > >>>>> > >>>>> 3(32096) ERROR: parse_via parse error, parsed so > >>>>> > >> far:<SIP/2.0/UDP > >> > >>>>> 87.202.97.60:59945;branc=> > >>>>> 3(32096) ERROR: get_hdr_field: bad via > >>>>> 3(32096) ERROR: bad header field > >>>>> 3(32096) ERROR: parse_msg: message=<REGISTER sip:sip.i-call.gr > >>>>> SIP/2.0 > >>>>> Via: SIP/2.0/UDP 87.202.97.60:59945;branc==z9hG4bK2e302aa9;rport > >>>>> From: <sip:gdt@sip.i-call.gr>;tag=as52e610af > >>>>> To: <sip:gdt@sip.i-call.gr> > >>>>> Call-ID: 1b7dabcf26487db47f520b5c7195958e(a)gdt.ath.cx > >>>>> CSeq: 4471 REGISTER > >>>>> User-Agent: Asterisk PBX > >>>>> Max-Forwards: 70 > >>>>> Expires: 120 > >>>>> Contact: <sip:s@87.202.97.60:59945> > >>>>> Event: registration > >>>>> Content-Length: 0 > >>>>> > >>>>> 3(32096) ERROR: receive_msg: parse_msg failed > >>>>> 3(32096) WARNING: script writer didn't release transaction > >>>>> 3(32096) WARNING: script writer didn't release transaction > >>>>> 1(32087) WARNING: script writer didn't release transaction > >>>>> 3(32096) WARNING: script writer didn't release transaction > >>>>> 1(32087) WARNING: script writer didn't release transaction > >>>>> 3(32096) WARNING: script writer didn't release transaction > >>>>> 2(32093) WARNING: script writer didn't release transaction > >>>>> 1(32087) WARNING: script writer didn't release transaction > >>>>> 2(32093) WARNING: script writer didn't release transaction > >>>>> 2(32093) WARNING: script writer didn't release transaction > >>>>> 0(32073) child process 32133 exited by a signal 6 > >>>>> 0(32073) core was generated > >>>>> 0(32073) INFO: terminating due to SIGCHLD > >>>>> 1(32087) INFO: signal 15 received > >>>>> 2(32093) INFO: signal 15 received > >>>>> 3(32096) INFO: signal 15 received > >>>>> 5(32102) INFO: signal 15 received > >>>>> 6(32103) INFO: signal 15 received > >>>>> 13(32123) INFO: signal 15 received > >>>>> 14(32127) INFO: signal 15 received > >>>>> 15(32130) INFO: signal 15 received > >>>>> 1(32087) 4(32099) 7(32104) INFO: signal 15 received > >>>>> 8(32109) INFO: signal 15 received > >>>>> 9(32112) INFO: signal 15 received > >>>>> 10(32115) INFO: signal 15 received > >>>>> 11(32118) INFO: signal 15 received > >>>>> 12(32121) INFO: signal 15 received > >>>>> INFO: signal 15 received > >>>>> INFO: signal 15 received > >>>>> 0(32073) INFO:mi_fifo:mi_destroy: seems that fifo child > >>>>> > >> is already > >> > >>>>> dead! > >>>>> > >>>>> > >>>>> > >>>>> 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 > >>>>> > > > > _______________________________________________ > > Users mailing list > > Users(a)openser.org > > http://openser.org/cgi-bin/mailman/listinfo/users > > > > > >

3 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users