Thread: [OpenSIPStack] SoftPhoneInterface - Incoming Call Event not triggered
Brought to you by:
joegenbaclor
Menu
▾
▴
opensipstack-devel
|
From: Jacob W. <wat...@go...> - 2007-12-06 14:33:01
|
Hi,
I am using the SoftPhoneInterface class as a basis for a softphone
implementation. I am able to register and make calls just fine, but when it
comes to receiving calls, even after having registered with my SIP
provider's server, no event is triggered in the SoftPhoneInterface class
(Event_IncomingCall), and so I am unable to answer a call.
Using Wireshark, however, I see that the INVITE request is being received by
my SIP provider's server, but all that is returned from my end,
automatically, is a "Status: 100 Trying" message, and then nothing else
happens.
Here is my Wireshark protocol:
No. Time Source Destination Protocol
Info
*Registering*
264 19.624891 Local.Address.1.35 Remote.Address.90.138
SIP Request: REGISTER sip:Remote.Address.90.138
268 19.853526 Remote.Address.90.138 Local.Address.1.35
SIP Status: 407 Proxy Authentication Required (1 bindings)
270 19.895982 Local.Address.1.35 Remote.Address.90.138
SIP Request: REGISTER sip:Remote.Address.90.138
271 20.099519 Local.Address.1.35 Remote.Address.90.138
SIP Request: REGISTER sip:Remote.Address.90.138
272 20.120145 Remote.Address.90.138 Local.Address.1.35
SIP Status: 200 OK (1 bindings)
273 20.321326 Remote.Address.90.138 Local.Address.1.35
SIP Status: 200 OK (1 bindings)
*Making a call - Successful*
4632 334.556501 Local.Address.1.35 Remote.Address.90.138
SIP/SDP Request: INVITE sip:Dia...@Re...dress.90.138, with
session description
4635 334.634657 Local.Address.1.35 Remote.Address.90.138
SIP/SDP Request: INVITE sip:Dia...@Re...dress.90.138, with
session description
4639 334.785283 Remote.Address.90.138 Local.Address.1.35
SIP Status: 100 Trying
4640 334.801885 Remote.Address.90.138 Local.Address.1.35
SIP/SDP Status: 200 OK, with session description
4642 334.866339 Remote.Address.90.138 Local.Address.1.35
SIP/SDP Status: 200 OK, with session description
4652 335.302885 Remote.Address.90.138 Local.Address.1.35
SIP/SDP Status: 200 OK, with session description
4660 336.302943 Remote.Address.90.138 Local.Address.1.35
SIP/SDP Status: 200 OK, with session description
4691 338.348935 Remote.Address.90.138 Local.Address.1.35
SIP/SDP Status: 200 OK, with session description
4750 342.363792 Remote.Address.90.138 Local.Address.1.35
SIP/SDP Status: 200 OK, with session description
4795 345.240244 Local.Address.1.35 Remote.Address.90.138
SIP Request: ACK sip:Dia...@Re...dress.90.138:5060
6852 367.034986 Local.Address.1.35 Remote.Address.90.138
SIP Request: BYE sip:Dia...@Re...dress.90.138:5060
6859 367.139967 Local.Address.1.35 Remote.Address.90.138
SIP Request: BYE sip:Dia...@Re...dress.90.138:5060
6860 367.243944 Remote.Address.90.138 Local.Address.1.35
SIP Status: 200 OK
6862 367.346488 Remote.Address.90.138 Local.Address.1.35
SIP Status: 200 OK
*Receiving a call - "Status: 100 Trying"*
7104 386.368960 Remote.Address.90.138 Local.Address.1.35
SIP/SDP Request: INVITE sip:MyN...@Lo...dress.1.35:5060, with session
description
7105 386.397928 Local.Address.1.35 Remote.Address.90.138
SIP Status: 100 Trying
*Unregistering*
7653 425.373636 Local.Address.1.35 Remote.Address.90.138
SIP Request: REGISTER sip:Remote.Address.90.138 (remove all
bindings)
7657 425.606269 Remote.Address.90.138 Local.Address.1.35
SIP Status: 200 OK (0 bindings)
Any ideas as to why this might be the case would be greatly appreciated.
Thanks!
Best regards,
Jacob
|
|
From: Ilian J. C. P. <ip...@so...> - 2007-12-07 04:34:58
|
Jacob, That's strange. Can you post the entire SIP message and not just the compressed form? That will be very helpful. - Ilian Jacob Waterman wrote: > Hi, > > I am using the SoftPhoneInterface class as a basis for a softphone > implementation. I am able to register and make calls just fine, but when it > comes to receiving calls, even after having registered with my SIP > provider's server, no event is triggered in the SoftPhoneInterface class > (Event_IncomingCall), and so I am unable to answer a call. > > Using Wireshark, however, I see that the INVITE request is being received by > my SIP provider's server, but all that is returned from my end, > automatically, is a "Status: 100 Trying" message, and then nothing else > happens. > > Here is my Wireshark protocol: > > No. Time Source Destination Protocol > Info > > *Registering* > 264 19.624891 Local.Address.1.35 Remote.Address.90.138 > SIP Request: REGISTER sip:Remote.Address.90.138 > 268 19.853526 Remote.Address.90.138 Local.Address.1.35 > SIP Status: 407 Proxy Authentication Required (1 bindings) > 270 19.895982 Local.Address.1.35 Remote.Address.90.138 > SIP Request: REGISTER sip:Remote.Address.90.138 > 271 20.099519 Local.Address.1.35 Remote.Address.90.138 > SIP Request: REGISTER sip:Remote.Address.90.138 > 272 20.120145 Remote.Address.90.138 Local.Address.1.35 > SIP Status: 200 OK (1 bindings) > 273 20.321326 Remote.Address.90.138 Local.Address.1.35 > SIP Status: 200 OK (1 bindings) > > *Making a call - Successful* > 4632 334.556501 Local.Address.1.35 Remote.Address.90.138 > SIP/SDP Request: INVITE sip:Dia...@Re...dress.90.138, with > session description > 4635 334.634657 Local.Address.1.35 Remote.Address.90.138 > SIP/SDP Request: INVITE sip:Dia...@Re...dress.90.138, with > session description > 4639 334.785283 Remote.Address.90.138 Local.Address.1.35 > SIP Status: 100 Trying > 4640 334.801885 Remote.Address.90.138 Local.Address.1.35 > SIP/SDP Status: 200 OK, with session description > 4642 334.866339 Remote.Address.90.138 Local.Address.1.35 > SIP/SDP Status: 200 OK, with session description > 4652 335.302885 Remote.Address.90.138 Local.Address.1.35 > SIP/SDP Status: 200 OK, with session description > 4660 336.302943 Remote.Address.90.138 Local.Address.1.35 > SIP/SDP Status: 200 OK, with session description > 4691 338.348935 Remote.Address.90.138 Local.Address.1.35 > SIP/SDP Status: 200 OK, with session description > 4750 342.363792 Remote.Address.90.138 Local.Address.1.35 > SIP/SDP Status: 200 OK, with session description > 4795 345.240244 Local.Address.1.35 Remote.Address.90.138 > SIP Request: ACK sip:Dia...@Re...dress.90.138:5060 > 6852 367.034986 Local.Address.1.35 Remote.Address.90.138 > SIP Request: BYE sip:Dia...@Re...dress.90.138:5060 > 6859 367.139967 Local.Address.1.35 Remote.Address.90.138 > SIP Request: BYE sip:Dia...@Re...dress.90.138:5060 > 6860 367.243944 Remote.Address.90.138 Local.Address.1.35 > SIP Status: 200 OK > 6862 367.346488 Remote.Address.90.138 Local.Address.1.35 > SIP Status: 200 OK > > *Receiving a call - "Status: 100 Trying"* > 7104 386.368960 Remote.Address.90.138 Local.Address.1.35 > SIP/SDP Request: INVITE sip:MyN...@Lo...dress.1.35:5060, with session > description > 7105 386.397928 Local.Address.1.35 Remote.Address.90.138 > SIP Status: 100 Trying > > *Unregistering* > 7653 425.373636 Local.Address.1.35 Remote.Address.90.138 > SIP Request: REGISTER sip:Remote.Address.90.138 (remove all > bindings) > 7657 425.606269 Remote.Address.90.138 Local.Address.1.35 > SIP Status: 200 OK (0 bindings) > > Any ideas as to why this might be the case would be greatly appreciated. > > Thanks! > > Best regards, > > Jacob > ------------------------------------------------------------------------- > SF.Net email is sponsored by: The Future of Linux Business White Paper > from Novell. From the desktop to the data center, Linux is going > mainstream. Let it simplify your IT future. > http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 > _______________________________________________ > opensipstack-devel mailing list > ope...@li... > https://lists.sourceforge.net/lists/listinfo/opensipstack-devel > > |
|
From: Jacob W. <wat...@go...> - 2007-12-11 13:55:32
|
Hi Ilian, Hi Joegen,
Thanks for your responses! Here is the full INVITE message and the
corresponding "100: Trying" response.
No. Time Source Destination Protocol
Info
885 99.833033 Rem.Addr.90.138 Loc.Addr.1.35 SIP/SDP
Request: INVITE sip:Des...@Lo...dr.1.35:5060, with session description
Frame 885 (941 bytes on wire, 941 bytes captured)
Ethernet II, Src: ZyxelCom_7f:5b:cd (00:13:49:7f:5b:cd), Dst:
CompalCo_d9:53:e9 (00:16:d4:d9:53:e9)
Internet Protocol, Src: Rem.Addr.90.138 (Rem.Addr.90.138), Dst:
Loc.Addr.1.35 (Loc.Addr.1.35)
User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 5060 (5060)
Session Initiation Protocol
Request-Line: INVITE sip:Des...@Lo...dr.1.35:5060 SIP/2.0
Method: INVITE
[Resent Packet: False]
Message Header
Via: SIP/2.0/UDP Rem.Addr.90.138:5060
Via: SIP/2.0/UDP Rem.Addr.90.141
:5060;branch=z9hG4bK2299f16cbf64a411fd8a1986
Max-Forwards: 69
From: <sip:Ori...@Re...dr.90.138>;tag=2299f16cbfc5e3b2fd8a1998
To: <sip:Des...@Re...dr.90.138>
Call-ID: 229...@Re...dr.90.141
CSeq: 1 INVITE
User-agent: SysMaster VoIP Gateway v1.2.0
Contact: <sip:sm...@Re...dr.90.138:5060>
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,REFER,SUBSCRIBE
Content-Type: application/sdp
Content-Length: 342
Message body
Session Description Protocol
Session Description Protocol Version (v): 0
Owner/Creator, Session Id (o): - 223217380501517 1 IN IP4
Rem.Addr.90.138
Session Name (s): -
Connection Information (c): IN IP4 Rem.Addr.90.138
Time Description, active time (t): 0 0
Media Description, name and address (m): audio 22614 RTP/AVP 0 8
18 4 101
Media Attribute (a): rtpmap:0 PCMU/8000
Media Attribute (a): rtpmap:8 PCMA/8000
Media Attribute (a): rtpmap:18 G729/8000
Media Attribute (a): fmtp:18 annexb=no
Media Attribute (a): rtpmap:4 G723/8000
Media Attribute (a): rtpmap:101 telephone-event/8000
Media Attribute (a): fmtp:101 0-16
Media Description, name and address (m): video 22616 RTP/AVP 102
Media Attribute (a): rtpmap:102 H263-1998/90000
No. Time Source Destination Protocol
Info
886 99.856567 Loc.Addr.1.35 Rem.Addr.90.138 SIP
Status: 100 Trying
Frame 886 (375 bytes on wire, 375 bytes captured)
Ethernet II, Src: CompalCo_d9:53:e9 (00:16:d4:d9:53:e9), Dst:
ZyxelCom_7f:5b:cd (00:13:49:7f:5b:cd)
Internet Protocol, Src: Loc.Addr.1.35 (Loc.Addr.1.35), Dst: Rem.Addr.90.138(
Rem.Addr.90.138)
User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 5060 (5060)
Session Initiation Protocol
Status-Line: SIP/2.0 100 Trying
Status-Code: 100
[Resent Packet: False]
Message Header
From: <sip:Ori...@Re...dr.90.138>;tag=2299f16cbfc5e3b2fd8a1998
To: <sip:Des...@Re...dr.90.138>
Via: SIP/2.0/UDP Rem.Addr.90.138:5060
Via: SIP/2.0/UDP Rem.Addr.90.141
:5060;branch=z9hG4bK2299f16cbf64a411fd8a1986
CSeq: 1 INVITE
Call-ID: 229...@Re...dr.90.141
Content-Length: 0
Thanks again!
Best regards,
Jacob
On Dec 7, 2007 5:34 AM, Ilian Jeri C. Pinzon <ip...@so...>
wrote:
> Jacob,
>
> That's strange. Can you post the entire SIP message and not just the
> compressed form? That will be very helpful.
>
> - Ilian
>
> Jacob Waterman wrote:
> > Hi,
> >
> > I am using the SoftPhoneInterface class as a basis for a softphone
> > implementation. I am able to register and make calls just fine, but when
> it
> > comes to receiving calls, even after having registered with my SIP
> > provider's server, no event is triggered in the SoftPhoneInterface class
> > (Event_IncomingCall), and so I am unable to answer a call.
> >
> > Using Wireshark, however, I see that the INVITE request is being
> received by
> > my SIP provider's server, but all that is returned from my end,
> > automatically, is a "Status: 100 Trying" message, and then nothing else
> > happens.
> >
> > Here is my Wireshark protocol:
> >
> > No. Time Source Destination Protocol
> > Info
> >
> > *Registering*
> > 264 19.624891 Local.Address.1.35 Remote.Address.90.138
> > SIP Request: REGISTER sip:Remote.Address.90.138
> > 268 19.853526 Remote.Address.90.138 Local.Address.1.35
> > SIP Status: 407 Proxy Authentication Required (1 bindings)
> > 270 19.895982 Local.Address.1.35 Remote.Address.90.138
> > SIP Request: REGISTER sip:Remote.Address.90.138
> > 271 20.099519 Local.Address.1.35 Remote.Address.90.138
> > SIP Request: REGISTER sip:Remote.Address.90.138
> > 272 20.120145 Remote.Address.90.138 Local.Address.1.35
> > SIP Status: 200 OK (1 bindings)
> > 273 20.321326 Remote.Address.90.138 Local.Address.1.35
> > SIP Status: 200 OK (1 bindings)
> >
> > *Making a call - Successful*
> > 4632 334.556501 Local.Address.1.35 Remote.Address.90.138
> > SIP/SDP Request: INVITE sip:Dia...@Re...dress.90.138, with
> > session description
> > 4635 334.634657 Local.Address.1.35 Remote.Address.90.138
> > SIP/SDP Request: INVITE sip:Dia...@Re...dress.90.138, with
> > session description
> > 4639 334.785283 Remote.Address.90.138 Local.Address.1.35
> > SIP Status: 100 Trying
> > 4640 334.801885 Remote.Address.90.138 Local.Address.1.35
> > SIP/SDP Status: 200 OK, with session description
> > 4642 334.866339 Remote.Address.90.138 Local.Address.1.35
> > SIP/SDP Status: 200 OK, with session description
> > 4652 335.302885 Remote.Address.90.138 Local.Address.1.35
> > SIP/SDP Status: 200 OK, with session description
> > 4660 336.302943 Remote.Address.90.138 Local.Address.1.35
> > SIP/SDP Status: 200 OK, with session description
> > 4691 338.348935 Remote.Address.90.138 Local.Address.1.35
> > SIP/SDP Status: 200 OK, with session description
> > 4750 342.363792 Remote.Address.90.138 Local.Address.1.35
> > SIP/SDP Status: 200 OK, with session description
> > 4795 345.240244 Local.Address.1.35 Remote.Address.90.138
> > SIP Request: ACK sip:Dia...@Re...dress.90.138:5060
> > 6852 367.034986 Local.Address.1.35 Remote.Address.90.138
> > SIP Request: BYE sip:Dia...@Re...dress.90.138:5060
> > 6859 367.139967 Local.Address.1.35 Remote.Address.90.138
> > SIP Request: BYE sip:Dia...@Re...dress.90.138:5060
> > 6860 367.243944 Remote.Address.90.138 Local.Address.1.35
> > SIP Status: 200 OK
> > 6862 367.346488 Remote.Address.90.138 Local.Address.1.35
> > SIP Status: 200 OK
> >
> > *Receiving a call - "Status: 100 Trying"*
> > 7104 386.368960 Remote.Address.90.138 Local.Address.1.35
> > SIP/SDP Request: INVITE sip:MyN...@Lo...dress.1.35:5060, with
> session
> > description
> > 7105 386.397928 Local.Address.1.35 Remote.Address.90.138
> > SIP Status: 100 Trying
> >
> > *Unregistering*
> > 7653 425.373636 Local.Address.1.35 Remote.Address.90.138
> > SIP Request: REGISTER sip:Remote.Address.90.138 (remove all
> > bindings)
> > 7657 425.606269 Remote.Address.90.138 Local.Address.1.35
> > SIP Status: 200 OK (0 bindings)
> >
> > Any ideas as to why this might be the case would be greatly appreciated.
> >
> > Thanks!
> >
> > Best regards,
> >
> > Jacob
> >
> -------------------------------------------------------------------------
> > SF.Net email is sponsored by: The Future of Linux Business White Paper
> > from Novell. From the desktop to the data center, Linux is going
> > mainstream. Let it simplify your IT future.
> > http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
> > _______________________________________________
> > opensipstack-devel mailing list
> > ope...@li...
> > https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
> >
> >
>
>
> -------------------------------------------------------------------------
> SF.Net email is sponsored by:
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> opensipstack-devel mailing list
> ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>
|
|
From: Joegen E. B. <joe...@gm...> - 2007-12-12 02:27:52
|
Hi Jacob, Thanks for the packet capture but its not very helpful in investigating packet format problems. We need to see the actual state of the packet in the wire. You can send me the capture offlist if you are concerned about the privacy of your network. It will be for my eyes only given that you will trust my intent. Joegen Jacob Waterman wrote: > Hi Ilian, Hi Joegen, > > Thanks for your responses! Here is the full INVITE message and the > corresponding "100: Trying" response. > > No. Time Source Destination Protocol > Info > 885 99.833033 Rem.Addr.90.138 Loc.Addr.1.35 SIP/SDP > Request: INVITE sip:Des...@Lo...dr.1.35:5060, with session description > > Frame 885 (941 bytes on wire, 941 bytes captured) > Ethernet II, Src: ZyxelCom_7f:5b:cd (00:13:49:7f:5b:cd), Dst: > CompalCo_d9:53:e9 (00:16:d4:d9:53:e9) > Internet Protocol, Src: Rem.Addr.90.138 (Rem.Addr.90.138), Dst: > Loc.Addr.1.35 (Loc.Addr.1.35) > User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 5060 (5060) > Session Initiation Protocol > Request-Line: INVITE sip:Des...@Lo...dr.1.35:5060 SIP/2.0 > Method: INVITE > [Resent Packet: False] > Message Header > Via: SIP/2.0/UDP Rem.Addr.90.138:5060 > Via: SIP/2.0/UDP Rem.Addr.90.141 > :5060;branch=z9hG4bK2299f16cbf64a411fd8a1986 > Max-Forwards: 69 > From: <sip:Ori...@Re...dr.90.138>;tag=2299f16cbfc5e3b2fd8a1998 > To: <sip:Des...@Re...dr.90.138> > Call-ID: 229...@Re...dr.90.141 > CSeq: 1 INVITE > User-agent: SysMaster VoIP Gateway v1.2.0 > Contact: <sip:sm...@Re...dr.90.138:5060> > Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,REFER,SUBSCRIBE > Content-Type: application/sdp > Content-Length: 342 > Message body > Session Description Protocol > Session Description Protocol Version (v): 0 > Owner/Creator, Session Id (o): - 223217380501517 1 IN IP4 > Rem.Addr.90.138 > Session Name (s): - > Connection Information (c): IN IP4 Rem.Addr.90.138 > Time Description, active time (t): 0 0 > Media Description, name and address (m): audio 22614 RTP/AVP 0 8 > 18 4 101 > Media Attribute (a): rtpmap:0 PCMU/8000 > Media Attribute (a): rtpmap:8 PCMA/8000 > Media Attribute (a): rtpmap:18 G729/8000 > Media Attribute (a): fmtp:18 annexb=no > Media Attribute (a): rtpmap:4 G723/8000 > Media Attribute (a): rtpmap:101 telephone-event/8000 > Media Attribute (a): fmtp:101 0-16 > Media Description, name and address (m): video 22616 RTP/AVP 102 > Media Attribute (a): rtpmap:102 H263-1998/90000 > > No. Time Source Destination Protocol > Info > 886 99.856567 Loc.Addr.1.35 Rem.Addr.90.138 SIP > Status: 100 Trying > > Frame 886 (375 bytes on wire, 375 bytes captured) > Ethernet II, Src: CompalCo_d9:53:e9 (00:16:d4:d9:53:e9), Dst: > ZyxelCom_7f:5b:cd (00:13:49:7f:5b:cd) > Internet Protocol, Src: Loc.Addr.1.35 (Loc.Addr.1.35), Dst: Rem.Addr.90.138( > Rem.Addr.90.138) > User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 5060 (5060) > Session Initiation Protocol > Status-Line: SIP/2.0 100 Trying > Status-Code: 100 > [Resent Packet: False] > Message Header > From: <sip:Ori...@Re...dr.90.138>;tag=2299f16cbfc5e3b2fd8a1998 > To: <sip:Des...@Re...dr.90.138> > Via: SIP/2.0/UDP Rem.Addr.90.138:5060 > Via: SIP/2.0/UDP Rem.Addr.90.141 > :5060;branch=z9hG4bK2299f16cbf64a411fd8a1986 > CSeq: 1 INVITE > Call-ID: 229...@Re...dr.90.141 > Content-Length: 0 > > Thanks again! > > Best regards, > > Jacob > > On Dec 7, 2007 5:34 AM, Ilian Jeri C. Pinzon <ip...@so...> > wrote: > > >> Jacob, >> >> That's strange. Can you post the entire SIP message and not just the >> compressed form? That will be very helpful. >> >> - Ilian >> >> Jacob Waterman wrote: >> >>> Hi, >>> >>> I am using the SoftPhoneInterface class as a basis for a softphone >>> implementation. I am able to register and make calls just fine, but when >>> >> it >> >>> comes to receiving calls, even after having registered with my SIP >>> provider's server, no event is triggered in the SoftPhoneInterface class >>> (Event_IncomingCall), and so I am unable to answer a call. >>> >>> Using Wireshark, however, I see that the INVITE request is being >>> >> received by >> >>> my SIP provider's server, but all that is returned from my end, >>> automatically, is a "Status: 100 Trying" message, and then nothing else >>> happens. >>> >>> Here is my Wireshark protocol: >>> >>> No. Time Source Destination Protocol >>> Info >>> >>> *Registering* >>> 264 19.624891 Local.Address.1.35 Remote.Address.90.138 >>> SIP Request: REGISTER sip:Remote.Address.90.138 >>> 268 19.853526 Remote.Address.90.138 Local.Address.1.35 >>> SIP Status: 407 Proxy Authentication Required (1 bindings) >>> 270 19.895982 Local.Address.1.35 Remote.Address.90.138 >>> SIP Request: REGISTER sip:Remote.Address.90.138 >>> 271 20.099519 Local.Address.1.35 Remote.Address.90.138 >>> SIP Request: REGISTER sip:Remote.Address.90.138 >>> 272 20.120145 Remote.Address.90.138 Local.Address.1.35 >>> SIP Status: 200 OK (1 bindings) >>> 273 20.321326 Remote.Address.90.138 Local.Address.1.35 >>> SIP Status: 200 OK (1 bindings) >>> >>> *Making a call - Successful* >>> 4632 334.556501 Local.Address.1.35 Remote.Address.90.138 >>> SIP/SDP Request: INVITE sip:Dia...@Re...dress.90.138, with >>> session description >>> 4635 334.634657 Local.Address.1.35 Remote.Address.90.138 >>> SIP/SDP Request: INVITE sip:Dia...@Re...dress.90.138, with >>> session description >>> 4639 334.785283 Remote.Address.90.138 Local.Address.1.35 >>> SIP Status: 100 Trying >>> 4640 334.801885 Remote.Address.90.138 Local.Address.1.35 >>> SIP/SDP Status: 200 OK, with session description >>> 4642 334.866339 Remote.Address.90.138 Local.Address.1.35 >>> SIP/SDP Status: 200 OK, with session description >>> 4652 335.302885 Remote.Address.90.138 Local.Address.1.35 >>> SIP/SDP Status: 200 OK, with session description >>> 4660 336.302943 Remote.Address.90.138 Local.Address.1.35 >>> SIP/SDP Status: 200 OK, with session description >>> 4691 338.348935 Remote.Address.90.138 Local.Address.1.35 >>> SIP/SDP Status: 200 OK, with session description >>> 4750 342.363792 Remote.Address.90.138 Local.Address.1.35 >>> SIP/SDP Status: 200 OK, with session description >>> 4795 345.240244 Local.Address.1.35 Remote.Address.90.138 >>> SIP Request: ACK sip:Dia...@Re...dress.90.138:5060 >>> 6852 367.034986 Local.Address.1.35 Remote.Address.90.138 >>> SIP Request: BYE sip:Dia...@Re...dress.90.138:5060 >>> 6859 367.139967 Local.Address.1.35 Remote.Address.90.138 >>> SIP Request: BYE sip:Dia...@Re...dress.90.138:5060 >>> 6860 367.243944 Remote.Address.90.138 Local.Address.1.35 >>> SIP Status: 200 OK >>> 6862 367.346488 Remote.Address.90.138 Local.Address.1.35 >>> SIP Status: 200 OK >>> >>> *Receiving a call - "Status: 100 Trying"* >>> 7104 386.368960 Remote.Address.90.138 Local.Address.1.35 >>> SIP/SDP Request: INVITE sip:MyN...@Lo...dress.1.35:5060, with >>> >> session >> >>> description >>> 7105 386.397928 Local.Address.1.35 Remote.Address.90.138 >>> SIP Status: 100 Trying >>> >>> *Unregistering* >>> 7653 425.373636 Local.Address.1.35 Remote.Address.90.138 >>> SIP Request: REGISTER sip:Remote.Address.90.138 (remove all >>> bindings) >>> 7657 425.606269 Remote.Address.90.138 Local.Address.1.35 >>> SIP Status: 200 OK (0 bindings) >>> >>> Any ideas as to why this might be the case would be greatly appreciated. >>> >>> Thanks! >>> >>> Best regards, >>> >>> Jacob >>> >>> >> ------------------------------------------------------------------------- >> >>> SF.Net email is sponsored by: The Future of Linux Business White Paper >>> from Novell. From the desktop to the data center, Linux is going >>> mainstream. Let it simplify your IT future. >>> http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 >>> _______________________________________________ >>> opensipstack-devel mailing list >>> ope...@li... >>> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel >>> >>> >>> >> ------------------------------------------------------------------------- >> SF.Net email is sponsored by: >> Check out the new SourceForge.net Marketplace. >> It's the best place to buy or sell services for >> just about anything Open Source. >> http://sourceforge.net/services/buy/index.php >> _______________________________________________ >> opensipstack-devel mailing list >> ope...@li... >> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel >> >> > ------------------------------------------------------------------------- > SF.Net email is sponsored by: > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ > opensipstack-devel mailing list > ope...@li... > https://lists.sourceforge.net/lists/listinfo/opensipstack-devel > > > |
|
From: Joegen E. B. <joe...@gm...> - 2007-12-10 01:40:52
|
It seems like OpenSIPStack is not able to parse the INVITe and is getting discarded. Would you be able to send a capture of this INVITE? Jacob Waterman wrote: > Hi, > > I am using the SoftPhoneInterface class as a basis for a softphone > implementation. I am able to register and make calls just fine, but when it > comes to receiving calls, even after having registered with my SIP > provider's server, no event is triggered in the SoftPhoneInterface class > (Event_IncomingCall), and so I am unable to answer a call. > > Using Wireshark, however, I see that the INVITE request is being received by > my SIP provider's server, but all that is returned from my end, > automatically, is a "Status: 100 Trying" message, and then nothing else > happens. > > Here is my Wireshark protocol: > > No. Time Source Destination Protocol > Info > > *Registering* > 264 19.624891 Local.Address.1.35 Remote.Address.90.138 > SIP Request: REGISTER sip:Remote.Address.90.138 > 268 19.853526 Remote.Address.90.138 Local.Address.1.35 > SIP Status: 407 Proxy Authentication Required (1 bindings) > 270 19.895982 Local.Address.1.35 Remote.Address.90.138 > SIP Request: REGISTER sip:Remote.Address.90.138 > 271 20.099519 Local.Address.1.35 Remote.Address.90.138 > SIP Request: REGISTER sip:Remote.Address.90.138 > 272 20.120145 Remote.Address.90.138 Local.Address.1.35 > SIP Status: 200 OK (1 bindings) > 273 20.321326 Remote.Address.90.138 Local.Address.1.35 > SIP Status: 200 OK (1 bindings) > > *Making a call - Successful* > 4632 334.556501 Local.Address.1.35 Remote.Address.90.138 > SIP/SDP Request: INVITE sip:Dia...@Re...dress.90.138, with > session description > 4635 334.634657 Local.Address.1.35 Remote.Address.90.138 > SIP/SDP Request: INVITE sip:Dia...@Re...dress.90.138, with > session description > 4639 334.785283 Remote.Address.90.138 Local.Address.1.35 > SIP Status: 100 Trying > 4640 334.801885 Remote.Address.90.138 Local.Address.1.35 > SIP/SDP Status: 200 OK, with session description > 4642 334.866339 Remote.Address.90.138 Local.Address.1.35 > SIP/SDP Status: 200 OK, with session description > 4652 335.302885 Remote.Address.90.138 Local.Address.1.35 > SIP/SDP Status: 200 OK, with session description > 4660 336.302943 Remote.Address.90.138 Local.Address.1.35 > SIP/SDP Status: 200 OK, with session description > 4691 338.348935 Remote.Address.90.138 Local.Address.1.35 > SIP/SDP Status: 200 OK, with session description > 4750 342.363792 Remote.Address.90.138 Local.Address.1.35 > SIP/SDP Status: 200 OK, with session description > 4795 345.240244 Local.Address.1.35 Remote.Address.90.138 > SIP Request: ACK sip:Dia...@Re...dress.90.138:5060 > 6852 367.034986 Local.Address.1.35 Remote.Address.90.138 > SIP Request: BYE sip:Dia...@Re...dress.90.138:5060 > 6859 367.139967 Local.Address.1.35 Remote.Address.90.138 > SIP Request: BYE sip:Dia...@Re...dress.90.138:5060 > 6860 367.243944 Remote.Address.90.138 Local.Address.1.35 > SIP Status: 200 OK > 6862 367.346488 Remote.Address.90.138 Local.Address.1.35 > SIP Status: 200 OK > > *Receiving a call - "Status: 100 Trying"* > 7104 386.368960 Remote.Address.90.138 Local.Address.1.35 > SIP/SDP Request: INVITE sip:MyN...@Lo...dress.1.35:5060, with session > description > 7105 386.397928 Local.Address.1.35 Remote.Address.90.138 > SIP Status: 100 Trying > > *Unregistering* > 7653 425.373636 Local.Address.1.35 Remote.Address.90.138 > SIP Request: REGISTER sip:Remote.Address.90.138 (remove all > bindings) > 7657 425.606269 Remote.Address.90.138 Local.Address.1.35 > SIP Status: 200 OK (0 bindings) > > Any ideas as to why this might be the case would be greatly appreciated. > > Thanks! > > Best regards, > > Jacob > ------------------------------------------------------------------------- > SF.Net email is sponsored by: The Future of Linux Business White Paper > from Novell. From the desktop to the data center, Linux is going > mainstream. Let it simplify your IT future. > http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 > _______________________________________________ > opensipstack-devel mailing list > ope...@li... > https://lists.sourceforge.net/lists/listinfo/opensipstack-devel > > > |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X