reSIProcate

Mailing Lists

Source Code

Google Search:



< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index  

Re: [reSIProcate-users] Problem with Altitude uCI 7.1

'%' is an illegal character in uris, except in the context of escaping. So, if the switch _really_ wanted to put a '%' there, it would have to read "sip:6414%25trusde03@xxxxxxxxxxxxx" (since %25 is the escaped encoding of '%'). 

If you wish to interop with the broken implementation anyway, you can comment out Uri.cxx:23 and recompile.

Also, I should note that SipMessage::isInvalid() is meant only to catch semantic brokenness in the SipMessage as a whole. Right now this includes multiple headers that are supposed to be single (ie, To, From, Call-Id, etc), and incorrect Content-Length (inconsistent with the length of the datagram; of course this does not apply for stream-based transports). Malformed header field values are not taken into account here. For more info on checking for malformed header field values, see https://www.resiprocate.org/Use_Overview#Headers

Best regards,
Byron Campen

We are having a problem with the Altitude uCI 7.1 switch, recently upgraded to patch level 380. At the same time, the Altitude vBox (IP PVB) was upgraded to version 3.5, patch level 380.

 

Since the upgrade of this switch, certain SIP packets are failing the buffer parsing process, inside the dataUnescaped function. They fail the anchor position check, and if forced past that check they fail the Hex test because, well, it’s not hex.

 

I believe I’ve traced the problem packets to any containing a ‘%’ in the sip address, which in glancing at the code is expected to be an escape character.

 

So Sip packets with an address of “sip:0130119@xxxxxxxxxxxx” work just fine.

 

Sip packets with an address of “sip:6414%trusde03@xxxxxxxxxxxxx” cause problems in resip.

 

We only started getting packets resembling the second example after the upgrade to the switch. They are common, but not all packets are like that.

 

I tried filtering by the SipMessage IsInvalid check, but they pass the valid test.

 

Any help on this subject would be greatly appreciated.

 

Thanks,

 
 

 

Jared Thigpen

System Team Developer

jared.thigpen@xxxxxxxxx

ph:   214.981.3112

www.autonomy.com

 

CONFIDENTIALITY NOTICE: This communication and any files or attachments transmitted with it contain information that is confidential to the sender, privileged or exempt from disclosure under applicable law. It is intended solely for the use of the individual or the entity to which it is addressed. If you are not the intended recipient(s), you are hereby notified that any use, dissemination, or copying of this communication is strictly prohibited; please do not read, copy, use or disclose the content of this communication to others. If you have received this communication in error, please forward it, in its entirety, to the network manager at administrator@xxxxxxxxx and delete it.  Thank you.

 
 
_______________________________________________
resiprocate-users mailing list

Attachment: smime.p7s
Description: S/MIME cryptographic signature