Re: [reSIProcate] SUBSCRIBE to LCS failing
One idea may help.
Would you use Windows Messenger ( the latest version)
to communicate with LCS and capture the SIP message
with ethereal, and send the same message emited from
Windows Messenger to LCS?
Windows Messenger should be able to communicate with
LCS easily.
Never try this, since I have no LCS on site.
kaiduan
--- Chris Rigg <cdrigg@xxxxxxxxxxx> wrote:
> Hey Resip folks,
>
> I'm wondering if one of you SIP gurus out there can
> tell me what's wrong
> with my SUBSCRIBE that I'm sending (from my resip
> app) to an LCS Access
> Proxy (configured for Federation mode). LCS is
> complaining about my
> Contact field and I have NO idea why. Hopefully the
> answer will be
> obvious to one of you folks out there.
>
> Here is the SUBSCRIBE I'm sending:
>
> SUBSCRIBE sip:naim@xxxxxxxxxx;transport=TLS SIP/2.0
> To: <sip:naim@xxxxxxxxxx>
> From: "Chris"
> <sip:cdrigg@xxxxxxx>;tag=1928301774;epid=1234567890
> Via: SIP/2.0/TLS
> 10.94.150.51:5061;branch=z9hG4bKnashds8;rport
> Call-ID: a84b4c76e66710
> CSeq: 1 SUBSCRIBE
> Contact:
>
<sip:cdrigg@xxxxxxx:5061;transport=TLS;maddr=bldr-ccm51.sip.com;epid=1234567890>
> Max-Forwards: 70
> Accept: application/pidf+xml
> User-Agent: SIPimp.org/0.2.5 (curses)
> Event: presence
> Content-Length: 0
>
> Here is the Error response I receive back from the
> LCS Access Proxy:
>
> SIP/2.0 400 Invalid Contact information
> Via: SIP/2.0/TLS
>
10.94.150.51:5061;branch=z9hG4bKnashds8;rport;received=10.94.150.51;ms-received-port=53629;ms-received-cid=100
> From: "Chris"
> <sip:cdrigg@xxxxxxx>;tag=1928301774;epid=1234567890
> To:
>
<sip:naim@xxxxxxxxxx>;tag=6874DB54FE540E7746B0FA5A3878A44F
> Call-ID: a84b4c76e66710
> CSeq: 1 SUBSCRIBE
> Content-Length: 0
>
> In the error logs on the LCS AP, I see the
> following:
>
> exit. trying to provide a contact host different
> from the source of
> the request.
> exit. failed to process contact entry. Returned
> C3ED180F(SIPPROXY_E_CONTACT_NOT_AUTHORIZED)
>
> Not sure what it means by "different from the source
> of the request". I
> assume it's complaining about my maddr field but I
> don't know why. I can
> ping that exact maddr FQDN from the AP so I don't
> know what the problem
> is. Here is a SUBSCRIBE that LCS sends to me (for
> comparison)...
>
> SUBSCRIBE sip:naim@xxxxxxxxxx SIP/2.0
> Contact:
>
<sip:cdrigg@xxxxxxxxxxx:5060;transport=tls;maddr=bldr-ccm4.lcs-im2.com;epid=a77cce963d>
> Via: SIP/2.0/TLS
>
10.94.150.104:1566;branch=z9hG4bK8C1EC119.2BD55AAA;branched=FALSE;ms-internal-info="dasUZ47s2g9aGGVkRjBLk5UoyXXaMA"
> Max-Forwards: 68
> ms-asserted-verification-level:
> ms-source-verified-user=verified
> Via: SIP/2.0/TLS
>
10.94.150.90:2350;branch=z9hG4bKEFC20B43.887A39B8;branched=FALSE;ms-received-port=2350;ms-received-cid=13f00
> Via: SIP/2.0/TLS
>
10.94.150.90:2501;ms-received-port=2501;ms-received-cid=e300
> From: "Chris"
>
<sip:cdrigg@xxxxxxxxxxx>;tag=e9120583b8;epid=a77cce963d
> To: <sip:naim@xxxxxxxxxx>
> Call-ID: d24ea4e1799d4788ac146d7cdfe90d6a
> CSeq: 1 SUBSCRIBE
> User-Agent: LCC/1.3
> Event: presence
> Accept: application/xpidf+xml, text/xml+msrtc.pidf,
> application/pidf+xml
> Supported: com.microsoft.au
>
>
> Any ideas??
>
> Thanks,
> Chris
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel@xxxxxxxxxxxxxxxxxxx
>
https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com