Issue in Transfering a ongoing call to a new Number
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
Research direction
Start by reproducing the ongoing-call transfer using the transfer function and the configured aleg_url, then trace whether the request reaches that URL. Review the Plivo API documentation and the library's transfer entry point; done means identifying why the callback is not hit and documenting or fixing a reproducible cause.
Written by the indexing model from the issue text.
Description
I am stuck in transfering a ongoing call to a new number. I read all api docs and implimented then but its not working. I tried the transfer function but the aleg_url is never being hit .
- Dominant language
- Python
- Stars
- 69
- Forks
- 68
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from plivo/plivo-python
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
plivo/plivo-python#298 · 1 comment · 2 reactions ·
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
plivo/plivo-python#295 · 3 comments · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
plivo/plivo-python#290 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
plivo/plivo-python#289 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 55/100
plivo/plivo-python#283 ·
All issues in plivo/plivo-python
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100