Dgeka25594
commented
2 years ago I rebuilt Kamailio (on VMachine) and the difference was in the configs compared to the IMS_Kamailio template. Now there is such an error on the PCSCF:
3(141510) NOTICE: <script>: PCSCF: REGISTER sip:ims.mnc001.mcc001.3gppnetwork.org (sip:bob@ims.mnc001.mcc001.3gppnetwork.org (10.2.16.7:5060) to sip:bob@ims.mnc001.mcc001.3gppnetwork.org, 2e1cf44b667071def5332be769f348d1@10.2.16.7)
3(141510) INFO: rr [rr_mod.c:515]: pv_get_route_uri_f(): No route header present.
3(141510) NOTICE: <script>: PCSCF REGISTER:
Destination URI: <null>
Request URI: sip:ims.mnc001.mcc001.3gppnetwork.org
3(141510) INFO: rr [rr_mod.c:515]: pv_get_route_uri_f(): No route header present.
3(141510) NOTICE: <script>: Source IP and Port: (10.2.16.7:5060)
Route-URI:
3(141510) NOTICE: <script>: Received IP and Port: (192.168.56.117:5060)
3(141510) NOTICE: <script>: Contact header: <sip:bob@10.2.16.7:5060>
3(141510) INFO: ims_registrar_pcscf [sec_agree.c:264]: cscf_get_security(): No security parameters found
3(141510) INFO: ims_registrar_pcscf [sec_agree.c:296]: cscf_get_security_verify(): No security-verify parameters found
3(141510) ERROR: cdp [routing.c:274]: get_routing_peer(): get_routing_peer(): No connected DefaultRoute peer found for app_id 16777236 and vendor id 10415.
3(141510) ERROR: cdp [diameter_comm.c:142]: AAASendMessage(): AAASendMessage(): Can't find a suitable connected peer in the routing table.
3(141510) ERROR: ims_qos [ims_qos_mod.c:1414]: w_rx_aar_register(): Failed to send AAR
3(141510) ERROR: ims_qos [ims_qos_mod.c:1458]: w_rx_aar_register(): Error trying to send AAR
3(141510) WARNING: tm [t_lookup.c:1504]: t_unref(): script writer didn't release transaction
So I understand the problem with the Kamailio routes. But why was it not a problem with my configs.
Hi, herlesupreeth! I would be grateful if you can help me, I broke my head solving this problem. Immediately apologize for my English.
I am setting up Kamailio IMS on VirtualBox: FHоSS 192.168.56.110 PCSCF 192.168.56.112 ICSCF 192.168.56.113 SCSCF 192.168.56.109 Instead of UE, I use ims-communicator (https://sourceforge.net/projects/imscommunicator.berlios/), the authentification algorithm I use AKAv1-MD5. User profiles are standard, Bob. I answer:
I don't understand the error from the CSCSCF logs, the user status is written to HSS as AUTH-PENDING.
The dump shows that after the second REGISTER comes Status: 403 Authentitication Failed. The dump shows that ims-communicator is sending the second REGISTER with the authentification algorithm AKAv1-MD5. In scscf.cfg I have included AKAv1-MD5.
I found errors in the PCSCF log, No security parameters found, but I assume they are due to the fact that the client is without IPSEC and does not interfere with the request further.
I cannot determine the source of the problem. dumps.zip
Dumps, log and config are attache icscf.zip pcscf.zip scscf.zip hss.zip