Forum Discussion
Graph API: create a PSTN call and invite a PSTN participant
Thank you.
yisroelperton
This is my code for the MakeCall:
var call = new Call
{
CallbackUri = Config.CurrentValue.CallBackUrl + ConfigurationConstants.CallbackSuffixCallEvents,
TenantId = Config.CurrentValue.ApplicationClient.TenantId,
Source = new ParticipantInfo
{
Identity = new IdentitySet
{
// 05.11.2021 GW Handle PSTN calls
AdditionalData = new Dictionary<string, object>()
{
{"applicationInstance", new Identity()
{
DisplayName = Config.CurrentValue.ApplicationClient.DisplayName,
Id = Config.CurrentValue.ApplicationClient.BotUserObjectId
}
}
}
},
Region = null,
LanguageId = null
},
Targets = new List<InvitationParticipantInfo>() { device },
RequestedModalities = new List<Modality> { Modality.Audio },
MediaConfig = new ServiceHostedMediaConfig { },
Direction = CallDirection.Outgoing,
};
var result = await graphAppClient.Communications.Calls
.Request(RequestHeader)
.AddResponseAsync(call);
Sayali-MSFTMicrosoft
bsingh1700 - Sure.Sayali-MSFT Any update on the issue if its being fixed now. Also created service request and support ticket for MS. Please let me know for any update
Frank_Roger365 I also do not see any tickets in my admin center. Did they asked for tenant id from you or it was resolved automatically
- For us still not a single outbound call is working. Hope they will apply the fix for all tenants ASAP.
- Its visible in your admin center (for us at least) since the links point to your own tenant. However, we think the fix is already deployed here and there, as we notice some of the calls succeeding again.
- Can u please give us the link where there are updates regarding the fix..like u mention TM521711
- FYI, this will (is being) fixed. TM521711
- Sayali-MSFTbsingh1700 - If you have any business-critical issue which need immediate attention, please raise a support request here:
https://docs.microsoft.com/en-us/microsoft-365/admin/get-help-support?view=o365-worldwide&tabs=online Sayali-MSFT Thanks. Please raise the priority as business is impacting directly due to this sudden issue.
- Sayali-MSFTbsingh1700 , dhaerle-mirage - We are informing the engineering team, we will let you know the once we get any update.
- We do have the exact same issue - no outbound calls possible via BOT and Inviteparticipant. It started last week with some calls and since yesterday every call is not working.
Sayali-MSFT our call center solution is also impacted by this, please provide a fix as soon as possible. Thanks!
Sayali-MSFT We are also facing same exact issue. It was working fine until last week. Suddenly it stopped working for few users and now for everyone. Can u please check and revert as its top priority for us. Our whole production system is affected by the same.
We are also having same error in invite participant -
"resultInfo": {
"@odata.type": "#microsoft.graph.resultInfo",
"code": 500,
"subcode": 10339,
"message": "addParticipants failed for participant 4:+491234568889. Underlying reason: Server Internal Error. DiagCode: 500#10339.@"
},
"id": "c1fd6eab-5b09-4a9c-ba8d-b718c044526d"
}
}
]}- Sayali-MSFTFrank_Roger365 - We are checking it internally and let you know once we get any updates.
Previously, we were able to invite a PSTN number into the conversation if it was the first escalation. Meaning:
1. Bot called teams user
2. Teams user accepted (p-p call)
3. Inviteparticipant to PSTN.
4. Now a groupcall with bot, teamsuser and PSTN user.
As of last week this started to fail randomly (for some users) and now it just is not working anymore at all. The invite is accepted, but it fails, returning 'addParticipants failed for participant 4:...' with 'DiagCode: 500#10339.@'.
Does anyone know why this changed / what the errorcode means (the 10339 part)?- Ok, thank you. Hopefully this helps. Thanks for your time.
