Description

I have an instance of Kamailio running with topos module enabled as described bellow:

(Core network) <---> (Kamailio running on 192.168.70.106:5061) <--> (Provider network)

Here is the scenario:

  1. An INVITE comming from Core network through Kamailio to the Provider network and the call is established correctly (with 200 OK and ACK correctly routed).
  2. The call is put on hold by the callee. A RE-INVITE comming from Provider network through Kamailio to the Core network. This REINVITE is routed correctly.
  3. The Core network sent 200 OK reply to the RE-INVITE. The 200 OK message reached the Kamailio and was dropped there. (It SHOULD go back to the Provider network).

Log Messages

When Kamailio received this 200 OK, I see this log message:

ERROR: topos [tps_storage.c:1299]: tps_db_update_dialog(): no valid dlg uuid (0: - 0:)

SIP Traffic

Here is the REINVITE message arriving from our provider:

INVITE sip:btpsh-5acddf40-d74-5@192.168.70.106:5061 SIP/2.0
Call-ID: 79acbb714c21354c
Contact: sip:80.10.231.10:5060;transport=udp
Content-Type: application/sdp
CSeq: 1 INVITE
From: sip:xxxx@xxxx;user=phone;tag=SDt2dkc98-04020267673121
Max-Forwards: 63
Record-Route: sip:192.168.70.126:5060;user=i0o0S000000ad;lr;Cpkt=XWJOA;C=xxxx,sip:192.168.70.126:5070;user=00000214;lr;Cpkt=YJJEE;C=xxx
To: sip:+yyyy@xxxx;user=phone;tag=1713351228
Via: SIP/2.0/UDP 192.168.70.126:5060;branch=z9hG4bK-XWJO-000227ab-7eda6242,SIP/2.0/UDP 192.168.70.126:5070;received=192.168.70.126;rport=5070;branch=z9hG4bK-YJJE-000a057c-0bf8ef7c,SIP/2.0/UDP 193.200.4.20:5060;emission,SIP/2.0/UDP 80.10.231.10:5060;received=80.10.231.10;rport=5060;branch=z9hG4bK5g8vgn00cobc0atd6hf0sb0000g00.1
Accept: application/sdp
Allow: INVITE,ACK,CANCEL,BYE,OPTIONS,PRACK
Content-Length: 236

Here is the REINVITE comming out of Kamailio into our core side:

INVITE sip:192.168.40.106:5090;did=d03.e3be0354 SIP/2.0
Via: SIP/2.0/UDP 192.168.70.106:5061;branch=z9hG4bK443f.2ec12863719a69f1e3851178d9cb21d0.0
Call-ID: 79acbb714c21354c
Content-Type: application/sdp
CSeq: 1 INVITE
From: sip:+xxx@xxxx;tag=SDt2dkc98-04020267673121
Max-Forwards: 62
To: sip:xxx@xxxx;tag=1713351228
Accept: application/sdp
Allow: INVITE,ACK,CANCEL,BYE,OPTIONS,PRACK
Content-Length: 236
Route: xxx
Contact: sip:atpsh-5acddf40-d75-5@192.168.70.106:5061

Here is the 200 OK for this REINVITE message comming from the Core network (This message arrived to Kamailio but is never sent to our provider).

SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.70.106:5061;branch=z9hG4bK443f.2ec12863719a69f1e3851178d9cb21d0.0
From: sip:+xxx@xxxx;tag=SDt2dkc98-04020267673121
To: sip:xxx@xxxx;tag=1713351228
Call-ID: 79acbb714c21354c
CSeq: 1 INVITE
Contact: sip:192.168.40.106:5090;did=d03.e3be0354
Allow: ACK, INVITE, BYE, CANCEL, REGISTER, REFER, OPTIONS, INFO
Content-Type: application/sdp
Content-Length: 197

Additional Information

kamailio 5.1.2

Centos Linux 3.10.0-514.26.1.el7.x86_64

PostgreSQL 9.4

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.