Acme Packet (MOSC)

MOSC Banner

IWF H323 to SIP in access deployment with no registration

edited Jun 26, 2017 5:00AM in Acme Packet (MOSC) 7 commentsAnswered

Hi,

 

I'm trying to configure IWF for H323 to SIP video (h264) calls in an access scenario with no endpoint registration.

 

Endpoint --(H323)--> SBC --(SIP)--> MCU

 

I have the calls being placed through the SBC to the MCU but the header is not formatted in the manner I need.

 

When placing an H.323 call to the SBC to be interworked to SIP the destination address: h323-ID: test1@company.com does not get translated into a valid SIP TO header. Instead of the expected SIP URI test1@company.com I get instead To: <sip:192.168.30.211:5060>, which the MCU does not recognise.

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center