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:[email protected]>;tag=5a4b8eb7-dfff-1810-8a19-0013ce9f9d7e. > i: 5a4b8eb7-dfff-1810-8a1a-0013ce9f9...@vaio. > t: <sip:[email protected]>. > m: <sip:[email protected]: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:[email protected]
_______________________________________________ ekiga-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/ekiga-list
