Topic: Unable to create channel of type 'SIP' (cause 3...)

[soprom]

I get lots of these in the log and I'm loosing calls.
I need help to understand what it means..

Code: [Select]

[Apr 10 15:14:36] WARNING[5653] app_dial.c: Unable to create channel of type 'IAX2' (cause 3 - No route to destination)
[Apr 10 15:14:36] WARNING[5653] app_dial.c: Unable to create channel of type 'SIP' (cause 3 - No route to destination)
[Apr 10 15:36:54] WARNING[5834] app_dial.c: Unable to create channel of type 'IAX2' (cause 3 - No route to destination)
[Apr 10 15:36:54] WARNING[5834] app_dial.c: Unable to create channel of type 'SIP' (cause 3 - No route to destination)
No route to host would mean a connectivity or network interface problem?

I also have this:
app_dial.c:1196 dial_exec_full:

[gippsweb]

I only ever see that on our remote extensions when I try to call one from here and the modem at the other end has locked up.
Fortunately it doesn't happen very often though...

[soprom]

Thanks for the hint!
I switched off the auto-anwser on the fax.
I'll see if it does it.
Thanks again!

[soprom]

The warnings concerned unregistered softphones.
But I keep loosing calls.
The calls are answered with a brief "hish" sound, and then it hangs up.

[SARK devs]

loosing calls to the softphone or loosing inbound calls?  What are the endpoints and where are they?

Best

S

[soprom]

I'm loosing inbound calls (sip provider) to sip hardphones on the LAN.
Allthough the status on the trunks is Ok, asterisk says :

Code: [Select]

[Apr 11 09:16:13] NOTICE[10918] chan_sip.c:    -- Registration for '5145551111@sip02.unlimitel.ca' timed out, trying again (Attempt #14)
[Apr 11 09:16:33] NOTICE[10918] chan_sip.c:    -- Registration for '5145551111@sip02.unlimitel.ca' timed out, trying again (Attempt #15)
[Apr 11 09:16:53] NOTICE[10918] chan_sip.c:    -- Registration for '5145551111@sip02.unlimitel.ca' timed out, trying again (Attempt #16)
[Apr 11 09:17:13] NOTICE[10918] chan_sip.c:    -- Registration for '5145551111@sip02.unlimitel.ca' timed out, trying again (Attempt #17)
I also loose calls inbound from iax2 provider to the same local sip hardphones. This problem is solved with a server reboot and appears after a couple of hours. It's not clear yet. Now it's been stable for half a day...

[SARK devs]

Are you running server-gateway or server-only (i.e. behind a firewall)?

I have seen this occasionally with one supplier/carrier in the UK.  Usually an asterisk restart cures it (rather than a reboot),  but I've never really figured out how/why it happens.  If you watch the TCP packets (with wireshark) you will see the sip register being sent out from asterisk and then nothing coming back.  If you ask the carrier to trace they will probably tell you that they have received the register and sent a 200 OK.  Unfortunately the 200 OK never arrives back at asterisk.  You might want to check this on your server.  Are you familiar with wireshark?

Install with

yum install wireshark


run your trace with

tethereal -R sip -i eth1 -f "host {your carrier uri or ip address}"

or you can run

tethereal -R iax2 -i eth1 -f "host {your carrier uri or ip address}"

Stop the trace with Ctrl+C

Use eth0 if you are running server-only

C'est tout



S

 
       

[soprom]

I installed wireshark (with lots of "g: user mockbuild does not exist - using root")
and I will look into it.

I read here and elsewhere that it had to do with Zap when a fax/modem hangs because of an interrupted call.

So after disabling autoanswer on the fax, seting the server-only mode, uninstalling OCS-Inventory (you can see here of mouvement of panic!!), the PBX was working correctly.

When I will reactivate the fax, i'll work with wireshark.

Thanks

Part of the logs shows:

Code: [Select]

[Apr 11 20:01:11] NOTICE[4566]: chan_iax2.c:8580 __iax2_poke_noanswer: Peer '5145551111peer' is now UNREACHABLE! Time: 9
[Apr 11 20:01:11] NOTICE[4574]: chan_iax2.c:8580 __iax2_poke_noanswer: Peer '5145552222peer' is now UNREACHABLE! Time: 10
[Apr 11 20:01:13] NOTICE[4572]: chan_iax2.c:8580 __iax2_poke_noanswer: Peer '4185553333peer' is now UNREACHABLE! Time: 10
[Apr 11 20:01:13] NOTICE[4568]: chan_iax2.c:8580 __iax2_poke_noanswer: Peer '5145554444peer' is now UNREACHABLE! Time: 9
[Apr 11 20:01:14] NOTICE[4562]: chan_sip.c:15683 sip_poke_noanswer: Peer '51455555555peer' is now UNREACHABLE!  Last qualify: 17
[Apr 11 20:01:19] NOTICE[4562]: chan_sip.c:15683 sip_poke_noanswer: Peer '5008' is now UNREACHABLE!  Last qualify: 26
[Apr 11 20:02:03] NOTICE[4570]: chan_iax2.c:7671 socket_process: Peer '5145551111peer' is now REACHABLE! Time: 2010
[Apr 11 20:02:03] NOTICE[4571]: chan_iax2.c:7671 socket_process: Peer '5145552222peer' is now REACHABLE! Time: 2010
[Apr 11 20:02:03] NOTICE[4574]: chan_iax2.c:7671 socket_process: Peer '4185553333peer' is now REACHABLE! Time: 10
[Apr 11 20:02:03] NOTICE[4565]: chan_iax2.c:7671 socket_process: Peer '5145554444peer' is now REACHABLE! Time: 10
[Apr 11 20:02:03] NOTICE[4562]: chan_sip.c:12532 handle_response_peerpoke: Peer '5008' is now Reachable. (2030ms / 3000ms)
[Apr 11 20:02:12] NOTICE[4562]: chan_sip.c:12532 handle_response_peerpoke: Peer '51455555555peer' is now Reachable. (16ms / 3000ms)