Closed ljpmingyue closed 2 weeks ago
Can someone please help me check this issue? Thank you
Sorry, there is an issue with the picture provided. In fact, the Event and Expires fields were added later, but the result is still the same
As the remote is the one deciding to reject it, you can check the remote log for the reason of such rejection.
Currently the issue page is for bug report or feature request only, not for asking enquiries.
Describe the bug
The PJSIP library sends subscribe messages, but the receiver of the Exosip library classifies the messages into the message class instead of subscribe class,and during the reprocessing process, exosip directly replied with 400。When I want to reply, prompt me that the message has already been replied to。But when I use the exosip library to send subscribe messages, the receiving end can process and reply normally
Steps to reproduce
I am sending the code for implementing subscribe messages using the pjsip library below. May I ask if there are any issues with my implementation
PJSIP version
2.13
Context
pj_status_t send_subscribe(pjsip_endpoint endpt, const pj_str_t local_uri, const pj_str_t target_uri) { pj_pool_t pool; pjsip_tx_data *tdata; pj_status_t status;
}
int main() { pj_status_t status; pjsip_endpoint *endpt; pj_caching_pool cp; pj_str_t target_uri = pj_str(SIP_TARGET);
}
Log, call stack, etc