Extension '*992*10*4004' does not exist in context 'from-internal' or has no associated hint


(Hawk McDuck) #1

I’m running FreePBX FreePBX 14.0.13.26 / Asterisk 13.32.0. All modules are up to date and there are, among other IP phones, two Sangoma S500 phones which were provisioned via Zero Touch Provisioning. S500 phone 1 has four pj_sip extensions, 4001, 4002, 4003, and 4004, and S500 phone 2 has 4011, 4012, 4013 and 4014. Every few minutes /var/log/asterisk/full spews out the following:

[2020-03-24 07:10:39] NOTICE[22419] res_pjsip_exten_state.c: Endpoint '4011' state subscription failed: Extension '*992*10*4013' does not exist in context 'from-internal' or has no associated hint
[2020-03-24 07:10:39] NOTICE[30963] res_pjsip_exten_state.c: Endpoint '4011' state subscription failed: Extension '*992*11*4013' does not exist in context 'from-internal' or has no associated hint
[2020-03-24 07:10:39] NOTICE[25734] res_pjsip_exten_state.c: Endpoint '4011' state subscription failed: Extension '*992*12*4013' does not exist in context 'from-internal' or has no associated hint
[2020-03-24 07:10:39] NOTICE[8179] res_pjsip_exten_state.c: Endpoint '4011' state subscription failed: Extension '*992*16*4013' does not exist in context 'from-internal' or has no associated hint
[2020-03-24 07:10:40] NOTICE[8179] res_pjsip_exten_state.c: Endpoint '4001' state subscription failed: Extension '*992*3*4004' does not exist in context 'from-internal' or has no associated hint
[2020-03-24 07:10:40] NOTICE[30963] res_pjsip_exten_state.c: Endpoint '4001' state subscription failed: Extension '*992*15*4004' does not exist in context 'from-internal' or has no associated hint
[2020-03-24 07:10:40] NOTICE[25734] res_pjsip_exten_state.c: Endpoint '4001' state subscription failed: Extension '*992*10*4004' does not exist in context 'from-internal' or has no associated hint
[2020-03-24 07:10:40] NOTICE[30963] res_pjsip_exten_state.c: Endpoint '4001' state subscription failed: Extension '*992*11*4004' does not exist in context 'from-internal' or has no associated hint
[2020-03-24 07:10:40] NOTICE[8179] res_pjsip_exten_state.c: Endpoint '4001' state subscription failed: Extension '*992*12*4004' does not exist in context 'from-internal' or has no associated hint
[2020-03-24 07:10:40] NOTICE[22419] res_pjsip_exten_state.c: Endpoint '4001' state subscription failed: Extension '*992*16*4004' does not exist in context 'from-internal' or has no associated hint

It appears that there is something wrong in the pj_sip configuration of extensions 4004 and 4013. Can someone point me to the issue?


(Lorne Gaetz) #2

They are related to BLF hints for Phone Apps buttons. Just ignore.


(Hawk McDuck) #3

Thanks, will do.


(Jared Busch) #4

This is a horrible suggestion as it makes later troubleshooting more difficult when you have to wade through this stuff in the logs. Also, IMO only, it is a contributing factor as to why these phones are so sluggish. Everything under the sun is enabled by default.

When I first got a Sangoma S500 phone for testing I noticed this also. I went through and figured out what all of the hints were related to and removed the appropriate ones from the phone.
I should have documented that better, but I didn’t.


(Hawk McDuck) #5

@sorvani Thanks for your reply. Since I’m lying around home at the moment with nothing else to do, I’ll take you up on your suggestion. However, I’m not sure where to start, so perhaps you could point me in the right direction.

If I do eventually get this sorted out, I’ll document for all to see.


(Jared Busch) #6

Open the template in EPM.
Click on the model of phone you have.
look at all the XML-API. Those are the ones doing that.

*992*10*EXT is tied to one of those.

Actually, you can see the same on your extension. so I guess the template is the wrong place to “test”

If you open your extension from Extension Mapping, and change things there one by one, you can always reset your extension back to template if you break things…


(Hawk McDuck) #7

@sovani Thanks again for your reply. BTW, my system is not a production system. I’m happy enough to do testing on it.

I went into Endpoint Manager–>Extension Mapping. There were only the 8 extensions, 4001, 4002, 4003, 4004, 4011, 4012, 4013 and 4014. From the logs in the original post above, the only two extensions reporting problems were 4004 and 4013. I clicked on the edit button for 4004 and confirmed everything looked OK. I did save, rebuild and reboot both phones.

I watched /var/log/asterisk/full and the mis-config was still showing up on ext. 4004 and 4013.

However, in Reports–>Asterisk Info–>Chan_PJSip info I noticed that ext. 4014 was not showing up and on further investigation, I saw from the web GUI of the second Sangoma S500 that Account 4 (i.e, ext. 4014) was disabled. I enabled Account 4, rebooted the phone and was surprised to see that–with only this change–the mis-config was now on ext. 4004 and ext. 4014. No mis-config was showing on ext. 4013.

[2020-03-26 16:25:51] NOTICE[4894] res_pjsip_exten_state.c: Endpoint ‘4001’ state subscription failed: Extension ‘992154004’ does not exist in context ‘from-internal’ or has no associated hint
[2020-03-26 16:25:51] NOTICE[14124] res_pjsip_exten_state.c: Endpoint ‘4001’ state subscription failed: Extension '99210
4004’ does not exist in context ‘from-internal’ or has no associated hint
[2020-03-26 16:25:51] NOTICE[4894] res_pjsip_exten_state.c: Endpoint ‘4001’ state subscription failed: Extension ‘992114004’ does not exist in context ‘from-internal’ or has no associated hint
[2020-03-26 16:25:51] NOTICE[14124] res_pjsip_exten_state.c: Endpoint ‘4001’ state subscription failed: Extension '99212
4004’ does not exist in context ‘from-internal’ or has no associated hint
[2020-03-26 16:25:51] NOTICE[4894] res_pjsip_exten_state.c: Endpoint ‘4001’ state subscription failed: Extension ‘992164004’ does not exist in context ‘from-internal’ or has no associated hint
[2020-03-26 16:32:51] NOTICE[14124] res_pjsip_exten_state.c: Endpoint ‘4011’ state subscription failed: Extension '99215
4014’ does not exist in context ‘from-internal’ or has no associated hint
[2020-03-26 16:32:51] NOTICE[14124] res_pjsip_exten_state.c: Endpoint ‘4011’ state subscription failed: Extension ‘992104014’ does not exist in context ‘from-internal’ or has no associated hint
[2020-03-26 16:32:51] NOTICE[15770] res_pjsip_exten_state.c: Endpoint ‘4011’ state subscription failed: Extension '99211
4014’ does not exist in context ‘from-internal’ or has no associated hint
[2020-03-26 16:32:51] NOTICE[4894] res_pjsip_exten_state.c: Endpoint ‘4011’ state subscription failed: Extension ‘992124014’ does not exist in context ‘from-internal’ or has no associated hint
[2020-03-26 16:32:51] NOTICE[14124] res_pjsip_exten_state.c: Endpoint ‘4011’ state subscription failed: Extension '99216
4014’ does not exist in context ‘from-internal’ or has no associated hint

I’ll have to think on this for a while.


(Hawk McDuck) #8

Here are the errors:

Endpoint ‘4001’ state subscription failed: Extension ‘*992*15*4004’ does not exist in context ‘from-internal’ or has no associated hint
Endpoint ‘4001’ state subscription failed: Extension ‘*992*10*4004’ does not exist in context ‘from-internal’ or has no associated hint
Endpoint ‘4001’ state subscription failed: Extension ‘*992*11*4004’ does not exist in context ‘from-internal’ or has no associated hint
Endpoint ‘4001’ state subscription failed: Extension ‘*992*12*4004’ does not exist in context ‘from-internal’ or has no associated hint
Endpoint ‘4001’ state subscription failed: Extension ‘*992*16*4004’ does not exist in context ‘from-internal’ or has no associated hint
Endpoint ‘4011’ state subscription failed: Extension ‘*992*15*4014’ does not exist in context ‘from-internal’ or has no associated hint
Endpoint ‘4011’ state subscription failed: Extension ‘*992*10*4014’ does not exist in context ‘from-internal’ or has no associated hint
Endpoint ‘4011’ state subscription failed: Extension ‘*992*11*4014’ does not exist in context ‘from-internal’ or has no associated hint
Endpoint ‘4011’ state subscription failed: Extension ‘*992*12*4014’ does not exist in context ‘from-internal’ or has no associated hint
Endpoint ‘4011’ state subscription failed: Extension ‘*992*16*4014’ does not exist in context ‘from-internal’ or has no associated hint

Here’s the result of grepping for the offending strings in /tftpboot:

tftpboot]$ grep -i “992” cfg0050*.xml | cut -c20-
: <P20219>*992*5*4014</P20219>
: <P20224>*992*2*4014</P20224>
: <P20229>*992*14*4014</P20229>
: <P20239>*992*6*4014</P20239>
: <P20244>*992*3*4014</P20244>
: <P20249>*992*15*4014</P20249>
: <P20259>*992*8*4014</P20259>
: <P20264>*992*9*4014</P20264>
: <P20269>*992*10*4014</P20269>
: <P20274>*992*11*4014</P20274>
: <P20279>*992*12*4014</P20279>
: <P20289>*992*16*4014</P20289>
: <P20992>1</P20992>
: <P20219>*992*5*4004</P20219>
: <P20224>*992*2*4004</P20224>
: <P20229>*992*14*4004</P20229>
: <P20239>*992*6*4004</P20239>
: <P20244>*992*3*4004</P20244>
: <P20249>*992*15*4004</P20249>
: <P20259>*992*8*4004</P20259>
: <P20264>*992*9*4004</P20264>
: <P20269>*992*10*4004</P20269>
: <P20274>*992*11*4004</P20274>
: <P20279>*992*12*4004</P20279>
: <P20289>*992*16*4004</P20289>
: <P20992>1</P20992>
[tftpboot]$

I edited the cfg0050*.xml files [i.e., the Sangoma S500 config files] in /tftpboot and removed each of the ten offending entries that were showing as ‘state subscription failed’. For example, <P20269>*992*10*4014</P20269> was changed to <P20269></P20269> .

Thus far the error messages in /var/log/asterisk/full have stopped.

I will watch and if any side effects are found, I will report back.


(Jared Busch) #9

Right. That will stop the errors until you next rebuild the config files. but what I was implying was that I had figured out what app each of the numbers after the *992 was tied to by removing apps form the EPM template and then rebuilding the config.

Also I thought I have seen a list from a post on the forum here someplace, but I cannot find it again.


#10

@sgseidel An effective solution if you can’t just ignore them, kudos

perhaps make it scriptable with sed , possibly something close to:-

sed -i 's/\(<P.*>\).*\(</P.*>\)/\1\2/g' cfg0050*.xml

if rebuilding the configs is ever needed until that problem is fixed, reapply such a patch after doing that.


(Hawk McDuck) #11

@sorvani After I removed the offending lines in the xml files, I rebooted each of the phones, and yes, I’m pretty sure that I will have to do this again if I rebuild the config files.

But it is amazing how clean the /var/log/asterisk/full log file is. A wonder to behold!


(Hawk McDuck) #12

@dicko Well ‘sed’! I too am a fan of sed, and I’m sure I can come up with a script that will do the trick if the errors in the logs overly annoy me.