2 OPTIONS
> Call-ID: 5bf37c2d2d25a9346cc272d71c3a8...@172.11.0.201
> Contact:
> Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE,
> NOTIFY, PRACK, UPDATE, REFER
> User-Agent: PolycomSoundPointIP-SPIP_601-UA/2.2.0.0047
> Content-Length: 0
>
>
> Hmmm
s-boun...@lists.digium.com
[mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Steve Howes
Sent: Thursday, March 25, 2010 11:35 AM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] SIP OPTIONS response from the peer is ignored -
peer becomes UNREA
On 25 Mar 2010, at 10:18, Asterisk wrote:
> How is it possible that the peer becames UNREACHABLE eventhough Wireshark
> logged its proper response?
Wireshark received it, doesn't mean Asterisk did. what does a sip debug in
Asterisk show?
S
--
__
Hi guys,
I have one tricky question regarding SIP peers becoming unreachable.
I was logging the network traffic with Wireshark, and this is what it logged:
10:22:33.319719000 == sent from Asterisk to the phone:
OPTIONS sip:mytestph...@172.11.8.30 SIP/2.0
Via: SIP/2.0/UDP 172.32.0.201:5060;branch
