I have same problem in xmpp messages , I can not understand well those module's configure (jabber.so ,pa.so),Can I used the jid as a ser account?
Thanks
Zhaomin
----- Original Message -----
From: "Steven Poveda" <stepoca(a)hotmail.com>
To: <serusers(a)iptel.org>
Sent: Wednesday, May 25, 2005 6:42 AM
Subject: [Serusers] How to configure pa?
> Hi,
>
> I have just installed SER and I can see the server is not supporting PUBLISH method. I have loaded pa module but the reject to PUBLISH method is stil there.
>
> Where can I find information regarding pa configuration ?
>
> Regards,
>
> Steven
>
>
>
>
> --------------------------------------------------------------------------------
> Don't just search. Find. MSN Search Check out the new MSN Search!
--------------------------------------------------------------------------------
> _______________________________________________
> Serusers mailing list
> Serusers(a)iptel.org
> http://mail.iptel.org/mailman/listinfo/serusers
>
Hi,
I am trying to get an ATA phone working for SER server.
Now the ATA phone can receive calls from softphone(kphone) on a PC,
while it cannot call out. (softphone, ATA phone and SER server are in
the same subnet)
$ serctl ul show 100
<sip:100@192.168.1.100:5600>;q=0.00;expires=802
Any idea on how to resolve the problem? Thanks!
--
Best regards,
Min
Hello,
is it possible to use add_rcv_param() also for Contact-HF of INVITEs,
instead of fix_nated_contact()?
This would make sure that the NATed End Device gets fed exactly the
contact as R-URI that it announced in the INVITE:
Example R-URI in Loose-Route Requests for fix_nated_contact():
Ser (1.2.3.4):
INVITE device(a)4.5.6.7
Route: 1.2.3.4;lr=on
Device (10.0.0.1, NAT 4.5.6.7):
INVITE device(a)123.123.123.123
With add_rcv_param():
Ser:
INVITE device(a)10.0.0.1;rcv_param=4.5.6.7
Route: 1.2.3.4;lr=on
Device:
INVITE device(a)10.0.0.1
The problem is that the End-Device, in the fix_nated_contact() callflow,
has to accept a Request that is not really for this device (IP in
Request-URI != IP of the Device). Imagine a Ser checkip uri == myself.
This would fail without knowing the public IP of the NAT and
hard-conding it into Ser.cfg.
Does Ser support the rcv_param in Request-URI also?
What do you think? Any experience on this?
Regards,
Martin
Hi,
Whenever I uncomment i change the integer value of
modparam("usrloc", "db_mode", 0) changed to 1 or 2 and when i about to
restart SER using ./serctl stop then ./serctl start, SER strat but when
i check ps aux | grep ser no SER is running. I checked /var/log/debug/
and i got this messages:
Jun 9 00:45:10 sip ./ser[7553]: DEBUG: tm_shutdown : start
Jun 9 00:45:10 sip ./ser[7553]: DEBUG: tm_shutdown : empting DELETE list
Jun 9 00:45:10 sip ./ser[7553]: DEBUG: tm_shutdown : empting hash table
Jun 9 00:45:10 sip ./ser[7553]: DEBUG: tm_shutdown: releasing timers
Jun 9 00:45:10 sip ./ser[7553]: DEBUG: tm_shutdown : removing semaphores
Jun 9 00:45:10 sip ./ser[7553]: DEBUG: tm_shutdown : done
Jun 9 00:45:10 sip ./ser[7553]: shm_mem_destroy
Jun 9 00:45:10 sip ./ser[7553]: destroying the shared memory lock
Whats the meaning of destroying the shared memory lock? I'm running SER
on FreeBSD/sparc64.
Thanks,
--
Ryan Pagquil
Infodyne Inc. - PhilOnline.com
3603 Antel Global Corporate Center
Doña Julia Vargas Ave.
Ortigas Center Pasig City
Tel: 687-0715
Web: www.philonline.com
Just my 2 cents....
Since SER is transaction aware and not dialog aware, it is not easy to maintain consistent Cseq values during a dialog. I'm sure UAC maintainers are thinking on it and they will come with a solution, but just let them work without stress ;)
However, don't think the UAC approach is the right one having TLS around......I would prefer pushing for TLS instead of adding a table of existing dialog in SER with the appropriate values. I'm sure there's lots of providers reading this list so if everybody starts asking for TLS....well, big providers will start providing it for auth. I'm not an expert but I've been told implementing TLS is not a hard job....;)
Samuel.
Unclassified.
>>> "Greger V. Teigre" <greger(a)teigre.com> 06/09/05 07:18AM >>>
Michael Ulitskiy wrote:
> Greg, do you really believe that avoiding added, but optional
> complexity
> is good enough reason for not having IMHO necessary functionality?
Not at all. My point was that it is extremely important to add functionality
where it belongs logically and where you can ensure that regular ser.cfg
users are able to use the functionality without understanding the specs.
> Again, IMHO, having something better than ip auth is a must in
> today's internet.
Again, I agree.
> On the subject:
> I guess the reason is, as I said before, that not only cseq in
> original invite must be incremented, but cseq in all subsequent
> in-dialog messages must
> be adjusted (decremented for messages relayed to callee and
> incremented
> for messages relayed to called party). That is what, I guess, is hard
> to do in today's ser.
> I've posted my thoughts on how it possibly could be accomplished
> at http://lists.iptel.org/pipermail/serdev/2005-May/004589.html and
> haven't received any feedback or comments.
> I guess either there's a lack of interest for getting it to work
> which I guess is really strange or it's too hard to implement at
> current stage.
> As always any comments are welcome :)
I don't think it's a lack of interest or lack of need for it. All the
developers are bombarded with requests and have long lists of core things to
do. Sometimes its even hard to get them to evaluate and include patches in
CVS.
IMHO, increment cseq belongs in the UAC module (can do far too much harm
if users play around with it). If you cannot get the maintainers attention,
there is only one way: Get your hands dirty ;-)
g-)
_______________________________________________
Serdev mailing list
serdev(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serdev
First of all: there's no need to send the e-mail more than once...it will just make people not answering.
Probably what happens is that you have the old libraries (the ones you compiled with the HEAD version of SEMS) and SEMS rel_0.8.12. Be sure the libraries are correct.
Samuel
Unclassified.
>>> Llanos Serna García-Conde <llanosserna(a)hotmail.com> 06/09/05 09:49AM >>>
Hi all, I'm trying to make SEMS work.
First I was working with SER 0.8.14 and SEMS cvs but I always got the error consume_request(): consumed.
I only want SEMS for voicemail, so the list recommended that I downloaded the SEMS rel_0.8.12, which is supposed to be compatible with SER 0.8.14, but when loading the plug-ins I get errors about undefined symbols. I've been reading previous posts and it seems that it's either an incompatibility between versions, or that SEMS is working with another version's modules or something like that. I don't know how to solve this. Here are the errors I'm getting:
Configuration:
configuration file: /usr/local/etc/sems/sems12.conf
Ser's FIFO: /tmp/ser_fifo
our FIFO: /tmp/am_fifo
plug-in path: /usr/local/src/sems_rel_0_8_12/lib
daemon mode: 0
local IP: 172.25.97.19
(4851) DEBUG: main (sems.cpp:386): Loading application plug-ins
(4851) DEBUG: load (AmPlugIn.cpp:89): loading /usr/local/src/sems_rel_0_8_12/lib/apps/bot.so ...
(4851) ERROR: loadPlugIn (AmPlugIn.cpp:103): AmPlugIn::loadPlugIn: /usr/local/src/sems_rel_0_8_12/lib/apps/bot.so: undefined symbol: _ZN12AmRequestUAC7dialoutERKSsS1_S1_S1_
(4851) ERROR: load (AmPlugIn.cpp:91): while loading plug-in '/usr/local/src/sems_rel_0_8_12/lib/apps/bot.so'
(4850) WARNING: sig_usr_fifo (sems.cpp:84): signal 17 received
(4850) INFO: sig_usr_fifo (sems.cpp:93): finished
Please help, thanks a lot,
Llanos
I have installed the cvs head version of ser as of today. Ser seems to start
OK but serctl moni reports:
Error opening ser's FIFO /tmp/ser_fifo
Make sure you have line fifo=/tmp/ser_fifo in your config
I am using the same ser.cfg file as was running successfully on v 0.9.0.
Could anyone advise what I'm doing wrong?
ser.cfg
debug=3
fork=yes
log_stderror=yes
dns=no
rev_dns=no
fifo="/tmp/ser_fifo"
fifo_db_url="mysql://user:pword@localhost/ser"
sock_mode=0666
listen=ip.ip.ip.ip
port=5060
children=4
Regards
Cameron