Quantcast
Channel: Developer Group
Viewing all articles
Browse latest Browse all 1888

Forum Post: Diva Management API issue

$
0
0
Hello everyone I have an issue on Diva Mgmt API and it occurred intermittently. I'm using Diva V-2PRI HS board for data modem and using the latest SDK and SR8.5 WIN I think it is caused by SDK issue because I just compiled management samples offered by SDK. We use it for monitoring and it can't affect for service operating. But if the end user know this case, it may be serious problems. In my investigation, I think it may be caused by DID-Length difference. So if possible I'd like to know how to modify DID-Length value.  And somebody who know this would you please comment me? 17:40:13.883 L 3 rw- Ascii 1 Config\DID-Special-Number = "" 17:40:13.883 L 3 rw- UInt 2 Config\DID-Collect-Timeout = 0 17:40:13.883 L 3 rw- UInt 2 Config\DID-Collect-NoCPN-Timeout = 0 17:40:13.883 L 3 rw- UInt 1 Config\Version = 0 17:40:13.883 L 3 rw- UInt 1 Config\ DID-Length = 3 17:40:13.883 L 3 rw- Bool 1 Config\Ringertone = FALSE 17:40:13.883 L 3 rw- UInt 2 Config\Alert-Timeout = 6000 17:40:13.883 L 3 rw- UInt 2 Config\Redial-Timeout = 0 17:40:13.883 L 3 rw- UInt 1 Config\Redial-Attempts = 0 17:40:13.883 L 3 rw- Bool 1 Config\NT = FALSE 17:40:13.883 L 3 r-- Bool 1 Config\PRI = TRUE 17:40:13.883 L 3 rw- Bool 1 Config\GlobalCRs = TRUE 17:40:13.883 L 3 rw- Bool 1 Config\NoOrderCheck = FALSE   Symptom In case of using library for extracting caller number there's some troubles that last word with garbage data 1   Ex. normal data : 24710411 [date time] Framing:  Modem Async(9) [date time] Layer2 Protocol: V.42(7) [date time] Layer3 Protocol: Transparent(4) [date time] Local Address: 247104116 (abnormal) [date time] Remote Address: 15998741 include dimgmtif.h typedef struct _B_CHANNEL { DWORD m_Framing; DWORD m_LineState; DWORD m_Layer2Protocol; DWORD m_Layer3Protocol; DWORD m_LineType; char m_RemoteAddress[MAX_PARAM_LEN]; char m_RemoteSubAddr[MAX_PARAM_LEN]; char m_LocalAddress[MAX_PARAM_LEN]; char m_LocalSubAddr[MAX_PARAM_LEN]; char m_BC[MAX_PARAM_LEN]; char m_HLC[MAX_PARAM_LEN]; char m_LLC[MAX_PARAM_LEN]; DWORD m_dwCharges; DWORD m_dwCallReference; DWORD m_dwLastDiscCause; char m_UserID[MAX_PARAM_LEN]; } B_CHANNEL_INFO; Best regards JH Chang

Viewing all articles
Browse latest Browse all 1888

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>