Re: [OpenSIPStack] Problem with OnOutgoingCallConnected

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

Hi Tom,

Hmmm. Can you check if you the latest versions of SoftphoneInterface.* 
and Softphone.*?

This does not happen in my setup. My From headers are correct.

Here are my logs:

SEND: enc=0 531 Bytes to 70.42.73.140:5060:UDP (REGISTER 
sip:70.42.73.140 SIP/2.0) Interface Address=
REGISTER sip:70.42.73.140 SIP/2.0
From: 300 <sip:300@70.42.73.140>;tag=24b4836f04f9181094d7a2088e6bd734
To: sip:300@70.42.73.140
Via: SIP/2.0/UDP 
192.168.0.107:5060;iid=1769;branch=z9hG4bK24b4836f04f9181094d8a2088e6bd734;uas-addr=70.42.73.140;rport
CSeq: 1 REGISTER
Call-ID: 24b4836f-04f9-1810-8824-a2088e6bd734
Contact: "300" <sip:300@192.168.0.107:5060;transport=udp>
User-Agent: OpenSIPStack-1.1.6-166
Expires: 3600
Max-Forwards: 10
Allow: INVITE, BYE, ACK, REFER, MESSAGE, INFO, NOTIFY, OPTIONS
Content-Length: 0

----------------5:46:55.280----------------
RCV: enc=0 537 Bytes from RCVADDR: 70.42.73.140:RCVPORT: 5060:UDP 
(SIP/2.0 401 Unauthorized)
SIP/2.0 401 Unauthorized
From: 300 <sip:300@70.42.73.140>;tag=24b4836f04f9181094d7a2088e6bd734
To: sip:300@70.42.73.140
Via: SIP/2.0/UDP 
192.168.0.107:5060;iid=3329;branch=z9hG4bK24b4836f04f9181094d8a2088e6bd734;uas-addr=70.42.73.140;rport=5060;received=64.243.115.20
CSeq: 1 REGISTER
Call-ID: 24b4836f-04f9-1810-8824-a2088e6bd734
Server: OpenSIPStack-1.1.6-132
WWW-Authenticate: Digest realm="70.42.73.140", 
nonce="0e73d21831c3e5cab945b3686a6f8fb3", 
opaque="c307ecf61b2e21296250e3a528cdf064", algorithm=MD5
Content-Length: 0

----------------5:46:55.341----------------
SEND: enc=0 717 Bytes to 70.42.73.140:5060:UDP (REGISTER 
sip:70.42.73.140 SIP/2.0) Interface Address=
REGISTER sip:70.42.73.140 SIP/2.0
From: 300 <sip:300@70.42.73.140>;tag=48f7836f04f9181094d8a2088e6bd734
To: sip:300@70.42.73.140
Via: SIP/2.0/UDP 
192.168.0.107:5060;iid=1769;branch=z9hG4bK48f7836f04f9181094d9a2088e6bd734;uas-addr=70.42.73.140;rport
CSeq: 2 REGISTER
Call-ID: 24b4836f-04f9-1810-8824-a2088e6bd734
Contact: "300" <sip:300@192.168.0.107:5060;transport=udp>
User-Agent: OpenSIPStack-1.1.6-166
Expires: 3600
Max-Forwards: 10
Authorization: Digest username="300", realm="70.42.73.140", 
nonce="0e73d21831c3e5cab945b3686a6f8fb3", uri="sip:70.42.73.140", 
response="b85374c0f0b2adcdc6c983c70ff61dd4", algorithm=MD5
Allow: INVITE, BYE, ACK, REFER, MESSAGE, INFO, NOTIFY, OPTIONS
Content-Length: 0

----------------5:46:55.427----------------
RCV: enc=0 454 Bytes from RCVADDR: 70.42.73.140:RCVPORT: 5060:UDP 
(SIP/2.0 200 OK)
SIP/2.0 200 OK
From: 300 <sip:300@70.42.73.140>;tag=48f7836f04f9181094d8a2088e6bd734
To: sip:300@70.42.73.140
Via: SIP/2.0/UDP 
192.168.0.107:5060;iid=3329;branch=z9hG4bK48f7836f04f9181094d9a2088e6bd734;uas-addr=70.42.73.140;rport=5060;received=64.243.115.20
CSeq: 2 REGISTER
Call-ID: 24b4836f-04f9-1810-8824-a2088e6bd734
Contact: "300" <sip:300@192.168.0.107:5060;transport=udp>
Server: OpenSIPStack-1.1.6-132
Expires: 3600
Content-Length: 0

----------------5:47:02.795----------------
SEND: enc=0 767 Bytes to 70.42.73.140:5060:UDP (INVITE 
sip:613@70.42.73.140 SIP/2.0) Interface Address=192.168.0.107
INVITE sip:613@70.42.73.140 SIP/2.0
From: 300 <sip:300@70.42.73.140>;tag=24388f6f04f9181094daa2088e6bd734
To: sip:613@70.42.73.140
Via: SIP/2.0/UDP 
192.168.0.107:5060;iid=1770;branch=z9hG4bK24388f6f04f9181094d9a2088e6bd734;uas-addr=70.42.73.140;rport
CSeq: 4711 INVITE
Call-ID: 24388f6f-04f9-1810-8825-a2088e6bd734
Contact: "300" <sip:300@192.168.0.107:5060>
User-Agent: OpenSIPStack-1.1.6-166
Max-Forwards: 10
Allow: INVITE, BYE, ACK, REFER, MESSAGE, INFO, NOTIFY, OPTIONS
Content-Type: application/sdp
Content-Length: 229

v=0
o=- 1182855278 1182855278 IN IP4 192.168.0.107
s=OSS RTP Session
c=IN IP4 192.168.0.107
t=0 0
m=audio 5000 RTP/AVP 101 8 0
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
----------------5:47:02.841----------------
SEND: enc=0 767 Bytes to 70.42.73.140:5060:UDP (INVITE 
sip:613@70.42.73.140 SIP/2.0) Interface Address=192.168.0.107
INVITE sip:613@70.42.73.140 SIP/2.0
From: 300 <sip:300@70.42.73.140>;tag=24388f6f04f9181094daa2088e6bd734
To: sip:613@70.42.73.140
Via: SIP/2.0/UDP 
192.168.0.107:5060;iid=1770;branch=z9hG4bK24388f6f04f9181094d9a2088e6bd734;uas-addr=70.42.73.140;rport
CSeq: 4711 INVITE
Call-ID: 24388f6f-04f9-1810-8825-a2088e6bd734
Contact: "300" <sip:300@192.168.0.107:5060>
User-Agent: OpenSIPStack-1.1.6-166
Max-Forwards: 10
Allow: INVITE, BYE, ACK, REFER, MESSAGE, INFO, NOTIFY, OPTIONS
Content-Type: application/sdp
Content-Length: 229

v=0
o=- 1182855278 1182855278 IN IP4 192.168.0.107
s=OSS RTP Session
c=IN IP4 192.168.0.107
t=0 0
m=audio 5000 RTP/AVP 101 8 0
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
----------------5:47:02.928----------------
RCV: enc=0 563 Bytes from RCVADDR: 70.42.73.140:RCVPORT: 5060:UDP 
(SIP/2.0 407 Proxy Authentication Required)
SIP/2.0 407 Proxy Authentication Required
From: 300 <sip:300@70.42.73.140>;tag=24388f6f04f9181094daa2088e6bd734
To:  <sip:613@70.42.73.140>;tag=e9128a6f04f918108bdfd184264b0e8e
Via: SIP/2.0/UDP 
192.168.0.107:5060;iid=1770;branch=z9hG4bK24388f6f04f9181094d9a2088e6bd734;uas-addr=70.42.73.140;rport=5060;received=64.243.115.20
CSeq: 4711 INVITE
Call-ID: 24388f6f-04f9-1810-8825-a2088e6bd734
Proxy-Authenticate: Digest realm=70.42.73.140, 
nonce="ec52dfdc48854008a4e1f5b327b6a7ab", 
opaque="4c7f21d239815332ea078702ccd86d83", algorithm=MD5
Content-Length: 0

