Registration failed: Error 606

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Create SIP Ekiga Account
2. Provision stack with the information
3. Try to register.

Registration fails:
INFO/[RCS][RegistrationManager](1640): Registration has failed: 2, reason=606 
Not Acceptable

My colleague in US is getting this error. But I am in India and I am able to 
register using same credentials. My colleague has tried both 3G and wifi but 
getting same issue.

Imp logs are:
---------------
12-21 09:51:02.770: INFO/[RCS][ImsConnectionManager](1640): IMS user profile: 
IMS username=14087726355, IMS private ID=1408772xxxx@ekiga.net, IMS 
password=xxxx, IMS home domain=ekiga.net, XDM 
server=10.194.117.34:8080/services, XDM login=, XDM password=password, IM 
Conference URI=sip:Conference-Factory@ekiga.net

12-21 09:51:02.848: VERBOSE/[RCS][PublishManager](1640): New entity tag: null, 
expire at=-1

12-21 09:51:02.856: INFO/[RCS][ImsModule](1640): IMS module has been created

12-21 09:51:02.856: INFO/[RCS][Core](1640): Terminal core is created with 
success

12-21 09:51:02.856: INFO/[RCS][ImsModule](1640): Start the IMS module

12-21 09:51:02.856: INFO/[RCS][CallManager](1640): Start call monitoring

12-21 09:51:02.864: INFO/[RCS][ImsModule](1640): IMS module is started

12-21 09:51:02.864: INFO/[RCS][AddressBookManager](1640): Start address book 
monitoring

12-21 09:51:02.879: INFO/[RCS][ImsServiceDispatcher](1640): Start background 
processing

12-21 09:51:02.887: VERBOSE/[RCS][RcsCoreService](1640): Handle event core 
started

12-21 09:51:02.903: INFO/[RCS][Core](1640): RCS core service has been started 
with success

12-21 09:51:02.911: INFO/[RCS][RcsCoreService](1640): RCS core service started 
with success

12-21 09:51:02.919: VERBOSE/[RCS][RcsWidgetProvider](1640): Widget mode set to 
ON but not registered

12-21 09:51:02.934: VERBOSE/[RCS][CallManager](1640): Call is IDLE: last 
number=null

12-21 09:51:02.934: VERBOSE/[RCS][RichcallService](1640): Abort all pending 
sessions

12-21 09:51:02.934: VERBOSE/[RCS][RcsWidgetProvider](1640): Widget mode set to 
ON but not registered

12-21 09:51:02.942: VERBOSE/[RCS][ImsConnectionManager](1640): Connection event 
android.net.conn.CONNECTIVITY_CHANGE

12-21 09:51:02.942: VERBOSE/[RCS][ImsConnectionManager](1640): Local IP address 
is 10.107.120.125

12-21 09:51:02.950: VERBOSE/[RCS][ImsConnectionManager](1640): Disconnect from 
IMS: IP address has changed

12-21 09:51:02.950: VERBOSE/[RCS][MobileNetworkInterface](1640): Registration 
has been terminated

12-21 09:51:02.950: INFO/[RCS][MobileNetworkAccess](1640): Disconnecting from 
null

12-21 09:51:02.950: INFO/[RCS][ImsConnectionManager](1640): Data connection 
state: CONNECTED to mobile

12-21 09:51:02.973: VERBOSE/[RCS][ImsConnectionManager](1640): Connect to IMS

12-21 09:51:02.973: INFO/[RCS][MobileNetworkAccess](1640): Connecting to 
10.107.120.125

12-21 09:51:02.973: INFO/[RCS][ImsConnectionManager](1640): Start the IMS 
connection manager

12-21 09:51:02.981: VERBOSE/[RCS][ImsConnectionManager](1640): Start polling of 
the IMS connection

12-21 09:51:03.012: VERBOSE/[RCS][ImsConnectionManager](1640): Polling: check 
IMS connection

12-21 09:51:03.020: VERBOSE/[RCS][ImsConnectionManager](1640): Not yet 
registered to IMS: try registration

12-21 09:51:03.020: VERBOSE/[RCS][MobileNetworkInterface](1640): Register to IMS

12-21 09:51:03.044: VERBOSE/[RCS][SipInterface](1640): SIP outbound proxy set 
to 86.64.162.35:5060

12-21 09:51:03.208: VERBOSE/[RCS][SipInterface](1640): Default SIP provider is 
UDP

12-21 09:51:03.208: VERBOSE/[RCS][SipInterface](1640): SIP stack started at 
10.107.120.125:5062

12-21 09:51:03.208: VERBOSE/[RCS][SipInterface](1640): Add a SIP listener

12-21 09:51:03.223: INFO/[RCS][RegistrationManager](1640): Send REGISTER, 
expire=3600

12-21 09:51:03.231: VERBOSE/[RCS][SipInterface](1640): Create a transaction 
context vA3vhRT5AA@10.107.120.125

12-21 09:51:03.231: VERBOSE/[RCS][SipInterface](1640): >>> Send SIP REGISTER

12-21 09:51:03.270: INFO/[RCS][RegistrationManager](1640): Wait response

12-21 09:51:03.301: DEBUG/dalvikvm(1640): GC_CONCURRENT freed 371K, 46% free 
3413K/6279K, external 716K/1038K, paused 4ms+5ms

12-21 09:51:03.309: INFO/dalvikvm(1640): Jit: resizing JitTable from 512 to 1024

12-21 09:51:04.747: INFO/urilc(2742): [ATURilListenerLoop]:  rxd 32 size packet

12-21 09:51:04.747: INFO/urilc(2742): [HandleNotificationPacket] 1009

12-21 09:51:04.747: INFO/urilc(2742): [DispatchNotifCallback] enter 0x0

12-21 09:51:04.747: INFO/urilc(2742): [DispatchNotifCallback] exit

12-21 09:51:04.762: DEBUG/SurfaceFlinger(1374): Layer[2b6680] [2] non-RGB565 
reloads

12-21 09:51:07.458: VERBOSE/[RCS][SipInterface](1640): <<< Receive SIP 606 
response

Original issue reported on code.google.com by moondra....@gmail.com on 22 Dec 2011 at 9:02

[GoogleCodeExporter]

It seems EKIGA does not support clients behind NAT. Does RCS stack have any NAT 
traversal technology ?? 

Original comment by moondra....@gmail.com on 23 Dec 2011 at 8:36

[GoogleCodeExporter]

We use symetric SIP port and keep alive mechanism when a NAT is detected.
We don t support STUN.

Original comment by jmauffret@gmail.com on 23 Dec 2011 at 10:27

• Changed state: Done