16 Mar
2005
16 Mar
'05
7:14 p.m.
I'm not sure but can suggest you to use asterisk_b2bua (
http://developer.berlios.de/projects/b2bua/ ) and try with asterisk options
about simultenuous calls or write agi script that restricts them. I read
something about setgroup and restriction of simultenuous calls here
http://www.voip-info.org/tiki-likepages.php?page=Asterisk+sip+insecure .
But don't remember exactly the link.
Regards,
Steve
----- Original Message -----
From: "Richard" <richard(a)o-matrix.org>
To: "'Iqbal'" <iqbal(a)gigo.co.uk>
Cc: <serusers(a)lists.iptel.org>
Sent: Wednesday, March 16, 2005 8:04 PM
Subject: RE: [Serusers] using sipsak to send a BYE
How do you plan to prevent people making multiple
phone calls from the
same
account? E.g. the account has 20 minutes left. Call one starts, you will
kill it in 20 minutes. Call two starts almost at the same time, you will
kill it in 20 minutes. So the caller gets 40 minutes of talk time.
Richard
-----Original Message-----
From: serusers-bounces(a)iptel.org [mailto:serusers-bounces@lists.iptel.org] On
Behalf Of Iqbal
Sent: Wednesday, March 16, 2005 7:59 AM
To: somebody(a)braincrew.com; javarockx(a)gmail.com
Cc: serusers(a)lists.iptel.org
Subject: Re: [Serusers] using sipsak to send a BYE
Owe you a beer...or whatever , will try it, I am trying to kludge a
semi-prepaid solution together, I dont need pure prepaid, hence the use
of a b2bua like asterisk for it, and handling all those streams is
pointless, so am adding a rate table to ser to price the calls for me
internally, and then gonna see if I can stop the clock on some
calls....I know its not nice...but by not handling the stream I can
scale much better, and I think voip will go flat rate in 6 mnths.
tks again
Iqbal
On 3/16/2005, "braincrew.com" <somebody(a)braincrew.com> wrote:
-------
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
Sorry about using my friend email...
Steve
----- Original Message -----
From: "Pavel Siderov - Hostmates" <pi(a)hostmates.com>
To: "Java Rockx" <javarockx(a)gmail.com>
Cc: <serusers(a)lists.iptel.org>
Sent: Wednesday, March 16, 2005 7:39 PM
Subject: Re: [Serusers] using sipsak to send a BYE
> Attaching my ser.cfg (with little changes - the ips)
>
> Regards,
> Steve
>
> ----- Original Message -----
> From: "Java Rockx" <javarockx(a)gmail.com>
> To: "braincrew.com" <somebody(a)braincrew.com>
> Cc: <serusers(a)lists.iptel.org>
> Sent: Wednesday, March 16, 2005 7:11 PM
> Subject: Re: [Serusers] using sipsak to send a BYE
>
>
>> My problems last week regarding missing BYE messages at our PSTN GW
>> were due to a bug in my loose_route() logic. Basically I was doing
>> naughty things if loose_route() was TRUE, when I should have only
>> been
>> using t_relay().
>>
>> In your case I'd say make sure you have the accounting flag set when
>> you receive a BYE or CANCEL message. You can set this flag
>> immediately
>> after your "sanity checks" at the top of the main route block.
>>
>> Regards,
>> Paul
>>
>>
>> On Wed, 16 Mar 2005 19:07:16 +0200, braincrew.com
>> <somebody(a)braincrew.com> wrote:
>>> Hi Paul,
>>>
>>> many thanks to your replies last week about user agent expiration
(Sorry
>>> for
>>> not thanking you but
>>> just working ... 24 hours these days :( ).
>>>
>>> I'm facing the similar issue with the byes on the side of ser. My
B2BUA
>>> sends bye to ser but bye
>>> is not recorded in the database at about less than 10% of the calls.
You
>>> have some idea what
>>> maybe the case ?
>>>
>>> Thanks in advance :),
>>> Steve
>>>
>>>
>>> ----- Original Message -----
>>> From: "Java Rockx" <javarockx(a)gmail.com>
>>> To: "Iqbal" <iqbal(a)gigo.co.uk>
>>> Cc: <serusers(a)lists.iptel.org>
>>> Sent: Wednesday, March 16, 2005 5:12 AM
>>> Subject: Re: [Serusers] using sipsak to send a BYE
>>>
>>> >I have. During my debugging with a 3rd party PSTN GW provider I
>>> > sometimes didn't send them a BYE message and they couldn't close
their
>>
> billing record.
>> >
>> > So I stored this in a file and used sipsak to close their billing
>> > record.
>> >
>> > BYE sip:5135551234@216.229.118.76:4060 SIP/2.0
>> > Route: <sip:216.229.127.60:5060;lr>
>> > From: sip:5135551234@64.152.60.6;user=phone
>> > To: sip:9145550000@66.243.109.99:5060;user=phone
>> > Contact: sip:9145550000@66.243.109.99:5060;user=phone
>> > CSeq: 42759 BYE
>> > Call-ID: 9787963-3319555348-76751(a)66.243.109.99
>> > User-Agent: Grandstream BT100 1.0.5.11
>> > Max-Forwards: 16
>> > Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE
>> > Content-Length: 0
>> >
>> > sipsak -f <filename> -s sip:<some IP address>
>> >
>> > Regards,
>> > Paul
>> >
>> > On Wed, 16 Mar 2005 03:07:05 GMT, Iqbal <iqbal(a)gigo.co.uk> wrote:
>> >>
>> >> Hi
>> >>
>> >> Has anyone done this successfully to hangup a call.
>> >>
>> >> Iqbal
>> >>
>> >> _______________________________________________
>> >> Serusers mailing list
>> >> serusers(a)lists.iptel.org
>> >> http://lists.iptel.org/mailman/listinfo/serusers
>> >>
>> >
>> > _______________________________________________
>> > Serusers mailing list
>> > serusers(a)lists.iptel.org
>> > http://lists.iptel.org/mailman/listinfo/serusers
>> >
>>
>>
>
> _______________________________________________
> Serusers mailing list
> serusers(a)lists.iptel.org
> http://lists.iptel.org/mailman/listinfo/serusers
>
------------------------------------------------------------------------- _______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers