Re: [Partysip-dev] Windows messenger doesn't seem to be sending back 100/trying and 180/ringing

[Aymeric Moizard]

Are you sure the firewall is not active if you are using windows XP?
Aymeric

On Sun, 27 Apr 2003, Benam Muppidi wrote:

> Hi,
>
> I have just downloaded and started the proxy on a windows server and I'm
> trying to use windows messengers as user agents from two different PCs (all
> of them have public IP's w/o any FWs).
>
> After registering the messengers with proxy, when I tried to make a call
> from PC1 to PC2, I can see INVITE from the proxy to PC2 but for some reason
> PC2's windows messenger isn't sending back 100/trying and 180/ringing, for
> that matter I don't even see the invitation slide of the messenger but I was
> able to see the INVITE packet from the proxy to PC2 using ethereal in it.
>
> I'm I missing some kind of configuration property in the proxy or may be my
> RTC DLL got corrupted?
>
> Please let me know your thoughts, I'm attaching a copy of the invitation
> packet I received.
>
> Thanks in advance,
> Benam
>
> Source: 69.5.128.18 (69.5.128.18) #proxy
> Destination: 202.88.175.234 (202.88.175.234) #PC2
>
> User Datagram Protocol, Src Port: 5061 (5061), Dst Port: 14592 (14592)
> Source port: 5061 (5061)
> Destination port: 14592 (14592)
>
> Session Initiation Protocol
> Request line: INVITE sip:202.88.175.234:14592 SIP/2.0
> Message Header
> Via: SIP/2.0/UDP 69.5.128.18:5060 default
> value;branch=z9hG4bKff986a409ff505133287cc81033
> Via: SIP/2.0/UDP 202.88.191.78:13810
> From: "work" <sip:address@hidden>;tag=3679c7ed-c016-48f2-a9ea-ff9e1961b70d
> To: <sip:address@hidden>
> Call-ID: address@hidden
> CSeq: 1 INVITE
> Contact: <sip:202.88.191.78:13810>
> user-agent: Windows RTC/1.0
> Content-Type: application/sdp
> Content-Length: 276
>
> Session Description Protocol
> Session Description Protocol Version (v): 0
> Owner/Creator, Session Id (o): Administrator 0 0 IN IP4 202.88.191.78
> Owner Username: Administrator
> Session ID: 0
> Session Version: 0
> Owner Network Type: IN
> Owner Address Type: IP4
> Owner Address: 202.88.191.78
> Session Name (s): session
> Connection Information (c): IN IP4 202.88.191.78
> Connection Network Type: IN
> Connection Address Type: IP4
> Connection Address: 202.88.191.78
> Bandwidth Information (b): CT:1000
> Bandwidth Modifier: CT
> Bandwidth Value: 1000
> Time Description, active time (t): 0 0
> Session Start Time: 0
> Session Start Time: 0
> Media Description, name and address (m): audio 16300 RTP/AVP 97 0 8 4 101
> Media Type: audio
> Media Port: 16300
> Media Proto: RTP/AVP
> Media Format: 97
> Media Format: 0
> Media Format: 8
> Media Format: 4
> Media Format: 101
> Media Attribute (a): rtpmap:97 red/8000
> Media Attribute Fieldname: rtpmap
> Media Attribute Value: 97 red/8000
> Media Attribute (a): rtpmap:0 PCMU/8000
> Media Attribute Fieldname: rtpmap
> Media Attribute Value: 0 PCMU/8000
> Media Attribute (a): rtpmap:8 PCMA/8000
> Media Attribute Fieldname: rtpmap
> Media Attribute Value: 8 PCMA/8000
> Media Attribute (a): rtpmap:4 G723/8000
> Media Attribute Fieldname: rtpmap
> Media Attribute Value: 4 G723/8000
> Media Attribute (a): rtpmap:101 telephone-event/8000
> Media Attribute Fieldname: rtpmap
> Media Attribute Value: 101 telephone-event/8000
> Media Attribute (a): fmtp:101 0-16
> Media Attribute Fieldname: fmtp
> Media Attribute Value: 101 0-16
>
>
>
>
> _______________________________________________
> Partysip-dev mailing list
> address@hidden
> http://mail.nongnu.org/mailman/listinfo/partysip-dev
>