sr-users August 2003

sr-users@lists.kamailio.org

67 participants
144 discussions

RE: [Serusers] Windows messenger 5.0 and instant messages not working with ser?
by Timo Santi 25 Aug '03

25 Aug '03

You are probably right. If have send report to MS, so lets see what they will answer. Here is SIP messages so that you can also see what is happening. Here is printed messages from capture. If you wan't to have captured files I can send those by e-mail. ********************************************************** Instant message from messenger 4.7 to messenger 5.0 message is not received and 4.7 messenger doesn't show any error ********************************************************** ********************************************************** Frame 2 (619 bytes on wire, 619 bytes captured) Linux cooked capture Internet Protocol, Src Addr: MESSENGER 4.7, Dst Addr: SIP SERVER User Datagram Protocol, Src Port: 3241 (3241), Dst Port: 5060 (5060) Session Initiation Protocol Request line: MESSAGE sip:timo.santi@finlux.fi SIP/2.0 Method: MESSAGE Message Header Via: SIP/2.0/UDP 10.1.1.9:7822 From: "trainingcenter" <sip:trainingcenter@finlux.fi>;tag=36d7fa67-ed2d-44e3- b020-80bd4acb3acb To: <sip:timo.santi@finlux.fi> Call-ID: a24f9bfc-79c7-41aa-8ef4- 4107c733b73a(a)10.1.1.9 CSeq: 1 MESSAGE Contact: <sip:10.1.1.9:7822> User-Agent: Windows RTC/1.0 Content-Type: text/plain; charset=UTF- 8;msgr=WAAtAE0ATQBTAC0ASQBNAC0ARgBvAHIAbQBhAHQAOgAgAEYATgA 9AE0AUwAlADIAMABTAGgAZQBsAGwAJQAyADAARABsAGcAOwAgAEUARgA9A DsAIABDAE8APQAwADsAIABDAFMAPQAwADsAIABQAEYAPQAwAA0ACgANAAo A Content-Length: 5 Session Description Protocol Invalid line: qqqqq Frame 3 (697 bytes on wire, 697 bytes captured) Linux cooked capture Internet Protocol, Src Addr: SIP SERVER, Dst Addr: MESSENGER 5.0 User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 7752 (7752) Session Initiation Protocol Request line: MESSAGE sip:192.168.19.127:7752 SIP/2.0 Method: MESSAGE Message Header Max-Forwards: 10 Via: SIP/2.0/UDP 80.74.213.68;branch=z9hG4bKe13d.5fff58c6.0 Via: SIP/2.0/UDP 10.1.1.9:7822 From: "trainingcenter" <sip:trainingcenter@finlux.fi>;tag=36d7fa67-ed2d-44e3- b020-80bd4acb3acb To: <sip:timo.santi@finlux.fi> Call-ID: a24f9bfc-79c7-41aa-8ef4- 4107c733b73a(a)10.1.1.9 CSeq: 1 MESSAGE Contact: <sip:10.1.1.9:7822> User-Agent: Windows RTC/1.0 Content-Type: text/plain; charset=UTF- 8;msgr=WAAtAE0ATQBTAC0ASQBNAC0ARgBvAHIAbQBhAHQAOgAgAEYATgA 9AE0AUwAlADIAMABTAGgAZQBsAGwAJQAyADAARABsAGcAOwAgAEUARgA9A DsAIABDAE8APQAwADsAIABDAFMAPQAwADsAIABQAEYAPQAwAA0ACgANAAo A Content-Length: 5 Session Description Protocol Invalid line: qqqqq Frame 4 (437 bytes on wire, 437 bytes captured) Linux cooked capture Internet Protocol, Src Addr: MESSENGER 5.0, Dst Addr: SIP SERVER User Datagram Protocol, Src Port: 3015 (3015), Dst Port: 5060 (5060) Session Initiation Protocol Status line: SIP/2.0 100 Trying Status-Code: 100 Message Header Via: SIP/2.0/UDP 80.74.213.68;branch=z9hG4bKe13d.5fff58c6.0 Via: SIP/2.0/UDP 10.1.1.9:7822 From: "trainingcenter" <sip:trainingcenter@finlux.fi>;tag=36d7fa67-ed2d-44e3- b020-80bd4acb3acb To: <sip:timo.santi@finlux.fi>;tag=93cc5f563a2645f49698e4b3f55 981c9 Call-ID: a24f9bfc-79c7-41aa-8ef4- 4107c733b73a(a)10.1.1.9 CSeq: 1 MESSAGE User-Agent: RTC/1.2 Content-Length: 0 Frame 5 (469 bytes on wire, 469 bytes captured) Linux cooked capture Internet Protocol, Src Addr: MESSENGER 5.0, Dst Addr: SIP SERVER User Datagram Protocol, Src Port: 3015 (3015), Dst Port: 5060 (5060) Session Initiation Protocol Status line: SIP/2.0 200 OK Status-Code: 200 Message Header Via: SIP/2.0/UDP 80.74.213.68;branch=z9hG4bKe13d.5fff58c6.0 Via: SIP/2.0/UDP 10.1.1.9:7822 From: "trainingcenter" <sip:trainingcenter@finlux.fi>;tag=36d7fa67-ed2d-44e3- b020-80bd4acb3acb To: <sip:timo.santi@finlux.fi>;tag=93cc5f563a2645f49698e4b3f55 981c9 Call-ID: a24f9bfc-79c7-41aa-8ef4- 4107c733b73a(a)10.1.1.9 CSeq: 1 MESSAGE Contact: <sip:192.168.19.127:7752> User-Agent: RTC/1.2 Content-Length: 0 Frame 6 (408 bytes on wire, 408 bytes captured) Linux cooked capture Internet Protocol, Src Addr: SIP SERVER, Dst Addr: MESSENGER 4.7 User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 7822 (7822) Session Initiation Protocol Status line: SIP/2.0 200 OK Status-Code: 200 Message Header Via: SIP/2.0/UDP 10.1.1.9:7822 From: "trainingcenter" <sip:trainingcenter@finlux.fi>;tag=36d7fa67-ed2d-44e3- b020-80bd4acb3acb To: <sip:timo.santi@finlux.fi>;tag=93cc5f563a2645f49698e4b3f55 981c9 Call-ID: a24f9bfc-79c7-41aa-8ef4- 4107c733b73a(a)10.1.1.9 CSeq: 1 MESSAGE Contact: <sip:192.168.19.127:7752> User-Agent: RTC/1.2 Content-Length: 0 Frame 8 (407 bytes on wire, 407 bytes captured) Linux cooked capture Internet Protocol, Src Addr: MESSENGER 5.0, Dst Addr: MESSENGER 4.7 User Datagram Protocol, Src Port: 3017 (3017), Dst Port: 7822 (7822) Session Initiation Protocol Request line: BYE sip:10.1.1.9:7822 SIP/2.0 Method: BYE Message Header Via: SIP/2.0/UDP 192.168.19.127:7752 Max-Forwards: 70 From: <sip:timo.santi@finlux.fi>;tag=93cc5f563a2645f49698e4b3f55 981c9 To: "trainingcenter" <sip:trainingcenter@finlux.fi>;tag=36d7fa67-ed2d-44e3- b020-80bd4acb3acb Call-ID: a24f9bfc-79c7-41aa-8ef4- 4107c733b73a(a)10.1.1.9 CSeq: 1 BYE User-Agent: RTC/1.2 Content-Length: 0 Frame 11 (412 bytes on wire, 412 bytes captured) Linux cooked capture Internet Protocol, Src Addr: MESSENGER 4.7, Dst Addr: MESSENGER 5.0 User Datagram Protocol, Src Port: 3242 (3242), Dst Port: 7752 (7752) Session Initiation Protocol Status line: SIP/2.0 200 OK Status-Code: 200 Message Header Via: SIP/2.0/UDP 192.168.19.127:7752 From: <sip:timo.santi@finlux.fi>;tag=93cc5f563a2645f49698e4b3f55 981c9 To: "trainingcenter" <sip:trainingcenter@finlux.fi>;tag=36d7fa67-ed2d-44e3- b020-80bd4acb3acb Call-ID: a24f9bfc-79c7-41aa-8ef4- 4107c733b73a(a)10.1.1.9 CSeq: 1 BYE Contact: <sip:10.1.1.9:7822> User-Agent: Windows RTC/1.0 Content-Length: 0 ********************************************************** Instant message from messenger 5.0 to messenger 5.0 message is not received and 5.0 messenger shows error "The following message could not be delivered to all recipients:" ********************************************************** ************************************* Frame 14 (554 bytes on wire, 554 bytes captured) Linux cooked capture Internet Protocol, Src Addr: MESSENGER 5.0 SENDER, Dst Addr: SIP SERVER User Datagram Protocol, Src Port: 3254 (3254), Dst Port: 5060 (5060) Session Initiation Protocol Request line: INVITE sip:timo.santi@finlux.fi SIP/2.0 Method: INVITE Message Header Via: SIP/2.0/UDP 10.1.1.9:9549 Max-Forwards: 70 From: "trainingcenter(a)finlux.fi" <sip:trainingcenter@finlux.fi>;tag=2109e870f95843b485f2537 b4df42fb2;epid=bb96c233b3 To: <sip:timo.santi@finlux.fi> Call-ID: b2569878755a467c863981bbc2192b49(a)10.1.1.9 CSeq: 1 INVITE Contact: <sip:10.1.1.9:9549> User-Agent: RTC/1.2 Content-Type: application/sdp Content-Length: 97 Session Description Protocol Session Description Protocol Version (v): 0 Owner/Creator, Session Id (o): - 0 0 IN IP4 10.1.1.9 Owner Username: - Session ID: 0 Session Version: 0 Owner Network Type: IN Owner Address Type: IP4 Owner Address: 10.1.1.9 Session Name (s): session Connection Information (c): IN IP4 10.1.1.9 Connection Network Type: IN Connection Address Type: IP4 Connection Address: 10.1.1.9 Time Description, active time (t): 0 0 Session Start Time: 0 Session Start Time: 0 Media Description, name and address (m): x-ms-message 5060 sip null Media Type: x-ms-message Media Port: 5060 Media Proto: sip Media Format: null Frame 16 (578 bytes on wire, 578 bytes captured) Linux cooked capture Internet Protocol, Src Addr: SIP SERVER, Dst Addr: MESSENGER 5.0 SENDER User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 9549 (9549) Session Initiation Protocol Status line: SIP/2.0 100 trying -- your call is important to us Status-Code: 100 Message Header Via: SIP/2.0/UDP 10.1.1.9:9549 From: "trainingcenter(a)finlux.fi" <sip:trainingcenter@finlux.fi>;tag=2109e870f95843b485f2537 b4df42fb2;epid=bb96c233b3 To: <sip:timo.santi@finlux.fi> Call-ID: b2569878755a467c863981bbc2192b49(a)10.1.1.9 CSeq: 1 INVITE Server: Sip EXpress router (0.8.10 (i386/linux)) Content-Length: 0 Warning: 392 80.74.213.68:5060 "Noisy feedback tells: pid=17349 req_src_ip=10.1.1.9 in_uri=sip:timo.santi@finlux.fi out_uri=sip:192.168.19.127:7752 via_cnt==1" Frame 17 (614 bytes on wire, 614 bytes captured) Linux cooked capture Internet Protocol, Src Addr: SIP SERVER, Dst Addr: MESSENGER 5.0 RECEIVER User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 7752 (7752) Session Initiation Protocol Request line: INVITE sip:192.168.19.127:7752 SIP/2.0 Method: INVITE Message Header Via: SIP/2.0/UDP 80.74.213.68;branch=z9hG4bK20d5.2468f597.0 Via: SIP/2.0/UDP 10.1.1.9:9549 Max-Forwards: 69 From: "trainingcenter(a)finlux.fi" <sip:trainingcenter@finlux.fi>;tag=2109e870f95843b485f2537 b4df42fb2;epid=bb96c233b3 To: <sip:timo.santi@finlux.fi> Call-ID: b2569878755a467c863981bbc2192b49(a)10.1.1.9 CSeq: 1 INVITE Contact: <sip:10.1.1.9:9549> User-Agent: RTC/1.2 Content-Type: application/sdp Content-Length: 97 Session Description Protocol Session Description Protocol Version (v): 0 Owner/Creator, Session Id (o): - 0 0 IN IP4 10.1.1.9 Owner Username: - Session ID: 0 Session Version: 0 Owner Network Type: IN Owner Address Type: IP4 Owner Address: 10.1.1.9 Session Name (s): session Connection Information (c): IN IP4 10.1.1.9 Connection Network Type: IN Connection Address Type: IP4 Connection Address: 10.1.1.9 Time Description, active time (t): 0 0 Session Start Time: 0 Session Start Time: 0 Media Description, name and address (m): x-ms-message 5060 sip null Media Type: x-ms-message Media Port: 5060 Media Proto: sip Media Format: null Frame 18 (454 bytes on wire, 454 bytes captured) Linux cooked capture Internet Protocol, Src Addr: MESSENGER 5.0 RECEIVER, Dst Addr: SIP SERVER User Datagram Protocol, Src Port: 3015 (3015), Dst Port: 5060 (5060) Session Initiation Protocol Status line: SIP/2.0 100 Trying Status-Code: 100 Message Header Via: SIP/2.0/UDP 80.74.213.68;branch=z9hG4bK20d5.2468f597.0 Via: SIP/2.0/UDP 10.1.1.9:9549 From: "trainingcenter(a)finlux.fi" <sip:trainingcenter@finlux.fi>;tag=2109e870f95843b485f2537 b4df42fb2;epid=bb96c233b3 To: <sip:timo.santi@finlux.fi>;tag=0de4e1d5e1d84606a6c44f4b1ff c5bc1 Call-ID: b2569878755a467c863981bbc2192b49(a)10.1.1.9 CSeq: 1 INVITE User-Agent: RTC/1.2 Content-Length: 0 Frame 19 (628 bytes on wire, 628 bytes captured) Linux cooked capture Internet Protocol, Src Addr: MESSENGER 5.0 RECEIVER, Dst Addr: SIP SERVER User Datagram Protocol, Src Port: 3015 (3015), Dst Port: 5060 (5060) Session Initiation Protocol Status line: SIP/2.0 200 OK Status-Code: 200 Message Header Via: SIP/2.0/UDP 80.74.213.68;branch=z9hG4bK20d5.2468f597.0 Via: SIP/2.0/UDP 10.1.1.9:9549 From: "trainingcenter(a)finlux.fi" <sip:trainingcenter@finlux.fi>;tag=2109e870f95843b485f2537 b4df42fb2;epid=bb96c233b3 To: <sip:timo.santi@finlux.fi>;tag=0de4e1d5e1d84606a6c44f4b1ff c5bc1 Call-ID: b2569878755a467c863981bbc2192b49(a)10.1.1.9 CSeq: 1 INVITE Contact: <sip:192.168.19.127:7752> User-Agent: RTC/1.2 Content-Type: application/sdp Content-Length: 109 Session Description Protocol Session Description Protocol Version (v): 0 Owner/Creator, Session Id (o): - 0 0 IN IP4 192.168.19.127 Owner Username: - Session ID: 0 Session Version: 0 Owner Network Type: IN Owner Address Type: IP4 Owner Address: 192.168.19.127 Session Name (s): session Connection Information (c): IN IP4 192.168.19.127 Connection Network Type: IN Connection Address Type: IP4 Connection Address: 192.168.19.127 Time Description, active time (t): 0 0 Session Start Time: 0 Session Start Time: 0 Media Description, name and address (m): x-ms-message 5060 sip null Media Type: x-ms-message Media Port: 5060 Media Proto: sip Media Format: null Frame 20 (567 bytes on wire, 567 bytes captured) Linux cooked capture Internet Protocol, Src Addr: SIP SERVER, Dst Addr: MESSENGER 5.0 SENDER User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 9549 (9549) Session Initiation Protocol Status line: SIP/2.0 200 OK Status-Code: 200 Message Header Via: SIP/2.0/UDP 10.1.1.9:9549 From: "trainingcenter(a)finlux.fi" <sip:trainingcenter@finlux.fi>;tag=2109e870f95843b485f2537 b4df42fb2;epid=bb96c233b3 To: <sip:timo.santi@finlux.fi>;tag=0de4e1d5e1d84606a6c44f4b1ff c5bc1 Call-ID: b2569878755a467c863981bbc2192b49(a)10.1.1.9 CSeq: 1 INVITE Contact: <sip:192.168.19.127:7752> User-Agent: RTC/1.2 Content-Type: application/sdp Content-Length: 109 Session Description Protocol Session Description Protocol Version (v): 0 Owner/Creator, Session Id (o): - 0 0 IN IP4 192.168.19.127 Owner Username: - Session ID: 0 Session Version: 0 Owner Network Type: IN Owner Address Type: IP4 Owner Address: 192.168.19.127 Session Name (s): session Connection Information (c): IN IP4 192.168.19.127 Connection Network Type: IN Connection Address Type: IP4 Connection Address: 192.168.19.127 Time Description, active time (t): 0 0 Session Start Time: 0 Session Start Time: 0 Media Description, name and address (m): x-ms-message 5060 sip null Media Type: x-ms-message Media Port: 5060 Media Proto: sip Media Format: null Frame 22 (425 bytes on wire, 425 bytes captured) Linux cooked capture Internet Protocol, Src Addr: MESSENGER 5.0 RECEIVER, Dst Addr: MESSENGER 5.0 SENDER User Datagram Protocol, Src Port: 3018 (3018), Dst Port: 9549 (9549) Session Initiation Protocol Request line: BYE sip:10.1.1.9:9549 SIP/2.0 Method: BYE Message Header Via: SIP/2.0/UDP 192.168.19.127:7752 Max-Forwards: 70 From: <sip:timo.santi@finlux.fi>;tag=0de4e1d5e1d84606a6c44f4b1ff c5bc1 To: "trainingcenter(a)finlux.fi" <sip:trainingcenter@finlux.fi>;tag=2109e870f95843b485f2537 b4df42fb2;epid=bb96c233b3 Call-ID: b2569878755a467c863981bbc2192b49(a)10.1.1.9 CSeq: 1 BYE User-Agent: RTC/1.2 Content-Length: 0 Frame 25 (425 bytes on wire, 425 bytes captured) Linux cooked capture Internet Protocol, Src Addr: MESSENGER 5.0 SENDER, Dst Addr: MESSENGER 5.0 RECEIVER User Datagram Protocol, Src Port: 3255 (3255), Dst Port: 7752 (7752) Session Initiation Protocol Request line: ACK sip:192.168.19.127:7752 SIP/2.0 Method: ACK Message Header Via: SIP/2.0/UDP 10.1.1.9:9549 Max-Forwards: 70 From: "trainingcenter(a)finlux.fi" <sip:trainingcenter@finlux.fi>;tag=2109e870f95843b485f2537 b4df42fb2;epid=bb96c233b3 To: <sip:timo.santi@finlux.fi>;tag=0de4e1d5e1d84606a6c44f4b1ff c5bc1 Call-ID: b2569878755a467c863981bbc2192b49(a)10.1.1.9 CSeq: 1 ACK User-Agent: RTC/1.2 Content-Length: 0 Frame 28 (694 bytes on wire, 694 bytes captured) Linux cooked capture Internet Protocol, Src Addr: MESSENGER 5.0 SENDER, Dst Addr: MESSENGER 5.0 RECEIVER User Datagram Protocol, Src Port: 3255 (3255), Dst Port: 7752 (7752) Session Initiation Protocol Request line: MESSAGE sip:192.168.19.127:7752 SIP/2.0 Method: MESSAGE Message Header Via: SIP/2.0/UDP 10.1.1.9:9549 Max-Forwards: 70 From: "trainingcenter(a)finlux.fi" <sip:trainingcenter@finlux.fi>;tag=2109e870f95843b485f2537 b4df42fb2;epid=bb96c233b3 To: <sip:timo.santi@finlux.fi>;tag=0de4e1d5e1d84606a6c44f4b1ff c5bc1 Call-ID: b2569878755a467c863981bbc2192b49(a)10.1.1.9 CSeq: 2 MESSAGE Contact: <sip:10.1.1.9:9549> User-Agent: RTC/1.2 Content-Type: text/plain; charset=UTF- 8;msgr=WAAtAE0ATQBTAC0ASQBNAC0ARgBvAHIAbQBhAHQAOgAgAEYATgA 9AE0AUwAlADIAMABTAGgAZQBsAGwAJQAyADAARABsAGcAJQAyADAAMgA7A CAARQBGAD0AOwAgAEMATwA9ADAAOwAgAEMAUwA9ADEAOwAgAFAARgA9ADA ADQAKAA0ACgA Content-Length: 5 Session Description Protocol Invalid line: ttttt Frame 31 (392 bytes on wire, 392 bytes captured) Linux cooked capture Internet Protocol, Src Addr: MESSENGER 5.0 SENDER, Dst Addr: MESSENGER 5.0 RECEIVER User Datagram Protocol, Src Port: 3255 (3255), Dst Port: 7752 (7752) Session Initiation Protocol Status line: SIP/2.0 200 OK Status-Code: 200 Message Header Via: SIP/2.0/UDP 192.168.19.127:7752 From: <sip:timo.santi@finlux.fi>;tag=0de4e1d5e1d84606a6c44f4b1ff c5bc1 To: "trainingcenter(a)finlux.fi" <sip:trainingcenter@finlux.fi>;tag=2109e870f95843b485f2537 b4df42fb2;epid=bb96c233b3 Call-ID: b2569878755a467c863981bbc2192b49(a)10.1.1.9 CSeq: 1 BYE User-Agent: RTC/1.2 Content-Length: 0 Frame 34 (423 bytes on wire, 423 bytes captured) Linux cooked capture Internet Protocol, Src Addr: MESSENGER 5.0 RECEIVER, Dst Addr: MESSENGER 5.0 SENDER User Datagram Protocol, Src Port: 3018 (3018), Dst Port: 9549 (9549) Session Initiation Protocol Status line: SIP/2.0 481 Call Leg/Transaction Does Not Exist Status-Code: 481 Message Header Via: SIP/2.0/UDP 10.1.1.9:9549 From: "trainingcenter(a)finlux.fi" <sip:trainingcenter@finlux.fi>;tag=2109e870f95843b485f2537 b4df42fb2;epid=bb96c233b3 To: <sip:timo.santi@finlux.fi>;tag=0de4e1d5e1d84606a6c44f4b1ff c5bc1 Call-ID: b2569878755a467c863981bbc2192b49(a)10.1.1.9 CSeq: 2 MESSAGE User-Agent: RTC/1.2 Content-Length: 0 ********************************************************** -----Original Message----- From: Jiri Kuthan [mailto:jiri@iptel.org] Sent: 21. elokuuta 2003 8:22 To: Timo Santi; serusers(a)lists.iptel.org Subject: Re: [Serusers] Windows messenger 5.0 and instant messages not working with ser? We haven't tested against 5.0. The error possibly lies in Messenger itself -- 481 is mostly sent when dialog processing between two UAs is broken. SER inbetween two UAs does not affect dialog state. Anyhow, we will look at it. Thanks for reporting. -jiri At 10:21 PM 8/20/2003, Timo Santi wrote: >Hi all, > >Have anyone else notice any problems with new windows messenger 5.0 working with ser? Instant messages are working nicely with windows messenger 4.7, but with Windows messenger 5.0 voice and video calls are working, but messages cannot be sent. In capture I'm receiving "481 Call Leg/Transaction Does Not Exist". In SDP it is also saying: invalid line: "message text". I have tried with ser 0.8.10 and 0.8.11pre29. > >-Timo- >_______________________________________________ >Serusers mailing list >serusers(a)lists.iptel.org >http://lists.iptel.org/mailman/listinfo/serusers -- Jiri Kuthan http://iptel.org/~jiri/

1 0

RE: [Serusers] Latest STABLE build without using CVS
by Jitender Arora 25 Aug '03

25 Aug '03

Hi Andrei, I tried building with what u suggested , but this also did not help ...... the SER module builds o.k ...but other modules are not able to resolve some symbols ..... Here is the output : gmake[1]: Entering directory `/home/jitender/sip_router/modules/acc' gmake[1]: Leaving directory `/home/jitender/sip_router/modules/acc' gmake[1]: Entering directory `/home/jitender/sip_router/modules/acc' gcc -g -O9 -funroll-loops -Wall -mcpu=ultrasparc -mtune=ultrasparc -DNAM E='"ser"' -DVERSION='"0.8.11rc3"' -DARCH='"sparc64"' -DOS='"solaris"' -DCOMPILER ='"gcc 3.3"' -D__CPU_sparc64 -D__OS_solaris -DCFG_DIR='"/etc/ser/"' -DPKG_MALLOC -DSHM_MEM -DSHM_MMAP -DADAPTIVE_WAIT -DADAPTIVE_WAIT_LOOPS=1024 -DDNS_IP_HACK -DFAST_LOCK -DHAVE_GETIPNODEBYNAME -DHAVE_SYS_SOCKIO_H -DHAVE_SCHED_YIELD -c ac c.c -o acc.o gcc -g -O9 -funroll-loops -Wall -mcpu=ultrasparc -mtune=ultrasparc -DNAM E='"ser"' -DVERSION='"0.8.11rc3"' -DARCH='"sparc64"' -DOS='"solaris"' -DCOMPILER ='"gcc 3.3"' -D__CPU_sparc64 -D__OS_solaris -DCFG_DIR='"/etc/ser/"' -DPKG_MALLOC -DSHM_MEM -DSHM_MMAP -DADAPTIVE_WAIT -DADAPTIVE_WAIT_LOOPS=1024 -DDNS_IP_HACK -DFAST_LOCK -DHAVE_GETIPNODEBYNAME -DHAVE_SYS_SOCKIO_H -DHAVE_SCHED_YIELD -c ac c_mod.c -o acc_mod.o gcc acc.o acc_mod.o -o acc.so Undefined first referenced symbol in file dprint acc.o parse_uri acc.o get_authorized_cred acc.o mem_block acc.o isflagset acc_mod.o parse_headers acc_mod.o resetflag acc_mod.o parse_from_header acc_mod.o get_reply_status acc.o main /usr/local/lib/gcc-lib/sparc-sun-solaris2.7/ 3.3/crt1.o parse_orig_ruri acc_mod.o log_stderr acc.o qm_malloc acc.o find_export acc_mod.o qm_free acc.o debug acc.o ld: fatal: Symbol referencing errors. No output written to acc.so collect2: ld returned 1 exit status gmake[1]: *** [acc.so] Error 1 gmake[1]: Leaving directory `/home/jitender/sip_router/modules/acc' gmake[1]: Entering directory `/home/jitender/sip_router/modules/auth' gmake[1]: Leaving directory `/home/jitender/sip_router/modules/auth' gmake[1]: Entering directory `/home/jitender/sip_router/modules/auth' gcc -g -O9 -funroll-loops -Wall -mcpu=ultrasparc -mtune=ultrasparc -DNAM E='"ser"' -DVERSION='"0.8.11rc3"' -DARCH='"sparc64"' -DOS='"solaris"' -DCOMPILER ='"gcc 3.3"' -D__CPU_sparc64 -D__OS_solaris -DCFG_DIR='"/etc/ser/"' -DPKG_MALLOC -DSHM_MEM -DSHM_MMAP -DADAPTIVE_WAIT -DADAPTIVE_WAIT_LOOPS=1024 -DDNS_IP_HACK -DFAST_LOCK -DHAVE_GETIPNODEBYNAME -DHAVE_SYS_SOCKIO_H -DHAVE_SCHED_YIELD -c ap i.c -o api.o gcc -g -O9 -funroll-loops -Wall -mcpu=ultrasparc -mtune=ultrasparc -DNAM E='"ser"' -DVERSION='"0.8.11rc3"' -DARCH='"sparc64"' -DOS='"solaris"' -DCOMPILER ='"gcc 3.3"' -D__CPU_sparc64 -D__OS_solaris -DCFG_DIR='"/etc/ser/"' -DPKG_MALLOC -DSHM_MEM -DSHM_MMAP -DADAPTIVE_WAIT -DADAPTIVE_WAIT_LOOPS=1024 -DDNS_IP_HACK -DFAST_LOCK -DHAVE_GETIPNODEBYNAME -DHAVE_SYS_SOCKIO_H -DHAVE_SCHED_YIELD -c au th_mod.c -o auth_mod.o gcc -g -O9 -funroll-loops -Wall -mcpu=ultrasparc -mtune=ultrasparc -DNAM E='"ser"' -DVERSION='"0.8.11rc3"' -DARCH='"sparc64"' -DOS='"solaris"' -DCOMPILER ='"gcc 3.3"' -D__CPU_sparc64 -D__OS_solaris -DCFG_DIR='"/etc/ser/"' -DPKG_MALLOC -DSHM_MEM -DSHM_MMAP -DADAPTIVE_WAIT -DADAPTIVE_WAIT_LOOPS=1024 -DDNS_IP_HACK -DFAST_LOCK -DHAVE_GETIPNODEBYNAME -DHAVE_SYS_SOCKIO_H -DHAVE_SCHED_YIELD -c ch allenge.c -o challenge.o gcc -g -O9 -funroll-loops -Wall -mcpu=ultrasparc -mtune=ultrasparc -DNAM E='"ser"' -DVERSION='"0.8.11rc3"' -DARCH='"sparc64"' -DOS='"solaris"' -DCOMPILER ='"gcc 3.3"' -D__CPU_sparc64 -D__OS_solaris -DCFG_DIR='"/etc/ser/"' -DPKG_MALLOC -DSHM_MEM -DSHM_MMAP -DADAPTIVE_WAIT -DADAPTIVE_WAIT_LOOPS=1024 -DDNS_IP_HACK -DFAST_LOCK -DHAVE_GETIPNODEBYNAME -DHAVE_SYS_SOCKIO_H -DHAVE_SCHED_YIELD -c co mmon.c -o common.o gcc -g -O9 -funroll-loops -Wall -mcpu=ultrasparc -mtune=ultrasparc -DNAM E='"ser"' -DVERSION='"0.8.11rc3"' -DARCH='"sparc64"' -DOS='"solaris"' -DCOMPILER ='"gcc 3.3"' -D__CPU_sparc64 -D__OS_solaris -DCFG_DIR='"/etc/ser/"' -DPKG_MALLOC -DSHM_MEM -DSHM_MMAP -DADAPTIVE_WAIT -DADAPTIVE_WAIT_LOOPS=1024 -DDNS_IP_HACK -DFAST_LOCK -DHAVE_GETIPNODEBYNAME -DHAVE_SYS_SOCKIO_H -DHAVE_SCHED_YIELD -c no nce.c -o nonce.o gcc -g -O9 -funroll-loops -Wall -mcpu=ultrasparc -mtune=ultrasparc -DNAM E='"ser"' -DVERSION='"0.8.11rc3"' -DARCH='"sparc64"' -DOS='"solaris"' -DCOMPILER ='"gcc 3.3"' -D__CPU_sparc64 -D__OS_solaris -DCFG_DIR='"/etc/ser/"' -DPKG_MALLOC -DSHM_MEM -DSHM_MMAP -DADAPTIVE_WAIT -DADAPTIVE_WAIT_LOOPS=1024 -DDNS_IP_HACK -DFAST_LOCK -DHAVE_GETIPNODEBYNAME -DHAVE_SYS_SOCKIO_H -DHAVE_SCHED_YIELD -c rp id.c -o rpid.o gcc api.o auth_mod.o challenge.o common.o nonce.o rpid.o -o auth.so Undefined first referenced symbol in file insert_new_lump_before rpid.o dprint api.o parse_uri common.o check_dig_cred api.o parse_to rpid.o parse_credentials api.o build_lump_rpl common.o get_authorized_cred challenge.o mem_block auth_mod.o MD5Update nonce.o add_lump_rpl common.o anchor_lump rpid.o parse_headers api.o MD5Final nonce.o parse_from_header common.o mark_authorized_cred api.o main /usr/local/lib/gcc-lib/sparc-sun-solaris2.7/ 3.3/crt1.o log_stderr api.o del_lump challenge.o qm_malloc auth_mod.o find_export auth_mod.o qm_free auth_mod.o debug api.o MD5Init nonce.o ld: fatal: Symbol referencing errors. No output written to auth.so collect2: ld returned 1 exit status gmake[1]: *** [auth.so] Error 1 gmake[1]: Leaving directory `/home/jitender/sip_router/modules/auth' Thanks , Jitender -----Original Message----- From: Andrei Pelinescu-Onciul [mailto:pelinescu-onciul@fokus.fraunhofer.de] Sent: Friday, August 22, 2003 10:11 AM To: Jitender Arora Cc: 'serusers(a)lists.iptel.org' Subject: Re: [Serusers] Latest STABLE build without using CVS On Aug 22, 2003 at 09:25, Jitender Arora <jarora(a)aastra.com> wrote: > Thanks ... > > I have Sun,Ultra2 Machine..... > > Here is the version Info > home/jitender % version > Machine hardware: sun4u > OS version: 5.7 > Processor type: sparc > Hardware: SUNW,Ultra-2 Please send me also the output of uname -s and uname -m (uname -m should return sun4u, but it seems it doesn't). > > Now the SER is build o.k , but i am not able to build other modules as > during the Linking Time , i get some errors , > that it is not able to find some symbos , which are being used This are all symbols from ser. The modules link flags are bad. Try adding ARCH=sparc64 & OS=solaris. If you still have problems, send me the compilation output (I want to see the "linking line" especially, the last gcc line when compiling a module). You can try just: gmake ARCH=sparc64 OS=solaris modules=modules/textops modules -- to test-compile just one module; if it works recompile the whole ser this way: gmake proper; gmake ARCH=sparc64 OS=solaris all and drop me an email. Andrei

