We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
in the voip example in v2.4 release. https://github.com/espressif/esp-adf/tree/release/v2.4/examples/advanced_examples/voip in the sip event handler, there is event->type and event->data which contain type of event and the data. for example, when there is a SIP_EVENT_RINGING the event->data will contain the caller id.
event->type
event->data
SIP_EVENT_RINGING
in the current voip master branch. https://github.com/espressif/esp-adf/tree/master/examples/protocols/voip the sip event handler only contain the event type without the data. is there any way to get the caller id when there is ESP_RTC_EVENT_INCOMING event like the version 2.4 release?
ESP_RTC_EVENT_INCOMING
The text was updated successfully, but these errors were encountered:
Hi @Latifly ,
You can get caller id though esp_rtc_get_peer API.
br.
Sorry, something went wrong.
This topic has become inactive so I'm going to close the issue. Please reopen this if you have any questions or need any further assistance.
No branches or pull requests
in the voip example in v2.4 release.
https://github.com/espressif/esp-adf/tree/release/v2.4/examples/advanced_examples/voip
in the sip event handler, there is
event->type
andevent->data
which contain type of event and the data. for example, when there is aSIP_EVENT_RINGING
theevent->data
will contain the caller id.in the current voip master branch.
https://github.com/espressif/esp-adf/tree/master/examples/protocols/voip
the sip event handler only contain the event type without the data. is there any way to get the caller id when there is
ESP_RTC_EVENT_INCOMING
event like the version 2.4 release?The text was updated successfully, but these errors were encountered: