I had kind of hijacked @Disciplus topic at
https://wazo-platform.discourse.group/t/wazo-ui-connexion-impossible/121
on root user/password so I decided to continue our conversation here in this topic dedicated to our conversation.
I activated
asterisk -r
to start monitoring the log of activity when making the call tests
I have the incalls getting to my server but am getting the errror messages as shown (I replaced the at symbol with {at} since the forum thought I was trying to tag people with each use of the at symbol and would not let me post)
For Outcall from extension 11002 to {RealNumberHidden}
[2020-01-03 12:53:06.3136] NOTICE[11564]: res_pjsip_session.c:3057 new_invite: Call from ‘11002’ (UDP:{RealISourcePaddressHidden}:57956) to extension ‘{RealNumberHidden}’ rejected because extension not found in context ‘StokeInternalContext’.
The {RealNumberHidden} is the 10-digit NorthAmerican number bing dialed, which, since the Internal Context only is defined to allow extensions from numbers ranging from 10000 to 99999 , it is understandable that it would not contain the {RealNumberHidden}. In the Incall Context, I defined the allowed numbers to be 10-digit from 2010000000 to 9999999999.
For Incall to user SoftPhone from {RealNumberHidden}
[Jan 3 13:09:07] – Executing [s{at}StokeIncallContext:1] NoOp(“PJSIP/{RealNumberHidden}-0000000f”, “”) in new stack
[Jan 3 13:09:07] – Executing [s{at}StokeIncallContext:2] GotoIf(“PJSIP/{RealNumberHidden}-0000000f”, “1?:not-pjsip”) in new stack
[Jan 3 13:09:07] – Executing [s{at}StokeIncallContext:3] GotoIf(“PJSIP/{RealNumberHidden}-0000000f”, “1?:error-loop”) in new stack
[Jan 3 13:09:07] – Executing [s{at}StokeIncallContext:4] Set(“PJSIP/{RealNumberHidden}-0000000f”, “XIVO_DID_NEXT_EXTEN=s”) in new stack
[Jan 3 13:09:07] – Executing [s{at}StokeIncallContext:5] Set(“PJSIP/{RealNumberHidden}-0000000f”, “XIVO_FROM_S=1”) in new stack
[Jan 3 13:09:07] – Executing [s{at}StokeIncallContext:6] Goto(“PJSIP/{RealNumberHidden}-0000000f”, “StokeIncallContext,s,1”) in new stack
[Jan 3 13:09:07] – Goto (StokeIncallContext,s,1)
[Jan 3 13:09:07] – Executing [s{at}StokeIncallContext:1] NoOp(“PJSIP/{RealNumberHidden}-0000000f”, “”) in new stack
[Jan 3 13:09:07] – Executing [s{at}StokeIncallContext:2] GotoIf(“PJSIP/{RealNumberHidden}-0000000f”, “1?:not-pjsip”) in new stack
[Jan 3 13:09:07] – Executing [s{at}StokeIncallContext:3] GotoIf(“PJSIP/{RealNumberHidden}-0000000f”, “0?:error-loop”) in new stack
[Jan 3 13:09:07] – Goto (StokeIncallContext,s,10)
[Jan 3 13:09:07] – Executing [s{at}StokeIncallContext:10] NoOp(“PJSIP/{RealNumberHidden}-0000000f”, “”) in new stack
[Jan 3 13:09:07] – Executing [s{at}StokeIncallContext:11] Log(“PJSIP/{RealNumberHidden}-0000000f”, “ERROR, Dialplan loop detected. Got PJSIP header To: sip:s@192.168.1.201”) in new stack
[2020-01-03 13:09:07.0920] ERROR[12564][C-0000000d]: Ext. s:11 {at} StokeIncallContext: Dialplan loop detected. Got PJSIP header To: sip:s{at}{RealServerIPaddressHidden}
[Jan 3 13:09:07] – Executing [s{at}StokeIncallContext:12] Hangup(“PJSIP/{RealNumberHidden}-0000000f”, “”) in new stack
[Jan 3 13:09:07] == Spawn extension (StokeIncallContext, s, 12) exited non-zero on ‘PJSIP/{RealNumberHidden}-0000000f’
which looks like it is looping, but I do not speak Asterisk as well as you I am sure.
I did notice that there is a spot when defining Contexts to include other Contexts, but I did not have that setup when I ran these tests. I did try adding the to-extern and from-extern Contexts to the Internal Context and other combinations but it did not seem to make a difference.
Is this giving you any indication why the Incalls and Outcalls are not working?
Just to show that the trunk is registered, when I did a
asterisk -rx “pjsip show registrations”
I got back
<Registration/ServerURI…> <Auth…> <Status…>
reg_{RealNumberHidden}{at}{HostFQDNhidden}/sip:{HostFQDN-lessTLD-hidden}. auth_reg_{RealNumberHidden}{at}sip02.unlimitel.ca Registered
Not sure where to go next …
Any suggestions are appreciated.