Rejecting unknown SIP connection from local device

Hi. First steps in Asterisk/FreePBX, so this is bound to be very simple, but I can’t see the wood for the trees at the moment. All the posted topics on rejecting unkown SIP seem to be about external access. This is rejecting the phone it’s meant to see.

So. Using latest RaspBX distro of FreePBX/Asterisk, versions are
Phones are Cisco 7940 and I’ve had some fun getting the right images/boot seq etc. so I suspect the issue is in the authentication setup but I think it’s right.

First phone - created a Chan Sip extension. 298. 7940 is configured through bootup TFTP xfers so copied the extension and password secret to the phone specific SIP config file as:

SIP Configuration Generic File

image_version: P0S3-8-12-00

Line 1 appearance

line1_name: 298

Line 1 Registration Authentication

line1_authname: 298

Line 1 Registration Password


In extension app I have display name 298 and same password - copied and matches extension version, no leading/trailing spaces.

Checked in phone once booted and it’s got the correct IP address for FreePBX/Asterisk. Password is **** out on the phone but I have to assume is OK - unless there’s a length issue, but I can’t find anything about this in CIsco docs.

Anyway the phone tries to connect but what I see in the Asterisk console log (using asterisk -rvvvv) is:

Connected to Asterisk 13.15.0 currently running on raspbx (pid = 1844)
== Using SIP RTP TOS bits 184
== Using SIP RTP CoS mark 5
– Executing [[email protected]:1] NoOp(“SIP/”, “Received incoming SIP connection from unknown peer to 299”) in new stack
– Executing [[email protected]:2] Set(“SIP/”, “DID=299”) in new stack
– Executing [[email protected]:3] Goto(“SIP/”, “s,1”) in new stack
– Goto (from-sip-external,s,1)
– Executing [[email protected]:1] GotoIf(“SIP/”, “1?setlanguage:checkanon”) in new stack
– Goto (from-sip-external,s,2)
– Executing [[email protected]:2] Set(“SIP/”, “CHANNEL(language)=en”) in new stack
– Executing [[email protected]:3] GotoIf(“SIP/”, “1?noanonymous”) in new stack
– Goto (from-sip-external,s,5)
– Executing [[email protected]:5] Set(“SIP/”, “TIMEOUT(absolute)=15”) in new stack
– Channel will hangup at 2017-07-24 14:31:16.789 BST.
– Executing [[email protected]:6] Log(“SIP/”, "WARNING,“Rejecting unknown SIP connection from"”) in new stack
[2017-07-24 14:31:01] WARNING[9300][C-00000008]: Ext. s:6 @ from-sip-external: "Rejecting unknown SIP connection from"
– Executing [[email protected]:7] Answer(“SIP/”, “”) in new stack
– Executing [[email protected]:8] Wait(“SIP/”, “2”) in new stack
– Executing [[email protected]:9] Playback(“SIP/”, “ss-noservice”) in new stack
– <SIP/> Playing ‘ss-noservice.ulaw’ (language ‘en’)
– Executing [[email protected]:10] PlayTones(“SIP/”, “congestion”) in new stack
– Executing [[email protected]:11] Congestion(“SIP/”, “5”) in new stack
== Spawn extension (from-sip-external, s, 11) exited non-zero on ‘SIP/’
– Executing [[email protected]:1] Hangup(“SIP/”, “”) in new stack
== Spawn extension (from-sip-external, h, 1) exited non-zero on ‘SIP/’

The IP address of the rejected peer is the phone on the local network, but I can’t see a reason why. Any old timers with 7940 config experience able to put me on the right path?

The only other thing I have noticed, which I’m sure has nothing to do with this but… is sometimes when I edit the extension (or any other test one I have created) I get a brief flash of a dialogue in top right of screen - dark rectangle with warning shield and Error in it. No more than that and no explanation.


Your password is too long for your phone, search the forum ,. Reduce the length tless than 31 chars

That’s way too long for a 7940.

Many thanks guys, now I can progress onto the fun stuff…