Hello
I'd like to know if there is any current development in process regarding
LDAP module and PA module. I'd definitely check out the CVS repository for
the latest build, but if anyone could let me know, me & my team would like
to contribute to the SER as well, if we do have the opportunity.
Thanx
Shakil
_______________________________
Do you Yahoo!?
Declare Yourself - Register online to vote today!
http://vote.yahoo.com
Hi All.
I'm using ser-0.8.99-dev10 with flatstore.so.
Can anyone tell me how to determine when a flatstore log file will no longer be
written to?
The reason I ask is that I need to move these flatstore files periodically to
my billing system and I need to make sure that I don't interfere with flatstore
when doing so. I also need to make sure I remove CDRs that I've already sent to
my billing server.
So for example, I want to grab all CDRs every hour - on the hour. So I would
copy the previous hour's call records to my billing server. Then I would delete
these calls from the ser flatstore directory to avoid getting duplicate CDRs in
my billing system. How can I achieve this?
I'm very unclear on how flatstore.so decides to rotate logs.
Regards,
Paul
_______________________________
Do you Yahoo!?
Declare Yourself - Register online to vote today!
http://vote.yahoo.com
Hi Marian:
There seem to be more than a versioning problem with my isdn g/w. I
synch'ed SER rel_0_8_14 to SEMS ser_rel_0_8_12 and, although the problem
with t_reply() is gone, here's another issue:
I can dial from inside and outside the g/w, call is established, but
nothing can be heard on either side, i.e. no media exchange. Also,
hangup is not possible.
I've tried using both isdn4linux and CAPI drivers, same result. Here's
sems' output:
(10164) DEBUG: changePSTNState (IsdnCall.cpp:419): terminating i4l
inbound listener thread
(10164) DEBUG: changePSTNState (IsdnCall.cpp:435): now both sides
connected, running connectAudio!
(10164) INFO: putVoiceStream (IsdnDevice.cpp:478): isdn device not
available for writing, dropping data
(10164) INFO: putVoiceStream (IsdnDevice.cpp:478): isdn device not
available for writing, dropping data
(10164) INFO: putVoiceStream (IsdnDevice.cpp:478): isdn device not
available for writing, dropping data
(10164) INFO: putVoiceStream (IsdnDevice.cpp:478): isdn device not
available for writing, dropping data
(10164) INFO: putVoiceStream (IsdnDevice.cpp:478): isdn device not
available for writing, dropping data
(10164) INFO: putVoiceStream (IsdnDevice.cpp:478): isdn device not
available for writing, dropping data
If ser.cfg, sems.conf, and isdngw.conf would help people come up with
some advice I could post them to the list.
Thanks
--
Socrates.
Marian Dumitru wrote:
> Hi Socrates,
>
> yes, you are using mismatched version. For SER rel_0_8_14 use SEMS
> ser_rel_0_8_12.
>
> Best regards,
> Marian Dumitru
>
>
> Socrates Varakliotis wrote:
>
>> Hi Marian:
>>
>> Thanks for the answer.
>>
>> Given that my ser.cfg loads the tm module, I presume the problem emanates
>> from SER/SEMS versions. I've checked out rel_0_8_14 of sip_router and the
>> CVS head of SEMS. Are these known to have conflicts?
>>
>> I recall there was a reason for me checking out the tagged version of
>> sip_router, something I've read or experienced about mysql, or serweb
>> (don't
>> remember what exactly). Which raises an issue with synch'ing the two
>> s/w in
>> the CVS.
>>
>> Is there a corresponding tag for answer_machine then?
>>
>> Regards,
>> --
>> Socrates.
>>
>>
>>
>> ----- Original Message ----- From: "Marian Dumitru"
>> <marian.dumitru(a)voice-sistem.ro>
>> To: "Socrates Varakliotis" <S.Varakliotis(a)cs.ucl.ac.uk>
>> Cc: <serusers(a)lists.iptel.org>
>> Sent: Monday, October 25, 2004 8:47 PM
>> Subject: Re: [Serusers] SER + SEMS + isdngw problem
>>
>>
>>
>>> Hi Socrates,
>>>
>>> My first guess is you haven't load TM module which makes available
>>> function "t_reply" or you are mixing the version of SER and SEMS.
>>>
>>>
>>> Best regards,
>>> Marian Dumitru
>>>
>>>
>>> Socrates Varakliotis wrote:
>>>
>>>> Hi All:
>>>>
>>>> I'm trying to make an outgoing call from Kphone to an ISDN line.
>>>> Although the called phone rings, when I pickup the call drops and I get
>>>> the following errors on the logfiles:
>>>>
>>>> Has anyone come across this?
>>>> Any suggestions welcome.
>>>>
>>>> Regards,
>>>> --
>>>> Socrates.
>>>>
>>>>
>>>>
>>>>
>>>> ------------------- SER.log ---------------------------
>>>>
>>>> ...
>>>>
>>>> sip_request.isdngw
>>>> INVITE
>>>> 76793696
>>>> .
>>>> 128.16.64.71
>>>> 128.16.64.71
>>>> .
>>>> sip:576793696@128.16.64.71
>>>> sip:root@128.16.64.71:5062;transport=udp
>>>> "Socrates Varakliotis" <sip:6222@shaggy.cs.ucl.ac.uk>
>>>> <sip:576793696@128.16.64.71>
>>>> 183464563
>>>> 64247849
>>>> .
>>>> 5593
>>>> 55871:1543819790
>>>> .
>>>> .
>>>> P-MsgFlags: 0
>>>> .
>>>> v=0
>>>> o=username 0 0 IN IP4 128.16.64.71
>>>> s=The Funky Flow
>>>> c=IN IP4 128.16.64.71
>>>> t=0 0
>>>> m=audio 32802 RTP/AVP 0 97 3
>>>> a=rtpmap:0 PCMU/8000
>>>> a=rtpmap:3 GSM/8000
>>>> a=rtpmap:97 iLBC/8000
>>>>
>>>> >
>>>> 5(4251) DEBUG: write_to_vm_fifo: write completed
>>>> 5(4251) DEBUG: add_to_tail_of_timer[0]: 0x402e35a4
>>>> 5(4251) DEBUG:destroy_avp_list: destroing list (nil)
>>>> 5(4251) receive_msg: cleaning up
>>>> 9(4255) ERROR: fifo_server: command t_reply is not available
>>>> 9(4255) ERROR: fifo_server: command must begin with :: isgndw: ringing
>>>> 9(4255) ERROR: fifo_server: command must begin with :: 000010A77D8E0A09
>>>> 9(4255) ERROR: fifo_server: command must have at least 3 chars
>>>> 9(4255) INFO: fifo_server: command empty
>>>> 9(4255) ERROR: fifo_server: command t_reply is not available
>>>> 9(4255) ERROR: fifo_server: command must have at least 3 chars
>>>> 9(4255) ERROR: fifo_server: command must begin with :: 000010A77D8E0A09
>>>> 9(4255) ERROR: fifo_server: command must begin with :: Content-Type:
>>>> application/sdp
>>>> 9(4255) ERROR: fifo_server: command must begin with :: v=0
>>>> 9(4255) ERROR: fifo_server: command must begin with :: s=session
>>>> 9(4255) ERROR: fifo_server: command must begin with :: t=0 0
>>>> 9(4255) ERROR: fifo_server: command must begin with :: a=rtpmap:0
>>>> PCMU/8000
>>>> 9(4255) INFO: fifo_server: command empty
>>>> 9(4255) ERROR: fifo_server: command t_reply is not available
>>>> 9(4255) ERROR: fifo_server: command must begin with :: could not send
>>>> response.
>>>> 9(4255) ERROR: fifo_server: command must begin with :: 000010A77D8E0A09
>>>> 9(4255) ERROR: fifo_server: command must have at least 3 chars
>>>> 9(4255) INFO: fifo_server: command empty
>>>> 10(4257) DEBUG: timer routine:0,tl=0x402e35a4 next=(nil)
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> ------------------- SEMS.log ---------------------------
>>>>
>>>> ....
>>>>
>>>> 180
>>>> isgndw: ringing
>>>> 55871:1543819790
>>>> 000010A77D8E0A09
>>>> Contact: <sip:76793696@128.16.64.71>
>>>> .
>>>> .
>>>>
>>>> >
>>>> (4263) DEBUG: write_to_fifo (SerClient.cpp:244): Write to fifo:
>>
>>
>> completed
>>
>>>> (4263) DEBUG: getReturnCode (AmRequest.cpp:357): response from Ser: 500
>>>> command 't_reply' not available
>>>> (4263) ERROR: reply (AmRequest.cpp:335): AmRequestUAS::reply: 500
>>>> command 't_reply' not available
>>>> (4263) DEBUG: cb_connect_active_ind (IsdnCapiConnection.cpp:282):
>>>> callback funtion called: cb_connect_active_ind!
>>>> (4263) DEBUG: cb_connect_active_ind (IsdnCapiConnection.cpp:290):
>>>> physical connection established, now creating logical connection
>>>> (4263) DEBUG: cb_connect_b3_conf (IsdnCapiConnection.cpp:308):
>>>> connected, now unlocking mutex
>>>> (4263) DEBUG: changePSTNState (IsdnCall.cpp:348): CALL: PSTN state
>>>> (outbound): from (CONNECTING|CONNECTING) to (CONNECTING|CONNECTED)
>>>> (4263) DEBUG: changePSTNState (IsdnCall.cpp:550): DONE: PSTN state
>>>> (outbound): from (CONNECTING|IDLE) to (CONNECTING|CONNECTING)
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Serusers mailing list
>>>> serusers(a)lists.iptel.org
>>>> http://lists.iptel.org/mailman/listinfo/serusers
>>>>
>>>
>>> --
>>> Voice Sistem
>>> http://www.voice-sistem.ro
>>>
>>
>>
>>
>
Ups.. forgot to CC the list.
Marian Dumitru wrote:
> Hi Socrates,
>
> yes, you are using mismatched version. For SER rel_0_8_14 use SEMS
> ser_rel_0_8_12.
>
> Best regards,
> Marian Dumitru
>
>
> Socrates Varakliotis wrote:
>
>> Hi Marian:
>>
>> Thanks for the answer.
>>
>> Given that my ser.cfg loads the tm module, I presume the problem emanates
>> from SER/SEMS versions. I've checked out rel_0_8_14 of sip_router and the
>> CVS head of SEMS. Are these known to have conflicts?
>>
>> I recall there was a reason for me checking out the tagged version of
>> sip_router, something I've read or experienced about mysql, or serweb
>> (don't
>> remember what exactly). Which raises an issue with synch'ing the two
>> s/w in
>> the CVS.
>>
>> Is there a corresponding tag for answer_machine then?
>>
>> Regards,
>> --
>> Socrates.
>>
>>
>>
>> ----- Original Message ----- From: "Marian Dumitru"
>> <marian.dumitru(a)voice-sistem.ro>
>> To: "Socrates Varakliotis" <S.Varakliotis(a)cs.ucl.ac.uk>
>> Cc: <serusers(a)lists.iptel.org>
>> Sent: Monday, October 25, 2004 8:47 PM
>> Subject: Re: [Serusers] SER + SEMS + isdngw problem
>>
>>
>>
>>> Hi Socrates,
>>>
>>> My first guess is you haven't load TM module which makes available
>>> function "t_reply" or you are mixing the version of SER and SEMS.
>>>
>>>
>>> Best regards,
>>> Marian Dumitru
>>>
>>>
>>> Socrates Varakliotis wrote:
>>>
>>>> Hi All:
>>>>
>>>> I'm trying to make an outgoing call from Kphone to an ISDN line.
>>>> Although the called phone rings, when I pickup the call drops and I get
>>>> the following errors on the logfiles:
>>>>
>>>> Has anyone come across this?
>>>> Any suggestions welcome.
>>>>
>>>> Regards,
>>>> --
>>>> Socrates.
>>>>
>>>>
>>>>
>>>>
>>>> ------------------- SER.log ---------------------------
>>>>
>>>> ...
>>>>
>>>> sip_request.isdngw
>>>> INVITE
>>>> 76793696
>>>> .
>>>> 128.16.64.71
>>>> 128.16.64.71
>>>> .
>>>> sip:576793696@128.16.64.71
>>>> sip:root@128.16.64.71:5062;transport=udp
>>>> "Socrates Varakliotis" <sip:6222@shaggy.cs.ucl.ac.uk>
>>>> <sip:576793696@128.16.64.71>
>>>> 183464563
>>>> 64247849
>>>> .
>>>> 5593
>>>> 55871:1543819790
>>>> .
>>>> .
>>>> P-MsgFlags: 0
>>>> .
>>>> v=0
>>>> o=username 0 0 IN IP4 128.16.64.71
>>>> s=The Funky Flow
>>>> c=IN IP4 128.16.64.71
>>>> t=0 0
>>>> m=audio 32802 RTP/AVP 0 97 3
>>>> a=rtpmap:0 PCMU/8000
>>>> a=rtpmap:3 GSM/8000
>>>> a=rtpmap:97 iLBC/8000
>>>>
>>>> >
>>>> 5(4251) DEBUG: write_to_vm_fifo: write completed
>>>> 5(4251) DEBUG: add_to_tail_of_timer[0]: 0x402e35a4
>>>> 5(4251) DEBUG:destroy_avp_list: destroing list (nil)
>>>> 5(4251) receive_msg: cleaning up
>>>> 9(4255) ERROR: fifo_server: command t_reply is not available
>>>> 9(4255) ERROR: fifo_server: command must begin with :: isgndw: ringing
>>>> 9(4255) ERROR: fifo_server: command must begin with :: 000010A77D8E0A09
>>>> 9(4255) ERROR: fifo_server: command must have at least 3 chars
>>>> 9(4255) INFO: fifo_server: command empty
>>>> 9(4255) ERROR: fifo_server: command t_reply is not available
>>>> 9(4255) ERROR: fifo_server: command must have at least 3 chars
>>>> 9(4255) ERROR: fifo_server: command must begin with :: 000010A77D8E0A09
>>>> 9(4255) ERROR: fifo_server: command must begin with :: Content-Type:
>>>> application/sdp
>>>> 9(4255) ERROR: fifo_server: command must begin with :: v=0
>>>> 9(4255) ERROR: fifo_server: command must begin with :: s=session
>>>> 9(4255) ERROR: fifo_server: command must begin with :: t=0 0
>>>> 9(4255) ERROR: fifo_server: command must begin with :: a=rtpmap:0
>>>> PCMU/8000
>>>> 9(4255) INFO: fifo_server: command empty
>>>> 9(4255) ERROR: fifo_server: command t_reply is not available
>>>> 9(4255) ERROR: fifo_server: command must begin with :: could not send
>>>> response.
>>>> 9(4255) ERROR: fifo_server: command must begin with :: 000010A77D8E0A09
>>>> 9(4255) ERROR: fifo_server: command must have at least 3 chars
>>>> 9(4255) INFO: fifo_server: command empty
>>>> 10(4257) DEBUG: timer routine:0,tl=0x402e35a4 next=(nil)
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> ------------------- SEMS.log ---------------------------
>>>>
>>>> ....
>>>>
>>>> 180
>>>> isgndw: ringing
>>>> 55871:1543819790
>>>> 000010A77D8E0A09
>>>> Contact: <sip:76793696@128.16.64.71>
>>>> .
>>>> .
>>>>
>>>> >
>>>> (4263) DEBUG: write_to_fifo (SerClient.cpp:244): Write to fifo:
>>
>>
>> completed
>>
>>>> (4263) DEBUG: getReturnCode (AmRequest.cpp:357): response from Ser: 500
>>>> command 't_reply' not available
>>>> (4263) ERROR: reply (AmRequest.cpp:335): AmRequestUAS::reply: 500
>>>> command 't_reply' not available
>>>> (4263) DEBUG: cb_connect_active_ind (IsdnCapiConnection.cpp:282):
>>>> callback funtion called: cb_connect_active_ind!
>>>> (4263) DEBUG: cb_connect_active_ind (IsdnCapiConnection.cpp:290):
>>>> physical connection established, now creating logical connection
>>>> (4263) DEBUG: cb_connect_b3_conf (IsdnCapiConnection.cpp:308):
>>>> connected, now unlocking mutex
>>>> (4263) DEBUG: changePSTNState (IsdnCall.cpp:348): CALL: PSTN state
>>>> (outbound): from (CONNECTING|CONNECTING) to (CONNECTING|CONNECTED)
>>>> (4263) DEBUG: changePSTNState (IsdnCall.cpp:550): DONE: PSTN state
>>>> (outbound): from (CONNECTING|IDLE) to (CONNECTING|CONNECTING)
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Serusers mailing list
>>>> serusers(a)lists.iptel.org
>>>> http://lists.iptel.org/mailman/listinfo/serusers
>>>>
>>>
>>> --
>>> Voice Sistem
>>> http://www.voice-sistem.ro
>>>
>>
>>
>>
>
--
Voice Sistem
http://www.voice-sistem.ro
Hi all,
I have (finally!) gotten SER working with the default config!!(Thanks
for all your help answering my stupid questions). Now I want to turn
authentication on and create user accounts.
I've successfully created account by doing the following:
serctl add aisling password aisling(a)bla.com
I've also uncommented the portion of the config file that deals with
authentication. However, authentication still does not apply and any
user can connect to the server. Is there something I've forgotten?
All the best,
Aisling.
-------------------Legal Disclaimer---------------------------------------
The above electronic mail transmission is confidential and intended only for the person to whom it is addressed. Its contents may be protected by legal and/or professional privilege. Should it be received by you in error please contact the sender at the above quoted email address. Any unauthorised form of reproduction of this message is strictly prohibited. The Institute does not guarantee the security of any information electronically transmitted and is not liable if the information contained in this communication is not a proper and complete record of the message as transmitted by the sender nor for any delay in its receipt.
----------------------------------------------------------------------------------------
Hi all,
I'm new to SER and currently i'm installing SER 0.8.12 into RH9. My serweb version is 2004-01-04.tar.gz. When I tried to login at the admin page (http://x.x.x.x/serweb/admin/index.php)with "admin" and "heslo", serweb prompted me an error message, i.e. "cannot connect to sql server". But I had no problem to get connected to the ser database with the same username/password, via mysql command (mysql -u ser ser -p).
Could somebody out there give me some clues?
Thanks in advance.
Chew
--
_______________________________________________
Find what you are looking for with the Lycos Yellow Pages
http://r.lycos.com/r/yp_emailfooter/http://yellowpages.lycos.com/default.as…
Steve,
Make sure you are running the lastest version of the firmware as this will
support your multiple domain issue. If you need more support call
866-VOIPBOX option 2 tech support. Just saw your request at
http://lists.iptel.org/pipermail/serusers/2004-October/012269.html
Marc Dyman
SVP Worldwide Sales
813-749-1445 Direct Line
727-243-4357 Mobile
866-713-0555 Follow Me and Fax
www.thebox.com <http://www.thebox.com/>
Hello,
If a ser 0.8.14 named "server" receives the following message:
ACK sip:final@destination:5060 SIP/2.0.
Route: <sip:route@server:5060;ftag=0006283e0a6800774f26ee45-1c475c78;lr=on>.
And loose_route() is called on that server, shouldn't it return true? Or is
loose_route() only true if there is another Route Header field left after
removing self?
To my understanding, loose_route should return true if there was a Route
header field removed by the function, so that we know we have reached the
end of a server chain and can t_relay the request without further local
processing.
Best regards,
Martin
Hi there i am trying to debug my accounting problem but so far without success.
I followed the instructions in the module README
Here is the part of my config
modparam("acc","log_level", 1)
modparam("acc","log_flag", 1)
modparam("acc", "db_flag", 2)
and in rr part of the script i have a setflag(1);
but still i cannot see any updates in the database ???
Any one have an idea why
Thanks
Decebal