You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
Sure, here is an example of an aor replicated to registrars_1:
{
"jsonrpc": "2.0",
"result": {
"AoR": "example_user@example.com",
"Contacts": [{
"Contact": {
"Address": "sip:example_user@212.2.172.228:43356;rinstance=4dc262b9af47682f;transport=UDP",
"Expires": 98,
"Q": -1,
"Call-ID": "4HEiFls2hkky2XR6hL8Nrg..",
"CSeq": 30,
"User-Agent": "Z 3.15.40006 rv2.8.20",
"Received": "sip:212.2.172.228:43356",
"Path": "<sip:10.7.0.186:5062;lr;received=sip:212.2.172.228:43356>",
"State": "CS_NEW",
"Flags": 2,
"CFlags": 64,
"Socket": "[not set]",
"Methods": -1,
"Ruid": "uloc-2-5a04296d-4ed0-e1",
"Instance": "[not set]",
"Reg-Id": 0,
"Last-Keepalive": 1510227057,
"Last-Modified": 1510227057
}
}]
},
"id": 20184
}
This aor is being serviced by registrar_2 and I can see the server_id being sent in the kdmq message to registrar_1, server_id is clearly set to 2:
KDMQ sip:usrloc@10.6.0.189:5060 SIP/2.0.
Via: SIP/2.0/UDP 10.6.0.190;branch=z9hG4bK5568.b7ee8e11000000000000000000000000.0.
To: <sip:usrloc@10.6.0.189:5060>.
From: <sip:usrloc@10.6.0.190:5060>;tag=21afb82da9b0dd18e43e09ed8956ffc8-9f49.
CSeq: 10 KDMQ.
Call-ID: 1a806e9948d055d0-20402@10.6.0.190.
Content-Length: 514.
User-Agent: kamailio (Registrar 2).
Max-Forwards: 1.
Content-Type: application/json.
.
{"action":1,"aor":"example_user@example.com","ruid":"uloc-2-5a04296d-4ed0-e1","c":"sip:example_user@212.2.172.228:43356;rinstance=4dc262b9af47682f;transport=UDP","received":"sip:212.2.172.228:43356","path":"<sip:10.7.0.186:5062;lr;received=sip:212.2.172.228:43356>","callid":"4HEiFls2hkky2XR6hL8Nrg..","user_agent":"Z 3.15.40006 rv2.8.20","instance":"","expires":1510227474,"cseq":34,"flags":0,"cflags":64,"q":-1,"last_modified":1510227361,"methods":4294967295,"reg_id":0,"server_id":2}
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.