-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with sender id, using bot connector rest api v3 #1191
Comments
@puneetsngh the sender id format is specific per channel. the 29: format is specific to Skype. Which channel are you interacting with, and could you share code for the appropriate section of your code that's receiving the error? |
I am using Skype bot rest api latest v3 version and the documentation say that the sender id starts with |
My bot is in python `
` now here in place of sender in url the sender id in format but for the above issue the sender id is coming as |
@puneetsngh that looks like you are using skype directly (apis.skype.com) bypassing bot connector (skype.botframework.com). Thus we will need some addtional information: ContextId and Date header values of the request skype made to your bot service when you get |
I am sorry but I didn't have the context id for that msg...I wasn't logging that but I have the Json converted to dict. and the date of the msg. I hope that this will help, Secondly, as you are saying I am bypassing Service URL, but the documentation of SkypeBot listed that domain only. Is that mean that I can also use |
I have same dout how to get this "conversationId" for sending message |
@puneetsngh I tried to send messages use the following request I'm try to send use this request i got error |
@shijuamt I am sorry buddy but I don't know anything about node.js syntax. |
the host should be apis.skype.com |
@konstlut but what about my issue? 😅 |
Could you please add
For the replies you should use message's serviceUrl field, when you get a message (activity) from Skype. |
if I user the serviceUrl which is Everything is working fine as the documentation also mentioned that the id's will be in the form |
@konstlut ok I delved into the serviceUrl and now with response 202 they are too working, I just changed the type to |
Are you seeing it still? Anyway, to answer that we will need the mentioned header values, please. |
@konstlut I got this sender id 2 times and both times just before my bot got rejected, it seems like these ids are from bot review teams. I again sent my bot for review if the third time I get same kind of sender id then it will be for sure coming from bot review teams. As you mentioned you need header info for the troubleshooting. But the issue is I haven't logged contextID header yet. And from now on I will log that too. I was seeing the request headers and I didn't find the contextID mentioned in it. There were cookies, authentication token, user agent, content type but no contextid. Should I have to generate the contextId. If yes then can you guide me about it a little as I didn't found much information about context id in bot framework documentation. |
A side question @puneetsngh ; have you created or are using a python SDK for the Bot Framework, or are you coding to the REST API directly? |
@jameslew is there sdk available in Python for bot framework? because I am using rest api for skype bot |
@puneetsngh Is it possible to share that rest api request format please |
@shijuamt you can see my repository for Python Skype bot api wrapper |
@puneetsngh no, there is not at this time. I thought you might have been building one :). |
@jameslew I created a wrapper for Skype bot api...and wanted to support other channels too but the documentation is not very conducive for developers other than c# or node.js And for the issue I raised, I think the msg to my bot coming from emulator as I earlier was using |
Hi @puneetsngh, were you able to get this working? |
@dandriscoll i changed from I still not getting contextID in response header even after using serviceUrl |
ContextId will be available soon -- it will be included in our next deployment (likely this week). Looking through the thread, are you certain you aren't seeing the 'FOzadrPvGja' ID from another channel, like Web Chat, or the Bot Framework emulator? IDs in that format are not generated by Skype by they are generated by the Emulator and the ID. Accordingly, the ServiceUrl and ChannelId will reflect that channel. |
Also, another issue: this message is not a v3 Bot Framework message.
|
@dandriscoll I haven't enabled web chat for my bot, and the msg was not also from emulator, as I personally checked with emulator...there other issue encountered first then this. 1 thing which I feel is that the msg can be from review team as this kind of msges came twice to my bot that too just before my bot got rejected for no response.
|
This appears to be an internal data structure. Do you have an HTTP trace of the JSON messages being sent/received by your bot? I'm pretty certain the 'FOzadrPvGja' ID is from a different Bot Framework channel. |
@puneetsngh ? Have you resolved your issue? |
Hello All |
You are getting it all wrong, Skype id's are always like |
Closing due to age. If you still have the problem, please let us know and we will reopen. |
id 'FOzadrPvGja' looks like part from link to chat. Also, I have a question. I have link to that chat - like this https://join.skype.com/FOzadrPvGja |
As per the documentation the sender id should be format
29:1Gusfsfsf2323ds.....
something like this but today my bot gets a request from sender idFOzadrPvGja
and the bot didn't send any reply to the user. The response I receive is400
. Can you explain the issue here please, is it my fault or the user using some old device.Please also provide the documentation in this regard as I didn't find sender id like
FOzadrPvGja
in the rest api'sThe text was updated successfully, but these errors were encountered: