|
View:
New views
4 Messages
—
Rating Filter:
Alert me
|
|
|
Ekiga/windows UAC BUG: Incorrect headers then calling to external domainHi,
Was trying to call from ekiga client for windows to my own domain. Ekiga client configure with ekiga account, i am calling to my domain riki.ru to user andres.moya@.... My SIP proxy receive such INVITE from IP of ekiga UAC: U 78.146.165.51:10574 -> 195.167.152.55:5060 INVITE sip:andres.moya@... SIP/2.0. Date: Sun, 15 Nov 2009 00:13:54 GMT. CSeq: 1 INVITE. v: SIP/2.0/UDP 78.146.165.51:10574;branch=z9hG4bK63888eb7-dfff-1810-8a1b-0013ce9f9d7e;rport. User-Agent: Ekiga/3.2.6. f: "Mangust" <sip:Mangust@...>;tag=5a4b8eb7-dfff-1810-8a19-0013ce9f9d7e. i: 5a4b8eb7-dfff-1810-8a1a-0013ce9f9d7e@VAIO. t: <sip:andres.moya@...>. m: <sip:Mangust@...:10574>. Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING. c: application/sdp. l: 1016. Max-Forwards: 70. . v=0. o=- 1258244034 1 IN IP4 78.146.165.51. s=Opal SIP Session. c=IN IP4 78.146.165.51. t=0 0. m=audio 5062 RTP/AVP 123 122 3 108 0 8 9 101 126. a=sendrecv. a=rtpmap:123 Speex/16000/1. a=fmtp:123 sr=16000,mode=any. a=rtpmap:122 Speex/8000/1. a=fmtp:122 sr=8000,mode=any. a=rtpmap:3 gsm/8000/1. a=rtpmap:108 iLBC/8000/1. a=fmtp:108 mode=20. a=rtpmap:0 PCMU/8000/1. a=rtpmap:8 PCMA/8000/1. a=rtpmap:9 G722/8000/1. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-16,32,36. a=rtpmap:126 NSE/8000. a=fmtp:126 192-193. m=video 5064 RTP/AVP 107 125 31 34 106 112. b=AS:4096. b=TIAS:4096000. a=sendrecv. a=rtpmap:107 h264/90000. a=fmtp:107 packetization-mode=1;profile-level-id=42C01E. a=rtpmap:125 theora/90000. a=fmtp:125 height=576;width=704. a=rtpmap:31 h261/90000. a=fmtp:31 CIF=1;QCIF=1. a=rtpmap:34 h263/90000. a=fmtp:34 F=1;CIF=1;CIF4=1;QCIF=1. a=rtpmap:106 h263-1998/90000. a=fmtp:106 D=1;F=1;I=1;J=1;CIF=1;CIF4=1;QCIF=1;CUSTOM=320,240 # OK, ekiga UAC is clever to check riki.ru in DNS and connect directly to my proxy. But it use some simplified names for fields of a header: *************************** v: SIP/2.0/UDP 78.146.165.51:10574;branch=z9hG4bK63888eb7-dfff-1810-8a1b-0013ce9f9d7e;rport. User-Agent: Ekiga/3.2.6. f: "Mangust" <sip:Mangust@...>;tag=5a4b8eb7-dfff-1810-8a19-0013ce9f9d7e. i: 5a4b8eb7-dfff-1810-8a1a-0013ce9f9d7e@VAIO. t: <sip:andres.moya@...>. m: <sip:Mangust@...:10574>. Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING. c: application/sdp. l: 1016. *************************** Can it be fixed some how? _______________________________________________ ekiga-list mailing list ekiga-list@... http://mail.gnome.org/mailman/listinfo/ekiga-list |
|
|
|
Re: Ekiga/windows UAC BUG: Incorrect headers then calling to external domain
Le dimanche 15 novembre 2009 à 00:31 +0000, Andres Moya a écrit :
But it use some simplified names for fields of a header: *************************** v: SIP/2.0/UDP 78.146.165.51:10574;branch=z9hG4bK63888eb7-dfff-1810-8a1b-0013ce9f9d7e;rport. User-Agent: Ekiga/3.2.6. f: "Mangust" <sip:Mangust@...>;tag=5a4b8eb7-dfff-1810-8a19-0013ce9f9d7e. i: 5a4b8eb7-dfff-1810-8a1a-0013ce9f9d7e@VAIO. t: <sip:andres.moya@...>. m: <sip:Mangust@...:10574>. Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING. c: application/sdp. l: 1016. *************************** Can it be fixed some how? The "short" version of SIP headers perfectly legal and documented in the RFC. The reason why it uses short headers is related to the fact that you enabled too many codecs. It leads to a long SIP message that can't be transmitted reliably over UDP, so Ekiga uses the compact form for the headers to circumvent that.
_______________________________________________ ekiga-list mailing list ekiga-list@... http://mail.gnome.org/mailman/listinfo/ekiga-list |
|
|
|
Re: Ekiga/windows UAC BUG: Incorrect headers then calling to external domainCool, will try again, but looks like my nokia phone was confused about
this headers. Now i am testing OpenSER installation, so anyone welcome to test call me on sip:andres.moya@... Damien Sandras wrote: > Le dimanche 15 novembre 2009 à 00:31 +0000, Andres Moya a écrit : >> But it use some simplified names for fields of a header: >> *************************** >> v: SIP/2.0/UDP >> 78.146.165.51:10574;branch=z9hG4bK63888eb7-dfff-1810-8a1b-0013ce9f9d7e;rport. >> User-Agent: Ekiga/3.2.6. >> f: "Mangust" >> <sip:Mangust@...>;tag=5a4b8eb7-dfff-1810-8a19-0013ce9f9d7e. >> i: 5a4b8eb7-dfff-1810-8a1a-0013ce9f9d7e@VAIO. >> t: <sip:andres.moya@...>. >> m: <sip:Mangust@...:10574>. >> Allow: >> INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING. >> c: application/sdp. >> l: 1016. >> *************************** >> Can it be fixed some how? >> > > The "short" version of SIP headers perfectly legal and documented in > the RFC. > The reason why it uses short headers is related to the fact that you > enabled too many codecs. It leads to a long SIP message that > can't be transmitted reliably over UDP, so Ekiga uses the compact form > for the headers to circumvent that. > > > -- > _ Damien Sandras > (o- > //\ Ekiga Softphone : http://www.ekiga.org/ > v_/_ Be IP : http://www.beip.be/ > FOSDEM : http://www.fosdem.org/ > SIP Phone : sip:dsandras@... > > > > ------------------------------------------------------------------------ > > _______________________________________________ > ekiga-list mailing list > ekiga-list@... > http://mail.gnome.org/mailman/listinfo/ekiga-list ekiga-list mailing list ekiga-list@... http://mail.gnome.org/mailman/listinfo/ekiga-list |
|
|
|
Re: Ekiga/windows UAC BUG: Incorrect headers then calling to external domainOh! i have same problem. How can i reduce my own packets same way in
OpenSER for example? ;) I m not fitting in MTU with my nokia :( how this is oficially called? Damien Sandras wrote: > Le dimanche 15 novembre 2009 à 00:31 +0000, Andres Moya a écrit : >> But it use some simplified names for fields of a header: >> *************************** >> v: SIP/2.0/UDP >> 78.146.165.51:10574;branch=z9hG4bK63888eb7-dfff-1810-8a1b-0013ce9f9d7e;rport. >> User-Agent: Ekiga/3.2.6. >> f: "Mangust" >> <sip:Mangust@...>;tag=5a4b8eb7-dfff-1810-8a19-0013ce9f9d7e. >> i: 5a4b8eb7-dfff-1810-8a1a-0013ce9f9d7e@VAIO. >> t: <sip:andres.moya@...>. >> m: <sip:Mangust@...:10574>. >> Allow: >> INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING. >> c: application/sdp. >> l: 1016. >> *************************** >> Can it be fixed some how? >> > > The "short" version of SIP headers perfectly legal and documented in > the RFC. > The reason why it uses short headers is related to the fact that you > enabled too many codecs. It leads to a long SIP message that > can't be transmitted reliably over UDP, so Ekiga uses the compact form > for the headers to circumvent that. > > > -- > _ Damien Sandras > (o- > //\ Ekiga Softphone : http://www.ekiga.org/ > v_/_ Be IP : http://www.beip.be/ > FOSDEM : http://www.fosdem.org/ > SIP Phone : sip:dsandras@... > > > > ------------------------------------------------------------------------ > > _______________________________________________ > ekiga-list mailing list > ekiga-list@... > http://mail.gnome.org/mailman/listinfo/ekiga-list ekiga-list mailing list ekiga-list@... http://mail.gnome.org/mailman/listinfo/ekiga-list |
| Free embeddable forum powered by Nabble | Forum Help |