sr-users August 2003

sr-users@lists.kamailio.org

67 participants
144 discussions

[Serusers] ERROR: bad config file - Additional Informaton
by Chad Brown 27 Aug '03

27 Aug '03

Additional log information that sync with previous logs sent: Aug 26 23:26:03 imsip01 ser: ERROR: cfg. parser: unexpected EOF: 2 comments open Aug 26 23:26:03 imsip01 ser: parse error (126,1-1): parse error Thanks, Chad

3 2

[Serusers] Re: Messenger 5.0 and SER issues
by Gavin Bensom 27 Aug '03

27 Aug '03

Hello, I'm running RH Linux 9.0. SER 0.8.11pre29 was installed via RPM. I running with mySQL enabled. I'm able to get users to login via Windows Messenger 5.0 and users can see presence of other users, but when users try to send an instant message to other online users, the response is "The following message could not be delivered to all recipients." When users try to have a voice conversation with other users Messenger reports that the called user has declined the invitation. in /var/log/messages I'm getting: WARNING: sip_msg_cloner: header body ignored: 8192 My ser.cfg file is the default config file with the following changes. 1. uncommented and commented lines to enable MySQL integration 2. added lookup("aliases"); #in the route {} section 3. added lookup("locations"); 4. added save("aliases"); 5. added alias="domain_alias"; 6. added some log(1,"log messages"); I've read as much documentation as I can find, including the current 0.8.11pre29 seruser.pdf from the ftp site and I'm not sure what to do next. Thanks for the help. G. --------------------------------- Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. --------------------------------- Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo.

2 3

[Serusers] ERROR: bad config file
by Chad Brown 27 Aug '03

27 Aug '03

When restarting SER after modifying the script to support mysql authentication I get the message... ERROR: bad config file (1 errors) I started with a fresh install of SER and MYSQL. Below is pertinent information: Name and version of your operating system: Redhat 9 SER distribution: tarball SER build: ser 0.8.11rc5 (i386/linux) I enabled advanced logging and here is the output around the reported error. Please let me know if more of the log would be helpful when diagnosing the problem. Also, if the ser.cfg script would be helpful please let me know. However, I did follow the Install instructions verbatim and restored the original to start over several times in case of a typo. 0(9840) qm_malloc(0x80b9f80, 15) called from cfg.lex: addstr(404) 0(9840) qm_malloc(0x80b9f80, 16) returns address 0x80c1eb8 frag. 0x80c1ea0 (siz e=16) on 1 -th hit 0(9840) find_export: found <sl_reply_error> in module sl_module [/usr/local/lib /ser/modules/sl.so] 0(9840) qm_malloc(0x80b9f80, 32) called from route_struct.c: mk_action(87) 0(9840) qm_malloc(0x80b9f80, 32) returns address 0x80c1ef8 frag. 0x80c1ee0 (siz e=32) on 1 -th hit 0(9840) qm_malloc(0x80b9f80, 32) called from route_struct.c: mk_action(87) 0(9840) qm_malloc(0x80b9f80, 32) returns address 0x80c1f48 frag. 0x80c1f30 (siz e=32) on 1 -th hit ERROR: bad config file (1 errors) 0(9840) qm_free(0x80b9f80, 0x80c0ad4), called from sr_module.c: destroy_modules (303) 0(9840) qm_free: freeing frag. 0x80c0abc alloc'ed from sr_module.c: register_mo dule(135) 0(9840) qm_free(0x80b9f80, 0x80c0a3c), called from sr_module.c: destroy_modules (303) 0(9840) qm_free: freeing frag. 0x80c0a24 alloc'ed from sr_module.c: register_mo dule(135) 0(9840) qm_free(0x80b9f80, 0x80c09a8), called from sr_module.c: destroy_modules (303) 0(9840) qm_free: freeing frag. 0x80c0990 alloc'ed from sr_module.c: register_mo dule(135) Thanks, Chad

1 0

Re: [Serusers] Can anyone point me to the SER config File
by Jiri Kuthan 26 Aug '03

