VS2013下編譯osip和exosip的5.0版本靜態庫及搭建和簡單例子的實現

阿新 • • 發佈：2019-02-02

# include <eXosip2/eXosip.h>
# include <stdio.h>
# include <stdlib.h>
# include <Winsock2.h>

int main(int argc, char *argv[])
{
struct eXosip_t *context_eXosip = eXosip_malloc();
eXosip_event_t *je = NULL;
osip_message_t *ack = NULL;
osip_message_t *invite = NULL;
osip_message_t *answer = NULL;
sdp_message_t *remote_sdp = NULL;
int call_id, dialog_id;
int i, j;
//int id;
char *sour_call = "sip:

[email protected]";
char *dest_call = "sip:[email protected]:15060";//client ip
//char command;
char tmp[4096];
//char localip[128];
int pos = 0;
//初始化sip
i = eXosip_init(context_eXosip);
if (i != 0)
{
printf("Can't initialize eXosip!\n");
return -1;
}
else
{
printf("eXosip_init successfully!\n");
}
i = eXosip_listen_addr(context_eXosip, IPPROTO_UDP, NULL, 15061, AF_INET, 0);
if (i != 0)
{
eXosip_quit(context_eXosip);
fprintf(stderr, "eXosip_listen_addr error!\nCouldn't initialize transport layer!\n");
}
for (;;)
{
//偵聽是否有訊息到來
je = eXosip_event_wait(context_eXosip, 0, 50);
//協議棧帶有此語句,具體作用未知
eXosip_lock(context_eXosip);
eXosip_default_action(context_eXosip, je);
//eXosip_automatic_refresh(context_eXosip);
eXosip_unlock(context_eXosip);
if (je == NULL)//沒有接收到訊息
continue;
// printf ("the cid is %s, did is %s/n", je->did, je->cid);
switch (je->type)
{
case EXOSIP_MESSAGE_NEW://新的訊息到來
printf(" EXOSIP_MESSAGE_NEW!\n");
if (MSG_IS_MESSAGE(je->request))//如果接受到的訊息型別是MESSAGE
{
{
osip_body_t *body;
osip_message_get_body(je->request, 0, &body);
printf("I get the msg is: %s\n", body->body);
//printf ("the cid is %s, did is %s/n", je->did, je->cid);
}
//按照規則，需要回復OK資訊
eXosip_message_build_answer(context_eXosip, je->tid, 200, &answer);
eXosip_message_send_answer(context_eXosip, je->tid, 200, answer);
}
break;
case EXOSIP_CALL_INVITE:
//得到接收到訊息的具體資訊
printf("Received a INVITE msg from %s:%s, UserName is %s, password is %s\n", je->request->req_uri->host,
je->request->req_uri->port, je->request->req_uri->username, je->request->req_uri->password);
//得到訊息體,認為該訊息就是SDP格式.
remote_sdp = eXosip_get_remote_sdp(context_eXosip, je->did);
call_id = je->cid;
dialog_id = je->did;

eXosip_lock(context_eXosip);
eXosip_call_send_answer(context_eXosip, je->tid, 180, NULL);
i = eXosip_call_build_answer(context_eXosip, je->tid, 200, &answer);
if (i != 0)
{
printf("This request msg is invalid!Cann't response!\n");
eXosip_call_send_answer(context_eXosip, je->tid, 400, NULL);
}
else
{
/*snprintf(tmp, 4096,
"v=0\r\n"
"o=anonymous 0 0 IN IP4 0.0.0.0\r\n"
"t=1 10\r\n"
"a=username:rainfish\r\n"
"a=password:123\r\n");
*/
//設定回覆的SDP訊息體,下一步計劃分析訊息體
//沒有分析訊息體，直接回復原來的訊息，這一塊做的不好。
osip_message_set_body(answer, tmp, strlen(tmp));
osip_message_set_content_type(answer, "application/sdp");

eXosip_call_send_answer(context_eXosip, je->tid, 200, answer);
printf("send 200 over!\n");
}
eXosip_unlock(context_eXosip);

//顯示出在sdp訊息體中的attribute 的內容,裡面計劃存放我們的資訊
printf("the INFO is :\n");
while (!osip_list_eol(&(remote_sdp->a_attributes), pos))
{
sdp_attribute_t *at;

at = (sdp_attribute_t *)osip_list_get(&remote_sdp->a_attributes, pos);
printf("%s : %s\n", at->a_att_field, at->a_att_value);//這裡解釋了為什麼在SDP訊息體中屬性a裡面存放必須是兩列

pos++;
}
break;
case EXOSIP_CALL_ACK:
printf("ACK recieved!\n");
// printf ("the cid is %s, did is %s/n", je->did, je->cid);
break;
case EXOSIP_CALL_CLOSED:
printf("the remote hold the session!\n");
// eXosip_call_build_ack(dialog_id, &ack);
//eXosip_call_send_ack(dialog_id, ack);
i = eXosip_call_build_answer(context_eXosip, je->tid, 200, &answer);
if (i != 0)
{
printf("This request msg is invalid!Cann't response!\n");
eXosip_call_send_answer(context_eXosip, je->tid, 400, NULL);

}
else
{
eXosip_call_send_answer(context_eXosip, je->tid, 200, answer);
printf("bye send 200 over!\n");
}
break;
case EXOSIP_CALL_MESSAGE_NEW://至於該型別和EXOSIP_MESSAGE_NEW的區別，原始碼這麼解釋的
/*
// request related events within calls (except INVITE)
EXOSIP_CALL_MESSAGE_NEW, < announce new incoming request.
// response received for request outside calls
EXOSIP_MESSAGE_NEW, < announce new incoming request.
我也不是很明白，理解是：EXOSIP_CALL_MESSAGE_NEW是一個呼叫中的新的訊息到來，比如ring trying都算，所以在接受到後必須判斷
該訊息型別，EXOSIP_MESSAGE_NEW而是表示不是呼叫內的訊息到來。
該解釋有不妥地方，僅供參考。
*/
printf(" EXOSIP_CALL_MESSAGE_NEW\n");
if (MSG_IS_INFO(je->request)) //如果傳輸的是INFO方法
{
eXosip_lock(context_eXosip);
i = eXosip_call_build_answer(context_eXosip, je->tid, 200, &answer);
if (i == 0)
{
eXosip_call_send_answer(context_eXosip, je->tid, 200, answer);
}
eXosip_unlock(context_eXosip);
{
osip_body_t *body;
osip_message_get_body(je->request, 0, &body);
printf("the body is %s\n", body->body);
}
}
break;
default:
printf("Could not parse the msg!\n");
}
}
}

VS2013下編譯osip和exosip的5.0版本靜態庫及搭建和簡單例子的實現

VS2013下編譯osip和exosip的5.0版本靜態庫及搭建和簡單例子的實現

Linux系統下 MySQL 5.7和8.0 版本安裝指南

iOS 9 平臺上 AFNetworking 框架 3.0 版本號解決的問題和問題解決

【軟件編譯】vs2013下編譯notepad++源碼

在VS2013下編譯json-c庫，並簡單生成json格式數據

Win 7 下安裝 MIB-BROWSER 8.0 版本

ubuntu下同時安裝和使用不同版本的庫

Ubuntu下編譯SqlCipher以及解密微信資料庫EnMicroMsg.db過程和坑

Ubuntu18.04下安裝配置Caffe-SSD-GPU版本並MNIST模型測試和matlab caffe介面測試

jiacrontab 1.4.0 版本釋出，任務定時和常駐管理工具

mysql 5.5和5.6版本關於timestamp插null和0的處理

Centos6下編譯安裝gcc6.4.0

編譯原理(九) LR(0)文法分析法(演算法描述和C++程式碼實現)

[筆記]Win10下編譯Tesseract-OCR 4.0

記levelDB在vs2013下編譯及測試過程

linux下g++ 編譯時動態庫和靜態庫的連結和標頭檔案問題

CUDA8.0和9.0版本切換

[環境配置]Ubuntu16.04下編譯安裝gcc6.3.0

Bminer從11.0.0版本開發支援Ethash (ETH) 和Tensority (BTM) 的雙挖

Centos 6.5 X64 環境下編譯 hadoop 2.6.0 --已驗證

VS2013下編譯osip和exosip的5.0版本靜態庫及搭建和簡單例子的實現

相關推薦