Hi Jeff,
Jeff Kronlage wrote:
Anca,
Thanks for the quick reply. I tried as you suggested, on a development box,
and while it didn't work, it did look a lot more like what I was expecting to
see.
However, I guess I am looking for more of a tack on solution for what I've
already
Indiver,
X-Lite might sent those commands not in plain text, but HTML embedded.
The _very first_ character in the body of the message must be a sharp (i.e.,
#). As HTML starts , it is not considered as a command.
Try using sipsak or some client where you can force plain text to create the
Hi Sebastian,
Thanks for quick reply. As per your suggestion i tried from sipsak the
#create chat-000 private command. But it is taking it as '' only it is not
recognizing #. Is the above code enough for creating chat rooms. If so from
where i can send the join,create chat commands.Thanks in
There is really one one param that is needed to be configured in opensiops
and openxcap. And I did it correctly on both. That is the xmlrpc port. After
I restart openxcap and opensips I see no error on oenxcap now.
63.148.166.3 'PUT /xcap-root/pidf-manipulation/users/
I'm curious...
Do static or 1 to 1 natted locations produce a null resort in the received
column of the location table?
Some natted locations show received as the outside ip and contact with the
inside ip which is usually an internal ip behind a firewall.
Some others show null as the received
Hello,
I am installing the new 1.6 and getting a strange behavior.
When the call ended on one side the other side does not get disconnected,
and the log shows:
Nov 10 18:40:38 en4 /sbin/opensips[20610]: WARNING:dialog:dlg_onroute:
unable to find dialog for BYE with route param 'a94.cd4c751'
Nov
I want to know if xmlrpc is working between openxcap and opensips. OPenxcap
accepts all the data I'm trying to save from the client and sends 200 OK.
OPensips is listening to the correct xmlrpc port that I configured on
opensips.cfg.
On opensips.cfg I have :
loadmodule mi_xmlrpc.so
2009/11/10 mani sivaraman mani.opens...@gmail.com:
OPenxcap sends the Notify pidf to the
watcher with only offline status. It is not sending the full pidf with all
the tuple and person info. It sends a second Notify with no pidf payload and
with subscription status active and expires value =
Hi there
I got 2 Subnets with the addresses 192.168.1.0 and 172.31.10.0
Between those two OpenSips is a Linux Debian Gateway installed with IP
forwarding and 2 Network Interfaces.
OpenSips1 Gateway OpenSips2
My Goal is to config the OpenSips that i can call from Subnet 1 to
Subnet 2
So this might be a stupid question, but is OpenSIPS1 able to ping
OpenSIPS2??? I am wondering if you Network Gateway/Router is the issue. If
you can ping then what do you see on OpenSIPS2 when you perform an ngrep for
the SIP packets?
On Tue, Nov 10, 2009 at 8:27 PM, Duc-Lam Tran
10 matches
Mail list logo
