Linksys SPA8000 And yeastar s100 PBX 404 issue on registration

mefisto74 · ‎06-21-2021

hello i'm currently trying to make work linksys spa 8000 GATEWAY and yeastar s100 PBX
i configured line in yeastar pbx and in linksys spa 8000 but this doesnt work. in logs i see errors like

[2021-06-21 11:50:27] WARNING[20733]: res_pjsip_outbound_registration.c:1068 handle_registration_response: '404' fatal response received from 'sip:192.168.200.32:5060;transport=udp' on registration attempt to 'sip:<mynumber>@192.168.200.32:5060', retrying in '5' seconds

200.32 is SPA gateway and in SPA gateway i also have 404 errors when trying to register as i can see in logs

what im doing wrong?

Dan Lukes · ‎06-22-2021

Disclose content of the SIP packets we are speaking here of about.

mefisto74 · ‎06-22-2021

im getting packages like this

<--- Transmitting SIP request (586 bytes) to UDP:192.168.200.32:5060 --->
REGISTER sip:192.168.200.32:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 192.168.200.8:5060;rport;branch=z9hG4bKPj007994f3-037f-444a-8108-8d396d0a0dd8
From: <sip:<mynumber>@192.168.200.32>;tag=e61abddd-0bd7-41a8-bc61-3e507d218309
To: <sip:<mynumber>@192.168.200.32>
Call-ID: 17b76411-8f62-455e-b244-56a57ef65d22
CSeq: 69699 REGISTER
Contact: <sip:<mynumber>@192.168.200.8:5060>
Expires: 1800
Allow: OPTIONS, NOTIFY, SUBSCRIBE, NOTIFY, PUBLISH, INVITE, ACK, BYE, CANCEL, UPDATE, PRACK, REFER, REGISTER, MESSAGE
Max-Forwards: 70
User-Agent: Yeastar S100-30.12.0.10
Content-Length: 0

<--- Received SIP response (410 bytes) from UDP:192.168.200.32:5060 --->
SIP/2.0 404 Not Found
To: <sip:<mynubmer>@192.168.200.32>;tag=a2f585298180e61di0
From: <sip:<mynumber>@192.168.200.32>;tag=e61abddd-0bd7-41a8-bc61-3e507d218309
Call-ID: 17b76411-8f62-455e-b244-56a57ef65d22
CSeq: 69699 REGISTER
Via: SIP/2.0/UDP 192.168.200.8:5060;branch=z9hG4bKPj007994f3-037f-444a-8108-8d396d0a0dd8
Server: Linksys/SPA8000-6.1.12SR1
Allow-Events: talk, hold, conference
Content-Length: 0

[2021-06-22 14:53:54] DEBUG[20733]: res_pjsip_outbound_registration.c:1157 sip_outbound_registration_response_cb: Received REGISTER response 404(Not Found)
[2021-06-22 14:53:54] DEBUG[20733]: res_pjsip_outbound_registration.c:923 handle_registration_response: Processing REGISTER response 404 from server 'sip:192.168.200.32:5060;transport=udp' for client 'sip:<mynubmer>@192.168.200.32:5060'

[2021-06-22 14:53:54] DEBUG[20733]: res_pjsip_outbound_registration.c:647 schedule_registration: Scheduling outbound registration to server 'sip:192.168.200.32:5060;transport=udp' from client 'sip:<mynumber>@192.168.200.32:5060' in 5 seconds

Dan Lukes · ‎06-22-2021

It's more clear now. You are trying to register S100 client to SPA8000 server. It's uncommon configuration. I never hear about it. 404 error mean "no such user exists", but it includes case "no user exists at all" as well. I'm unsure the SPA8000 is capable to be server of such kind.

Common configuration is - the SPA8000 is registering to upstream (S100 here). It's known to work.

I recommend you to follow standard way. Otherwise, you need to identify correct credentials for register. As claimed already, I'm unsure there are some.

mefisto74 · ‎06-23-2021

looks like you right but as i can see "to" and "from" have identical ip. but as i think "from" must be SPA 8000 and to S100. but i dont get why they the same. i typed proxy in line 1 and trunk 1 ip of S100 and in s100 ip of spa

Dan Lukes · ‎06-23-2021

Two issues here. One, the IP used in FROM and TO. You wish not to solve this issue - it's still about registration of S100 to SPA8000 which I consider impossible. So even if you will change the IP, S100 just twill not REGISTER to SPA8000 because SPA8000 provide no such service at all.

You need to register SPA8000 to S100 instead. It require: reconfigure S100 to STOP registration attempts. It needs accept registration attempts from SPA8000 instead. Once you will have S100 reconfigured, configure SPA8000 to register to S100. Use credentials as required by S100 for it.