alright, i opened all the ports on my router, to see what happens....i saw that my accoount with diamondcards registered, but my ekiga account did not...it gives registration failed, when i checked the logs it gives (606 not acceptable)
CSeq: 3 REGISTER Via: SIP/2.0/UDP 192.168.1.6:5063 ;branch=z9hG4bKdc63f840-520e-de11-85f8-0022159c30c4;rport User-Agent: Ekiga/2.0.12 From: <sip:[email protected] <sip%[email protected]> >;tag=6c5bf840-520e-de11-85f8-0022159c30c4 Call-ID: bad1f740-520e-de11-85f8-0022159c3...@khalfan-laptop To: <sip:[email protected] <sip%[email protected]>> Contact: <sip:[email protected]:5063;transport=udp> Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Expires: 3600 Content-Length: 0 Max-Forwards: 70 2009/03/13 18:35:30.831 0:04.894 GMAccounts...t:0a201470 PWLib File handle high water mark set: 57 PUDPSocket 2009/03/13 18:35:30.831 0:04.894 GMAccounts...t:0a201470 OpalUDP Binding to interface: 192.168.1.6:57641 2009/03/13 18:35:30.831 0:04.894 GMAccounts...t:0a201470 SIP Created transport udp$0.0.0.0<if=udp$192.168.1.6:57641> 2009/03/13 18:35:30.832 0:04.895 GMAccounts...t:0a201470 OpalUDP Started connect to 86.64.162.35:5060 2009/03/13 18:35:30.832 0:04.895 GMAccounts...t:0a201470 PWLib File handle high water mark set: 58 PUDPSocket 2009/03/13 18:35:30.832 0:04.896 GMAccounts...t:0a201470 OpalUDP Connect on pre-bound interface: 192.168.1.6 2009/03/13 18:35:30.833 0:04.896 GMAccounts...t:0a201470 PWLib File handle low water mark set: 57 PUDPSocket 2009/03/13 18:35:30.833 0:04.896 GMAccounts...t:0a201470 PWLib File handle high water mark set: 59 Thread unblock pipe 2009/03/13 18:35:30.833 0:04.896 GMAccounts...t:0a201470 PWLib Thread high water mark set: 10 2009/03/13 18:35:30.834 0:04.897 GMAccounts...t:0a201470 SIP Created Transport for Registrar udp$86.64.162.35:5060<if=udp$ 192.168.1.6:5064> 2009/03/13 18:35:30.836 0:04.899 SIP Transport:a2de820 SIP Read thread started. 2009/03/13 18:35:30.836 0:04.899 SIP Transport:a2de820 SIP Waiting for PDU on udp$86.64.162.35:5060<if=udp$192.168.1.6:5064> 2009/03/13 18:35:30.836 0:04.899 GMAccounts...t:0a201470 SIP Sending PDU on udp$86.64.162.35:5060<if=udp$192.168.1.6:5064> SUBSCRIBE sip:[email protected] <sip%[email protected]> SIP/2.0 CSeq: 4 SUBSCRIBE Via: SIP/2.0/UDP 192.168.1.6:5064 ;branch=z9hG4bK8e810041-520e-de11-85f8-0022159c30c4;rport User-Agent: Ekiga/2.0.12 From: <sip:[email protected] <sip%[email protected]> >;tag=10780041-520e-de11-85f8-0022159c30c4 Call-ID: 70e1ff40-520e-de11-85f8-0022159c3...@khalfan-laptop To: <sip:[email protected] <sip%[email protected]>> Contact: <sip:[email protected]:5064;transport=udp> Accept: application/simple-message-summary Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Expires: 3600 Event: message-summary Content-Length: 0 Max-Forwards: 70 2009/03/13 18:35:30.965 0:05.028 SIP Transport:a2b5d50 SIP PDU Received on udp$62.4.81.186:5060<if=udp$192.168.1.6:5061> SIP/2.0 100 Trying CSeq: 1 REGISTER Via: SIP/2.0/UDP 192.168.1.6:5061 ;branch=z9hG4bK2885e540-520e-de11-85f8-0022159c30c4;rport server: Generic SIP Proxy From: <sip:[email protected] <sip%[email protected]> >;tag=4c7ae540-520e-de11-85f8-0022159c30c4 Call-ID: 208be240-520e-de11-85f8-0022159c3...@khalfan-laptop To: <sip:[email protected] <sip%[email protected]>> Content-Length: 0 Record-Route: <sip:[email protected]:5060;lr> 2009/03/13 18:35:30.968 0:05.031 SIP Transport:a2b5d50 SIP Transaction 1 REGISTER proceeding. 2009/03/13 18:35:30.969 0:05.032 SIP Transport:a2b5d50 OpalUDP Ended connect, selecting 192.168.1.6:5061 2009/03/13 18:35:30.970 0:05.034 SIP Transport:a2b5d50 SIP Waiting for PDU on udp$62.4.81.186:5060<if=udp$192.168.1.6:5061> 2009/03/13 18:35:30.972 0:05.035 SIP Transport:a2b5d50 SIP PDU Received on udp$62.4.81.186:5060<if=udp$192.168.1.6:5061> SIP/2.0 401 Unauthorized CSeq: 1 REGISTER Via: SIP/2.0/UDP 192.168.1.6:5061 ;branch=z9hG4bK2885e540-520e-de11-85f8-0022159c30c4;rport server: Generic SIP Proxy From: <sip:[email protected] <sip%[email protected]> >;tag=4c7ae540-520e-de11-85f8-0022159c30c4 Call-ID: 208be240-520e-de11-85f8-0022159c3...@khalfan-laptop To: <sip:[email protected] <sip%[email protected]> >;tag=2ba7c5e834a5e32ce93c7ba7714e70b8.e90e Content-Length: 0 WWW-Authenticate: Digest realm="sip.diamondcard.us", nonce="49ba7e726ef215fa32009b697e1d7bd14ccfb367" Record-Route: <sip:[email protected]:5060;lr> 2009/03/13 18:35:30.978 0:05.041 SIP Transport:a2b5d50 SIP Transaction 1 REGISTER completed. 2009/03/13 18:35:30.978 0:05.041 SIP Transport:a2b5d50 SIP Received Authentication Required response 2009/03/13 18:35:30.979 0:05.042 SIP Transport:a2b5d50 SIP Updated realm to sip.diamondcard.us 2009/03/13 18:35:30.980 0:05.043 SIP Transport:a2b5d50 SIP Adding authentication information 2009/03/13 18:35:30.983 0:05.047 SIP Transport:a2b5d50 SIP Sending PDU on udp$62.4.81.186:5060<if=udp$192.168.1.6:5061> REGISTER sip:sip.diamondcard.us SIP/2.0 CSeq: 5 REGISTER Via: SIP/2.0/UDP 192.168.1.6:5061 ;branch=z9hG4bK48981641-520e-de11-85f8-0022159c30c4;rport User-Agent: Ekiga/2.0.12 Authorization: Digest username="324278", realm="sip.diamondcard.us", nonce="49ba7e726ef215fa32009b697e1d7bd14ccfb367", uri="sip: sip.diamondcard.us", algorithm=md5, response="ad56d2307cb11e2f0abae1d8ed9487ab" From: <sip:[email protected] <sip%[email protected]> >;tag=4c7ae540-520e-de11-85f8-0022159c30c4 Call-ID: 208be240-520e-de11-85f8-0022159c3...@khalfan-laptop To: <sip:[email protected] <sip%[email protected]>> Contact: <sip:[email protected]:5061;transport=udp> Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Expires: 3600 Content-Length: 0 Max-Forwards: 70 2009/03/13 18:35:30.985 0:05.048 SIP Transport:a2af908 SIP PDU Received on udp$86.64.162.35:5060<if=udp$192.168.1.6:5063> SIP/2.0 606 Not Acceptable CSeq: 3 REGISTER Via: SIP/2.0/UDP 192.168.1.6:5063 ;branch=z9hG4bKdc63f840-520e-de11-85f8-0022159c30c4;rport server: Kamailio (1.4.0-notls (i386/linux)) From: <sip:[email protected] <sip%[email protected]> >;tag=6c5bf840-520e-de11-85f8-0022159c30c4 Call-ID: bad1f740-520e-de11-85f8-0022159c3...@khalfan-laptop To: <sip:[email protected] <sip%[email protected]> >;tag=c64e1f832a41ec1c1f4e5673ac5b80f6.fc3f Content-Length: 0 Record-Route: <sip:[email protected]:5060;lr> On Mon, Mar 9, 2009 at 1:21 PM, Fedor vonBock <[email protected]> wrote: > well...at least i knew the router carries some of the blame...i hooked my > laptop straight to a dsl model and the registration succeeded..i'll see how > to resolve this issue > > > > > On Sun, Mar 8, 2009 at 9:25 PM, Fedor vonBock <[email protected]> wrote: > >> yeah...same thing....i'll just monitor the udp packets i >> guess.....appreciate your follow up, i'll keep you posted of any >> updates/questions >> >> >> On Sun, Mar 8, 2009 at 8:14 PM, Damien Sandras <[email protected]>wrote: >> >>> Le dimanche 08 mars 2009 à 20:01 +0300, Fedor vonBock a écrit : >>> > can you tell me how ekiga does the registration process....i'm going >>> > to to find a way to trace the process and see where the problem is >>> >>> It sends a REGISTER SIP Request to port 5060 of Ekiga.net, over UDP. >>> >>> Before doing so, it does a STUN detection to try determining what UDP >>> port will be open on your gateway for this request. >>> >>> Have you tried disabling STUN and see if it changes anything? >>> -- >>> _ Damien Sandras >>> (o- >>> //\ Ekiga Softphone : http://www.ekiga.org/ >>> v_/_ <http://www.ekiga.org/%0Av_/_> Be IP : >>> http://www.beip.be/ >>> FOSDEM : http://www.fosdem.org/ >>> SIP Phone : sip:[email protected]<sip%[email protected]> >>> >>> >>> _______________________________________________ >>> ekiga-list mailing list >>> [email protected] >>> http://mail.gnome.org/mailman/listinfo/ekiga-list >>> >> >> >
_______________________________________________ ekiga-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/ekiga-list
