Acme Packet (MOSC)

MOSC Banner

SBC behavior of SIP-I (ISUP) INVITE

edited May 31, 2016 12:06PM in Acme Packet (MOSC) 5 commentsAnswered ✓

Hi All

Upon receiving the SIP Message to ISUP is included, it gives a 400 error in the SBC.

I want to SBC receives an ISUP SIP Message.

Do I need a ISP setting of the SBC?

The following is a SIP Message that contains the ISUP.

INVITE sip:+82220890500@61.43.35.168:5060 SIP/2.0

Via: SIP/2.0/UDP 27.93.181.21:5060;branch=z9hG4bK08B8fbe2dbf42ed7732

From: <sip:+81333475539@27.93.181.21:5060>;tag=gK08051e34

To: <sip:+82220890500@61.43.35.168:5060>

Call-ID: 621318050_60735730@27.93.181.21

CSeq: 2029366139 INVITE

Max-Forwards: 70

Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,OPTIONS

Accept: application/sdp

Contact: <sip:27.93.181.21:5060>

Supported: timer,100rel,precondition

Session-Expires: 1800;refresher=uas

Min-SE: 90

Content-Length:   456

Content-Type: multipart/mixed;boundary=sonus-content-delim

MIME-Version: 1.0

--sonus-content-delim

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

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center