----------------5:47:02.979----------------
SEND: enc=0 963 Bytes to 70.42.73.140:5060:UDP (INVITE 
sip:613@70.42.73.140 SIP/2.0) Interface Address=192.168.0.107
INVITE sip:613@70.42.73.140 SIP/2.0
From: 300 <sip:300@70.42.73.140>;tag=24388f6f04f9181094daa2088e6bd734
To: sip:613@70.42.73.140
Via: SIP/2.0/UDP 
192.168.0.107:5060;iid=1770;branch=z9hG4bKe69f8f6f04f9181094daa2088e6bd734;uas-addr=70.42.73.140;rport
CSeq: 4712 INVITE
Call-ID: 24388f6f-04f9-1810-8825-a2088e6bd734
Contact: "300" <sip:300@192.168.0.107:5060>
User-Agent: OpenSIPStack-1.1.6-166
Max-Forwards: 10
Proxy-Authorization: Digest username="300", realm="70.42.73.140", 
nonce="ec52dfdc48854008a4e1f5b327b6a7ab", uri="sip:613@70.42.73.140", 
response="3606c0c2a3553f1be2de540d929d0965", algorithm=MD5
Allow: INVITE, BYE, ACK, REFER, MESSAGE, INFO, NOTIFY, OPTIONS
Content-Type: application/sdp
Content-Length: 229

v=0
o=- 1182855278 1182855278 IN IP4 192.168.0.107
s=OSS RTP Session
c=IN IP4 192.168.0.107
t=0 0
m=audio 5000 RTP/AVP 101 8 0
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
----------------5:47:02.944----------------
RCV: enc=0 563 Bytes from RCVADDR: 70.42.73.140:RCVPORT: 5060:UDP 
(SIP/2.0 407 Proxy Authentication Required)
SIP/2.0 407 Proxy Authentication Required
From: 300 <sip:300@70.42.73.140>;tag=24388f6f04f9181094daa2088e6bd734
To:  <sip:613@70.42.73.140>;tag=e9128a6f04f918108bdfd184264b0e8e
Via: SIP/2.0/UDP 
192.168.0.107:5060;iid=1770;branch=z9hG4bK24388f6f04f9181094d9a2088e6bd734;uas-addr=70.42.73.140;rport=5060;received=64.243.115.20
CSeq: 4711 INVITE
Call-ID: 24388f6f-04f9-1810-8825-a2088e6bd734
Proxy-Authenticate: Digest realm=70.42.73.140, 
nonce="ec52dfdc48854008a4e1f5b327b6a7ab", 
opaque="4c7f21d239815332ea078702ccd86d83", algorithm=MD5
Content-Length: 0

----------------5:47:03.040----------------
SEND: enc=0 539 Bytes to 70.42.73.140:5060:UDP (ACK sip:613@70.42.73.140 
SIP/2.0) Interface Address=192.168.0.107
ACK sip:613@70.42.73.140 SIP/2.0
From: 300 <sip:300@70.42.73.140>;tag=24388f6f04f9181094daa2088e6bd734
To:  <sip:613@70.42.73.140>;tag=e9128a6f04f918108bdfd184264b0e8e
Via: SIP/2.0/UDP 
192.168.0.107:5060;iid=1770;branch=z9hG4bK24388f6f04f9181094d9a2088e6bd734;uas-addr=70.42.73.140;rport
CSeq: 4711 ACK
Call-ID: 24388f6f-04f9-1810-8825-a2088e6bd734
Contact: "300" <sip:300@192.168.0.107:5060>
User-Agent: OpenSIPStack-1.1.6-166
Max-Forwards: 10
Allow: INVITE, BYE, ACK, REFER, MESSAGE, INFO, NOTIFY, OPTIONS
Content-Length: 0

----------------5:47:03.029----------------
RCV: enc=0 563 Bytes from RCVADDR: 70.42.73.140:RCVPORT: 5060:UDP 
(SIP/2.0 407 Proxy Authentication Required)
SIP/2.0 407 Proxy Authentication Required
From: 300 <sip:300@70.42.73.140>;tag=24388f6f04f9181094daa2088e6bd734
To:  <sip:613@70.42.73.140>;tag=e9128a6f04f918108bdfd184264b0e8e
Via: SIP/2.0/UDP 
192.168.0.107:5060;iid=1770;branch=z9hG4bK24388f6f04f9181094d9a2088e6bd734;uas-addr=70.42.73.140;rport=5060;received=64.243.115.20
CSeq: 4711 INVITE
Call-ID: 24388f6f-04f9-1810-8825-a2088e6bd734
Proxy-Authenticate: Digest realm=70.42.73.140, 
nonce="ec52dfdc48854008a4e1f5b327b6a7ab", 
opaque="4c7f21d239815332ea078702ccd86d83", algorithm=MD5
Content-Length: 0