2 1

[Serusers] 45% OFF TOPIC (SIPTel settings)
by Director General: NEFACOMP 25 Aug '03

25 Aug '03

I have recently bought a SIPTel device (http://www.sipmicro.com) but after reading, rereading and rereading the manuals and the webpages I can't figure out how to use my phone with SER because I can't see where to set the SIP proxy address. Does any one know how I can do this? I sent an Email to them asking but they have never replied. The one who sold it to me is not willing or is not well trained to know how to tell me that because she seems to not know it. Of course it works with SIP proxy server of the one who sold it to me. 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/

2 1

Re: [Serusers] ser support IPv6 ?
by Jiri Kuthan 25 Aug '03

25 Aug '03

We have used our own very prototypical one, bonephone. -jiri At 06:18 AM 7/19/2003, Ng, Soo Sim wrote: >May I know which IPv6 UA Client do you use? >SSng > >_______________________________________________ >Serusers mailing list >serusers(a)lists.iptel.org >http://lists.iptel.org/mailman/listinfo/serusers -- Jiri Kuthan http://iptel.org/~jiri/

3 5

Re: [Serusers] bad header
by Jiri Kuthan 25 Aug '03

25 Aug '03

Gary, my appologies, your question apparently was never replied. Does the problem persist? If so, can you send the captured message which caused this behavour? Thanks, -jiri At 03:15 PM 8/4/2003, Gary Brewer wrote: >Hello, > >I am trying to get the SIP Express Router going on FreeBSD 4.8 Release. > >When I try to connect to the SIP server from MSN messenger 5.0.0149 I get >the following error message shown below, numerous times! > >Any ideas :) > >Gary > > >Aug 4 15:08:32 sniper ./ser[618]: ERROR: get_hdr_field: bad header >Aug 4 15:08:32 sniper ./ser[618]: ERROR: build_res_buf_from_sip_req: >alas, parse_headers failed > > > >_______________________________________________ >Serusers mailing list >serusers(a)lists.iptel.org >http://lists.iptel.org/mailman/listinfo/serusers -- Jiri Kuthan http://iptel.org/~jiri/