26 Aug '03

etc/ser.cfg in source distribution. -jiri At 11:40 PM 8/26/2003, Jitender Arora wrote: >Hi , > > Can Any one point me to the Basic SER config File , which can be used to start working with SER .... > >Regards, >Jitender >_______________________________________________ >Serusers mailing list >serusers(a)lists.iptel.org >http://lists.iptel.org/mailman/listinfo/serusers -- Jiri Kuthan http://iptel.org/~jiri/

1 0

[Serusers] Can anyone point me to the SER config File
by Jitender Arora 26 Aug '03

26 Aug '03

Hi , Can Any one point me to the Basic SER config File , which can be used to start working with SER .... Regards, Jitender

1 0

[Serusers] serweb configuration on alternate port
by Samy Touati 26 Aug '03

26 Aug '03

Hi, I installed ser along with mysql and serweb. I'm able to login in admin mode using serweb. I tried to create new users using the subscribe button, the process goes smootly, and I do get an email asking me to confirm. When I do click on the onfirmation link, the browser tries to access the confirmation page, but I never see it, and I never see any error (page not found..) it just goes balnk forever. In fact I can never see any link generated by php and sent via email (password retrieval, account confirmation). I'm running http on port 5001, but I'm taking care of adding the port when accessing the pages, but to no effect. Is anyone using serweb, is there something I should pay attention to if changing the default port number of apache ? Thanks. Samy.

2 1

[Serusers] ATA help
by Nitin Shelar 26 Aug '03

26 Aug '03

Dear All, I am in desparate need of the following ATA image. ATA image 2.16 ata18x (Build 030509a) Any help will be highly appriciated. If anybody is having the CCO login please send the image to shelar_n(a)sterlite.com or nitinshelar(a)rediffmail.com. Thanks & Regards Nitin Shelar Associate Manager - IT Sterlite Optical Technologies Ltd. Phone:- 0091-240-2564597/99 FAX:- 0091-240-2564598. www.sterliteoptical.com

1 0

[Serusers] meet at RIPE
by Jiri Kuthan 26 Aug '03

26 Aug '03

Hello, I will be presenting a SIP tutorial at the upcoming RIPE meeting in Amsterdam on September the 1st. If there is anybody on the list, who would like to meet, talk in person about SIP/SER or just say hello, let me know. Thanks -jiri http://www.ripe.net/ripe/meetings/ripe-46/index.html -- Jiri Kuthan http://iptel.org/~jiri/

1 0

[Serusers] SER version question
by Nell Bolen 25 Aug '03

25 Aug '03

Hello Serusers, A few days ago, installed SER and some addons on a linux 686 using rpms for 386. Seems to work okay. Also serweb pages seem to be working. However, today, in someone's list post, there was a link to a "tarball" directory. After looking through there, I see that the ser rpm brings fewer modules along, and of course also, is not as up to date as the tarball tar.gz-. Question 1: If I want to install the tar.gz, do I delete the current rpm version first or just write over? If delete first, clues for a method to do that would be appreciated. Know where most of the rpm ser files are, but not for sure. Just stop the current ser and then delete its files and other references to it elsewhere? Question 2: While looking over tarball files, I saw more than once references to a second auth module that I cannot find anywhere in tarball -- has to do with databasing, something like auth_db.so or something like that. Is that module no longer needed, and if it is needed, what does it support/enable and where to find it? Thank you once more for your help -- Nell Bolen ________________________________________ Web Classic Design Webhosting, Design, Programming, Maintenance Contact WCD: Phone: 1-866-800-5117 (Toll Free) Email: info(a)webclassicdesign.net On the World Wide Web

3 2

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

25 Aug '03

It seems Microsoft Messenger uses a proprietary model for session opening. 4.7 sends a primer MESSAGE, 5.0 sends an INVITE which 4.7 does not understand. -jiri At 04:10 PM 8/25/2003, Timo Santi wrote: >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/ -- Jiri Kuthan http://iptel.org/~jiri/

1 0

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