sr-users July 2003

sr-users@lists.kamailio.org

67 participants
160 discussions

Re: [Serusers] ser support IPv6 ?
by Yoshiharu Maekawa 22 Jul '03

22 Jul '03

Hi, > May I know which IPv6 UA Client do you use? We use our original ipv6 client which is internal use only. Thanks maekawa

1 0

[Serusers] Çäåñü òåìà 238260
by 238260＠yahoo.com 21 Jul '03

21 Jul '03

1 0

[Serusers] SER can not be started after reboot
by Kevin Chu 21 Jul '03

21 Jul '03

Hi, I installed the latest SER (0.8.11pre29) on a RedHat Linux 9 machine, and it can run pretty well without any problem. However, when I tried to reboot the Linux box, it was stuck there for starting SER as a service. I tried to skip starting SER at boot time, and tried to start it later manually, but the problem is still there. The SER can not be started anymore after reboot. Does anybody have the same problem before? Please help me out. Thanks! Kevin

2 1

[Serusers] Acc with Radius support failed.
by Younger Wang 21 Jul '03

21 Jul '03

I tried to load SER with Radius Account support. SER failed to start with the following error message: 0(30753) ERROR: load_module: could not open module </usr/local/lib/ser/modules/acc.so>: libradiusclient.so.0: cannot open shared object file: No such file or directory 0(30753) parse error (42,13-47): failed to load module 0(30753) set_mod_param_regex: No module matching acc found | 0(30753) parse error (54,32-33): Can't set module parameter 0(30753) set_mod_param_regex: No module matching acc found | 0(30753) parse error (58,33-34): Can't set module parameter 0(30753) set_mod_param_regex: No module matching acc found | 0(30753) parse error (59,31-32): Can't set module parameter 0(30753) set_mod_param_regex: No module matching acc found | 0(30753) parse error (62,31-32): Can't set module parameter 0(30753) set_mod_param_regex: No module matching acc found | 0(30753) parse error (64,42-43): Can't set module parameter 0(30753) set_mod_param_regex: No module matching acc found | 0(30753) parse error (65,41-42): Can't set module parameter 0(30753) set_mod_param_regex: No module matching acc found | 0(30753) parse error (66,58-59): Can't set module parameter 0(30753) set_mod_param_regex: No module matching acc found | 0(30753) parse error (67,29-30): Can't set module parameter 0(30753) set_mod_param_regex: No module matching acc found | 0(30753) parse error (68,35-36): Can't set module parameter 0(30753) set_mod_param_regex: No module matching acc found | 0(30753) parse error (69,37-38): Can't set module parameter ERROR: bad config file (11 errors) I cannot figure out what went wrong. I installed my SER with the latest CVS. I also have radiusclient and freeradius installed on the same machine. Any idea? Younger Wang

2 2

[Serusers] serweb installation
by giAndrea 20 Jul '03

20 Jul '03

hello i've installed serweb and ser 0.8.10. when i call http://mydomain/serweb/user_interface i login with my account but nothing happens. I've configured files in /var/www/html/htdocs/serweb like the http://www.fitawi.com/ser-Howto.html how to. any suggestion ? thanks. Andrea ---------------------------------- Legge di Clarke sulle idee rivoluzionarie Ogni idea rivoluzionaria - in campo scientifico, artistico o altro provoca tre stadi di reazione, riassumibili nelle seguenti frasi: 1. "E' impossibile; non farmi perdere tempo". 2. "E' possibile, ma non val la pena di farlo". 3. "L'ho sempre detto, io, che era un'ottima idea".

2 1

[Serusers] Troubles matching 487's to subsequent ACKs
by Maxim Sobolev 20 Jul '03

20 Jul '03