1 0

[Serusers] questions about ser & MSN 4.6
by Hassan CHOUMAR 25 Aug '03

25 Aug '03

Hello, I installed serweb with the server SIP on a PC, and he works very well, But I have a problem at the level of the recording on one to use User Agent MSNMessenger 4.6, I configured well the MSN and later, during the recording, it does not give me the permission, On the other hand mysql work with the server ser, because I made out a will ca by: root >/usr/sbin/serctl moni and root >/usr/sbin/serctl ps I realized an analysis of the network between the server and the machine, I saw that the message to registrar SIP is sent on the server but he does not answer to accuse the demand. Anybody between you knows where from comes the problem Thank you in advance Hassan ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/

1 0

[Serusers] questions about redirect server ??
by Hassan CHOUMAR 25 Aug '03

25 Aug '03

Hello all, I shall want to know how we realize redirect of call in ser, What is that it is enough to put the code existing in the guide ( redirect.cfg ) in the ser.cfg file and redemarrer the waiter(server) or how?? # # $Id: redirect.cfg,v 1.4 2002/10/04 21:37:11 jiri Exp $ # # this example shows use of ser as stateless redirect server # # ------------------ module loading ---------------------------------- loadmodule "modules/sl/sl.so" # ------------------------- request routing logic ------------------- # main routing logic route{ # for testing purposes, simply okay all REGISTERs if (method=="REGISTER") { log("REGISTER"); sl_send_reply("200", "ok"); break; }; # rewrite current URI, which is always part of destination ser rewriteuri("sip:parallel@iptel.org:9"); # append one more URI to the destination ser append_branch("sip:redirect@iptel.org:9"); # redirect now sl_send_reply("300", "Redirect"); } Thank you in advance Hassan ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/

