Ignore:
Timestamp:
Jan 13, 2007 11:22:40 PM (14 years ago)
Author:
bennylp
Message:

More work on ticket #50: binding of PJSUA-API account to specific transport, and minor fixes in PJSIP core implementation. Tested okay.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • pjproject/trunk/pjsip/src/pjsua-lib/pjsua_call.c

    r875 r881  
    331331    call->user_data = user_data; 
    332332 
     333    /* If account is locked to specific transport, then lock dialog 
     334     * to this transport too. 
     335     */ 
     336    if (acc->cfg.transport_id != PJSUA_INVALID_ID) { 
     337        pjsip_tpselector tp_sel; 
     338 
     339        pjsua_init_tpselector(acc->cfg.transport_id, &tp_sel); 
     340        pjsip_dlg_set_transport(dlg, &tp_sel); 
     341    } 
     342 
    333343    /* Set dialog Route-Set: */ 
    334344    if (!pj_list_empty(&acc->route_set)) 
     
    620630    inv->mod_data[pjsua_var.mod.id] = call; 
    621631 
     632    /* If account is locked to specific transport, then lock dialog 
     633     * to this transport too. 
     634     */ 
     635    if (pjsua_var.acc[acc_id].cfg.transport_id != PJSUA_INVALID_ID) { 
     636        pjsip_tpselector tp_sel; 
     637 
     638        pjsua_init_tpselector(pjsua_var.acc[acc_id].cfg.transport_id, &tp_sel); 
     639        pjsip_dlg_set_transport(dlg, &tp_sel); 
     640    } 
    622641 
    623642    /* Must answer with some response to initial INVITE. 
Note: See TracChangeset for help on using the changeset viewer.