search

herlesupreeth / Kamailio_IMS_Config

Fixed version of Kamailio IMS configuration files for basic calling
45 stars 36 forks source link

Enrolling in a Non-PCRF Scheme #19

Closed Dgeka25594 closed 2 years ago

Dgeka25594 commented 2 years ago

Hi, herlesupreeth! I would be grateful if you can help me, I broke my head solving this problem.

I failed the setup and decided to start over with your configs and ran into this problem:

When trying to register a sip client, pcscf rejects it:

I am setting up Kamailio IMS on VirtualBox:

 3(9360) 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(9360) ERROR: cdp [diameter_comm.c:142]: AAASendMessage(): AAASendMessage(): Can't find a suitable connected peer in the routing table.
 3(9360) ERROR: ims_qos [ims_qos_mod.c:1414]: w_rx_aar_register(): Failed to send AAR
 3(9360) ERROR: ims_qos [ims_qos_mod.c:1458]: w_rx_aar_register(): Error trying to send AAR

Full log:

 0(9357) INFO: <core> [core/udp_server.c:206]: probe_max_receive_buffer(): SO_RCVBUF is finally 360448
 0(9357) ERROR: <script>: event_route[htable:mod-init] 
 1(9358) INFO: rtpengine [rtpengine.c:2750]: rtpp_test(): rtp proxy <udp:localhost:2223> found, support for it enabled
 0(9357) INFO: cdp [cdp_mod.c:240]: cdp_child_init(): CDiameterPeer child starting ...
 0(9357) INFO: cdp [cdp_mod.c:242]: cdp_child_init(): ... CDiameterPeer child started
90(9528) INFO: cdp [worker.c:332]: worker_process(): [1] Worker process started...
92(9530) INFO: cdp [worker.c:332]: worker_process(): [3] Worker process started...
91(9529) INFO: cdp [worker.c:332]: worker_process(): [2] Worker process started...
93(9531) INFO: cdp [receiver.c:454]: receiver_process(): receiver_process(): [] Receiver process doing init on new process...
93(9531) INFO: cdp [receiver.c:459]: receiver_process(): receiver_process(): [] Receiver process starting up...
88(9523) INFO: ctl [io_listener.c:213]: io_listen_loop(): io_listen_loop:  using epoll_lt io watch method (config)
89(9526) INFO: cdp [worker.c:332]: worker_process(): [0] Worker process started...
94(9533) INFO: cdp [receiver.c:454]: receiver_process(): receiver_process(): [pcrf.epc.mnc001.mcc001.3gppnetwork.org] Receiver process doing init on new process...
94(9533) INFO: cdp [receiver.c:186]: add_serviced_peer(): add_serviced_peer(): Adding serviced_peer_t to receiver for peer [pcrf.epc.mnc001.mcc001.3gppnetwork.org]
94(9533) INFO: cdp [receiver.c:459]: receiver_process(): receiver_process(): [pcrf.epc.mnc001.mcc001.3gppnetwork.org] Receiver process starting up...
96(9535) INFO: cdp [timer.c:205]: timer_process(): Timer process starting up...
95(9534) INFO: cdp [acceptor.c:81]: acceptor_process(): Acceptor process starting up...
95(9534) WARNING: cdp [tcp_accept.c:120]: create_socket(): create_socket(): Trying to open/bind/listen on 192.168.56.120 port 3871
95(9534) WARNING: cdp [tcp_accept.c:145]: create_socket(): create_socket(): Successful socket open/bind/listen on 192.168.56.120 port 3871
95(9534) INFO: cdp [acceptor.c:95]: acceptor_process(): Acceptor opened sockets. Entering accept loop ...
100(9545) INFO: jsonrpcs [jsonrpcs_sock.c:443]: jsonrpc_dgram_process(): a new child 0/9545
96(9535) INFO: cdp [peerstatemachine.c:526]: I_Snd_Conn_Req(): I_Snd_Conn_Req(): Peer pcrf.epc.mnc001.mcc001.3gppnetwork.org 
96(9535) INFO: cdp [receiver.c:874]: peer_connect(): peer_connect(): Trying to connect to 192.168.56.106 port 3868
96(9535) INFO: cdp [receiver.c:954]: peer_connect(): peer_connect(): Peer pcrf.epc.mnc001.mcc001.3gppnetwork.org:3868 connected
94(9533) ERROR: cdp [receiver.c:688]: receive_loop(): select_recv(): Bad file descriptor
94(9533) INFO: cdp [receiver.c:222]: disconnect_serviced_peer(): drop_serviced_peer(): [pcrf.epc.mnc001.mcc001.3gppnetwork.org] Disconnecting from peer 
 3(9360) NOTICE: <script>: PCSCF: REGISTER sip:ims.mnc001.mcc001.3gppnetwork.org (sip:711122330@ims.mnc001.mcc001.3gppnetwork.org (192.168.56.1:49570) to sip:711122330@ims.mnc001.mcc001.3gppnetwork.org, c98e5026-d59d-7732-0343-1cd7bf8d4221)
 3(9360) INFO: rr [rr_mod.c:515]: pv_get_route_uri_f(): No route header present.
 3(9360) NOTICE: <script>: PCSCF REGISTER: 
 Destination URI: <null>
 Request URI: sip:ims.mnc001.mcc001.3gppnetwork.org
 3(9360) INFO: rr [rr_mod.c:515]: pv_get_route_uri_f(): No route header present.
 3(9360) NOTICE: <script>: Source IP and Port: (192.168.56.1:49570)
 Route-URI: 
 3(9360) NOTICE: <script>: Received IP and Port: (192.168.56.120:5060)
 3(9360) NOTICE: <script>: Contact header: <sip:711122330@192.168.56.1:49570;transport=udp>;expires=600000;+g.oma.sip-im;language="en,fr";+g.3gpp.smsip;+g.oma.sip-im.large-message;audio;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-application.ims.iari.gsma-vs";+g.3gpp.cs-voice
 3(9360) INFO: ims_registrar_pcscf [sec_agree.c:264]: cscf_get_security(): No security parameters found
 3(9360) INFO: ims_registrar_pcscf [sec_agree.c:296]: cscf_get_security_verify(): No security-verify parameters found
 3(9360) 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(9360) ERROR: cdp [diameter_comm.c:142]: AAASendMessage(): AAASendMessage(): Can't find a suitable connected peer in the routing table.
 3(9360) ERROR: ims_qos [ims_qos_mod.c:1414]: w_rx_aar_register(): Failed to send AAR
 3(9360) ERROR: ims_qos [ims_qos_mod.c:1458]: w_rx_aar_register(): Error trying to send AAR
 3(9360) WARNING: tm [t_lookup.c:1504]: t_unref(): script writer didn't release transaction
