[sadysta]

Hi,

I've created an RFCOMM-based service but I can't make it visible via SDP. I use the code from S60 Chat example. Unfortunately even the original Chat application is not visible via SDP. I'm enumerating services from PC using Windows Sockets API (WSALookupServiceBegin/WSALookupServiceNext,etc.). There's plenty of other services visible:

Service: SDP Server, Port: -1
Service: Dial-Up Networking, Port: 1
Service: OBEX Object Push, Port: 2
Service: Imaging, Port: 3
Service: Phonebook access PSESymbian Software Ltd, Port: 4
Service: Hands-Free Audio Gateway, Port: 5
Service: Headset Audio Gateway, Port: 6
Service: SyncMLClient, Port: 7
Service: Audio Source, Port: 25
Service: AVRCP ControllerAudio Video Remote Control, Port: 23
Service: OBEX File Transfer, Port: 8
Service: Nokia OBEX PC Suite Services, Port: 9

unfortunately mine is not. I know it should be visible as listening on port 11 (that's the port I get using KRFCOMMGetAvailableServerChannel request and set in TBTSockAddr). Furthermore I can use the port to successfully talk to the service. Interesting isn't it? Any ideas???

[bdonegan]

Okay, first question is: can you discover the device itself?

Also, could you share the code you're using to register the service?

[sadysta]

Yes, of course. The list of services up there is from the detected device.

I can't really post code used for detection but I can say that it's standard code as suggested by MSDN.