Skip to content
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

apps/mwi: why notify and some errors in created request #56

Open
dunst0 opened this issue Mar 22, 2017 · 0 comments
Open

apps/mwi: why notify and some errors in created request #56

dunst0 opened this issue Mar 22, 2017 · 0 comments

Comments

@dunst0
Copy link
Contributor

dunst0 commented Mar 22, 2017

Why was the method changed from PUBLISH to NOTIFY? apps/mwi/mwi.cpp#L109-L116

This module pre sets a Route-Header to the presence_server, which leads to the following SIP request:

NOTIFY sip:x.x.x.x SIP/2.0
Via: SIP/2.0/UDP x.x.x.y;branch=z9hG4bKbQU7laXT;rport
From: <sip:[email protected]>;tag=177BE301-58D2463A00053860-1F4F4700
To: domain.de
CSeq: 10 NOTIFY
Call-ID: [email protected]
Max-Forwards: 70
Event: message-summary
Subscription-State: active
Content-Type: application/simple-message-summary
Route: <sip:[email protected]>
Contact: <sip:x.x.x.y:5060;transport=udp>
Content-Length: 105

Messages-Waiting: yes
Message-Account: sip:[email protected]
Voice-Message: 1/0 (1/0)

I would like to use the module but not as it is, because it doesn't work for me. Are there any problems regarding a change back to PUBLISH method or should it be configurable? The To header will be bad sip, so I will fix it and I will remove the preset route set and let it be set in the config, because I don't need it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant