Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

OCL signon fails with status code 0xf5

Status
Not open for further replies.

vmguru

Vendor
Jun 6, 2010
5
US
I'm trying to write a simple OCL OSA application that does a SIGNON and then a MAILBOX READ BY UID in order to retreive all the mailbox profiles on an Octel running release 3.10. And while I can get the call request and call accept to work fine (so the VC is established), nothing I do gets the SIGNON command to work. I've looked at the status log, and the status indicates that it is either my APP ID or my password. It is an OSA app, so the APP ID should be 0xff (255). The password is the same as what is configured under menu 17. I've even tried creating an IVR app with an app ID of "7", so that I could generate the exact signon that is in the documentation - and it too fails in the same way. I've used the X.25 interface monitor to see that the data I'm sending is the data that is being received - byte for byte. My fear is that version 3.10 of the software is incompatible with the OCL documentation I have. Any thoughts?
 
Do you have the feature bit on for OCL? I think it is the CSA feature.

Is this Aria 3.1 or VIS 3.1?

Are you connecting using x.25 or tcp/ip? If tcp/ip there is a 16 byte header that needs to be sent with every message.
 
I can tell you it is not an incompatibility as we have used the OCL and the x.25 interface for years and years. And the LAN interface as well.

255 is used for CSA and that would or should allow you to pull the profile.

is this a 250 or a 350?

Ken Means

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)
 
This is a Sierra platform that is part of a cluster. Does that make a difference? Also, when I look at the status log, it shows the "app id" as 00 (at least, according to the field offsets from the documentation) when it generates the session error. However, I don't know if that is just because no session was ever created. I can see from the packet data that the "app id" is FF.

Below are the features that are enabled:

VPMOD Serial # ........ 30605 STN # 0 Software Release ...... 03.10.70-3

Y 8 - Bulletin Mailbox Y 9 - Centralized System Admin.

10 - Digital Paging 12 - Personal PowerCall

Y 15 - Network Dial-By-Name Y 16 - Call Detail Recording

17 - DB Retrieval - Non-Clustered Y 22 - Voice Forms Mailbox

23 - Monitor Mailbox 24 - Consolidated Messaging

25 - Seamless Messaging 26 - Enhanced Extension Mailbox

27 - Brazil Double Attendant 28 - GR1129

29 - Call Redirect 31 - TCAP Notification

Y 32 - General Line Types Y 34 - RS232 Integration

35 - In-band Integration / ISUP MW 38 - Digit Checking Table

39 - SS7 Option Y 40 - IVR

41 - Equal Access 42 - Message Waiting Count

Y 43 - DTMF Forms Mailbox Y 44 - OctelNet 500

Y 45 - Enhanced Call Processing 46 - Password Reset

Y 47 - Outcalling Y 48 - Information Center Mailboxes

55 - Conference Mailbox Y 56 - Fax Store & Forward

Y 58 - ACP - Multiple System Access Y 59 - ACP - Multiple Terminal Access

Y 60 - Skip Password 61 - Short Message Service

62 - Centralized Network Management Y 63 - Type 77 Mailbox

Y 65 - ANI 70 - Display Password

75 - Call Cases Option 76 - R2 Signaling

Y 77 - Mailbox Move 78 - NT Exchange Line Signaling

79 - Call Sender 80 - Signature Tone

81 - Dial Tone for Outbound Call 82 - Privacy Protection

83 - Apply Patches w/o Eng. Bit 84 - Transfer to Operator

85 - Voice Paging 87 - Competitive VMUIF

Y 88 - TCP/OCL Access 89 - SNMP

Y 90 - LAN Upgrades 91 - Message Notifier Server

92 - ADSI Visual Voicemail Y 94 - Deleted Message Recovery

95 - Retain Extended Absence Greeting 96 - Block Clear Text Password

97 - Simplified Listen Only Mailbox 98 - SMPP Notification

99 - CAMA Mailbox Move
 
I don't know where my OCL book is but when you say sign-on what are you referring to? just the app ID using the password you assigned it in menu 17?

Ken Means

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)
 
I did ultimately get the signon comamnd to work. It turns out that version 3.10 of the Octel software requires a different version ID in the sign on from the one documented in the 2.0 doc set. Anyway, it is working now - thanks!
 
What platform does this run on? I would love to have a copy of this.

Ken Means

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)
 
the software is C-based, running on Linux. I'm new to this forum - how do we chat?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top