RE: [Linphone-developers] Linphone & registration

[Klaus Darilion]

Possible reasons: 
- ser in combination with linphone has some problems with loose routing
and a pre-route-set
- codec problems. in LAN set linphone network settings to Ethernet. MSN
and linphone have different low-bandwidth codecs.

regards
Klaus

> -----Original Message-----
> From: Ivica Babarovic [mailto:address@hidden 
> Sent: Tuesday, April 15, 2003 5:57 PM
> To: address@hidden
> Subject: [Linphone-developers] Linphone & registration
> 
> 
> Hello!
> 
> I'm using SER SIP server. I connect to it with a windows 
> Windows Messenger client and a Linux Linphone client. I 
> managed to somehow force Linphone to register to the server. 
> This was done by my friend by tweaking a code a bit. What I 
> would like, is to see my linphone client in the contacts 
> window of a messenger as active. If I connect to the SER 
> server with two Win. Messengers they can see each other. 
> Also, if I call directly from Linphone to Messenger I manage 
> to establish a VoIP link. But I would like this to work over 
> a SER server, so windows client can call Linphone and vice 
> versa. But in order to do that it needs to know that a 
> Linphone client is on. So I think (IMHO) that Linphone is not 
> registering itself correctly at the server side.
> 
> Here is a short description of my setup.
> Machines:
> Lilija = SIP server (Linux)
> Raindrop = windows client (messenger)
> Emsy-Lj = another windows client (messenger)
> Winphony = linux client (linphone)
> 
> 1.)When I register to the SIP server with
> Messenger I get two packets on the port 5060
> on the Linux server (Lilija):
> 
> address@hidden root]# ngrep  *@  port 5060
> interface: eth0 (10.41.0.0/255.255.0.0)
> filter: ip and ( port 5060 )
> match: *@
> #
> U 10.41.2.56:1809 -> 10.41.2.53:5060
>    REGISTER sip:lilija.hermes.si SIP/2.0..Via: SIP/2.0/UDP 
> 10.41.2.56:13774..From: <sip:rain
>    
> address@hidden>;tag=14d78d4b-09d0-4884-8ac5-dd38
> ae5beb31..To: <sip:raindrop
>    address@hidden>..Call-ID: 
> address@hidden
>    : 1 REGISTER..Contact: 
> <sip:10.41.2.56:13774>;methods="INVITE, MESSAGE, INFO, SUBSCRIBE,
>    OPTIONS, BYE, CANCEL, NOTIFY, ACK"..User-Agent: Windows 
> RTC/1.0..Expires: 1200..Event: re
>    gistration..Allow-Events: presence..Content-Length: 0....
> #
> U 10.41.2.53:5060 -> 10.41.2.56:13774
>    SIP/2.0 200 OK..Via: SIP/2.0/UDP 10.41.2.56:13774..From: 
> <sip:address@hidden
>    es.si>;tag=14d78d4b-09d0-4884-8ac5-dd38ae5beb31..To: 
> <sip:address@hidden
>    i>;tag=d907c037823644515dfe0ede38ca9976.fb16..Call-ID: 
> 52e01823-61e8-429c-bb2e-bad12cc65c
>    address@hidden: 1 REGISTER..Contact: 
> <sip:10.41.2.56:13774>;q=0.00;expires=1200..Ser
>    ver: Sip EXpress router (0.8.10 
> (i386/linux))..Content-Length: 0..Warning: 392 10.41.2.53
>    :5060 "Noisy feedback tells: pid=811 req_src_ip=10.41.2.56 
> in_uri=sip:lilija.hermes.si ou
>    t_uri=sip:lilija.hermes.si via_cnt==1"....
> 
> 
> Notice how SIP Methods are reported on registration (first 
> packet). (methods="INVITE, MESSAGE, ...)
> 
> 2.)If I register with Linphone I get the following two packets.:
> 
> address@hidden root]# ngrep  *@  port 5060
> interface: eth0 (10.41.0.0/255.255.0.0)
> filter: ip and ( port 5060 )
> match: *@
> #
> U 10.41.2.41:5060 -> 10.41.2.53:5060
>    REGISTER sip:address@hidden SIP/2.0..Via: SIP/2.0/UDP 
> 10.41.2.41:5060;branch=4023049451..
>    From: <sip:address@hidden>;tag=2b178..To: 
> <sip:address@hidden>..Call-ID: 1714
>    address@hidden: 1 REGISTER..Contact: 
> <sip:address@hidden>..expires: 900..user-ag
>    ent: oSIP/Linphone-0.8.0..Content-Length: 0....
> #
> U 10.41.2.53:5060 -> 10.41.2.41:5060
>    SIP/2.0 200 OK..Via: SIP/2.0/UDP 
> 10.41.2.41:5060;branch=4023049451..From: <sip:address@hidden
>    .hermes.si>;tag=2b178..To: 
> <sip:address@hidden>;tag=d907c037823644515dfe0ede38ca997
>    6.0190..Call-ID: address@hidden: 1 
> REGISTER..Contact: <sip:address@hidden>;q
>    =0.00;expires=900..Server: Sip EXpress router (0.8.10 
> (i386/linux))..Content-Length: 0..W
>    arning: 392 10.41.2.53:5060 "Noisy feedback tells: pid=811 
> req_src_ip=10.41.2.41 in_uri=s
>    ip:address@hidden out_uri=sip:address@hidden via_cnt==1"....
> 
> 
> Here you can see that SIP methods are not registered.
> I wonder if this functionality is included in Linphone.
> And of course if this is really the problem.
> I only asume that messenger is not seeing Linphone couse of 
> methods. I'm maybe wrong.
> 
> 
> So my questions are:
> What is the status with registration code in Linphone. Where 
> do I start? What should I do? Is Linphone totaly SIP 
> compliant (as far as methods are concerned)? And if not, what 
> method should I report with Linphone so Messenger can see it 
> and start a conversation and of course vice versa.
> 
> I hope I was clear enuogh on my problem.
> 
> I'm using libosip-0.8.8, linphone-0.9.0
> 
> My .linphonec file is:
> 
> address@hidden ivo]$ cat .linphonec
> 
> [Placement]
> Dock=Menubar\\0,0,0,0
> 
> [version]
> version_id=1024
> 
> [global]
> local_addr=10.41.2.41
> if_name=eth0
> con_type=4
> 
> [rtp]
> audio_rtp_port=7078
> jitt_comp=60
> 
> [audio]
> driver_mode=0
> rec_lev=83
> play_lev=95
> source=109
> autokill=-1 local_ring=/usr/local/share/sounds/linphone/ring.wav
> remote_ring=/usr/local/share/sounds/linphone/ringback.wav
> sound_source=/dev/dsp
> sound_sink=/dev/dsp
> 
> [sip]
> sip_port=5060
> use_registrar=0
> username=ivo
> hostname=lilija.hermes.si
> registrar=sip:address@hidden
> reg_passwd=
> reg_expires=900
> as_proxy=0
> as_redirect=0
> as_outbound=0
> addr_of_rec=
> 
> [codecs]
> audio_codecs=367 366 371 259 264 256
> 
> 
> --------------------------------------------------------------
> ---------
> 
> 
> TIA,
> ivo
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> Linphone-developers mailing list
> address@hidden 
> http://mail.nongnu.org/mailman/listinfo/linpho> ne-developers
> 
>