callId is same in b2bua exampl

[FarhanAhmad]

From my understanding and from the rfc, the call ID should be different of both A and B leg of 1 sip call.. I've taken the logs generated by running the sipb2bua example, and the call id is same for both. Isn't this an issue?

Invite packet from A to server:
INVITE sip:[email protected] SIP/2.0
Via: SIP/2.0/TCP 172.30.128.75:41071;branch=z9hG4bK-1003163100;rport=41071;received=172.30.128.75
From: sip:[email protected]:5060;tag=536107915
To: sip:[email protected]
Contact: sip:[email protected]:41071;transport=tcp;+g.oma.sip-im;language="en,fr";+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"
Call-ID: 3a8f3345-9fdb-2140-4221-ddda22de9545
CSeq: 443837939 INVITE
Content-Type: application/sdp
Max-Forwards: 70
Accept-Contact: *;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"
P-Preferred-Service: urn:urn-7:3gpp-service.ims.icsi.mmtel
Allow: INVITE,ACK,CANCEL,BYE,MESSAGE,OPTIONS,NOTIFY,PRACK,UPDATE,REFER
Privacy: none
P-Access-Network-Info: ADSL; utran-cell-id-3gpp=00000000
User-Agent: IM-client/OMA1.0 android-ngn-stack/v2.586.1328 (doubango r1328 - Nexus 6P)
P-Preferred-Identity: sip:[email protected]:5060
Supported: 100rel
Content-Length: 507
....sdp content....

Invite Packet from server to B leg:
INVITE sip:[email protected]:46825 SIP/2.0
CSeq: 443837939 INVITE
Content-Type: application/sdp
Accept-Contact: *;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-service.ims.icsi.mmtel"
P-Preferred-Service: urn:urn-7:3gpp-service.ims.icsi.mmtel
Allow: INVITE,ACK,CANCEL,BYE,MESSAGE,OPTIONS,NOTIFY,PRACK,UPDATE,REFER
Privacy: none
P-Access-Network-Info: ADSL; utran-cell-id-3gpp=00000000
User-Agent: IM-client/OMA1.0 android-ngn-stack/v2.586.1328 (doubango r1328 - Nexus 6P)
P-Preferred-Identity: sip:[email protected]:5060
Supported: 100rel
Max-Forwards: 70
Call-ID: 3a8f3345-9fdb-2140-4221-ddda22de9545
From: sip:[email protected]:5060;tag=64b45f34
To: sip:[email protected]
Via: SIP/2.0/TCP 172.30.128.75:41071;branch=z9hG4bK-1003163100;rport=41071;received=172.30.128.75
Contact: sip:[email protected]:41071;transport=tcp
Content-Length: 507
...sdp content....

[yulianoifa-mobius]

Hi
Its not an issue. More then that in Invite handling ( when creating the second dialog ) you may modify the code for dialog creation and pass useSameCallId=false instead of true.
BR