Hello all,
I am trying to get this Polycom phone to register with TLS but with no luck.
Can anyone help me with what certificate are you guys using,is it ur own or
the defalut certificate.This phone doesn't seem to be liking my certificate
netiher its able to register with the default certificate.
Also anything with the firmware since I am not able to get this phone
registered as well.
Any help would be appreciated.
Thanks,
Sheetal
I'm getting an odd Via parsing error from SER 0.9.6:
Feb 23 16:52:49 death ser[17389]: error: parse_via_param
Feb 23 16:52:49 death ser[17389]: ERROR: parse_via on: <sip/2.0/udp
172.30.237.149:56755;branch=z9hg4bk-d87543-d75bc86d826ac929-1--d87543->
Feb 23 16:52:49 death ser[17389]: ERROR: parse_via parse error, parsed so
far:<sip/2.0/udp
172.30.237.149:56755;branch=z9hg4bk-d87543-d75bc86d826ac929-1--d87543->
Feb 23 16:52:49 death ser[17389]: ERROR: get_hdr_field: bad via
Feb 23 16:52:49 death ser[17389]: ERROR: parse_msg: message=<REGISTEl
sip:proxy.ideasip.com SIP/2.0>
Feb 23 16:52:49 death ser[17389]: ERROR: receive_msg: parse_msg failed
When I look at the packet, it looks like the actual SIP data is somehow
getting garbled... with odd characters showing up in the middle of headers, etc.
Any idea what might cause this?
U 148.233.151.30:43764 -> XX.XX.XX.XX:5060
REGISTEl sip:proxy.ideasip.com SIP/2.0.
Via: sip/2.0/udp
172.30.237.149:16240;branch=z9hg4bk-d87543-9332b73b5700e95c-1--d87543-.
Max-Forward2a:70.
Contactm:<sip:user@148.233.151.30:32332;rinstance=6c0c8351d99e79db>.
To: "mario"<sip:user@proxy.ideasip.com>.
From: "mario"<sip:user@proxy.ideasip.com>;tag=fe132761.
Call-ID: n2m5owi1odc4mzkznmm5mjflmzvmzmu3zgjmngqym2y..
CSe1h:1 register.
Expire1k:3600.
Allo0b:invite, ack, cancel, options, bye, refer, notify, message, subscribe, info.
User-Agen5m:x-lite release 1006e stamp 34025.
Content-Lengthl:0.
As you can see... things like REGISTEl, Max Forward2a: Expire1k:
All these things look garbled. Would this be a transmission error of some
kind (the garbled headers are identical for each submitted packet, though, so
it seems unlikely) ?
N.
Hi,
I would like to set up LCR and failover routing in my openser. I want
to find some working examples on how i can set that up. Can someone
point me to the right direction please?
If any one can offer me a sample config that will be great.
--
Howard Tang
I'm glad to inform all the members of the list that ALL modules, from ALL
OpenSER versions (0.9.x, 1.0.x, 1.1.x and 1.2.x) have been updated and
included on the Wiki page (http://www.openser.org/dokuwiki/doku.php/start).
All index are presented in a table format with three columns: the first has
the name of the 'thing' being referenced; the second the module from where
that reference came from; and the third is for user comments.
All indexes were generated after the files on the web, so it's possible that
there are some inconsistences between this files and the ones on CVS. Please
let me know about any update, so that I can re-run the script to update the
indexes.
Due to automatization, some documentation problems pops up. like the use of
a '$' sign in front of a MI command on the dialog module. They are others.
what I found I corrected manually..
So, feel free to use it, and don't forget to re-inform the list about any
changes on the original files. Sugestions, as always, are welcome. ;)
Edson.
Note: forwarded message attached.
____________________________________________________________________________________
We won't tell. Get more on shows you hate to love
(and love to hate): Yahoo! TV's Guilty Pleasures list.
http://tv.yahoo.com/collections/265
Hello, i am using the ser 0.8.12 and i am getting the next error in the
logs:
Feb 22 09:47:13 117 /usr/sbin/ser[11779]: ERROR: warning_builder: buffer
size exceeded
Feb 22 09:47:13 117 /usr/sbin/ser[11779]: WARNING: warning skipped -- too
big
Feb 22 09:47:16 117 /usr/sbin/ser[11779]: ERROR: warning_builder: buffer
size exceeded
Feb 22 09:47:16 117 /usr/sbin/ser[11779]: WARNING: warning skipped -- too
big
And when this happen some process block and dont permit to make and to do
calls.
Can anyone help me?
My ser is on a Red Hat enterprise linux 4
hi, thanks for your response.
is the sending of CANCEL handled by the openser engine internally? i need to do this from the openser config file. basically, my statement is like this:
onreply_route[2] {
if (status =~ "(183)|(2[0-9][0-9])") {
if (client_nat_test("1")) {
fix_contact();
append_hf("P-hint: Reply applied\r\n");
}
use_media_proxy();
}
if (status == "200") {
invoke_my_function_from_here("$fu:$tu:$ci");
if (retcode == 1)
{
# propagate OK to caller; do nothing
}
else
{
# terminate or cancel INVITE from here
}
}
}
i should also be able to do this in proxy1 from the figure below. i think i need to send CANCEL to UAC1 and BYE to UAC2. this is my understanding of the RFC. someone may have implemented a function or module to handle this. thanks again.
"Premnath, KN" <Premnath.KN(a)siemens.com> wrote: Hi Sho,
When you get 200OK, you send an "ACK", so it is a good indication for the initial "INVITE" that it is ACKnowledged. When you get an error, anyway you will not send "ACK" instead still send the "CANCEL" so the UAC2 is clearly handled (and it will not wait for ACK), give a try !!!
Thank You,.
With warm regards,
Premnath Narayanan
---------------------------------
From: users-bounces(a)openser.org [mailto:users-bounces@openser.org] On Behalf Of Web Monkey
Sent: Monday, February 26, 2007 9:24 AM
To: users(a)openser.org; users(a)iptel.org
Subject: [Users] cancelling INVITE during OK response
hi, is there a way to cancel or terminate an INVITE or call upon receipt of the OK reply. my configuration invokes an external program which either return success or failure for OK message (response to INVITE). when failure is returned, i want the script to terminate the call or cancel the INVITE (OK message will not be forwarded to the calling UA). is there an existing function or module to realize this? the scenario is drawn below with provisional messages removed.
UAC1 ------------------ proxy1 ----------------- proxy2 --------------- UAC2
call:
INVITE
---------------------------> INVITE
----------------------> INVITE
----------------->
OK
<----------------
*XXX
- error occurred
during processing
OK message
thanks,
sho
---------------------------------
It's here! Your new message!
Get new email alerts with the free Yahoo! Toolbar.
The new company Nokia Siemens Networks is expected to start operations in the first quarter of 2007, subject to customary regulatory approvals, the completion of standard closing conditions, and the agreement of a number of detailed implementation steps.
Disclaimer:
This e-mail may contain trade secrets or privileged, undisclosed or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation.
---------------------------------
Check out the all-new Yahoo! Mail beta - Fire up a more powerful email and get things done faster.
Ladies and gentlemen,
I'm glad to invite you to a meeting of SER users and developers in March 2007, in Prague,
Czech Republic. See more at http://www.iptel.org/ietf_meeting
I'm looking forward to seeing you there. In the meantime, please register yourself if you
plan to attend and don't hesitate to make any agenda suggestions -- SER related ideally,
even though any "social" suggestions are perfectly fine too.
I can promise you it will be a wonderful event -- Prague is beatiful, SER is beatiful,
and so is the folks involved in SER development -- LET'S MEET!
-jiri
--
Jiri Kuthan http://iptel.org/~jiri/
Hi!
I have a problem with mediaproxy 1.8. Whenever a session is deleted
there is an exception:
Feb 14 14:18:27 foobar mediaproxy[27053]: delete
OGI3Nzk1N2ExODY4NTIzYzIxMjc1NmYxN2MwMDBiZjU. info=
Feb 14 14:18:27 foobar mediaproxy[27053]: session
OGI3Nzk1N2ExODY4NTIzYzIxMjc1NmYxN2MwMDBiZjU.: 10558/10557/21113 packets,
778927/774750/1553531 bytes (caller/called/relayed)
Feb 14 14:18:27 foobar mediaproxy[27053]: session
OGI3Nzk1N2ExODY4NTIzYzIxMjc1NmYxN2MwMDBiZjU.: ended.
Feb 14 14:18:27 foobar mediaproxy[27053]: error: uncaptured python
exception, closing channel <rtphandler.CommandHandler connected
5.6.7.8:38879 at 0xb7d255ec> (exceptions.NameError:global name
'StopRecordSerializer' is not defined
[/usr/lib/python2.3/asyncore.py|readwrite|86]
[/usr/lib/python2.3/asyncore.py|handle_read_event|390]
[/opt/mediaproxy/modules/rtphandler.py|handle_read|441]
[/opt/mediaproxy/modules/rtphandler.py|process|568])
Feb 14 14:19:53 foobar mediaproxy[27053]: status
Feb 14 14:19:53 foobar mediaproxy[27053]: execution time: 0.11 ms
I could not find the problem - accounting.py with StopRecordSerializer
is there, and it is imported in rtphandler.
Do others also have problems and maybe a workaround?
regards
klaus
--
Klaus Darilion
nic.at