Pound Sign Translation And Encoding Problem
Last updated on OCTOBER 10, 2016
Applies to:Oracle Communications Service Broker - Version 188.8.131.52 and later
Information in this document applies to any platform.
When a subscriber is using a pound sign (#), for example when dialing #147, the OCSB sends a SIP requests towards a Number Normalization service which replies with 302 using the same SIP request Object and adds a Contact header.
The problem is that the Pound sign is encoded in the INVITE URI field of the SIP request sent by OCSB as a %23147.
The value in the TO address field is not encoded. When the Number Normalization service in the CCAS replies using the same request and adding the SIP Contact header, the Contact header as well as the Two fields are encoded as %023147 which causes that the OCSB to send Camel Connect instead of Continue.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms