Calls not routing; Asterisk running on Synology diskstation

Asterisk Asterisk Support
1

I wonder if anyone has any insight working with Asterisk on a Synology nas. I’m trying to set up inbound and outbound calling but am having problems. My main problem is getting inbound calls to route to an extension. Local switching between extensions is working fine (physical IP handsets), and my trunks are showing as registered with Sipgate, but when an external call hits the Asterisk box it doesn’t go anywhere regardless of what inbound routes I try - have tried using a ‘catch all’ route and also a specific route with my number in the DID, but the calls fail to connect to an extension and I can’t see any error messages anywhere.
Asterisk/1.8.13.1
Asterisk GUI-version : 2.1.0-rc1
Sip dialog below, can anyone see any obvious problems? (numbers have been altered slightly to protect the innocent;)
[color=#0000BF]<— SIP read from UDP:217.10.79.23:5060 —>
INVITE sip:s@93.96.123.123:5060 SIP/2.0
Record-Route: sip:217.10.79.23:5060;lr;ftag=as0785e8b8
Record-Route: sip:172.20.40.3;lr=on
Record-Route: sip:217.10.79.23:5060;lr;ftag=as0785e8b8
Via: SIP/2.0/UDP 217.10.79.23:5060;branch=z9hG4bK46f5.6b541091.0
Via: SIP/2.0/UDP 172.20.40.3;branch=z9hG4bK46f5.6b541091.0
Via: SIP/2.0/UDP 217.10.79.23:5060;received=217.10.68.222;branch=z9hG4bK15e50793
Via: SIP/2.0/UDP

217.116.117.10:5060;received=217.116.117.10;branch=z9hG4bK15e50793;rport=5060
Max-Forwards: 67
From: “07957123456” sip:07957123456@sipgate.co.uk;tag=as0785e8b8
To: sip:00441494123456@sipgate.co.uk
Contact: sip:07957123456@217.116.117.10
Call-ID: 2d2907846bba025e470aaa521a41bfaa@sipgate.co.uk
CSeq: 102 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO
Supported: replaces, timer
Content-Type: application/sdp
Content-Length: 467

v=0
o=root 759523207 759523207 IN IP4 217.116.117.10
s=sipgate VoIP GW
c=IN IP4 217.10.77.244
t=0 0
m=audio 58172 RTP/AVP 8 0 3 97 18 112 101
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:3 GSM/8000
a=rtpmap:97 iLBC/8000
a=fmtp:97 mode=30
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:112 G726-32/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=silenceSupp:off - - - -
a=ptime:20
a=sendrecv
a=direction:active
a=nortpproxy:yes

<------------->
— (18 headers 21 lines) —

Sending to 217.10.79.23:5060 (NAT)

Using INVITE request as basis request - 2d2907846bba025e470aaa521a41bfaa@sipgate.co.uk

Found peer ‘4153553’ for ‘07957123456’ from 217.10.79.23:5060

<— Reliably Transmitting (NAT) to 217.10.79.23:5060 —>
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP

217.10.79.23:5060;branch=z9hG4bK46f5.6b541091.0;received=217.10.79.23;rport=5060
Via: SIP/2.0/UDP 172.20.40.3;branch=z9hG4bK46f5.6b541091.0
Via: SIP/2.0/UDP 217.10.79.23:5060;received=217.10.68.222;branch=z9hG4bK15e50793
Via: SIP/2.0/UDP

217.116.117.10:5060;received=217.116.117.10;branch=z9hG4bK15e50793;rport=5060
From: “07957123456” sip:07957123456@sipgate.co.uk;tag=as0785e8b8
To: sip:00441494123456@sipgate.co.uk;tag=as392a975a
Call-ID: 2d2907846bba025e470aaa521a41bfaa@sipgate.co.uk
CSeq: 102 INVITE
Server: Asterisk PBX
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm=“asterisk”, nonce="7bdf4623"
Content-Length: 0

<------------>

Scheduling destruction of SIP dialog '2d2907846bba025e470aaa521a41bfaa@sipgate.co.uk’ in

32000 ms (Method: INVITE)

<— SIP read from UDP:217.10.79.23:5060 —>
ACK sip:s@93.96.123.123:5060 SIP/2.0
Via: SIP/2.0/UDP 217.10.79.23:5060;branch=z9hG4bK46f5.6b541091.0
Via: SIP/2.0/UDP 172.20.40.3;branch=z9hG4bK46f5.6b541091.0
From: “07957123456” sip:07957123456@sipgate.co.uk;tag=as0785e8b8
Call-ID: 2d2907846bba025e470aaa521a41bfaa@sipgate.co.uk
To: sip:00441494123456@sipgate.co.uk;tag=as392a975a
CSeq: 102 ACK
Max-Forwards: 69
Content-Length: 0
X-hint: rr-enforced[/color]

2

We need the complete sip debug of the call.

3

insecure=invite on the sipgate entry. If they have told them to use insecure=very, please tell them that that is no longer recognized and most people only need invite, not both port and invite. (The name was probably changed because if was being misused, but it is still being misused, even with the two insecurities

This ignores the Synology element of the problem and assumes they are using a currently supported version of Asterisk.

4

Thanks for the responses.

david55: That’s helpful - I changed the sipgate trunk to INVITE and am now getting this:
[Jan 14 23:17:47] NOTICE[8382]: chan_sip.c:22718 handle_request_invite: Call from ‘4153553’ (217.10.79.23:5060) to extension ‘s’ rejected because extension not found in context ‘DID_4153553’

Which is at least an error message I can work with so thank you :smile:

navaismo: That was all the info that popped up in the CLI when I made the inbound call; not sure how to get any more debug info than that to be honest. I’m a newbie with Asterisk, I’ve built a couple of trixboxes and I like working with Freepbx but I’m an Asterisk amateur still really - all advice is greatly appreciated!

Thanks both I’ll post back if I get this working.

Cheers

Al.

5

Getting s means you don’t have a true direct in dialing service. The VoIP community misuses DID to describe something that is direct in dialing to the ITSP but not the customer, i.e. pretty much any incoming line from the PSTN over SIP. Just treat it as you had DID with one line, numbered “s”.

6

Well I managed to get calls coming through now using the advice here:
http://forum.synology.com/enu/viewtopic.php?f=190&t=56018&start=15

Instructions:
You need to enable SSH access to your NAS - you can google instructions on that, then go to the directory where the asterisk config files are kept (should be something like /volume1/@appstore/Asterisk/etc/asterisk) then edit your extensions.conf

[quote]DiskStation> pwd
/volume1/@appstore/Asterisk/etc/asterisk
DiskStation> grep “Goto(default” *

extensions.conf:;exten = s,1,Goto(default|6000|1)
extensions.conf:exten = s,1,Goto(default,6000,1)[/quote]
I changed the line in my extensions.conf to exten = s,1,Goto(default,3837,1)
3837 being one of the extensions connected to my network. This is great and means I can actually get inbound calls. Now I just need to work out how to route calls coming in on specific Sipgate trunks(DDI’s) to specific extensions on the network! shouldn’t be too difficult as soon as I get some spare time.
Thanks for the pointers all :smiley:

p.s. Just as an extra hint for anyone who found this thread; once you have SSH access to your Synology NAS running Asterisk you can get debug info by switching to directory /volume1/@appstore/Asterisk/sbin/
Then run
./asterisk -vvvvvr

7

Hi,

I just wanted to thank [color=#40BF00]phon3y [/color]for his valued advice. I looked for hours for both finding a way to see Asterisk’s log in Synology as well as solving the inbound calls not ringing.
Two birds in one post :smile: