Hello All,
Has somebody any idea how to rewrite the part of the 'To'
field (165) the same as the part of header field (700403)..?
in other words, how to make the 'user' field of this part
of both messages the same?
INVITE sip:123456@20.30.40.50 SIP/2.0
To: <sip:789@myserver.com;user=phone>
~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,.
Mike Tkachuk, ph:380-3433-47067
YES ISP, fx:380-3433-47067
Valova 17, mike|a|yes.net.ua
Kolomyia, www.yes.net.ua
Ukraine 78200 FWD: 66518
23.09.2004
ICQ# 57698805
MSN: mike_tkachuk|a|hotmail.com
~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,.
I have ser-0.8.14 running on Fedora Core 2; it seems to run OK with just
a few test calls. I built the source on FC2 and ran it. As well it
seems to start fine on a reboot.
-----Original Message-----
From: serusers-bounces(a)iptel.org [mailto:serusers-bounces@lists.iptel.org] On
Behalf Of Daniel-Constantin Mierla
Sent: Monday, September 06, 2004 3:39 AM
To: Rose, John
Cc: serusers(a)lists.iptel.org
Subject: Re: [Serusers] 0.8.14 on Redhat Linux 9.0
Hello,
On 9/1/2004 11:38 PM, Rose, John wrote:
> Hello,
>
> 2 Questions:
>
> 1) Will the "ser-0.8.14_linux_i386.tar.gz" run on Redhat Linux 9.0?
> Or Fedora?
best way is to try and report the results -- none of us has a RH of
Fedora nearby -- it is up to the libraries installed into the system.
Compiling locally will be the safest way.
> 2) Just wondering if the "SER not starting up on a Redhat Linux 9.0
> reboot - 0.8.11 and 0.8.12" issue is gone or not.
There is some time since it wasn't reported anymore, but you never know
;-)
Daniel
>
> Thanks,
> John
>
>-----------------------------------------------------------------------
>-
>
>_______________________________________________
>Serusers mailing list
>serusers(a)lists.iptel.org
>http://lists.iptel.org/mailman/listinfo/serusers
>
>
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
Can you send a trace of the REGISTER message with the cpl script in the
body?
Upon uploading a cpl script that is in the body of the message, REGISTER
requires the following header:
Content-Type: application/cpl+xml
When downloading a cpl script, the REGISTER requires the following
header:
Accept: application/cpl+xml or *
Chris
> -----Original Message-----
> From: jacky [mailto:jacklyman@sohu.com]
> Sent: Thursday, September 23, 2004 9:56 PM
> To: Christopher Crawford
> Cc: serusers(a)lists.iptel.org
> Subject: ser cpl-c, dont work fine!
>
> help!
>
> I builded ser from cvs. installed cpl-c module. Use followed command
for
> ser subscriber
>
> /usr/local/sbin/serctl fifo LOAD_CPL 100001(a)10.0.0.77 /tmp/test.xml
>
> serctl print OK.
>
> database table cpl:
> -----------------------
> | 100001(a)10.0.0.77 | <?xml version="1.0" encoding="UTF-8"?>
>
> <!DOCTYPE cpl PUBLIC '-//IETF//DTD RFCxxxx CPL 1.0//EN' 'cpl.dtd'>
>
> <cpl>
> <incoming>
> <location url="sip:100002@10.0.0.77">
> <redirect/>
> </location>
> </incoming>
> </cpl>
> -----------------------
>
> in my ser.cfg:
>
> -----------------------------------------------------------
> log(1, "About to register cpl script\n");
> # register cpl
> if(!cpl_process_register()) {
> log(1, "Error: fail cpl
registering\n");
> break;
> }
> -----------------------------------------------------------
>
> but when I use ua 100003 call 100001, 100001 ring not 100002. and in
ser
> log file, can find "About to register cpl script", not "Error: fail
cpl
> registering".
>
>
> So I dont know I can do what or debug it. please help me!
Hi,
I have setup a server with the default config and my topology is as follows:
192.168.10.2 (my PC with SJPhone)
192.168.10.20 (ZyXEL Prestige 2000W)
192.168.10.50 (IPTel SER 0.8.14 src)
Both phones register fine.
When I make a call all packets traverse fine ... phones ring ... I pick up the phone and no sound.....
I know both phones work as I have had them running through asterisk without issues.
Here is a tcpdump from my PC:
djs:/home/dave # tcpdump -n net 192.168.10.0/24
tcpdump: listening on eth0
16:07:39.941268 192.168.10.2.5060 > 192.168.10.50.5060: udp 625 (DF)
16:07:39.942286 192.168.10.50.5060 > 192.168.10.2.5060: udp 583 (DF) [tos 0x10]
16:07:42.347992 192.168.10.50.5060 > 192.168.10.2.5060: udp 481 (DF) [tos 0x10]
16:07:43.157053 192.168.10.50.5060 > 192.168.10.2.5060: udp 481 (DF) [tos 0x10]
16:07:44.933756 arp who-has 192.168.10.2 tell 192.168.10.50
16:07:44.933787 arp reply 192.168.10.2 is-at 0:50:fc:72:48:a7
16:07:51.478977 192.168.10.50.5060 > 192.168.10.2.5060: udp 728 (DF) [tos 0x10]
16:07:51.483097 192.168.10.2.5060 > 192.168.10.50.5060: udp 493 (DF)
16:07:51.617704 arp who-has 192.168.10.2 tell 192.168.10.20
16:07:51.617742 arp reply 192.168.10.2 is-at 0:50:fc:72:48:a7
16:07:51.624504 192.168.10.20.2070 > 192.168.10.2.16390: udp 252
16:07:51.649217 192.168.10.20.2070 > 192.168.10.2.16390: udp 252
16:07:51.664914 192.168.10.20.2070 > 192.168.10.2.16390: udp 252
16:07:51.696964 192.168.10.20.2070 > 192.168.10.2.16390: udp 252
16:07:51.728381 192.168.10.20.2070 > 192.168.10.2.16390: udp 252
16:07:51.760793 192.168.10.20.2070 > 192.168.10.2.16390: udp 252
16:07:51.792979 192.168.10.20.2070 > 192.168.10.2.16390: udp 252
16:07:51.824425 192.168.10.20.2070 > 192.168.10.2.16390: udp 252
16:07:51.857219 192.168.10.20.2070 > 192.168.10.2.16390: udp 252
16:07:51.889120 192.168.10.20.2070 > 192.168.10.2.16390: udp 252
16:07:51.904975 192.168.10.20.2070 > 192.168.10.2.16390: udp 252
16:07:51.937186 192.168.10.20.2070 > 192.168.10.2.16390: udp 252
16:07:51.968744 192.168.10.20.2070 > 192.168.10.2.16390: udp 252
16:07:52.000985 192.168.10.20.2070 > 192.168.10.2.16390: udp 252
16:07:52.032817 192.168.10.20.2070 > 192.168.10.2.16390: udp 252
16:07:52.064412 192.168.10.20.2070 > 192.168.10.2.16390: udp 252
No matter which phone I make the call from packets only go like above from the ZyXEL to the SJPhone PC.
Am I right in thinking that packets should go both ways??
Any other ideas as to why I have no sound?
Pulling my hair out on this one :)
Cheers,
Dave
I found out a solution with the Cisco Phones. There is an Option
"Outbound Proxy" wich I didn't noticed before. It works if I set
"Outbound Proxy" to SERs IP Adress and "SIP Proxy" to the Domain.
But I have another problem with aliases. If I add some aliases (the same
ones as in ser-0.8.14), they don't work.
SER says "100@mydomain" not found in usrloc.
Here is a short part of my ser.cfg:
if (!lookup("aliases") && !lookup("location")) {
sl_send_reply("404", "Not Found");
break;
};
Jan Jankowski
help!
I builded ser from cvs. installed cpl-c module. Use followed command for ser subscriber
/usr/local/sbin/serctl fifo LOAD_CPL 100001(a)10.0.0.77 /tmp/test.xml
serctl print OK.
database table cpl:
-----------------------
| 100001(a)10.0.0.77 | <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE cpl PUBLIC '-//IETF//DTD RFCxxxx CPL 1.0//EN' 'cpl.dtd'>
<cpl>
<incoming>
<location url="sip:100002@10.0.0.77">
<redirect/>
</location>
</incoming>
</cpl>
-----------------------
in my ser.cfg:
-----------------------------------------------------------
log(1, "About to register cpl script\n");
# register cpl
if(!cpl_process_register()) {
log(1, "Error: fail cpl registering\n");
break;
}
-----------------------------------------------------------
but when I use ua 100003 call 100001, 100001 ring not 100002. and in ser log file, can find "About to register cpl script", not "Error: fail cpl registering".
So I dont know I can do what or debug it. please help me!
Can you post your radiusclient.conf to the list, I assume you have your
radius config connecting to 'localhost', can you check that your loop
back interface works?
Regards,
-Jev
AJ Grinnell wrote:
> Yes, it is freeradius 1.0.0 and not a thing appears when I run radiusd
> -X. Even if a request would come through, I would be happy and could
> debug from there. The SER debug is saying "radius_authorize_sterman():
> Failure". I can see that this is a problem, but not able to find a
> cause when searching google. At this point, I guess I am going to have
> to post a bounty or something!
>
>
> On Thu, 23 Sep 2004 12:52:59 -0700, Jev <jev(a)ecad.org> wrote:
>
>>Your using FreeRADIUS? Does anything appear when you run it with -X, any
>>errors?
>>
>>Double check your realm configuration, you were using an IP in one of
>>your earlier posts, it would probably be better to use a real domain
>>instead of IPs.
>>
>>Also, double check that your shared secret in radiusclientng and radius
>>server config is the same.
>>
>>Good luck.
>>-Jev
>>
>>
>>
>>AJ Grinnell wrote:
>>
>>
>>>What will it take to make this work. I have been trying for 2 weeks
>>>now, re-installed everything I can, and SER still will not even send a
>>>request to RADIUS. Radiusclient is corect and can talk to the radius
>>>server just fine, SER will not talk to radius. I am desperate at this
>>>point, what will it take for someone to help me with this?
>>>
>>>_______________________________________________
>>>Serusers mailing list
>>>serusers(a)lists.iptel.org
>>>http://lists.iptel.org/mailman/listinfo/serusers
>>>
>>
>
Dear Users
i have Fedora Core 1 intalled with a SER 8.0.14 working fine with
accounting and autentification with MySql,
but i 've been tried to configure with FreeRadius and RadiusClient 4.3 and
the next Error appears
When i configure all like Ser_Radius like this
/etc/raddb Dir
****************** file
dictioary************************************************************
$INCLUDE /usr/share/freeradius/dictionary
$INCLUDE /usr/local/etc/radiusclient/dictionary.ser ### the dictionary
thet cames with the source in ser_8.0.14
****************** File
users************************************************
test Auth-Type := Digest, User-Password == "test"
Reply-Message = "Hello, test with digest"
******************* File Clients.conf******************************
client 127.0.0.1 {
#
# The shared secret use to "encrypt" and "sign" packets between
# the NAS and FreeRADIUS. You MUST change this secret from the
# default, otherwise it's not a secret any more!
#
# The secret can be any string, up to 32 characters in length.
#
secret = xxxx
#
# The short name is used as an alias for the fully qualified
# domain name, or the IP address.
#
shortname = localhost
#
# the following three fields are optional, but may be used by
# checkrad.pl for simultaneous use checks
#
#
# The nastype tells 'checkrad.pl' which NAS-specific method to
# use to query the NAS for simultaneous use.
#
# Permitted NAS types are:
#
# cisco
# computone
# livingston
# max40xx
# multitech
# netserver
# pathras
# patton
# portslave
# tc
# usrhiper
# other # for all other types
#
nastype = other # localhost isn't usually a NAS...
#
# The following two configurations are for future use.
# The 'naspasswd' file is currently used to store the NAS
# login name and password, which is used by checkrad.pl
# when querying the NAS for simultaneous use.
#
# login = !root
# password = someadminpas
}
***********************File Radiusd.conf***********************************
i've been uncoment the line with diget in "Autentication" and "Authorize"
****************************************************************************
****
And i've been included the dictionary.ser in
/usr/local/etc/radiusclient/dictionary
so when i make a test like the ser_radius.txt
radclient -f digest localhost auth xxxxx
in the radius log apears :
rad_recv: Access-Request packet from host 127.0.0.1:32769, id=138,
length=140
User-Name = "test"
Digest-Response = "631d6d73147add2f9e437f59bbc3aeb7"
Digest-Attributes = "\001\013testrealm"
Digest-Attributes = "\002\n1234abcd"
Digest-Attributes = "\003\010INVITE"
Digest-Attributes = "\004\034sip:5555551212@example.com"
Digest-Attributes = "\006\005MD5"
Digest-Attributes = "\n\006test"
modcall: entering group authorize
modcall[authorize]: module "preprocess" returns ok
modcall[authorize]: module "chap" returns noop
rlm_eap: EAP-Message not found
modcall[authorize]: module "eap" returns noop
rlm_digest: Converting Digest-Attributes to something sane...
Digest-Realm = "testrealm"
Digest-Nonce = "1234abcd"
Digest-Method = "INVITE"
Digest-URI = "sip:5555551212@example.com"
Digest-Algorithm = "MD5"
Digest-User-Name = "test"
rlm_digest: Adding Auth-Type = DIGEST
modcall[authorize]: module "digest" returns ok
rlm_realm: No '@' in User-Name = "test", looking up realm NULL
rlm_realm: No such realm "NULL"
modcall[authorize]: module "suffix" returns noop
users: Matched DEFAULT at 152
modcall[authorize]: module "files" returns ok
modcall[authorize]: module "mschap" returns noop
modcall: group authorize returns ok
rad_check_password: Found Auth-Type DIGEST
auth: type "digest"
modcall: entering group authenticate
rlm_digest: Configuration item "User-Password" is required for
authentication. ##############this is my problem..................
modcall[authenticate]: module "digest" returns invalid
modcall: group authenticate returns invalid
auth: Failed to validate the user.
Delaying request 0 for 1 seconds
Finished request 0
Going to the next request
--- Walking the entire request list ---
Waking up in 1 seconds...
--- Walking the entire request list ---
Waking up in 1 seconds...
--- Walking the entire request list ---
Sending Access-Reject of id 138 to 127.0.0.1:32769
Waking up in 4 seconds...
****************************************************************************
******************
then if i change the dictionary.ser for dictionary.sip that comes with the
source in radiusClient4.3.................the test works well.......
but if i try to autenticate an UA like a ATA-186, the same message appears
rlm_digest: Configuration item "User-Password" is required for
authentication. ##############this is my problem..................
Best Regards
Gustaf
What will it take to make this work. I have been trying for 2 weeks
now, re-installed everything I can, and SER still will not even send a
request to RADIUS. Radiusclient is corect and can talk to the radius
server just fine, SER will not talk to radius. I am desperate at this
point, what will it take for someone to help me with this?
