< Previous by Date | Date Index | Next by Date > |
< Previous in Thread | Thread Index | Next in Thread > |
makeRegistration with a separate UserProfile is exactly what I am doing: ----- resip::SharedPtr<resip::UserProfile> newUserProfile(new resip::UserProfile()); // Set the outbound proxy to the new user profile newUserProfile->setOutboundProxy(url.uri()); resip::SharedPtr<resip::SipMessage> sipMessage = dum.makeRegistration( to, newUserProfile, new ResipAppDialogSet(*this, dum, strUuid.c_str())); // Modify the Request-Uri header resip::RequestLine rLine = sipMessage->header(resip::H_RequestLine::sGet()); rLine.uri() = url.uri(); sipMessage->header(resip::H_RequestLine::sGet()) = rLine; // Remove the existing Contact header sipMessage->header(resip::H_Contacts::sGet()).clear(); // Add the Contact header received in parameter for (size_t i = 0; i < vContact.size(); ++i) { sipMessage->header(resip::H_Contacts::sGet()).push_back(vContact[i]); } dum.send(sipMessage); ----- When a trace the code I can see that the object DialogSet::mClientRegistration are different for both registrations. But the ClientRegistrationHandle passed to ClientRegistrationHandler::onSuccess(...) is always the same. I validated that the registration messages were good by looking at them with wire shark. Francis
Express yourself with free Messenger emoticons. Get them today! |