search for: 9fa1

...ame. Only with one difference. Now you would think now i have 2 DC's running in you see this. But i have 3 DC's running. One is missing and i bet its the samba 4.13.2. (recently installed). And the 2 other servers originated from a samba 4.1.x Unknown invocation ID 00a544f5-964f-4348-9fa1-ae2b3ee4e08a Unknown invocation ID 7e4659b4-c78f-45a3-be02-9881e17b2cc8 Unknown invocation ID 00a544f5-964f-4348-9fa1-ae2b3ee4e08a Unknown invocation ID 7e4659b4-c78f-45a3-be02-9881e17b2cc8 Unknown invocation ID 00a544f5-964f-4348-9fa1-ae2b3ee4e08a Unknown invocation ID 7e4659b4-c78f-45a3-be02-9881...

Dan Cropp wrote: > I had my screenshots flipped. Is there a way to make sure the Contact field is NOT included in the ACK response to the OK (for the Answer)? > > PJSIP is including the Contact for the ACK response to the OK. > Contact:<sip:1234 at xxx.xxx.xx.xxx:5060> > There is no configuration option to configure this behavior. What is the full SIP signaling? -- Joshua

On 17/11/2020 11:54, mj via samba wrote: > Hi, > > Checking a bit more today, as the two changes on DC4 have *still* not > propagated? to DC2/DC3, I discovered the > ?samba-tool drs uptodateness > command. > > I gives the following output, not sure what "unknown invocation ID" > means. I hope someone here is able to explain..? > > It's output: >

...<--- Transmitting SIP request (1004 bytes) to UDP:64.2.142.93:5060 ---> INVITE sip:8005555555 at 64.2.142.93 SIP/2.0 Via: SIP/2.0/UDP XXX.XXX.XXX.XXX:5060;rport;branch=z9hG4bKPj61911226-4812-44da-b682-7ec02e8c821a From: "Dan" <sip:291 at XXX.XXX.XXX.XXX>;tag=781b4b63-0df9-47ad-9fa1-52a8729359c8 To: <sip:8005555555 at 64.2.142.93> Contact: <sip:15062fef-986e-4fcf-a93e-06b28da02fff at XXX.XXX.XXX.XXX:5060> Call-ID: 309ec892-56a8-46d2-95ba-a6b1d65d0c43 CSeq: 23191 INVITE Allow: OPTIONS, SUBSCRIBE, NOTIFY, PUBLISH, INVITE, ACK, BYE, CANCEL, UPDATE, PRACK, REFER, REGIS...