Hi, We have recently switched to 0.8.11 for our production server and I have noticed that ser no longer can match 487 Request cancelled reply to subsequent ACK, at least in the cases when ATA186 with latest firmware 2.16 is used as the originating UA. I wonder who is responsible for this: ATA or SER. The only strange thing that I see in the log is that ATA includes the following extra parameters into the first Via hf: rport=5060;received=195.234.212.178. ATA->SER INVITE sip:380445732729@64.180.102.72;user=phone SIP/2.0 Via: SIP/2.0/UDP 192.168.0.253:5060 From: <sip:380442466396@64.180.102.72;user=phone>;tag=4197094684 To: <sip:380445732729@64.180.102.72;user=phone> Call-ID: 2777157492(a)192.168.0.253 CSeq: 2 INVITE Contact: <sip:380442466396@192.168.0.253:5060;user=phone;transport=udp> User-Agent: Cisco ATA 186 v2.16 ata18x (030509a) Authorization: Digest username="380442466396",realm="64.180.102.72",nonce="3f168 ef30be264b823354f5b14bef51f8c3636de",uri="sip:380445732729@64.180.102.72",respon se="d5a544d0eb3103e9f67b4e2af839054d" Expires: 300 Content-Length: 257 Content-Type: application/sdp o=380442466396 40288 40288 IN IP4 192.168.0.253 s=ATA186 Call c=IN IP4 192.168.0.253 t=0 0 m=audio 13000 RTP/AVP 4 8 0 101 a=rtpmap:4 G723/8000/1 a=rtpmap:8 PCMA/8000/1 a=rtpmap:0 PCMU/8000/1 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 SER->ATA SIP/2.0 100 trying -- your call is important to us Via: SIP/2.0/UDP 192.168.0.253:5060;rport=5060;received=195.234.212.178 From: <sip:380442466396@64.180.102.72;user=phone>;tag=4197094684 To: <sip:380445732729@64.180.102.72;user=phone> Call-ID: 2777157492(a)192.168.0.253 CSeq: 2 INVITE Server: Sip EXpress router (0.8.11rc1 (i386/freebsd)) Content-Length: 0 SER->ATA SIP/2.0 183 Session Progress Via: SIP/2.0/UDP 192.168.0.253:5060;rport=5060;received=195.234.212.178 To: <sip:380445732729@64.180.102.72;user=phone>;tag=d429e01d From: <sip:380442466396@64.180.102.72;user=phone>;tag=4197094684 Call-ID: 2777157492(a)192.168.0.253 CSeq: 2 INVITE Record-Route: <sip:380445732729@64.180.102.72;lr> Content-Type: application/sdp Content-Length: 283 o=CiscoSystemsSIP-GW-UserAgent 503 692 IN IP4 212.119.160.61 s=SIP Call c=IN IP4 212.119.160.61 t=0 0 m=audio 17182 RTP/AVP 4 19 101 c=IN IP4 212.119.160.61 a=rtpmap:4 G723/8000 a=rtpmap:19 CN/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:4 annexa=no a=fmtp:101 0-15 ATA->SER CANCEL sip:380445732729@64.180.102.72;user=phone SIP/2.0 Via: SIP/2.0/UDP 192.168.0.253:5060 From: <sip:380442466396@64.180.102.72;user=phone>;tag=4197094684 To: <sip:380445732729@64.180.102.72;user=phone> Call-ID: 2777157492(a)192.168.0.253 CSeq: 2 CANCEL User-Agent: Cisco ATA 186 v2.16 ata18x (030509a) Authorization: Digest username="380442466396",realm="64.180.102.72",nonce="3f168 ef30be264b823354f5b14bef51f8c3636de",uri="sip:380445732729@64.180.102.72",respon se="2953586e366141c5b8062cdfe7678357" Content-Length: 0 SER->ATA SIP/2.0 200 cancelling Via: SIP/2.0/UDP 192.168.0.253:5060;rport=5060;received=195.234.212.178 From: <sip:380442466396@64.180.102.72;user=phone>;tag=4197094684 To: <sip:380445732729@64.180.102.72;user=phone>;tag=7fe8c93a8cb9c58b2cde45b60b0e 5d5c-7fd1 Call-ID: 2777157492(a)192.168.0.253 CSeq: 2 CANCEL Server: Sip EXpress router (0.8.11rc1 (i386/freebsd)) Content-Length: 0 SER->ATA SIP/2.0 487 Request cancelled Via: SIP/2.0/UDP 192.168.0.253:5060;rport=5060;received=195.234.212.178 From: <sip:380442466396@64.180.102.72;user=phone>;tag=4197094684 To: <sip:380445732729@64.180.102.72;user=phone>;tag=7fe8c93a8cb9c58b2cde45b60b0e 5d5c-7fd1 Call-ID: 2777157492(a)192.168.0.253 CSeq: 2 INVITE Server: Sip EXpress router (0.8.11rc1 (i386/freebsd)) Content-Length: 0 ATA->SER ACK sip:380445732729@64.180.102.72;user=phone SIP/2.0 Via: SIP/2.0/UDP 192.168.0.253:5060;rport=5060;received=195.234.212.178 From: <sip:380442466396@64.180.102.72;user=phone>;tag=4197094684 To: <sip:380445732729@64.180.102.72;user=phone>;tag=7fe8c93a8cb9c58b2cde45b60b0e 5d5c-7fd1 Call-ID: 2777157492(a)192.168.0.253 CSeq: 2 ACK User-Agent: Cisco ATA 186 v2.16 ata18x (030509a) Content-Length: 0 SER->ATA SIP/2.0 487 Request cancelled Via: SIP/2.0/UDP 192.168.0.253:5060;rport=5060;received=195.234.212.178 From: <sip:380442466396@64.180.102.72;user=phone>;tag=4197094684 To: <sip:380445732729@64.180.102.72;user=phone>;tag=7fe8c93a8cb9c58b2cde45b60b0e 5d5c-7fd1 Call-ID: 2777157492(a)192.168.0.253 CSeq: 2 INVITE Server: Sip EXpress router (0.8.11rc1 (i386/freebsd)) Content-Length: 0 ATA->SER ACK sip:380445732729@64.180.102.72;user=phone SIP/2.0 Via: SIP/2.0/UDP 192.168.0.253:5060;rport=5060;received=195.234.212.178 From: <sip:380442466396@64.180.102.72;user=phone>;tag=4197094684 To: <sip:380445732729@64.180.102.72;user=phone>;tag=7fe8c93a8cb9c58b2cde45b60b0e 5d5c-7fd1 Call-ID: 2777157492(a)192.168.0.253 CSeq: 2 ACK User-Agent: Cisco ATA 186 v2.16 ata18x (030509a) Content-Length: 0 An so on (487->ACK->487->ACK until timeout hits). -Maxim

