Hello,
How/Where would be the best place to purposely drop a particular reply
message ( > 400 )
I have armed both the reply route and failure route and attempted to drop
the message by calling the drop() function but this doesn't seem to work.
Is there a simple method for conditionally dropping a reply message?
My goal is to force the UAC that created the original request to retransmit
(UDP) the request in certain scenarios, such as when ACK to an initial
invite has not been fully processed by the downstream UAS but a re-invite
has been received by the UAS causing the UAS to return a 400 for the
re-invite. I do not want the UAC to see the 400 reply, instead I simply
want the UAC to resend the re-invite because no final response has been
received, presumably by this time the ACK processing will be finished and
the retransmitted re-invite would be handled smoothly.
I realize replies are routed based on via headers. Is there some way to
short circuit this routing other than drop()?
Thanks
Tim
Tried this from failure route
if(t_check_status("400"))
{
xlog( "L_ERR", "400 message in failure route 2 **********
\n" );
drop();
return;
}
Tried this from reply route
if(status == "400")
{
xlog( "L_ERR", "400 in reply route 2 .... dropping\n" );
drop();
return;
}
I have tried all sorts of configurations with both rtpproxy and media
proxy, but I continue to end up with audio only working on one end of
the call. The latest I tried to turn on rtpproxy for all calls. The
call goes through but audio is only heard from the callee to the caller.
Any help is greatly appreciated.
Taylor
Change log
xcap-lite (1.0.0) unstable; urgency=low
* Added control interface for OpenSER to inform the Presence agent
about
changes in the presrules document. This allows the presence
server to
imediately send Notify to the updated buddy list after the end-user
changes his presence policy document. Thanks to Anca Vamanu and
Juha
Heinanen for the support provided for adding this critical
functionality
* The configuration config.php has changed to allow for definition
of the
OpenSER management interface URL (refreshWatchersURL)
* OpenSER must have the mi_xmlrpc module loaded and listening on
the port
configured in config.php
* Fixed query in updateWatchers function
* OpenSER trunk version 2230 or higher is required when
refreshWatchersURL
setting is enabled in config.php
The software can be downloaded from:
http://download.dns-hosting.info/XCAP/xcap-lite-1.0.0.tar.gz
Regards,
Adrian
I may be misunderstanding things (very probably so), but all the
examples for both SER and OpenSER that I have seen either do not do
NAT or NAT but are not the "end point" for a UAC to the PSTN. From
what I can tell they are just sending on the SIP request to the next
destination as is. The setup I am trying to accomplish is
* SIP clients are all on a private network with connectivity to
OpenSER directly on one interface (on the same private network)
* OpenSER's other interface is on the external network (internet
facing)
* SIP clients are only sending telephone numbers
(sip:telephone_number@*... do not know about PSTN providers)
* OpenSER connects to the PSTN provider and send the number to
dial that came from the SIP client
* OpenSER "proxies" the entire call (with the help of rtpproxy or
mediaproxy for RTP of course)
* No incoming calls from the internet to OpenSER (no support for
that is needed)
* Registration not required for sip clients (they are all on same
private network and authorized)
I have found several posts, example configs, documents that have
pieces of what I need (from what I can tell).. and I have tried to
put it together, but it does not quite work...
So is there some example that fits this type of usage? If not one
then possibly several pieces from a few documents? I have been
thinking that OpenSER setup as a outbound proxy configured for
multihome, but everything I have seen on that just routes the calls
through to where ever the SIP client was requesting as a final
destination and I need to send to one destination (the PSTN
provider). Any help is greatly appreciated.
BTW, I was thinking the NAThelper or outbound proxy example from
http://www.voip-info.org/wiki-SER+tips+and+tricks
Looked close to what is needed, but have a bunch of stuff (seemingly)
unneeded for my scenario and have nothing about PSTN connectivity.
Thanks for taking the time to read this long post (if you made it
this far).
Taylor
Hello,
Im having some problems with cancelled calls. This is the scenario:
U1 Proxy
U2
INVITE -->>>
<<--- 100 Trying
INVITE -->>>
<<--- 100 Trying
<<--- 100 Trying
CANCEL ->>>
<<-- 200 Cancelling
CANCEL ->> <<--
180 Ringing
<<-- 487 Cancelled
<<-- 180 Ringing
<<-- 200 OK
(Wrong??)
<<-- 200 OK
My problem is that after some time waiting for "ringing", the user
cancel the call. Even that proxy responses "487" it still forward the
late 200 OK.
Should it forward? I guess not because the transaction was destroyed, right?
Can it be a configuration problem on my ser.cfg ou it can be in t_relay
implementation?
Thanks in advanced.
Regards,
Gustavo
Hi guys,
I dont know what the problem is.. Really.. Im out of ideas with
permissions and reinstallations for serweb's CTD and IM. During my 1st
installation with serweb they both worked fine. Then I had to
reinstall my OS (Ubuntu 7.x btw) and now they give both timeouts..
I have even copied send_im() and write2fifo() functions separately
into a PHP file and ran it from command line. Same old "408 Request
Timeout".. Please, suggest something.
Im basically using nat-mediaproxy.cfg for config file and I have tried
setting various ownerships and permissions to serweb dir and for
/tmp/serweb and /tmp/ser_fifo.. Nothing helps really. All packages are
installed for php4 including php4-cli, pear, pear-log, pear-DB,
XML_RPC and even classkit (which is useless here anyway).
Hello everybody,
as we want to provide more examples for the configuration the following the
question came up:
Do you prefer
- one big example configuration
- probably harder to understand
- easier to maintain for us
- one example config file per "feature"
- probably easier to understand your desired "feature"
- you might have problems to integrate all your desired "features" into one
config without breaking anything
- harder to maintain for us, as we have to update several files :-)
As the configuration examples are indented to be for the community, I would
like to know what you prefer or if you see other options.
Thanks
Nils
Hello,
We setup a SIP SIMPLE testbed using the latest OpenSER / XCAP-lite.
To make use of this testbed you need a recent Eyebeam commercial
version for Apple or Windows. Other SIP/SIMPLE/XCAP client
implementations are of course more then welcome and desired.
To use this test bed register a SIP account at:
http://sip2sip.info
Instructions about the SIP/Presence/XCAP settings are sent by email
to the registrant.
We appreciate any feedback regarding the software behavior so that we
can fix any bugs in the used implementations and update the wiki
pages with proper configuration samples.
Thank you for your support,
Adrian
Hi,
i have some memory errors after running OpenSER one day:
May 15 02:46:56 sip-b /opt/SER/SER0/bin/openser[20106]: [ID 381148
local0.error] ERROR: build_req_buf_from_sip_req: out of memory
May 15 02:46:56 sip-b /opt/SER/SER0/bin/openser[20106]: [ID 933771
local0.error] ERROR:tm:print_uac_request: no pkg_mem
May 15 02:46:56 sip-b /opt/SER/SER0/bin/openser[20106]: [ID 826633
local0.error] ERROR:tm:t_forward_nonack: failure to add branches
May 15 02:47:00 sip-b /opt/SER/SER0/bin/openser[20106]: [ID 381148
local0.error] ERROR: build_req_buf_from_sip_req: out of memory
May 15 02:47:00 sip-b /opt/SER/SER0/bin/openser[20106]: [ID 933771
local0.error] ERROR:tm:print_uac_request: no pkg_mem
May 15 02:47:00 sip-b /opt/SER/SER0/bin/openser[20106]: [ID 826633
local0.error] ERROR:tm:t_forward_nonack: failure to add branches
May 15 02:47:03 sip-b /opt/SER/SER0/bin/openser[20106]: [ID 381148
local0.error] ERROR: build_req_buf_from_sip_req: out of memory
May 15 02:47:03 sip-b /opt/SER/SER0/bin/openser[20106]: [ID 933771
local0.error] ERROR:tm:print_uac_request: no pkg_mem
Version: OpenSER 1.2.0
OS: Solaris 10
Arch: Sparc
Is there a memory leak an any module? or is my memory too low?