# Problem with xivo outgoing calls

**URL:** <https://wazo-platform.discourse.group/t/problem-with-xivo-outgoing-calls/29>\
**Category:** Installation/Configuration\
**Created:** [November 14, 2019, 2:09pm UTC](https://wazo-platform.discourse.group/t/problem-with-xivo-outgoing-calls/29 "2019-11-14T14:09:42Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![bwen](https://avatars.discourse-cdn.com/v4/letter/b/b487fb/32.png) [@bwen](https://wazo-platform.discourse.group/u/bwen)\
**Post date:** [November 14, 2019, 2:09pm UTC](https://wazo-platform.discourse.group/t/problem-with-xivo-outgoing-calls/29/1 "2019-11-14T14:09:42Z")

</div>

Hello,

I have a little trouble with Xivo, I have a line and when I try to dial a mobile number, it tells me that the extension is not found … this is normal since it uses the default context while 06XXXXXXXX is configured in the to-extern context. My question is therefore: why does it use the default context systematically and incidentally, how to solve this problem?

thanks in advance

---

<div class="post-metadata">

**Author:** ![pcm](https://avatars.discourse-cdn.com/v4/letter/p/b9bd4f/32.png) [@pcm](https://wazo-platform.discourse.group/u/pcm)\
**Post date:** [November 15, 2019, 9:20pm UTC](https://wazo-platform.discourse.group/t/problem-with-xivo-outgoing-calls/29/2 "2019-11-15T21:20:01Z")

</div>

Hi,

the outgoing call context is usually included in the internal context to allow users to call outside of the PBX.

In the context form you can check and make sure that your outgoing context is included in you internal context.

---

<div class="post-metadata">

**Author:** ![bwen](https://avatars.discourse-cdn.com/v4/letter/b/b487fb/32.png) [@bwen](https://wazo-platform.discourse.group/u/bwen)\
**Post date:** [November 17, 2019, 2:04pm UTC](https://wazo-platform.discourse.group/t/problem-with-xivo-outgoing-calls/29/3 "2019-11-17T14:04:19Z")

</div>

Hello,

Thank you for your answer, outgoing context was already included in default context but problem solved by adding default context on the trunk (outgoing context was the only one to be in)

regards
