sr-users July 2003

sr-users@lists.kamailio.org

67 participants
160 discussions

by Madan

hi i m using default ser config and mysql db/tables ..no modification whatsoever what i want is how can we disable/expire sip accounts..say for example i have a user A and i want to enable his sip account based on hrs/months etc how to go abt it? what all changes do i need to make? regards, Madan

21 years, 3 months

[Serusers] Searching archive...

by Tom Yerex

I am trying to find a search function for the serusers mailing list - I tried looking at the following locations: http://lists.iptel.org/mailman/listinfo/serusers http://lists.iptel.org/pipermail/serusers/ Does one exist? Tom Yerex Tel: 604-221-4321 Email: tomy(a)telus.net http://www.sparkyjones.com

21 years, 3 months

[Serusers] (no subject)

by Yoshiharu Maekawa

Hello, I installed ser-0.8.11pre29-1.i386.rpm on Linux PC. and started ser with default ser.cfg file. I registered ser with "ymaekawa" and "guest001" using Windows Messanger. then I send instant message from "guest001" to "ymaekawa". But, I can not send. What's wrong? # I attached ethereal log (text). regards, Maekawa. Frame 172 (564 bytes on wire, 564 bytes captured) Arrival Time: Jul 30, 2003 21:16:20.927451000 Time delta from previous packet: 5.180149000 seconds Time relative to first packet: 5.180149000 seconds Frame Number: 172 Packet Length: 564 bytes Capture Length: 564 bytes Ethernet II, Src: 00:03:47:e2:1a:f7, Dst: 00:00:4c:df:17:da Destination: 00:00:4c:df:17:da (NEC_df:17:da) Source: 00:03:47:e2:1a:f7 (Intel_e2:1a:f7) Type: IP (0x0800) Internet Protocol, Src Addr: 10.41.133.231 (10.41.133.231), Dst Addr: 10.41.133.39 (10.41.133.39) Version: 4 Header length: 20 bytes Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00) 0000 00.. = Differentiated Services Codepoint: Default (0x00) .... ..0. = ECN-Capable Transport (ECT): 0 .... ...0 = ECN-CE: 0 Total Length: 550 Identification: 0xc12b Flags: 0x00 .0.. = Don't fragment: Not set ..0. = More fragments: Not set Fragment offset: 0 Time to live: 128 Protocol: UDP (0x11) Header checksum: 0x583b (correct) Source: 10.41.133.231 (10.41.133.231) Destination: 10.41.133.39 (10.41.133.39) User Datagram Protocol, Src Port: 4640 (4640), Dst Port: 5060 (5060) Source port: 4640 (4640) Destination port: 5060 (5060) Length: 530 Checksum: 0x2c1c (correct) Session Initiation Protocol Request line: REGISTER sip:ssfch29.ssf.abk.nec.co.jp SIP/2.0 Method: REGISTER Message Header Via: SIP/2.0/UDP 10.41.133.231:8288 From: <sip:ymaekawa@ssfch29.ssf.abk.nec.co.jp>;tag=8d1f4e3b-d28e-4ab1-8010-6772160056b5 To: <sip:ymaekawa@ssfch29.ssf.abk.nec.co.jp> Call-ID: 69903aeb-76b5-48be-ab5a-bf53ab3daf3e(a)10.41.133.231 CSeq: 1 REGISTER Contact: <sip:10.41.133.231:8288>;methods="INVITE, MESSAGE, INFO, SUBSCRIBE, OPTIONS, BYE, CANCEL, NOTIFY, ACK" User-Agent: Windows RTC/1.0 Expires: 1200 Event: registration Allow-Events: presence Content-Length: 0 Frame 173 (678 bytes on wire, 678 bytes captured) Arrival Time: Jul 30, 2003 21:16:20.928332000 Time delta from previous packet: 0.000881000 seconds Time relative to first packet: 5.181030000 seconds Frame Number: 173 Packet Length: 678 bytes Capture Length: 678 bytes Ethernet II, Src: 00:00:4c:df:17:da, Dst: 00:03:47:e2:1a:f7 Destination: 00:03:47:e2:1a:f7 (Intel_e2:1a:f7) Source: 00:00:4c:df:17:da (NEC_df:17:da) Type: IP (0x0800) Internet Protocol, Src Addr: 10.41.133.39 (10.41.133.39), Dst Addr: 10.41.133.231 (10.41.133.231) Version: 4 Header length: 20 bytes Differentiated Services Field: 0x10 (DSCP 0x04: Unknown DSCP; ECN: 0x00) 0001 00.. = Differentiated Services Codepoint: Unknown (0x04) .... ..0. = ECN-Capable Transport (ECT): 0 .... ...0 = ECN-CE: 0 Total Length: 664 Identification: 0x0000 Flags: 0x04 .1.. = Don't fragment: Set ..0. = More fragments: Not set Fragment offset: 0 Time to live: 64 Protocol: UDP (0x11) Header checksum: 0x18e5 (correct) Source: 10.41.133.39 (10.41.133.39) Destination: 10.41.133.231 (10.41.133.231) User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 8288 (8288) Source port: 5060 (5060) Destination port: 8288 (8288) Length: 644 Checksum: 0x7c1d (correct) Session Initiation Protocol Status line: SIP/2.0 200 OK Status-Code: 200 Message Header Via: SIP/2.0/UDP 10.41.133.231:8288 From: <sip:ymaekawa@ssfch29.ssf.abk.nec.co.jp>;tag=8d1f4e3b-d28e-4ab1-8010-6772160056b5 To: <sip:ymaekawa@ssfch29.ssf.abk.nec.co.jp>;tag=b27e1a1d33761e85846fc98f5f3a7e58.9bdf Call-ID: 69903aeb-76b5-48be-ab5a-bf53ab3daf3e(a)10.41.133.231 CSeq: 1 REGISTER Contact: <sip:10.41.133.231:8288>;q=0.00;expires=1200 Server: Sip EXpress router (0.8.11pre29 (i386/linux)) Content-Length: 0 Warning: 392 10.41.133.39:5060 "Noisy feedback tells: pid=27811 req_src_ip=10.41.133.231 req_src_port=4640 in_uri=sip:ssfch29.ssf.abk.nec.co.jp out_uri=sip:ssfch29.ssf.abk.nec.co.jp via_cnt==1" Frame 174 (463 bytes on wire, 463 bytes captured) Arrival Time: Jul 30, 2003 21:16:20.935009000 Time delta from previous packet: 0.006677000 seconds Time relative to first packet: 5.187707000 seconds Frame Number: 174 Packet Length: 463 bytes Capture Length: 463 bytes Ethernet II, Src: 00:03:47:e2:1a:f7, Dst: 00:00:4c:df:17:da Destination: 00:00:4c:df:17:da (NEC_df:17:da) Source: 00:03:47:e2:1a:f7 (Intel_e2:1a:f7) Type: IP (0x0800) Internet Protocol, Src Addr: 10.41.133.231 (10.41.133.231), Dst Addr: 10.41.133.39 (10.41.133.39) Version: 4 Header length: 20 bytes Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00) 0000 00.. = Differentiated Services Codepoint: Default (0x00) .... ..0. = ECN-Capable Transport (ECT): 0 .... ...0 = ECN-CE: 0 Total Length: 449 Identification: 0xc12c Flags: 0x00 .0.. = Don't fragment: Not set ..0. = More fragments: Not set Fragment offset: 0 Time to live: 128 Protocol: UDP (0x11) Header checksum: 0x589f (correct) Source: 10.41.133.231 (10.41.133.231) Destination: 10.41.133.39 (10.41.133.39) User Datagram Protocol, Src Port: 4640 (4640), Dst Port: 5060 (5060) Source port: 4640 (4640) Destination port: 5060 (5060) Length: 429 Checksum: 0xd50d (correct) Session Initiation Protocol Request line: SUBSCRIBE sip:guest001@ssfch29.ssf.abk.nec.co.jp SIP/2.0 Method: SUBSCRIBE Message Header Via: SIP/2.0/UDP 10.41.133.231:8288 From: "ymaekawa" <sip:ymaekawa@ssfch29.ssf.abk.nec.co.jp>;tag=4f269f57-84df-46d1-aeef-18d57f0f0d11 To: <sip:guest001@ssfch29.ssf.abk.nec.co.jp> Call-ID: 71439ab0-bed1-4b23-9063-9f9239a81aeb(a)10.41.133.231 CSeq: 1 SUBSCRIBE Contact: <sip:10.41.133.231:8288> User-Agent: Windows RTC/1.0 Expires: 1800 Content-Length: 0 Frame 175 (660 bytes on wire, 660 bytes captured) Arrival Time: Jul 30, 2003 21:16:20.935590000 Time delta from previous packet: 0.000581000 seconds Time relative to first packet: 5.188288000 seconds Frame Number: 175 Packet Length: 660 bytes Capture Length: 660 bytes Ethernet II, Src: 00:00:4c:df:17:da, Dst: 00:03:47:e2:1a:f7 Destination: 00:03:47:e2:1a:f7 (Intel_e2:1a:f7) Source: 00:00:4c:df:17:da (NEC_df:17:da) Type: IP (0x0800) Internet Protocol, Src Addr: 10.41.133.39 (10.41.133.39), Dst Addr: 10.41.133.231 (10.41.133.231) Version: 4 Header length: 20 bytes Differentiated Services Field: 0x10 (DSCP 0x04: Unknown DSCP; ECN: 0x00) 0001 00.. = Differentiated Services Codepoint: Unknown (0x04) .... ..0. = ECN-Capable Transport (ECT): 0 .... ...0 = ECN-CE: 0 Total Length: 646 Identification: 0x0000 Flags: 0x04 .1.. = Don't fragment: Set ..0. = More fragments: Not set Fragment offset: 0 Time to live: 64 Protocol: UDP (0x11) Header checksum: 0x18f7 (correct) Source: 10.41.133.39 (10.41.133.39) Destination: 10.41.133.231 (10.41.133.231) User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 8288 (8288) Source port: 5060 (5060) Destination port: 8288 (8288) Length: 626 Checksum: 0x05a5 (correct) Session Initiation Protocol Status line: SIP/2.0 404 Not Found Status-Code: 404 Message Header Via: SIP/2.0/UDP 10.41.133.231:8288 From: "ymaekawa" <sip:ymaekawa@ssfch29.ssf.abk.nec.co.jp>;tag=4f269f57-84df-46d1-aeef-18d57f0f0d11 To: <sip:guest001@ssfch29.ssf.abk.nec.co.jp>;tag=b27e1a1d33761e85846fc98f5f3a7e58.9bdf Call-ID: 71439ab0-bed1-4b23-9063-9f9239a81aeb(a)10.41.133.231 CSeq: 1 SUBSCRIBE Server: Sip EXpress router (0.8.11pre29 (i386/linux)) Content-Length: 0 Warning: 392 10.41.133.39:5060 "Noisy feedback tells: pid=27809 req_src_ip=10.41.133.231 req_src_port=4640 in_uri=sip:guest001@ssfch29.ssf.abk.nec.co.jp out_uri=sip:guest001@ssfch29.ssf.abk.nec.co.jp via_cnt==1" Frame 495 (613 bytes on wire, 613 bytes captured) Arrival Time: Jul 30, 2003 21:16:30.264431000 Time delta from previous packet: 9.328841000 seconds Time relative to first packet: 14.517129000 seconds Frame Number: 495 Packet Length: 613 bytes Capture Length: 613 bytes Ethernet II, Src: 00:00:4c:df:17:da, Dst: 00:03:47:e2:1a:f7 Destination: 00:03:47:e2:1a:f7 (Intel_e2:1a:f7) Source: 00:00:4c:df:17:da (NEC_df:17:da) Type: IP (0x0800) Internet Protocol, Src Addr: 10.41.133.39 (10.41.133.39), Dst Addr: 10.41.133.231 (10.41.133.231) Version: 4 Header length: 20 bytes Differentiated Services Field: 0x10 (DSCP 0x04: Unknown DSCP; ECN: 0x00) 0001 00.. = Differentiated Services Codepoint: Unknown (0x04) .... ..0. = ECN-Capable Transport (ECT): 0 .... ...0 = ECN-CE: 0 Total Length: 599 Identification: 0x0000 Flags: 0x04 .1.. = Don't fragment: Set ..0. = More fragments: Not set Fragment offset: 0 Time to live: 64 Protocol: UDP (0x11) Header checksum: 0x1926 (correct) Source: 10.41.133.39 (10.41.133.39) Destination: 10.41.133.231 (10.41.133.231) User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 8288 (8288) Source port: 5060 (5060) Destination port: 8288 (8288) Length: 579 Checksum: 0xb172 (correct) Session Initiation Protocol Request line: SUBSCRIBE sip:10.41.133.231:8288 SIP/2.0 Method: SUBSCRIBE Message Header Max-Forwards: 10 Record-Route: <sip:ymaekawa@10.41.133.39;ftag=893c2373-524f-4666-8cdd-fab901a964ce;lr> Via: SIP/2.0/UDP 10.41.133.39;branch=z9hG4bK2c73.f0ffec02.0 Via: SIP/2.0/UDP 10.41.133.26:16755 From: "guest001" <sip:guest001@ssfch29.ssf.abk.nec.co.jp>;tag=893c2373-524f-4666-8cdd-fab901a964ce To: <sip:ymaekawa@ssfch29.ssf.abk.nec.co.jp> Call-ID: ec875329-4967-4bd6-bd86-c7fdb63fbc77(a)10.41.133.26 CSeq: 1 SUBSCRIBE Contact: <sip:10.41.133.26:16755> User-Agent: Windows RTC/1.0 Expires: 1800 Content-Length: 0 Frame 496 (610 bytes on wire, 610 bytes captured) Arrival Time: Jul 30, 2003 21:16:30.264829000 Time delta from previous packet: 0.000398000 seconds Time relative to first packet: 14.517527000 seconds Frame Number: 496 Packet Length: 610 bytes Capture Length: 610 bytes Ethernet II, Src: 00:03:47:e2:1a:f7, Dst: 00:00:4c:df:17:da Destination: 00:00:4c:df:17:da (NEC_df:17:da) Source: 00:03:47:e2:1a:f7 (Intel_e2:1a:f7) Type: IP (0x0800) Internet Protocol, Src Addr: 10.41.133.231 (10.41.133.231), Dst Addr: 10.41.133.39 (10.41.133.39) Version: 4 Header length: 20 bytes Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00) 0000 00.. = Differentiated Services Codepoint: Default (0x00) .... ..0. = ECN-Capable Transport (ECT): 0 .... ...0 = ECN-CE: 0 Total Length: 596 Identification: 0xc18c Flags: 0x00 .0.. = Don't fragment: Not set ..0. = More fragments: Not set Fragment offset: 0 Time to live: 128 Protocol: UDP (0x11) Header checksum: 0x57ac (correct) Source: 10.41.133.231 (10.41.133.231) Destination: 10.41.133.39 (10.41.133.39) User Datagram Protocol, Src Port: 4640 (4640), Dst Port: 5060 (5060) Source port: 4640 (4640) Destination port: 5060 (5060) Length: 576 Checksum: 0x967b (correct) Session Initiation Protocol Status line: SIP/2.0 200 OK Status-Code: 200 Message Header Via: SIP/2.0/UDP 10.41.133.39;branch=z9hG4bK2c73.f0ffec02.0 Via: SIP/2.0/UDP 10.41.133.26:16755 From: "guest001" <sip:guest001@ssfch29.ssf.abk.nec.co.jp>;tag=893c2373-524f-4666-8cdd-fab901a964ce To: <sip:ymaekawa@ssfch29.ssf.abk.nec.co.jp>;tag=7bcd92fb-7ee5-4df2-8405-c6481e77b20b Call-ID: ec875329-4967-4bd6-bd86-c7fdb63fbc77(a)10.41.133.26 CSeq: 1 SUBSCRIBE Record-Route: <sip:ymaekawa@10.41.133.39;ftag=893c2373-524f-4666-8cdd-fab901a964ce;lr> Contact: <sip:10.41.133.231:8288> User-Agent: Windows RTC/1.0 Expires: 1800 Content-Length: 0 Frame 3424 (817 bytes on wire, 817 bytes captured) Arrival Time: Jul 30, 2003 21:17:49.360760000 Time delta from previous packet: 79.095931000 seconds Time relative to first packet: 93.613458000 seconds Frame Number: 3424 Packet Length: 817 bytes Capture Length: 817 bytes Ethernet II, Src: 00:00:4c:df:17:da, Dst: 00:03:47:e2:1a:f7 Destination: 00:03:47:e2:1a:f7 (Intel_e2:1a:f7) Source: 00:00:4c:df:17:da (NEC_df:17:da) Type: IP (0x0800) Internet Protocol, Src Addr: 10.41.133.39 (10.41.133.39), Dst Addr: 10.41.133.231 (10.41.133.231) Version: 4 Header length: 20 bytes Differentiated Services Field: 0x10 (DSCP 0x04: Unknown DSCP; ECN: 0x00) 0001 00.. = Differentiated Services Codepoint: Unknown (0x04) .... ..0. = ECN-Capable Transport (ECT): 0 .... ...0 = ECN-CE: 0 Total Length: 803 Identification: 0x0000 Flags: 0x04 .1.. = Don't fragment: Set ..0. = More fragments: Not set Fragment offset: 0 Time to live: 64 Protocol: UDP (0x11) Header checksum: 0x185a (correct) Source: 10.41.133.39 (10.41.133.39) Destination: 10.41.133.231 (10.41.133.231) User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 8288 (8288) Source port: 5060 (5060) Destination port: 8288 (8288) Length: 783 Checksum: 0x0e6a (correct) Session Initiation Protocol Request line: MESSAGE sip:10.41.133.231:8288 SIP/2.0 Method: MESSAGE Message Header Max-Forwards: 10 Record-Route: <sip:ymaekawa@10.41.133.39;ftag=9ede1c1e-9770-4372-80c2-b2422462409b;lr> Via: SIP/2.0/UDP 10.41.133.39;branch=z9hG4bKad56.ba8de2f5.0 Via: SIP/2.0/UDP 10.41.133.26:16755 From: "guest001" <sip:guest001@ssfch29.ssf.abk.nec.co.jp>;tag=9ede1c1e-9770-4372-80c2-b2422462409b To: <sip:ymaekawa@ssfch29.ssf.abk.nec.co.jp> Call-ID: dd87d35b-d56d-441c-bc1d-7c9926d107b7(a)10.41.133.26 CSeq: 1 MESSAGE Contact: <sip:10.41.133.26:16755> User-Agent: Windows RTC/1.0 Content-Type: text/plain; charset=UTF-8;msgr=WAAtAE0ATQBTAC0ASQBNAC0ARgBvAHIAbQBhAHQAOgAgAEYATgA9AE0AUwAlADIAMABVAEkAJQAyADAARwBvAHQAaABpAGMAOwAgAEUARgA9ADsAIABDAE8APQAwADsAIABDAFMAPQA4ADAAOwAgAFAARgA9ADAADQAKAA0ACgA Content-Length: 5 Session Description Protocol Invalid line: hello Frame 3460 (817 bytes on wire, 817 bytes captured) Arrival Time: Jul 30, 2003 21:17:50.366345000 Time delta from previous packet: 1.005585000 seconds Time relative to first packet: 94.619043000 seconds Frame Number: 3460 Packet Length: 817 bytes Capture Length: 817 bytes Ethernet II, Src: 00:00:4c:df:17:da, Dst: 00:03:47:e2:1a:f7 Destination: 00:03:47:e2:1a:f7 (Intel_e2:1a:f7) Source: 00:00:4c:df:17:da (NEC_df:17:da) Type: IP (0x0800) Internet Protocol, Src Addr: 10.41.133.39 (10.41.133.39), Dst Addr: 10.41.133.231 (10.41.133.231) Version: 4 Header length: 20 bytes Differentiated Services Field: 0x10 (DSCP 0x04: Unknown DSCP; ECN: 0x00) 0001 00.. = Differentiated Services Codepoint: Unknown (0x04) .... ..0. = ECN-Capable Transport (ECT): 0 .... ...0 = ECN-CE: 0 Total Length: 803 Identification: 0x0000 Flags: 0x04 .1.. = Don't fragment: Set ..0. = More fragments: Not set Fragment offset: 0 Time to live: 64 Protocol: UDP (0x11) Header checksum: 0x185a (correct) Source: 10.41.133.39 (10.41.133.39) Destination: 10.41.133.231 (10.41.133.231) User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 8288 (8288) Source port: 5060 (5060) Destination port: 8288 (8288) Length: 783 Checksum: 0x0e6a (correct) Session Initiation Protocol Request line: MESSAGE sip:10.41.133.231:8288 SIP/2.0 Method: MESSAGE Message Header Max-Forwards: 10 Record-Route: <sip:ymaekawa@10.41.133.39;ftag=9ede1c1e-9770-4372-80c2-b2422462409b;lr> Via: SIP/2.0/UDP 10.41.133.39;branch=z9hG4bKad56.ba8de2f5.0 Via: SIP/2.0/UDP 10.41.133.26:16755 From: "guest001" <sip:guest001@ssfch29.ssf.abk.nec.co.jp>;tag=9ede1c1e-9770-4372-80c2-b2422462409b To: <sip:ymaekawa@ssfch29.ssf.abk.nec.co.jp> Call-ID: dd87d35b-d56d-441c-bc1d-7c9926d107b7(a)10.41.133.26 CSeq: 1 MESSAGE Contact: <sip:10.41.133.26:16755> User-Agent: Windows RTC/1.0 Content-Type: text/plain; charset=UTF-8;msgr=WAAtAE0ATQBTAC0ASQBNAC0ARgBvAHIAbQBhAHQAOgAgAEYATgA9AE0AUwAlADIAMABVAEkAJQAyADAARwBvAHQAaABpAGMAOwAgAEUARgA9ADsAIABDAE8APQAwADsAIABDAFMAPQA4ADAAOwAgAFAARgA9ADAADQAKAA0ACgA Content-Length: 5 Session Description Protocol Invalid line: hello Frame 3461 (479 bytes on wire, 479 bytes captured) Arrival Time: Jul 30, 2003 21:17:50.366680000 Time delta from previous packet: 0.000335000 seconds Time relative to first packet: 94.619378000 seconds Frame Number: 3461 Packet Length: 479 bytes Capture Length: 479 bytes Ethernet II, Src: 00:03:47:e2:1a:f7, Dst: 00:00:4c:df:17:da Destination: 00:00:4c:df:17:da (NEC_df:17:da) Source: 00:03:47:e2:1a:f7 (Intel_e2:1a:f7) Type: IP (0x0800) Internet Protocol, Src Addr: 10.41.133.231 (10.41.133.231), Dst Addr: 10.41.133.39 (10.41.133.39) Version: 4 Header length: 20 bytes Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00) 0000 00.. = Differentiated Services Codepoint: Default (0x00) .... ..0. = ECN-Capable Transport (ECT): 0 .... ...0 = ECN-CE: 0 Total Length: 465 Identification: 0xc4fa Flags: 0x00 .0.. = Don't fragment: Not set ..0. = More fragments: Not set Fragment offset: 0 Time to live: 128 Protocol: UDP (0x11) Header checksum: 0x54c1 (correct) Source: 10.41.133.231 (10.41.133.231) Destination: 10.41.133.39 (10.41.133.39) User Datagram Protocol, Src Port: 4640 (4640), Dst Port: 5060 (5060) Source port: 4640 (4640) Destination port: 5060 (5060) Length: 445 Checksum: 0x3236 (correct) Session Initiation Protocol Status line: SIP/2.0 400 Bad Request Status-Code: 400 Message Header Via: SIP/2.0/UDP 10.41.133.39;branch=z9hG4bKad56.ba8de2f5.0 Via: SIP/2.0/UDP 10.41.133.26:16755 From: "guest001" <sip:guest001@ssfch29.ssf.abk.nec.co.jp>;tag=9ede1c1e-9770-4372-80c2-b2422462409b To: <sip:ymaekawa@ssfch29.ssf.abk.nec.co.jp>;tag=35fee637-c0fa-45dd-a780-0f99f339568c Call-ID: dd87d35b-d56d-441c-bc1d-7c9926d107b7(a)10.41.133.26 CSeq: 1 MESSAGE User-Agent: Windows RTC/1.0 Content-Length: 0