1 0

[Serusers] Problem starting
by Felix Schmid 25 Aug '03

25 Aug '03

Hello all, I am a beginner to ser; I hope I can get some help on this list with my problem. I got ser running on several machines on my home network (it's not difficult though); however now I am trying run install ser on my internet host, which runs on a virtual machine, to set up my own small test bed. The provider limits the memory to be used by each vm to 32MB. When I start ser I get this error: #/usr/sbin/ser 'Too much shared memory demanded: 33554432' Is it possible to change the amount of memory ser allocates? I have read the docs and guides accompanying ser, but I can't remember having read something about an option like this. Can I just change the amount of memory being allocated in the sourcecode without screwing ser up? I can live with ser not being able to serve thousands of requests - a couple of dozens is enough for me. If so, can someone point me to the line of code that is causing the error (I am suspecting the ser memory allocation initialization routine)? Help would be very appreciated, cheers, felix

2 3

Re: [Serusers] Voicmail - Absence of DVOICE_MAIL and D_TOTAG in ser.cfg
by Jiri Kuthan 25 Aug '03

25 Aug '03

At 09:29 AM 8/25/2003, Chad Brown wrote: >Content-class: urn:content-classes:message >Content-Type: multipart/alternative; > boundary="----_=_NextPart_001_01C36ADA.9636EC00" > >Ser Version: ser 0.8.11rc4 (i386/linux) Downloaded from <http://iptel.org/ser/tarball>http://iptel.org/ser/tarball > > > >One of the first steps under Compilation and Installationof voicemail services mentions the necessity to uncomment DVOICE_MAIL and D_TOTAG in the ser.cfg file. (<ftp://ftp.berlios.de/pub/ser/0.8.11pre29/doc/seruser.pdf>ftp://ftp.berlios.de/pub/ser/0.8.11pre29/doc/seruser.pdf) Unfortunately, I was unable to find these sections/words in the file. > > > >Is this no longer necessary in the version I am running. (See above) That was mistakenly left over from 8.10 documentation and is removed now. -Jiri

1 0

Re: [Serusers] Force MySQL Authentication
by Jiri Kuthan 25 Aug '03

25 Aug '03

You need to configure your script correctly, that's it. You are reading the documentation on the web which refers to last release, 8.10, and using tarball of 8.11 -- that's where some of your confusion comes from. You need to rebuild with mysql support (make include_modules=mysql all, make include_modules=mysql install) and uncomment authentication-related lines from ser.cfg. The value of realm can be changed in the first parameter of www_(authorize|challenge). To deal with Windows Messenger bugs, preferablys set it to your sever's domain name. -Jiri ps -- I suggest you stick to problem reporting guidelines as on our website. It is hard otherwise to see what's wrong. Scripts and messages are important. At 09:01 AM 8/25/2003, Chad Brown wrote: >Content-class: urn:content-classes:message >Content-Type: multipart/alternative; > boundary="----_=_NextPart_001_01C36AD6.C426B8C4" > >Ser Version: ser 0.8.11rc4 (i386/linux) Downloaded from <http://iptel.org/ser/tarball>http://iptel.org/ser/tarball > > > >After downloading the .tgz on August 23: > > > * Installed latest version of MySQL > * ran: make all > * ran: make install > * performed steps outlined in Dan Austins HOWTO to enable MySQL authentication in ser.cfg > * Added user/s > * Restarted ser > > > >I noticed that users not in the database could still register with ser. > > > >FHI - There seams to be a discrepancy between Dan Austins HOWTO and the INSTALL document on <http://iptel.org/>http://iptel.org. Dans only mentioned uncommenting /usr/lib/ser/modules/mysql.so where the INSTALL document mentions loadmodule "/usr/local/lib/ser/modules/auth.so" as well. The reality is, there is a third line namely loadmodule "/usr/local/lib/ser/modules/auth_db.so". Regardless, I tried all variations. > > > >Just to be sure, I re-installed the MySQL module: make include_modules=mysql install > > > >Any ideas why my test users can still register without authentication? Why my users with valid accounts added via serctl seem to register rather than authenticate? > > > >Thanks, > > > >Chad > >_______________________________________________ >Serusers mailing list >serusers(a)lists.iptel.org >http://lists.iptel.org/mailman/listinfo/serusers -- Jiri Kuthan http://iptel.org/~jiri/

1 0

← Newer
1
2
3
4
5
6
7
...
15
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 August 2003