----------------5:47:03.086----------------
SEND: enc=0 539 Bytes to 70.42.73.140:5060:UDP (ACK sip:613@70.42.73.140 
SIP/2.0) Interface Address=192.168.0.107
ACK sip:613@70.42.73.140 SIP/2.0
From: 300 <sip:300@70.42.73.140>;tag=24388f6f04f9181094daa2088e6bd734
To:  <sip:613@70.42.73.140>;tag=e9128a6f04f918108bdfd184264b0e8e
Via: SIP/2.0/UDP 
192.168.0.107:5060;iid=1770;branch=z9hG4bK24388f6f04f9181094d9a2088e6bd734;uas-addr=70.42.73.140;rport
CSeq: 4711 ACK
Call-ID: 24388f6f-04f9-1810-8825-a2088e6bd734
Contact: "300" <sip:300@192.168.0.107:5060>
User-Agent: OpenSIPStack-1.1.6-166
Max-Forwards: 10
Allow: INVITE, BYE, ACK, REFER, MESSAGE, INFO, NOTIFY, OPTIONS
Content-Length: 0

----------------5:47:03.129----------------
SEND: enc=0 539 Bytes to 70.42.73.140:5060:UDP (ACK sip:613@70.42.73.140 
SIP/2.0) Interface Address=192.168.0.107
ACK sip:613@70.42.73.140 SIP/2.0
From: 300 <sip:300@70.42.73.140>;tag=24388f6f04f9181094daa2088e6bd734
To:  <sip:613@70.42.73.140>;tag=e9128a6f04f918108bdfd184264b0e8e
Via: SIP/2.0/UDP 
192.168.0.107:5060;iid=1770;branch=z9hG4bK24388f6f04f9181094d9a2088e6bd734;uas-addr=70.42.73.140;rport
CSeq: 4711 ACK
Call-ID: 24388f6f-04f9-1810-8825-a2088e6bd734
Contact: "300" <sip:300@192.168.0.107:5060>
User-Agent: OpenSIPStack-1.1.6-166
Max-Forwards: 10
Allow: INVITE, BYE, ACK, REFER, MESSAGE, INFO, NOTIFY, OPTIONS
Content-Length: 0

----------------5:47:03.337----------------
SEND: enc=0 963 Bytes to 70.42.73.140:5060:UDP (INVITE 
sip:613@70.42.73.140 SIP/2.0) Interface Address=192.168.0.107
INVITE sip:613@70.42.73.140 SIP/2.0
From: 300 <sip:300@70.42.73.140>;tag=24388f6f04f9181094daa2088e6bd734
To: sip:613@70.42.73.140
Via: SIP/2.0/UDP 
192.168.0.107:5060;iid=1770;branch=z9hG4bKe69f8f6f04f9181094daa2088e6bd734;uas-addr=70.42.73.140;rport
CSeq: 4712 INVITE
Call-ID: 24388f6f-04f9-1810-8825-a2088e6bd734
Contact: "300" <sip:300@192.168.0.107:5060>
User-Agent: OpenSIPStack-1.1.6-166
Max-Forwards: 10
Proxy-Authorization: Digest username="300", realm="70.42.73.140", 
nonce="ec52dfdc48854008a4e1f5b327b6a7ab", uri="sip:613@70.42.73.140", 
response="3606c0c2a3553f1be2de540d929d0965", algorithm=MD5
Allow: INVITE, BYE, ACK, REFER, MESSAGE, INFO, NOTIFY, OPTIONS
Content-Type: application/sdp
Content-Length: 229

v=0
o=- 1182855278 1182855278 IN IP4 192.168.0.107
s=OSS RTP Session
c=IN IP4 192.168.0.107
t=0 0
m=audio 5000 RTP/AVP 101 8 0
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000

tomach wrote:
> Instead of fields "From" above there should be:
>
> In invite it looks like this:
>
> From: 507 sip:507@192.168.2.45 ;tag=6204057789f818108168ffe5741f66c1
>
> and for register:
>
> From:  sip:507@192.168.2.69 ;tag=b94f4dd487f818108ff199e5a6d4f1ef
>
> -------------------------------------------------------------------------
> 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/
> _______________________________________________
> opensipstack-devel mailing list
> ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>
>
>   