-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
presence (BLFs) not working via wss #398
Comments
FreeSWITCH Version 1.10.2-release-13-f7bdd3845a~64bit (-release-13-f7bdd3845a 64bit) |
on a later run, with a different subscription, I saw with presence debug that it tries to send the notify, but nothing goes out... `2020-02-20 19:09:19.181709 [NOTICE] sofia_presence.c:2790 SEND PRESENCE 2020-02-20 19:09:19.181709 [ERR] sofia_presence.c:2304 SEND PRES NOTIFY: 2020-02-20 19:09:19.181709 [NOTICE] sofia_presence.c:2790 SEND PRESENCE 2020-02-20 19:09:19.181709 [ERR] sofia_presence.c:2304 SEND PRES NOTIFY: |
|
I don't think this was ever intended to work via WSS. |
ping... is probably not such a big bug... just getting the outbound socket right... or there is more to it? |
@gmaruzz seems it isn't bug from FreeSWITCH. It seems you are using SIP.js, right? If yes then seems bug from SIP.js because it's sending contact header |
anshkatriya: |
Brian:
I made a quick and dirty patch, attached |
@mjerris : I added a patch ^ that makes it work, is probably a bad patch in many aspects, but gives you an hint :) |
I'm also having the same problem. I was be able to fix the problem setting these params. However it's not working right now.
|
We adapted the patch also for the |
So there is no default fix from both ends right? |
if you subscribe via wss you get a correct 202 Accepted
But you will never get any NOTIFYs, they are not sent at all by FS
`SUBSCRIBE sip:[email protected] SIP/2.0
Via: SIP/2.0/WSS sfrf189ajb4d.invalid;branch=z9hG4bK1361360
Max-Forwards: 70
To: sip:[email protected]
From: sip:[email protected];tag=daqq4ltf69
Call-ID: 7f897lg1unplj6hqbnef
CSeq: 9414 SUBSCRIBE
Proxy-Authorization: Digest algorithm=MD5, username="1010", realm="192.168.10.1", nonce="61d1bc7a-ccc4-4ef7-975f-9ebe9507b249", uri="sip:[email protected]", response="8366b2a0e852276ddc3a22bddefb08d8", qop=auth, cnonce="5vpou1gt696t", nc=00000001
Event: presence
Expires: 3600
Contact: sip:[email protected];transport=wss
Allow: ACK,CANCEL,INVITE,MESSAGE,BYE,OPTIONS,INFO,NOTIFY,REFER
Supported: outbound
User-Agent: SIP.js
Content-Length: 0
SIP/2.0 202 Accepted
Via: SIP/2.0/WSS sfrf189ajb4d.invalid;branch=z9hG4bK1361360;received=192.168.10.32;rport=42396
From: sip:[email protected];tag=daqq4ltf69
To: sip:[email protected];tag=T7acd6tRLtjW
Call-ID: 7f897lg1unplj6hqbnef
CSeq: 9414 SUBSCRIBE
Contact: sip:[email protected]:5060
Expires: 3600
User-Agent: FreeSWITCH
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE
Supported: timer, path, replaces
Allow-Events: talk, hold, conference, presence, as-feature-event, dialog, line-seize, call-info, sla, include-session-description, presence.winfo, message-summary, refer
Subscription-State: active;expires=3600
Content-Length: 0
`
The text was updated successfully, but these errors were encountered: