On Thursday 15 July 2010 16:14:17 Stefan Sayer wrote:
> Hi,
>
> are you sure the local tag matches the one from the INVITE?
>
> this ERROR means that the session for the local tag could not be found.
>
> Stefan

Let's check ...

INV from SEMS to Proxy:

INVITE sip:[email protected] SIP/2.0
Via: SIP/2.0/UDP 91.XXX.XXX.XXX;branch=z9hG4bKnr0uEaZp;rport
From: 
<sip:[email protected]>;tag=46C0B764-4C3F2F20000DD85F-B735BB90
To: <sip:[email protected]>
CSeq: 11 INVITE
Call-ID: [email protected]
Contact: <sip:[email protected]:5060>
Route: <sip:91.XXX.XXX.XXB;lr>
Proxy-Authorization: Digest username="test", realm="dimension-virtual.com", 
nonce="4c3f304c2a86f51d7c25f38f36079f43593d9adc", 
uri="sip:[email protected]", 
response="9606b5c346e6556eb538483b5ccdbe98", algorithm=MD5
User-Agent: Sip Express Media Server (1.3.0-dev-38f51bc (x86/linux))
Max-Forwards: 70
Content-Type: application/sdp
Content-Length: 243

TRY from Proxy to SEMS:

SIP/2.0 100 Trying
Via: SIP/2.0/UDP 
91.XXX.XXX.XXX;branch=z9hG4bKnr0uEaZp;rport=5060;received=91.XXX.XXX.XXX
From: 
<sip:[email protected]>;tag=46C0B764-4C3F2F20000DD85F-B735BB90
To: <sip:[email protected]>
CSeq: 11 INVITE
Call-ID: [email protected]
Server: Kamailio (1.5.1-notls (i386/linux))
Content-Length: 0

INV from Proxy to MG:

INVITE sip:[email protected]:5060 SIP/2.0
Record-Route: 
<sip:91.XXX.XXX.XXB;lr=on;ftag=46C0B764-4C3F2F20000DD85F-B735BB90>
Via: SIP/2.0/UDP 91.XXX.XXX.XXB;branch=z9hG4bK2c03.fde582a4.0
Via: SIP/2.0/UDP 
91.XXX.XXX.XXX;received=91.XXX.XXX.XXX;branch=z9hG4bKnr0uEaZp;rport=5060
From: 
<sip:[email protected]>;tag=46C0B764-4C3F2F20000DD85F-B735BB90
To: <sip:[email protected]>
CSeq: 11 INVITE
Call-ID: [email protected]
Contact: <sip:[email protected]:5060>
User-Agent: Sip Express Media Server (1.3.0-dev-38f51bc (x86/linux))
Max-Forwards: 69
Content-Type: application/sdp
Content-Length: 243

TRY from MG to Proxy:

SIP/2.0 100 Trying
Via: SIP/2.0/UDP 
91.XXX.XXX.XXB;branch=z9hG4bK2c03.fde582a4.0;received=91.XXX.XXX.XXB
Via: SIP/2.0/UDP 
91.XXX.XXX.XXX;received=91.XXX.XXX.XXX;branch=z9hG4bKnr0uEaZp;rport=5060
From: 
<sip:[email protected]>;tag=46C0B764-4C3F2F20000DD85F-B735BB90
To: <sip:[email protected]>
Call-ID: [email protected]
CSeq: 11 INVITE
User-Agent: CallWeaver
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Max-Forwards: 70
Contact: <sip:[email protected]>
Content-Length: 0

SESSPROG from MG to Proxy:

SIP/2.0 183 Session Progress
Via: SIP/2.0/UDP 
91.XXX.XXX.XXB;branch=z9hG4bK2c03.fde582a4.0;received=91.XXX.XXX.XXB
Via: SIP/2.0/UDP 
91.XXX.XXX.XXX;received=91.XXX.XXX.XXX;branch=z9hG4bKnr0uEaZp;rport=5060
From: 
<sip:[email protected]>;tag=46C0B764-4C3F2F20000DD85F-B735BB90
To: <sip:[email protected]>;tag=as3d690895
Call-ID: [email protected]
CSeq: 11 INVITE
User-Agent: CallWeaver
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Max-Forwards: 70
Contact: <sip:[email protected]>
Content-Type: application/sdp
Content-Length: 282

SESSPROG from Proxy to SEMS:

SIP/2.0 183 Session Progress
Via: SIP/2.0/UDP 
91.XXX.XXX.XXX;received=91.XXX.XXX.XXX;branch=z9hG4bKnr0uEaZp;rport=5060
From: 
<sip:[email protected]>;tag=46C0B764-4C3F2F20000DD85F-B735BB90
To: <sip:[email protected]>;tag=as3d690895
Call-ID: [email protected]
CSeq: 11 INVITE
User-Agent: CallWeaver
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Max-Forwards: 70
Contact: <sip:[email protected]>
Content-Type: application/sdp
Content-Length: 282

200 Ok from MG to Proxy:

SIP/2.0 183 Session Progress
Via: SIP/2.0/UDP 
91.XXX.XXX.XXB;branch=z9hG4bK2c03.fde582a4.0;received=91.XXX.XXX.XXB
Via: SIP/2.0/UDP 
91.XXX.XXX.XXX;received=91.XXX.XXX.XXX;branch=z9hG4bKnr0uEaZp;rport=5060
From: 
<sip:[email protected]>;tag=46C0B764-4C3F2F20000DD85F-B735BB90
To: <sip:[email protected]>;tag=as3d690895
Call-ID: [email protected]
CSeq: 11 INVITE
User-Agent: CallWeaver
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Max-Forwards: 70
Contact: <sip:[email protected]>
Content-Type: application/sdp
Content-Length: 282

200 Ok from Proxy to SEMS:

SIP/2.0 200 OK
Via: SIP/2.0/UDP 
91.XXX.XXX.XXX;received=91.XXX.XXX.XXX;branch=z9hG4bKnr0uEaZp;rport=5060
Record-Route: 
<sip:91.XXX.XXX.XXB;lr=on;ftag=46C0B764-4C3F2F20000DD85F-B735BB90>
From: 
<sip:[email protected]>;tag=46C0B764-4C3F2F20000DD85F-B735BB90
To: <sip:[email protected]>;tag=as3d690895
Call-ID: [email protected]
CSeq: 11 INVITE
User-Agent: CallWeaver
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Max-Forwards: 70
Contact: <sip:[email protected]>
Content-Type: application/sdp
Content-Length: 282

And that's all .. from this point on ... anything happens ... no ACK from 
SEMS, so MG BYE the call 5s after, because of 200 retransmisions without ACK.
As far as I can check .. Tag's are ok ...

Any clue ? ...
-- 
Raúl Alexis Betancor Santana
Dimensión Virtual
_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems

Reply via email to