I have been looking at the source code. I guess that the failure lays
somewhere in the next lines of sipp.cpp :
/* This is simpler than doing a regular tolower, because there are
no
branches.
* We also inline it, so that we don't have function call overheads.
*
* An alternative to a table would be to do (c | 0x20), but that only
works if
* we are sure that we are searching for characters (or don't care if
they are
* not characters. */
unsigned char inline mytolower(unsigned char c) {
return tolower_table[c];
}
char * strcasestr2(char *s, char *find) {
char c, sc;
size_t len;
if ((c = *find++) != 0) {
c = mytolower((unsigned char)c);
len = strlen(find);
do {
do {
if ((sc = *s++) == 0)
return (NULL);
} while ((char)mytolower((unsigned char)sc) != c);
} while (strncasecmp(s, find, len) != 0);
s--;
}
return ((char *)s);
}
but I cannot give a solution for the problem. I hope that this helps
for a faster answer.
Thanks in advance.
Miguel
Quoting "Miguel.Gomez" <[EMAIL PROTECTED]>:
> Hi.
>
> We are testing sipp2-0 against OpenIMSCore. We detected a failure
in the way
> SIPp parses Record-Routes. To reproduce it, just follow the example
> in the wiki
> (http://sipp.sourceforge.net/wiki/index.php/INVITE).
>
>
> In the attached trace capture, you can checked that this results on
> some missing
> '>' characters:
>
> SIP/2.0 180 Ringing
> Record-Route: <sip:[EMAIL PROTECTED]:4060;lr,
> <sip:[EMAIL PROTECTED]:6060;lr,
<sip:[EMAIL PROTECTED]:6060;lr,
> <sip:[EMAIL PROTECTED]:4060;lr>
>
> It is really annoying, because it affects the whole behaviour of
> imscore, since
> the CSCFs don't recognize the sequence of SIP messages.
>
> Miguel Gomez
I have been looking at the source code. I guess that the failure lays
somewhere
in the next lines of sipp.cpp :
/* This is simpler than doing a regular tolower, because there are
no
branches.
* We also inline it, so that we don't have function call overheads.
*
* An alternative to a table would be to do (c | 0x20), but that only
works if
* we are sure that we are searching for characters (or don't care if
they are
* not characters. */
unsigned char inline mytolower(unsigned char c) {
return tolower_table[c];
}
char * strcasestr2(char *s, char *find) {
char c, sc;
size_t len;
if ((c = *find++) != 0) {
c = mytolower((unsigned char)c);
len = strlen(find);
do {
do {
if ((sc = *s++) == 0)
return (NULL);
} while ((char)mytolower((unsigned char)sc) != c);
} while (strncasecmp(s, find, len) != 0);
s--;
}
return ((char *)s);
}
but I cannot give a solution for the problem. I hope that this helps
for a
faster answer.
Thanks in advance.
Miguel
Quoting "Miguel.Gomez" <[EMAIL PROTECTED]>:
> Hi.
>
> We are testing sipp2-0 against OpenIMSCore. We detected a failure
in the way
> SIPp parses Record-Routes. To reproduce it, just follow the example
> in the wiki
> (http://sipp.sourceforge.net/wiki/index.php/INVITE).
>
>
> In the attached trace capture, you can checked that this results on
> some missing
> '>' characters:
>
> SIP/2.0 180 Ringing
> Record-Route: <sip:[EMAIL PROTECTED]:4060;lr,
> <sip:[EMAIL PROTECTED]:6060;lr,
<sip:[EMAIL PROTECTED]:6060;lr,
> <sip:[EMAIL PROTECTED]:4060;lr>
>
> It is really annoying, because it affects the whole behaviour of
> imscore, since
> the CSCFs don't recognize the sequence of SIP messages.
>
> Miguel Gomez
------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/
_______________________________________________ Sipp-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sipp-users
