Hello, are you already using kamailio 5.4.0 or 5.41? I did some fixes not long ago in the cdp modules.
About the error: 94(8085) ERROR: cdp [receiver.c:553]: do_receive(): do_receive(): [pcf.sip.example.com<http://pcf.sip.example.com>] Received Unknown version [72] This looks like one that should be more investigated. Have you looked into the Diameter network trace, to see if your server is answering correctly? Cheers, Henning -- Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.com<https://gilawa.com/> From: Pavithra Mohanraja <[email protected]> Sent: Thursday, September 17, 2020 12:50 PM To: Henning Westerholt <[email protected]> Cc: Kamailio (SER) - Users Mailing List <[email protected]>; supreeth herle <[email protected]>; Abdirahman A. Osman <[email protected]> Subject: Re: [SR-Users] Kamailio IMS Diameter Messages Hi, It is getting connected first and dropping then. thats y i am not sure why it is happening 96(8089) INFO: cdp [peerstatemachine.c:524]: I_Snd_Conn_Req(): I_Snd_Conn_Req(): Peer pcf.sip.example.com<http://pcf.sip.example.com> 96(8089) INFO: cdp [receiver.c:874]: peer_connect(): peer_connect(): Trying to connect to 10.45.7.47 port 29507 95(8086) INFO: cdp [acceptor.c:81]: acceptor_process(): Acceptor process starting up... 95(8086) WARNING: cdp [tcp_accept.c:120]: create_socket(): create_socket(): Trying to open/bind/listen on 10.1.68.36 port 3871 95(8086) WARNING: cdp [tcp_accept.c:145]: create_socket(): create_socket(): Successful socket open/bind/listen on 10.1.68.36 port 3871 95(8086) INFO: cdp [acceptor.c:95]: acceptor_process(): Acceptor opened sockets. Entering accept loop ... 96(8089) INFO: cdp [receiver.c:954]: peer_connect(): peer_connect(): Peer pcf.sip.example.com:29507<http://pcf.sip.example.com:29507> connected 94(8085) ERROR: cdp [receiver.c:553]: do_receive(): do_receive(): [pcf.sip.example.com<http://pcf.sip.example.com>] Received Unknown version [72] 94(8085) INFO: cdp [receiver.c:807]: receive_loop(): select_recv(): [pcf.sip.example.com<http://pcf.sip.example.com>] read on socket [35] returned 0 > ... dropping 94(8085) INFO: cdp [receiver.c:222]: disconnect_serviced_peer(): drop_serviced_peer(): [pcf.sip.example.com<http://pcf.sip.example.com>] Disconnecting from peer 101(8098) DEBUG: ims_qos [ims_qos_mod.c:1336]: w_rx_aar_register(): Creating new Rx session for contact <sip:[email protected]:55419;transport=TCP;ob> 101(8098) DEBUG: ims_qos [ims_qos_mod.c:379]: callback_for_cdp_session(): Ignoring event [23] from CDP session 101(8098) DEBUG: ims_qos [ims_qos_mod.c:1412]: w_rx_aar_register(): Calling send aar register101(8098) DEBUG: ims_qos [rx_aar.c:966]: rx_send_aar_register(): Send AAR register 101(8098) DEBUG: ims_qos [rx_avp.c:778]: rx_create_media_subcomponent_avp(): Need to add RTCP FD description - RTCP ports are by default next odd port number up from RTP ports 101(8098) DEBUG: ims_qos [rx_avp.c:793]: rx_create_media_subcomponent_avp(): RTCP A Port [55421] RCTP B Port [55421] 101(8098) DEBUG: ims_qos [rx_avp.c:1174]: rx_create_codec_data_avp(): data.len is calculated 16, sdp-stream has a len of 0 101(8098) DEBUG: ims_qos [rx_avp.c:1197]: rx_create_codec_data_avp(): data.s = "downlink offer " 101(8098) DEBUG: ims_qos [rx_avp.c:1174]: rx_create_codec_data_avp(): data.len is calculated 15, sdp-stream has a len of 0 101(8098) DEBUG: ims_qos [rx_avp.c:1197]: rx_create_codec_data_avp(): data.s = "uplink answer " 101(8098) DEBUG: ims_qos [rx_aar.c:1044]: rx_send_aar_register(): auth_lifetime 7200 101(8098) DEBUG: ims_qos [rx_aar.c:1055]: rx_send_aar_register(): sending AAR to PCRF 101(8098) ERROR: cdp [routing.c:274]: get_routing_peer(): get_routing_peer(): No connected DefaultRoute peer found for app_id 16777236 and vendor id 10415. 101(8098) ERROR: cdp [diameter_comm.c:142]: AAASendMessage(): AAASendMessage(): Can't find a suitable connected peer in the routing table. 101(8098) DEBUG: ims_usrloc_pcscf [usrloc.c:149]: get_aor_hash(): Returning hash: [1793713848] 101(8098) DEBUG: ims_usrloc_pcscf [usrloc.c:140]: get_hash_slot(): Returning hash slot: [184] 101(8098) ERROR: ims_qos [ims_qos_mod.c:1421]: w_rx_aar_register(): Failed to send AAR 101(8098) ERROR: ims_qos [ims_qos_mod.c:1465]: w_rx_aar_register(): Error trying to send AAR I am unable to get whats happening. Thats why i thought of asking how to use the diameter server module. Thanks, Pavithra On Thu, Sep 17, 2020 at 2:25 PM Henning Westerholt <[email protected]<mailto:[email protected]>> wrote: Hello, I am afraid that you need to dig into the log messages and try find out why its produced. Enable debugging to get more information, look to diameter network traces to see if the diameter kamailio module connects to the diameter server etc.. Cheers, Henning -- Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.com<https://gilawa.com/> From: Pavithra Mohanraja <[email protected]<mailto:[email protected]>> Sent: Thursday, September 17, 2020 8:55 AM To: Henning Westerholt <[email protected]<mailto:[email protected]>> Cc: Kamailio (SER) - Users Mailing List <[email protected]<mailto:[email protected]>>; supreeth herle <[email protected]<mailto:[email protected]>>; Abdirahman A. Osman <[email protected]<mailto:[email protected]>> Subject: Re: [SR-Users] Kamailio IMS Diameter Messages Hi Henning, ya sure ..Thanks for the reply .. PCF in 5G doesnot have Application ID. It only supports HTTP rest apis. This is my diameterPeer.xml file <?xml version="1.0" encoding="UTF-8"?> <DiameterPeer FQDN="pcscf.sip.example.com<http://pcscf.sip.example.com>" Realm="sip.example.com<http://sip.example.com>" Vendor_Id="10415" Product_Name="CDiameterPeer" AcceptUnknownPeers="1" DropUnknownOnDisconnect="0" Tc="30" Workers="4" QueueLength="8" TransactionTimeout="5" SessionsHashSize="128" DefaultAuthSessionTimeout="3600" MaxAuthSessionTimeout="3600" > <Peer FQDN="pcf.sip.example.com<http://pcf.sip.example.com>" Realm="sip.example.com<http://sip.example.com>" port="29507"/> <Acceptor port="3871" bind="10.1.68.36"/> <Auth id="16777236" vendor="10415"/> <!-- 3GPP Rx --> <Auth id="16777236" vendor="0"/> <!-- 3GPP Rx --> <DefaultRoute FQDN="pcf.sip.example.com<http://pcf.sip.example.com>" metric="10"/> </DiameterPeer> On Thu, Sep 17, 2020 at 12:22 PM Henning Westerholt <[email protected]<mailto:[email protected]>> wrote: Hello Pavithra, please only use the list address for new questions. 😊 The error looks like that the diameter peer xml cfg is not correct. There are some examples in the kamailio cfg example directory, I think. Cheers, Henning -- Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.com<https://gilawa.com/> From: sr-users <[email protected]<mailto:[email protected]>> On Behalf Of Pavithra Mohanraja Sent: Thursday, September 17, 2020 6:27 AM To: Kamailio (SER) - Users Mailing List <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>; David Villasmil <[email protected]<mailto:[email protected]>>; supreeth herle <[email protected]<mailto:[email protected]>>; Abdirahman A. Osman <[email protected]<mailto:[email protected]>> Subject: [SR-Users] Kamailio IMS Diameter Messages Hi, Is there any possibility of converting diameter messages to http requests in IMS. Since I am working in 5g based network, In order to connect pcscf to pcf, Rx interface has to be established. But PCF is not accepting diameter messages. It is failing with error "No connected DefaultRoute peer found for app_id 16777236 and vendor id 10415" I used IMS Diameter server since it is mentioned as converting diameter messages to http json messages. But even before calling that diameter server, It is failing with App_id issue. How it works? Need to understand, how the diameter messages are working since in 5g , everything is based on http rest apis. Is there any possibility of connecting to it or there is no support in kamailio IMS for 5g. If you have any idea, please let me know. It will be very useful for me. Thanks, Pavithra
_______________________________________________ Kamailio (SER) - Users Mailing List [email protected] https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
