There is no way to instruct SIP stack to add the header. It does that by itself when IPsec is used and the network and location information are available.
Type: Posts; User: jp40; Keyword(s):
There is no way to instruct SIP stack to add the header. It does that by itself when IPsec is used and the network and location information are available.
The header is automatically inserted to SIP requests when IPsec is in use, provided that the network information that is put into the P-Access-Network-Info is also available.
Certain SIP headers are treated as private and can't be added by application. P-Access-Network-Info is one of them.
Hi,
Unfortunately the headers can't be removed from the ACK, if they were present in the INVITE.
Hi bifihi,
The (proxy)-authorization headers are copied from INVITE to ACK, that's why clearing the cache does not cause ACK to be sent without them.
-jp40
Hi,
Maybe you got the UMTS Cell Identity, which is a 28 bit value.
-jp40
Hi,
CSIPRequestElements has a function CSeqHeader() for getting the CSeq.
-jp40
What is the expires value in the 200 OK?
-jp40
Hi,
The REGISTER request is retransmitted (if UDP is used) until a final response has been received or until the transaction timeouts.
-jp40
Hi,
When you create the CSIPProfileRegistry, the profile server is started and looks through all the existing SIP profiles and registers those that are configured "always on".
Other SIP profiles...
Hi,
Have you obtained an instance of the CSIPProfile before the registration is done?
class MSIPProfileRegistryObserver has a comment related to the events:
/**
*...
Hi,
From the description you gave it sounds like the second SIP request is treated like a retransmission of the previous one.
If the requests have same branch parameter in the Via-header, then...
Hi,
You can use CSIPExtensionHeader for adding it.
CSIP::SetSecurityHandlingL is only present in the Symbian OS 9.5 onwards.
Hi,
With CSIP::SetSecurityHandlingL() you can bypass the SIP stack's security handling, and then the 401/407 responses would get passed to the application.
Hi,
Since the emulator does not have the USIM card, the AKA challenges can't be properly tested with it.
You'd need to implement the IMS authentication and authorization algorithms that are...
Hi,
I looked the logs of your first post, I they look a bit strange:
SIPSecSIMCredProv:AuthenticatedL
SIP: lengths IK=16,CK=16,IMPI=0,RES=16,AUTS=0
SIP: IK=
SIP: 03 03 03 03 03 03 03 03 03...
Hi,
In this case the 401 contains AKA challenge, and such challenges are handled by the USIM card, and are not passed to application.
USIM provides the credentials and a new REGISTER is sent...
Hi,
You can use the CUri8 class instead.
Port and loose routing are set by adding the port number and ";lr" to the proxy/registrar URIs.
E.g. CSIPConcreteProfile::SetServerL(KSIPOutboundProxy, _L8("sip:1.1.1.1:222;lr"));
Hi miikkis,
After setting the profile parameters, you have to call CSIPManagedProfileRegistry::SaveL(), and then the new values will be used.
-jp40
The error happens since some header of the 401 has a parameter two times on it.
-jp40
At least a number like 123456789012345 still fits into a TInt64.
You can try this code:
TBuf8<128> zVeryBigNumber(_L8("123456789012345"));
TInt64 value(0);
TLex8 lex(zVeryBigNumber);...
Hi,
The SIP specific error codes are listed in the header file siperr.h, which also has a short description of each error code.
No other documentation exists for them.
-jp40
Hi,
To-header's tag in the 200 OK response does not cause the -17701 error.
It is a normal behaviour that UAS adds the To-tag.
-jp40