On Tue, February 14, 2006 12:59, Alex Fritze said: > Hi, > > I'm trying to get Wengo (the service) working with zap (the other > Mozilla-based SIP client [1]), and I'm having a bit of trouble with > Wengo's registration behaviour: > > Wengo persistently changes the host part of the contact I'm registering > to "192.168.70.52:5060". > > So if I'm registering with a Contact header > > Contact: > <sip:[EMAIL PROTECTED]:5076;grid=8153284ae949e21af165927794204ac2>, > > the registration will succeed (from Wengo's point of view), but the > returned 200 response contains a Contact header > > Contact: > <sip:[EMAIL PROTECTED]:5060;grid=8153284ae949e21af165927794204ac2>. > > Since this is a different address, zap will think that it is a binding > from some other registered endpoint. > > Can someone enlighten me about this behaviour? Is it intended or is it a > bug?
The wengo behaviour is not standard conform. Maybe this is caused by a buggy NAT traversal technology used at wengo. regards klaus _______________________________________________ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