21 years, 3 months

[Serusers] Does lookup("location") queries the database or the memory?

by Klaus Darilion

Hello! I have found the db_mode option in the userloc module, which controls updates in the location table. But how are the lookups handled in ser? If a user location will be requested by lookup("location"), will this query the backend database or only the RAM. Is this lookup behaviour also configurable (how?)? I'm thinking about a configuration with 2 ser proxies and one database backend. If the lookup only queries the cached location table, I would have to froward the registrations between the two proxies via t_replicate. But wouldn't this cause both proxies to update the database resulting in two entries in the location table for each registration? regards, Klaus

21 years, 3 months

[Serusers] Prepaid accounting

by Director General: NEFACOMP

Is there any module that implements a prepaid acccounting scheme with SER? Thanks, __________________________________ NZEYIMANA Emery Fabrice NEFA Computing Services, Inc. P.O. Box 5078 Kigali Office Phone: +250-51 11 06 Office Fax: +250-50 15 19 Mobile: +250-08517768 Email: dg(a)nefacomp.net http://www.nefacomp.net/

21 years, 3 months

[Serusers] sorry -- cannot open fifo

by Madan

hi why do i get this error while web provisioning l sorry -- cannot open fifo relevant part of my config.php $this->web_contact="sip:xyqw@sip.net4india.com"; //address of pseudo sender $this->fifo_server="/tmp/"; //path to fifo server $this->reply_fifo_filename="ser_fifo_".rand(); $this->reply_fifo_path="/tmp/".$this->reply_fifo_filename; i would appreciate any help regards, Madan

