Hi, I'm currently using ser and CDRTool for accounting purposes.
I'd like to start accouting and thus billing on "Connection"of the
calls. 200OK should be the starting point. Actually accounting module does
start on INVITE, and end on BYE .
Is there anybody who faced the same problem before?!.
TIA.
Hi,
My SER server has running and stable now but I have plan to do PREPAID SIP
business.
Can anyone tell me what best Prepaid Billing system for SER (GPL licensed
preffered) and have web user & admin friendly ?
Thanks
Asep
Hi Users
I downloaded the openser 1.0.1 three months back, Now the OpenSER Guys
are released the latest version 1.1.0.
I downloaded the previous Version ( 1.0.10 ) by CVS , Now I want to install
openser 1.1.0 into Box...
Who can I update the latest version Now.
But from CVS download I installed in /uar/loca/src/
Openser's didn't release the CVS for latest ...
Can any one help ...
--
Thanks and Regards with cheers
Sunkara Ravi Prakash (Voip Developer)
Hyperion Technology
Kondapur, Hi-tech city,
Hyderabad.
www.hyperion-tech.com
+91-9985077535
Hi!
Scenario: sipp sends INVITE to ser, ser replies with 404. sipp sends
3000 INVITEs per second with TCP. sipp + ser on the same machine,
packets will be snet over loopback device.
Suddenly ser reports a bad message:
Jul 26 16:39:31 t4000 ser[14152]: ERROR:parse_first_line: method not
followed by SP
Jul 26 16:39:31 t4000 ser[14152]: ERROR:parse_first_line: bad message
> rtpmap:0 PCMU/8000 087637 IN IP4 83.136.32.91sg:
message=<p@83.136.32.91:5066>;tag=6688
Jul 26 16:39:31 t4000 ser[14152]: ERROR: receive_msg: parse_msg failed
Although the message captured looks fine:
INVITE sip:service@83.136.32.91:5060 SIP/2.0
Via: SIP/2.0/TCP 83.136.32.91:5066;branch=z9hG4bK-6688-0
From: sipp <sip:sipp@83.136.32.91:5066>;tag=6688
To: sut <sip:service@83.136.32.91:5060>
Call-ID: 6688-14331(a)83.136.32.91
CSeq: 1 INVITE
Contact: sip:sipp@83.136.32.91:5066
Max-Forwards: 70
Subject: Performance Test
Content-Type: application/sdp
Content-Length: 135
v=0
o=user1 53655765 2353687637 IN IP4 83.136.32.91
s=-
c=IN IP4 83.136.32.91
t=0 0
m=audio 6002 RTP/AVP 0
a=rtpmap:0 PCMU/8000
Any hints for the problem debugging?
thanks
klaus
Hi,
I am trying to implement Third-Party registration in
IMS environment using OPENSER as S-CSCF. Here is what
I want to do:
UAC
.....................................................................................S-CSCF
(Openser)
REGISTER
----------------------------------->
200 OK
<--------------------------------------
This part is working fine.
Now, S-CSCF sends separate REGISTER to Application
Server (AS) and needs to get the response. But, this
response should NOT be sent to UAC.
S-CSCF
...........................................................................
AS
REGISTER
------------------------------------->
Response
([1-6]xx
<-----------------------------------------
I tried to send this REGISTER by removing old headers
from the first REGISTER received from UAC and
creating my own (using remove_hf and append_hf). Also,
I just removed the old "via" header, and Openser
automatically added new Via header with openser ip
address.
However, when AS sends the response, S-CSCF forwards
this response to UAC even though Via header does NOT
contain the UAC IP address. Why is that? How to
stop relaying the any response received from AS to
UAC? Or else, is it possible to create a new REGISTER
request from OpenSER?
Thanks,
Vivek
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
Speaking of which: there is no documentation regarding the flag set involved
in transactions; there is a flag tutorial, but it doesn't tell:
- that one flag set in a transaction will be set automatically in the reply,
too (in the on reply route, armed in a transaction) - is this correct?
- what's the flags behaviour with multiple branches (one branch sets a flag,
can i see this flag from some other branch or which of the flags will i see
in on failure route)?
WL.
---------- Forwarded message ----------
From: SourceForge.net <noreply(a)sourceforge.net>
Date: Jul 28, 2006 2:02 AM
Subject: [Devel] [ openser-Bugs-1530057 ] Resetting flags in branch_route
resets flags for ALL branchs
To: noreply(a)sourceforge.net
Bugs item #1530057, was opened at 2006-07-27 17:02
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=743020&aid=1530057&group_…
Please note that this message will contain a full copy of the comment
thread,
including the initial issue submission, for this request,
not just the latest update.
Category: core
Group: ver 1.0.x
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: Resetting flags in branch_route resets flags for ALL branchs
Initial Comment:
I'm using branch route to trigger mediaproxy logic per
branch for UAC
directed calls and i'm experiencing some strange behavior:
t_relay() is called, there are two branches
In both branches there are two flags set
During branch_route processing of the first branch both
are left intact.
During branch_route processing of the second branch,
both are reset
(unset)
The destination UAC for the first branch picks up the
phone call,
sending a SIP OK message
This is where i'm experiencing the problem
Inside of the onreply_route both flags are NOT set,
even though they
were unset in a different call branch
This makes it impossible to properly use mediaproxy on
calls with multiple branches (because some branches may
not need mediaproxy which will break the ones that do
in some circumstances because the "200 OK" that hits
the onreply_route will not be flagged to need
mediaproxying)
This is using a recent (1-2 weeks ago) cvs checkout of
OpenSER 1.0.0
tavis
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=743020&aid=1530057&group_…
_______________________________________________
Devel mailing list
Devel(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/devel
Hi Users,
Hello to every one to openser users,
Just recently OPENSER's Guy had release the version openser 1.1.0,
THat is compactable to do or Not ?
--
Thanks and Regards with cheers
Sunkara Ravi Prakash (Voip Developer)
Hyperion Technology
Kondapur, Hi-tech city,
Hyderabad.
www.hyperion-tech.com
+91-9985077535
Hi,
I am trying to setup openser as an outgoing proxy
through VPN with the following setup:
172.16.1.1 - VPN endpoint and also the machine running
openser
172.16.1.2 - remote NAT router at Network A(another
VPN endpoint)
192.168.1.x - sjphone client behind NAT router(Network
A)
I can register the client through 172.16.1.1 fine but
dialing out to other SIP address like
613(a)fwd.pulver.com never go through.
If I register through the public address of the
machine running openser, I can make the dialing fine
and can sort of having a two way communication, though
it drops after 5 seconds for unknown reason.
I am wondering if anyone know if the first
scenario(register through VPN) is possible.
Also, how to trace why the communication drops for the
normal registration method.
thanks for any help in advance.
regards,
gary
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com