^C107(9566) INFO: <core> [main.c:847]: sig_usr(): signal 2 received

I understand this due to the fact that I do not use PCRF, since I am not mobile UE, but I use SIP clients and connect directly to PCSCF. Tell me what I need to fix in order for the circuit to work SIP-client>>IMS>>SIP-client witout EPC. In your config I changed only IP

Dump and config attached kamailio_pcscf.zip pcscf_dump.zip

PCSCF 192.168.56.120 ICSCF SCSCF FHоSS 192.168.56.106

Dump and config attached

herlesupreeth commented 2 years ago

If you are using only SIP client and dont need VoLTE feature then change the following in pcscf.cfg

#!define WITH_RX
#!define WITH_RX_REG
#!define WITH_RX_CALL

TO

##!define WITH_RX
##!define WITH_RX_REG
##!define WITH_RX_CALL
Dgeka25594 commented 2 years ago

Thanks! it helped, registration is successful. But can't make a call. The caller receives a Server error on LIR select next S-CSCF message, but the subscribers and the IMS are on the same subnet and mo is correct. Probably the 408 Request Timeout message somehow contributes to this, but there are no problems with the network. image

Dump from all nodes in attachment (https://github.com/herlesupreeth/Kamailio_IMS_Config/files/7869756/dump_call.zip) [dump_call.zip] Probably because of the value, but I don't understand why it is taken

 1(10921) NOTICE: <script>: PCSCF: INVITE sip:bob@ims.mnc001.mcc001.3gppnetwork.org (sip:711122330@ims.mnc001.mcc001.3gppnetwork.org (192.168.56.1:56447) to sip:bob@ims.mnc001.mcc001.3gppnetwork.org, 65565356-8b86-23f3-9449-f8a940441526)
 1(10921) NOTICE: <script>: PCSCF MO: 
 Destination URI: sip:orig@scscf.ims.mnc001.mcc001.3gppnetwork.org:6060;lr
 Request URI: sip:bob@ims.mnc001.mcc001.3gppnetwork.org
 1(10921) NOTICE: <script>: Source IP and Port: (192.168.56.1:56447)
 Route-URI: sip:192.168.56.120:5060;lr;transport=udp
 1(10921) NOTICE: <script>: Received IP and Port: (192.168.56.120:5060)
 1(10921) NOTICE: <script>: Contact header: <sip:711122330@192.168.56.1:56447;transport=udp>;+g.oma.sip-im;language="en,fr";+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"
 1(10921) INFO: siputils [chargingvector.c:432]: sip_handle_pcv(): Generated PCV header P-Charging-Vector: icid-value=495653C0A83878A92A0000AC01000000; icid-generated-at=192.168.56.120
100(11110) ERROR: <core> [core/tcp_main.c:4635]: tcpconn_main_timeout(): connect 192.168.56.1:61499 failed (timeout) 
100(11110) ERROR: <core> [core/tcp_main.c:4635]: tcpconn_main_timeout(): connect 192.168.56.1:56447 failed (timeout) 
96(11104) NOTICE: <script>: PCSCF MO_reply: 
 Destination URI: <null>
 Request URI: <null>
96(11104) INFO: rr [rr_mod.c:515]: pv_get_route_uri_f(): No route header present.
96(11104) NOTICE: <script>: Source IP and Port: (192.168.56.106:6060)
 Route-URI: 
96(11104) NOTICE: <script>: Received IP and Port: (192.168.56.120:5060)
96(11104) NOTICE: <script>: Contact header: <null>
96(11104) ERROR: ims_ipsec_pcscf [cmd.c:886]: ipsec_forward(): No security parameters found in contact
 3(10923) NOTICE: <script>: PCSCF: INVITE sip:bob@192.168.56.1:5060;alias=192.168.56.1~5060~1 (sip:711122330@ims.mnc001.mcc001.3gppnetwork.org (192.168.56.106:6060) to sip:bob@ims.mnc001.mcc001.3gppnetwork.org, 65565356-8b86-23f3-9449-f8a940441526)
 3(10923) NOTICE: <script>: PCSCF MT: 
 Destination URI: sip:192.168.56.1:5060
 Request URI: sip:bob@192.168.56.1:5060
 3(10923) NOTICE: <script>: Source IP and Port: (192.168.56.106:6060)
 Route-URI: sip:term@pcscf.ims.mnc001.mcc001.3gppnetwork.org;lr
 3(10923) NOTICE: <script>: Received IP and Port: (192.168.56.120:5060)
 3(10923) NOTICE: <script>: Contact header: <sip:711122330@192.168.56.1:56447;transport=udp>;+g.oma.sip-im;language="en,fr";+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"
 3(10923) ERROR: ims_ipsec_pcscf [cmd.c:886]: ipsec_forward(): No security parameters found in contact
 2(10922) NOTICE: <script>: PCSCF: ACK sip:bob@192.168.56.1:5060;alias=192.168.56.1~5060~1 (sip:711122330@ims.mnc001.mcc001.3gppnetwork.org (192.168.56.106:6060) to sip:bob@ims.mnc001.mcc001.3gppnetwork.org, 65565356-8b86-23f3-9449-f8a940441526)
 2(10922) WARNING: tm [t_lookup.c:1504]: t_unref(): script writer didn't release transaction
97(11105) NOTICE: <script>: PCSCF MO_reply: 
 Destination URI: <null>
 Request URI: <null>
97(11105) INFO: rr [rr_mod.c:515]: pv_get_route_uri_f(): No route header present.
97(11105) NOTICE: <script>: Source IP and Port: (192.168.56.106:6060)
 Route-URI: 
97(11105) NOTICE: <script>: Received IP and Port: (192.168.56.120:5060)
97(11105) NOTICE: <script>: Contact header: <null>
97(11105) ERROR: ims_ipsec_pcscf [cmd.c:886]: ipsec_forward(): No security parameters found in contact
 4(10924) NOTICE: <script>: PCSCF: ACK sip:bob@ims.mnc001.mcc001.3gppnetwork.org (sip:711122330@ims.mnc001.mcc001.3gppnetwork.org (192.168.56.1:56447) to sip:bob@ims.mnc001.mcc001.3gppnetwork.org, 65565356-8b86-23f3-9449-f8a940441526)
 4(10924) WARNING: tm [t_lookup.c:1504]: t_unref(): script writer didn't release transaction
100(11110) ERROR: <core> [core/tcp_main.c:4635]: tcpconn_main_timeout(): connect 192.168.56.1:5060 failed (timeout)
Dgeka25594 commented 2 years ago

Do I need to somehow configure routes if both IMS and clients are on the same network? I do not see another reason for the 408 (Request Timeout) message yet, since both clients are registered.

herlesupreeth commented 2 years ago

If want to have both IMS and VoIP client on the same network then you would need two instances of P-CSCF with one Rx enabled and anther without Rx

Dgeka25594 commented 2 years ago

I wanted to make calls from sip-clients supporting IMS, like in your picture. I can't make calls via VoLTE yet. image

Dgeka25594 commented 2 years ago

I found suspicious messages in the SCSCF log during the call, but I still can't figure out why the dialog is being destroyed

 1(5585) DEBUG: ims_dialog [dlg_handlers.c:1176]: dlg_onreply(): ONREPLY CALL_BACK from TM received and type is [2] = [TMCB_RESPONSE_IN]
 1(5585) DEBUG: ims_dialog [dlg_hash.c:887]: lookup_dlg(): ref dlg 0x7f00dab0d400 with 1 -> 3
 1(5585) DEBUG: ims_dialog [dlg_hash.c:889]: lookup_dlg(): dialog id=7345 found on entry 1533
 1(5585) DEBUG: ims_dialog [dlg_handlers.c:1193]: dlg_onreply(): DLG dialogid is entry:id [1533:7345]
 1(5585) DEBUG: ims_dialog [dlg_profile.c:419]: set_current_dialog(): setting current dialog [1533:7345]
 1(5585) DEBUG: ims_dialog [dlg_hash.c:1066]: unref_dlg(): unref dlg 0x7f00dab0d400 with 1 -> 2
 3(5587) DEBUG: ims_dialog [dlg_handlers.c:1207]: dlg_onreply(): Ignoring request out as it's not a CANCEL
 3(5587) DEBUG: ims_dialog [dlg_hash.c:1066]: unref_dlg(): unref dlg 0x7f00dab0d400 with 1 -> 1
 2(5586) DEBUG: ims_dialog [dlg_handlers.c:1176]: dlg_onreply(): ONREPLY CALL_BACK from TM received and type is [2] = [TMCB_RESPONSE_IN]
 2(5586) DEBUG: ims_dialog [dlg_hash.c:887]: lookup_dlg(): ref dlg 0x7f00dab0d400 with 1 -> 2
 2(5586) DEBUG: ims_dialog [dlg_hash.c:889]: lookup_dlg(): dialog id=7345 found on entry 1533
 2(5586) DEBUG: ims_dialog [dlg_handlers.c:1193]: dlg_onreply(): DLG dialogid is entry:id [1533:7345]
 2(5586) DEBUG: ims_dialog [dlg_profile.c:419]: set_current_dialog(): setting current dialog [1533:7345]
 2(5586) DEBUG: ims_dialog [dlg_hash.c:1066]: unref_dlg(): unref dlg 0x7f00dab0d400 with 1 -> 1
 4(5588) DEBUG: ims_dialog [dlg_handlers.c:1176]: dlg_onreply(): ONREPLY CALL_BACK from TM received and type is [2] = [TMCB_RESPONSE_IN]
 4(5588) DEBUG: ims_dialog [dlg_hash.c:887]: lookup_dlg(): ref dlg 0x7f00dab0d400 with 1 -> 2
 4(5588) DEBUG: ims_dialog [dlg_hash.c:889]: lookup_dlg(): dialog id=7345 found on entry 1533
 4(5588) DEBUG: ims_dialog [dlg_handlers.c:1193]: dlg_onreply(): DLG dialogid is entry:id [1533:7345]
 4(5588) DEBUG: ims_dialog [dlg_profile.c:419]: set_current_dialog(): setting current dialog [1533:7345]
 4(5588) DEBUG: ims_dialog [dlg_hash.c:1066]: unref_dlg(): unref dlg 0x7f00dab0d400 with 1 -> 1
 4(5588) DEBUG: ims_dialog [dlg_handlers.c:1176]: dlg_onreply(): ONREPLY CALL_BACK from TM received and type is [128] = [TMCB_ON_FAILURE]
 4(5588) DEBUG: ims_dialog [dlg_hash.c:887]: lookup_dlg(): ref dlg 0x7f00dab0d400 with 1 -> 2
 4(5588) DEBUG: ims_dialog [dlg_hash.c:889]: lookup_dlg(): dialog id=7345 found on entry 1533
 4(5588) DEBUG: ims_dialog [dlg_handlers.c:1193]: dlg_onreply(): DLG dialogid is entry:id [1533:7345]
 4(5588) DEBUG: ims_dialog [dlg_profile.c:419]: set_current_dialog(): setting current dialog [1533:7345]
 4(5588) DEBUG: ims_dialog [dlg_hash.c:1066]: unref_dlg(): unref dlg 0x7f00dab0d400 with 1 -> 1
 4(5588) DEBUG: ims_dialog [dlg_handlers.c:1176]: dlg_onreply(): ONREPLY CALL_BACK from TM received and type is [1048576] = [TMCB_RESPONSE_READY]
 4(5588) DEBUG: ims_dialog [dlg_hash.c:887]: lookup_dlg(): ref dlg 0x7f00dab0d400 with 1 -> 2
 4(5588) DEBUG: ims_dialog [dlg_hash.c:889]: lookup_dlg(): dialog id=7345 found on entry 1533
 4(5588) DEBUG: ims_dialog [dlg_handlers.c:1193]: dlg_onreply(): DLG dialogid is entry:id [1533:7345]
 4(5588) DEBUG: ims_dialog [dlg_handlers.c:1235]: dlg_onreply(): Extracting to-tag from reply 4(5588) DEBUG: ims_dialog [dlg_handlers.c:1255]: dlg_onreply(): Got to-tag from response: 0c8226fe9a0a0933b505664e4b17b14c-d79845eb 
 4(5588) DEBUG: ims_dialog [dlg_handlers.c:1275]: dlg_onreply(): Calling next_state_dlg and event is 4 = DLG_EVENT_RPL3xx
 4(5588) DEBUG: ims_dialog [dlg_hash.c:1293]: next_state_dlg(): dialog 0x7f00dab0d400 changed from state 1 to state 6, due event 4
 4(5588) DEBUG: ims_dialog [dlg_handlers.c:1279]: dlg_onreply(): Checking if there is an existing dialog_out entry with same to-tag 4(5588) DEBUG: ims_dialog [dlg_handlers.c:1300]: dlg_onreply(): Extracting to-tag from reply 4(5588) DEBUG: ims_dialog [dlg_handlers.c:1331]: dlg_onreply(): Got to-tag from response: 0c8226fe9a0a0933b505664e4b17b14c-d79845eb 
 4(5588) DEBUG: ims_dialog [dlg_handlers.c:1338]: dlg_onreply(): Scanning dlg_entry_out list for dlg_out 4(5588) DEBUG: ims_dialog [dlg_handlers.c:1409]: dlg_onreply(): new state is 6 and old state is 1
 4(5588) DEBUG: ims_dialog [dlg_handlers.c:1489]: dlg_onreply(): dialog 0x7f00dab0d400 failed (negative reply)
 4(5588) DEBUG: ims_dialog [dlg_cb.c:277]: run_dlg_callbacks(): dialog=0x7f00dab0d400, type=4
 4(5588) DEBUG: ims_usrloc_scscf [contact_dlg_handlers.c:129]: contact_dlg_handler(): no dlg out... ignoring!!! for type [4] - usually happens on failure response in dialog
 4(5588) DEBUG: ims_dialog [dlg_hash.c:1066]: unref_dlg(): unref dlg 0x7f00dab0d400 with 1 -> 1
 4(5588) DEBUG: ims_dialog [dlg_hash.c:1066]: unref_dlg(): unref dlg 0x7f00dab0d400 with 1 -> 0
 4(5588) DEBUG: ims_dialog [dlg_hash.c:1066]: unref_dlg(): ref <=0 for dialog 0x7f00dab0d400
 4(5588) DEBUG: ims_dialog [dlg_hash.c:196]: destroy_dlg(): destroying dialog 0x7f00dab0d400
 4(5588) DEBUG: ims_dialog [dlg_hash.c:207]: destroy_dlg(): removed timer for dlg 0x7f00dab0d400 [1533:7345] with clid 'abc61176-0224-ad9a-ceaa-5272aa8b5340' and tags '17454264' 
 4(5588) DEBUG: ims_dialog [dlg_hash.c:218]: destroy_dlg(): About to run dlg callback for destroy
 4(5588) DEBUG: ims_dialog [dlg_cb.c:277]: run_dlg_callbacks(): dialog=0x7f00dab0d400, type=8192
 4(5588) DEBUG: ims_usrloc_scscf [contact_dlg_handlers.c:129]: contact_dlg_handler(): no dlg out... ignoring!!! for type [8192] - usually happens on failure response in dialog
 4(5588) DEBUG: ims_dialog [dlg_hash.c:220]: destroy_dlg(): DONE: About to run dlg callback for destroy
 4(5588) DEBUG: ims_dialog [dlg_hash.c:156]: destroy_entry_out(): Destroy dialog entry out
 3(5587) DEBUG: ims_dialog [dlg_handlers.c:1176]: dlg_onreply(): ONREPLY CALL_BACK from TM received and type is [2] = [TMCB_RESPONSE_IN]
 3(5587) DEBUG: ims_dialog [dlg_hash.c:887]: lookup_dlg(): ref dlg 0x7f00dab06090 with 1 -> 2
 3(5587) DEBUG: ims_dialog [dlg_hash.c:889]: lookup_dlg(): dialog id=7344 found on entry 1533
 3(5587) DEBUG: ims_dialog [dlg_handlers.c:1193]: dlg_onreply(): DLG dialogid is entry:id [1533:7344]
 3(5587) DEBUG: ims_dialog [dlg_profile.c:419]: set_current_dialog(): setting current dialog [1533:7344]
 3(5587) DEBUG: ims_dialog [dlg_hash.c:1066]: unref_dlg(): unref dlg 0x7f00dab06090 with 1 -> 1
 1(5585) NOTICE: <script>: SCSCF: ACK sip:711122331@ims.mnc001.mcc001.3gppnetwork.org (sip:711122330@ims.mnc001.mcc001.3gppnetwork.org (192.168.56.106:4060) to sip:711122331@ims.mnc001.mcc001.3gppnetwork.org, abc61176-0224-ad9a-ceaa-5272aa8b5340)
Dgeka25594 commented 2 years ago

Although I seem to have almost figured it out, PCSCF does not send an INVITE to my callee. It remains to understand why

100(2039) ERROR: <core> [core/tcp_main.c:4454]: handle_tcpconn_ev(): connect 192.168.56.107:61571 failed

Dgeka25594 commented 2 years ago

If want to have both IMS and VoIP client on the same network then you would need two instances of P-CSCF with one Rx enabled and anther without Rx

Or I misunderstood you ... did you mean that I need a second PCSCF, regardless of whether I use VoLTE or not, if I make calls within the same network from sip clients with IMS architecture?

herlesupreeth commented 2 years ago

Or I misunderstood you ... did you mean that I need a second PCSCF, regardless of whether I use VoLTE or not, if I make calls within the same network from sip clients with IMS architecture?

No, if you are purely using VoIP clients then you dont need second PCSCF

herlesupreeth commented 2 years ago

please repost the pcap taken for calling scenario.

Dgeka25594 commented 2 years ago

Happened! I apologize for the time spent, the problem was apparently in the client that I used. There were no problems with the payment through PhonerLite! http://phonerlite.de/download_en.htm @herlesupreeth , thanks again for your help. Tell me, what sip-clients did you use when making calls via IMS?

Dgeka25594 commented 2 years ago

Sorry for one more question. I changed the scheme, now the clients are on a different network x: Bob (ip 10.20.29.211)>>IMS (PCSCF 10.21.4.226(customer connection point),10.10.0.1 (internal IP for communication with I,S-CSCF) and I,S-CSCF, HSS 10.10.0.2>>Alice (IP 10.20.29.180) Do I understand correctly that I need to enable the listen=udp:10.10.0.1:5060 advertise 10.21.4.226:5060 setting on PCSCF?

Dgeka25594 commented 2 years ago

Everything was decided by the correct prerouting rules