21 years, 3 months

[Serusers] SER restarts X whenever there is a config error

by Director General: NEFACOMP

I don't know if this is a bug. Whenever SER encounters an error in the ser.cfg file, it restarts the X server (or KDE. I might be confused but what I know is that it logges me out). Is there any way of overcoming this problem. Because if I have some other jobs that I am doing, it closes everything and I have to relogin. Thanks, __________________________________ NZEYIMANA Emery Fabrice NEFA Computing Services, Inc. P.O. Box 5078 Kigali Office Phone: +250-51 11 06 Office Fax: +250-50 15 19 Mobile: +250-08517768 Email: dg(a)nefacomp.net http://www.nefacomp.net/

21 years, 3 months

[Serusers] send_reply() error from pa module

by Kevin Chu

Hi, I tried to use the pa modules to process SUBSCRIBE request from SIP user. However, the following error message was returned when the pa module tried to send 200 OK response: 0(19584) ERROR: t_reply: cannot send a t_reply to a message for which no T-state has been established 0(19584) send_reply(): Error while sending 200 OK Looks like the transaction state was missing while sending the response. Please see the attached debug and error message. I can't figure out the reason for that error, could anybody help me out? Thanks! BR, Kevin

21 years, 3 months

[Serusers] sipsack

by Madan

