I setup ser 0.8.1.2 on fedora core 2.
For some reason I cannot register to the proxy.
SEND TIME: 74104781
SEND >> 192.168.10.105:5060
REGISTER sip:192.168.10.105 SIP/2.0
Via: SIP/2.0/UDP
192.168.10.74:5060;rport;branch=z9hG4bK66CA3AADDEB546D2A7D2120C272E1A01
From: shi2 <sip:shi2@192.168.10.105>;tag=2675096432
To: shi2 <sip:shi2@192.168.10.105>
Contact: "shi2" <sip:shi2@192.168.10.74:5060>
Call-ID: CB68D1EE40E94F5EB33C98D96E9AA8F4(a)192.168.10.105
CSeq: 32167 REGISTER
Expires: 3600
Max-Forwards: 70
User-Agent: X-Lite release 1103a
Content-Length: 0
RECEIVE TIME: 74104812
RECEIVE << 192.168.10.105:5060
SIP/2.0 483 Too Many Hops
Via: SIP/2.0/UDP
192.168.10.74:5060;rport=5060;branch=z9hG4bK66CA3AADDEB546D2A7D2120C272E
1A01
From: shi2 <sip:shi2@192.168.10.105>;tag=2675096432
To: shi2
<sip:shi2@192.168.10.105>;tag=b27e1a1d33761e85846fc98f5f3a7e58.653f
Call-ID: CB68D1EE40E94F5EB33C98D96E9AA8F4(a)192.168.10.105
CSeq: 32167 REGISTER
Server: Sip EXpress router (0.8.12 (i386/linux))
Content-Length: 0
Warning: 392 192.168.10.105:5060 "Noisy feedback tells: pid=13463
req_src_ip=192.168.10.105 req_src_port=5060 in_uri=sip:192.168.10.105
out_uri=sip:192.168.10.105 via_cnt==71"
(Btw - the SER machine is the first hop).
At first I thought there was a problem at the ser.conf so I disabled the
Max-Forwards test.
What I got then was a server error ( the sl_reply_error();)
I guess that for some strange reason the proxy/system cannot decode the
sip messages.
(mf_process_maxfwd_header() - returns error when it cannot read the
Max-Forwards header and the ser.conf script just jumps over the register
process)
Any help would be great.
Shi Hoch
IP High Technologies Ltd.
shi(a)i-p-hi.com
Hi,
You could use RADIATOR...
kaiser
> Date: Sat, 03 Jul 2004 18:20:36 +0200
> From: Kai Militzer <kai(a)militzer.net>
> Subject: [Serusers] Ser RADIUS-Modules and Radiator!
> To: serusers(a)lists.iptel.org
> Message-ID: <1088871616.9589.3.camel@mobi>
> Content-Type: text/plain
>
> Hello everyone!
>
> Just one short question before I start searching in the wrong places
> and/or post messages on the list, that are not needed and will be to no
> help for anyone!
>
> Do the radius-modules only work with freeradius as server or can I use
> any radius-server such as Radiator?
>
> Thanks for any answers you will send.
>
> Best regard
>
> Kai
>
Please upgrade to latest 1.1.0
Adrian
----------
Hello,
Please adivse if someone have had the following error in
mediaproxy-1.0.1 (i
am using lates CVS ser).
proxydispatcher[12304]: ----------------------------------------
proxydispatcher[12304]: Exception happened during processing of request
from
proxydispatcher[12304]: Traceback (most recent call last):
proxydispatcher[12304]: File
"/usr/local/lib/python2.3/SocketServer.py",
line 463, in process_request_thread
proxydispatcher[12304]: self.finish_request(request,
client_address)
proxydispatcher[12304]: File
"/usr/local/lib/python2.3/SocketServer.py",
line 254, in finish_request
proxydispatcher[12304]: self.RequestHandlerClass(request,
client_address, self)
proxydispatcher[12304]: File
"/usr/local/lib/python2.3/SocketServer.py",
line 521, in __init__
proxydispatcher[12304]: self.handle()
proxydispatcher[12304]: File
"/etc/ser/mediaproxy/modules/dispatcher.py",
line 205, in handle
proxydispatcher[12304]: result = self.execute(command)
proxydispatcher[12304]: File
"/etc/ser/mediaproxy/modules/dispatcher.py",
line 238, in execute
proxydispatcher[12304]: proxy = self.proxyFor(domain)
proxydispatcher[12304]: File
"/etc/ser/mediaproxy/modules/dispatcher.py",
line 338, in proxyFor
proxydispatcher[12304]: proxies = proxyList(domain)
proxydispatcher[12304]: File
"/etc/ser/mediaproxy/modules/dispatcher.py",
line 294, in proxyList
proxydispatcher[12304]: answers =
DNS.DnsRequest().req(name=mediaproxyrec, qtype='SRV').answers
proxydispatcher[12304]: File
"/etc/ser/mediaproxy/modules/external/DNS/Base.py", line 173, in req
proxydispatcher[12304]: self.sendUDPRequest(server)
proxydispatcher[12304]: File
"/etc/ser/mediaproxy/modules/external/DNS/Base.py", line 193, in
proxydispatcher[12304]: self.response=self.processUDPReply()
proxydispatcher[12304]: File
"/etc/ser/mediaproxy/modules/external/DNS/Base.py", line 89, in
processUDPReply
proxydispatcher[12304]: raise DNSError, 'Timeout'
Hello,
Please adivse if someone have had the following error in mediaproxy-1.0.1 (i
am using lates CVS ser).
proxydispatcher[12304]: ----------------------------------------
proxydispatcher[12304]: Exception happened during processing of request
from
proxydispatcher[12304]: Traceback (most recent call last):
proxydispatcher[12304]: File "/usr/local/lib/python2.3/SocketServer.py",
line 463, in process_request_thread
proxydispatcher[12304]: self.finish_request(request, client_address)
proxydispatcher[12304]: File "/usr/local/lib/python2.3/SocketServer.py",
line 254, in finish_request
proxydispatcher[12304]: self.RequestHandlerClass(request,
client_address, self)
proxydispatcher[12304]: File "/usr/local/lib/python2.3/SocketServer.py",
line 521, in __init__
proxydispatcher[12304]: self.handle()
proxydispatcher[12304]: File "/etc/ser/mediaproxy/modules/dispatcher.py",
line 205, in handle
proxydispatcher[12304]: result = self.execute(command)
proxydispatcher[12304]: File "/etc/ser/mediaproxy/modules/dispatcher.py",
line 238, in execute
proxydispatcher[12304]: proxy = self.proxyFor(domain)
proxydispatcher[12304]: File "/etc/ser/mediaproxy/modules/dispatcher.py",
line 338, in proxyFor
proxydispatcher[12304]: proxies = proxyList(domain)
proxydispatcher[12304]: File "/etc/ser/mediaproxy/modules/dispatcher.py",
line 294, in proxyList
proxydispatcher[12304]: answers =
DNS.DnsRequest().req(name=mediaproxyrec, qtype='SRV').answers
proxydispatcher[12304]: File
"/etc/ser/mediaproxy/modules/external/DNS/Base.py", line 173, in req
proxydispatcher[12304]: self.sendUDPRequest(server)
proxydispatcher[12304]: File
"/etc/ser/mediaproxy/modules/external/DNS/Base.py", line 193, in
proxydispatcher[12304]: self.response=self.processUDPReply()
proxydispatcher[12304]: File
"/etc/ser/mediaproxy/modules/external/DNS/Base.py", line 89, in
processUDPReply
proxydispatcher[12304]: raise DNSError, 'Timeout'
proxydispatcher[12304]: DNSError: Timeout
proxydispatcher[12304]: ----------------------------------------
/usr/local/sbin/ser[11497]: error: use_media_proxy(): empty response from
mediaproxy
Ri Liang
Hello everyone!
Just one short question before I start searching in the wrong places
and/or post messages on the list, that are not needed and will be to no
help for anyone!
Do the radius-modules only work with freeradius as server or can I use
any radius-server such as Radiator?
Thanks for any answers you will send.
Best regard
Kai
Hello everyone!
Just one short question before I start searching in the wrong places
and/or post messages on the list, that are not needed and will be to no
help for anyone!
Do the radius-modules only work with freeradius as server or can I use
any radius-server such as Radiator?
Thanks for any answers you will send.
Best regard
Kai
Hi,
I have a syntax error in serweb (user_interface) when trying to click on the
"missed calls" or "accounting" tabs.
The error is as shown:
DB Error: syntax error, file:
/var/www/iptel/html/data_layer/missed_calls.php:63
DB Error: syntax error, file:
/var/www/iptel/html/data_layer/accounting.php:50
The installation is with ser+serweb+mysql (all compiled from CVS source
today. Version of ser 0.8.13-dev-31).
The tables were created with the shell script privided with the CVS version
of ser.
The versions of php4 is 4.3.3
I looked in the php files
In both files_calls, the offending line is:
$res=$this->db->query($q);
I'm at a loss why this error would occur.
any hints?
Dave.
Is possible that SER send a reply (ex: 487 request cancelled) at the expiration of the "fr_inv_timer" and this reply cant be handled by the "t_on_reply" command ??? I see this when a call expire fr_inv_timer (calee dont answer) and cause the imposibility to instruct the mediaproxy to end the session.
My ser.cfg like to be ok, when i cancel the call (after expire of fr_inv_timer) the CANCEL is handled by onreply_route and after eval the status i can do a end_media_proxy();
Thanks
Ezequiel Colombo
Hi
Yes, using the "!" instead makes it work. Is it common to use other
delimiters, since the Cisco SIP proxy parses correctly when using the
"wrong" delimiters? I know what the RFC says, but just wondering.
rgds and thanks for the help,
/Staffan
-----Ursprungligt meddelande-----
Från: Juha Heinanen [mailto:jh@tutpro.com]
Skickat: den 24 juni 2004 17:09
Till: Zeus Ng
Kopia: Kerker Staffan; serusers(a)lists.iptel.org
Ämne: RE: [Serusers] ENUM parsing error?
Zeus Ng writes:
> I'm not 100% sure, but I think enum module expect "!" as the delimiter for
> regexp. You may try:
>
> $ORIGIN 1.2.2.e164.mydomain.com.
> 0 NAPTR 100 10 "u" "sip+E2U" "!^(.*)$!sip:\\1@iptel2.mydomain.com!" .
that is right. currently enum module assumes that regexp delimiter is
"!", which seems to be a common convention and in etsi enum spec is
SHALL. i could make it more general, but right now i have other, higher
priority things to worry about.
-- juha
Hello,
can anyone explain to me the following error meesages
when I intend to start serweb by calling either
"user_interface" or "admin" index.php.
how to fix it.
=====================
Warning: Access denied for user: 'ser(a)mydomain.com'
(Using password: YES) in /var/www/phplib/db_mysql.inc
on line 73
Database error: pconnect(192.168.1.253, ser,
$Password) failed.
MySQL Error: ()
Session halted.
=======================
thank you/Linda
__________________________________________________
Do You Yahoo!?
Log on to Messenger with your mobile phone!
http://sg.messenger.yahoo.com
