Thanks Olivier & Peter for clarifying this for me.
Cheers,
Stephen
________________________________
From: Boulkroune, Olivier (Non-HP:Atos Origin) [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 28, 2007 1:51 AM
To: Stephen Cattaneo; [email protected]
Subject: RE: [Sipp-users] SIPp discarding msgs meant for itself.
Hello Stephen,
The call is discarded because the Call-ID contained in the INVITE received by B
does not match the Call-ID contained in the REGISTER sent by B. Therefore, B
does not recognize the incoming INVITE as being part of an existing sipp dialog.
The workaround for this use case is to use two sipp instances to emulate B: one
for registering and the other for waiting incoming calls from A.
Regards,
Olivier Boulkroune
________________________________
De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la part de Stephen Cattaneo
Envoyé : mercredi 27 juin 2007 21:27
À : [email protected]
Objet : [Sipp-users] SIPp discarding msgs meant for itself.
Greetings SIPp Listers,
I am trying to get a simple A calls B call to work with SIP server "Vocal."
Both endpoints are instances of SIPp.
The call flow is as follows:
B registers and waits for an invite from A
A registers and sends an invite to B
At this point Vocal forwards the invite from A to B and the instance of SIPp
representing B discards the incoming invite.
>From the error log:
------------------------------
2007-06-27 11:11:32:537 1182967892.537273: Discarding message which
can't be mapped to a k
n SIPp call:
INVITE sip:[EMAIL PROTECTED]:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.15.253:5060;branch=616456592b3ce05d63ba0fa255c4b2c6.4
Via: SIP/2.0/UDP 192.168.15.253:5060;branch=e8d40847badc1cf31d72dfbd9da8c4de.2
Via: SIP/2.0/UDP 192.168.15.220:6754
To: <sip:[EMAIL PROTECTED]>
From: <sip:[EMAIL PROTECTED]>;tag=1
Call-ID: [EMAIL PROTECTED]
CSeq: 1 INVITE
Max-Forwards: 69
Expires: 300
Record-Route: <sip:[EMAIL PROTECTED]:5060;maddr=192.168.15.253>,<sip:[EMAIL
PROTECTED]:5060;maddr=192.168.15.253>
Contact: <sip:[EMAIL PROTECTED]:6754;transport=UDP>
Allow: ACK,BYE,CANCEL,INVITE,NOTIFY,OPTIONS,REFER,REGISTER
Content-Type: application/sdp
Content-Length: 174
v=0
o=5107471050 19856 46548 IN IP4 192.168.15.220
s=SIPp Call
c=IN IP4 192.168.15.220
t=0 0
m=audio 6000 RTP/AVP 0 18
a=rtpmap:0 PCMU/8000/1
a=rtpmap:18 G729/8000/1
------------------------
The question: Why does SIPp disregard a message meant for itself?
I would assume that a SIP message on the port that the instance of SIPp is tied
to would be received and not discarded.
Thanks,
Steve
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users