6 9

[Serusers] exec_msg and exec_uri integration
by Cerrajetto 20 Jul '03

20 Jul '03

Hello, We are testing exec_msg and exec_uri. exec_msg sends via standard input all sip headers and contents, but exec_uri only sends current uri ... Therefore, we can only write external scripts to redirect on a "current_uri" basis. We would like to integrate "exec_msg" and "exec_uri" features, is it possible? We've found that after a change in ser.cfg it is needed to restart SER to apply changes, is there a way to force a "reload" of ser.cfg? Thank you, Mark

2 3

[Serusers] ser support IPv6 ?
by Ng, Soo Sim 19 Jul '03

19 Jul '03

May I know which IPv6 UA Client do you use? SSng

1 0

[Serusers] SIP library
by Victor Gamov 18 Jul '03

18 Jul '03

Sorry for my non SER-related question We need to write some SIP applications on UNIX (and may be M$) platform. Which SIP library is best for this purpose? Thanks!

1 0

[Serusers] ser support IPv6 ?
by maekawa＠cd.jp.nec.com 18 Jul '03

18 Jul '03

Hi, I think that ser supports IPv6. I used ser-0.8.10 and tried to transmit a REGISTER message from an IPv6 SIP client. However, I received an ICMP message of "port unreachable" from ser and was not able to register . I expect an appropriate advice. Best Regards Maekawa

2 1

← Newer
1
...
6
7
8
9
10
11
12
...
16
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users July 2003