Damien Sandras wrote: ............ >> Here's what ekiga.net says it received: >> <--- SIP read from UDP://86.64.162.35:5060 ---> >> SIP/2.0 406 Not Acceptable >> Via: SIP/2.0/UDP >> 10.10.11.180:5060;branch=z9hG4bK17818198;rport=5060;received=96.xxx.253.yy >> ............. >> >> so it knows both the public and the private. Does ekiga require both >> addresses to be public? If so, anybody know how to force asterisk to do >> this? > > No, you misunderstood. > Ekiga sees it receives a packet from Ekiga.net (86.64.162.35). > That packet is the answer from ekiga.net, which contains portions of the > original request, which in turn contains only private IP addresses, > which is wrong.
I must be slow here, but if I turn on sip debug in asterisk it shows: REGISTER 12 headers, 0 lines Reliably Transmitting (NAT) to 86.64.162.35:5060: REGISTER sip:ekiga.net SIP/2.0 Via: SIP/2.0/UDP 10.10.11.180:5060;branch=z9hG4bK0d4fbf8a;rport Max-Forwards: 70 From: <sip:[EMAIL PROTECTED]>;tag=as258f78ca To: <sip:[EMAIL PROTECTED]> Call-ID: [EMAIL PROTECTED] CSeq: 103 REGISTER User-Agent: Asterisk PBX 1.6.0-beta4 Expires: 120 Contact: <sip:[EMAIL PROTECTED]> Event: registration Content-Length: 0 --- <--- SIP read from UDP://86.64.162.35:5060 ---> SIP/2.0 406 Not Acceptable Via: SIP/2.0/UDP 10.10.11.180:5060;branch=z9hG4bK0d4fbf8a;rport=5060;received=99.xxx.253.yy From: <sip:[EMAIL PROTECTED]>;tag=as258f78ca To: <sip:[EMAIL PROTECTED]>;tag=12d18c5009a2de32fca8ae9d70ad0321.86aa Call-ID: [EMAIL PROTECTED] CSeq: 103 REGISTER Server: Sip EXpress router (0.9.6 (i386/linux)) Content-Length: 0 Warning: 392 86.64.162.35:5060 "Noisy feedback tells: pid=24584 req_src_ip=99.xxx.253.yy req_src_port=5060 in_uri=sip:ekiga.net out_uri=sip:ekiga.net via_cnt==1" I assume the first stanza is the registration packet sent by asterisk to ekiga, and the bottom stanza is the ekiga.net response. From the bottom stanza, it seems ekiga.net "knows" the public ip address - 99.xxx.253.yy ( see the 4th line of the stanza and the last line), as well as the private address. But this is not enough? How should the registration packet be changed? According to the asterisk docs, it should meet RFC3581 (;rport). Does it? If not, then it's a bug in asterisk. Or is RFC3581 not enough for ekiga.net? In which case, asterisk needs an additional way of sending sip registration requests to meet ekiga's requirements. I'd really like to use ekiga over asterisk. So if you can let me know how the sip registration packet should be changed, I'm happy to lobby for it on the asterisk lists. sean _______________________________________________ ekiga-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/ekiga-list