hi all m newbie to ser but have found it to be good, i have done the installation of ser with mysql and now i want to debugg,trace etc using sipstack but i m getting the following error after issuing the command - sipsak -s sip:100@sip.xyz.com -vv error: this FQDN or IP is not valid: sip i would appreciate if anybody on list can point me to a right direction regards, Madan

21 years, 3 months

[Serusers] Dynamic routing on SER

by jaime＠umtstrial.co.uk

Hello all, I am wondering if Iptel is thinking about implementing an extension to provide dynamic routing configuration obtained from an external device (a database or other SIP server). The extension could be a module that, given a specific criteria (specific user/group, SIP method, time of day, subscribed service) would route SIP messages (may be with modifications) to another SIP entity. I would imagine that with the current implementation of SER, you could use the existing location table store any triggers for a specific user, something like this: if (method==REGISTER) { # Authenticate user.... save ("location"); get_profile("Service_Set_DB"); set_profile("location"); } When any message from that user comes in, it would be possible to check the profile in this way: if (method==INVITE) { check_profile("location"); # may be modify SIP message according to what came back from DB t_relay(); } So any changes on routing criteria could be held on a database (SQL, LDAP, RADIUS, DIAMETER...) and changed there instead on the "route" clause. The difficult part would probably be to establish the Service Set format and modify the location or create another table to reflect those triggers for that particular user. But I think the rest is not that far from now... Is there anything like that in place or any plans to have it implemented? Jaime

21 years, 3 months

Jump to page:

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