Quantcast
Channel: Dialogic PowerMedia HMP GlobalCall and R4 API - Recent Threads
Viewing all 1151 articles
Browse latest View live
↧

SIP Instant Messaging via Dialogic HMP

December 16, 2015, 9:33 pm
$
0
0

Hi,

I am trying to use Dialogic HMP Win 3.0 to send SIP IM messages (RFC 3428).

I believe the code will look similar to this:


	long crn; // initialised by gc_MakeCall()
	GC_PARM_BLKP parameterBlock = nullptr;

	// Initialize the parameterBlock... but this is incomplete
	if (gc_util_insert_parm_val(&parameterBlock, IPSET_MSG_SIP, IPPARM_MSGTYPE, sizeof(int), IP_MSGTYPE_SIP_MESSAGE) < 0 || gc_util_insert_parm_ref_ex(&parameterBlock, IPSET_SIP_MSGINFO, IPPARM_TO_DISPLAY, (unsigned long)(message.length() + 1), (void *)message.c_str()) < 0)
	{
		// Log error
		if (parameterBlock != nullptr)
		{
			gc_util_delete_parm_blk(parameterBlock);
		}
		return false;
	}

	// Send the Request
	GC_PARM_BLKP returnBlock = nullptr;
	const unsigned long mode = EV_ASYNC;
	if (gc_Extension(GCTGT_GCLIB_CRN, crn, IPEXTID_SENDMSG, parameterBlock, &returnBlock, mode) == GC_SUCCESS)
	{
		// Success
		gc_util_delete_parm_blk(parameterBlock);
		return true;
	}

But can find no example in the documentation or online.

What additional parameters need to be set when using IP_MSGTYPE_SIP_MESSAGE?

Thanks for your help!

↧
Search

RE: HMP 4.1: how to record voice from IP?

February 25, 2016, 3:58 am
$
0
0

Thank you very much for your code example, but I'm still not able to record voice.

I have attached my source code example, perhaps you'll see what is wrong. Here what my demo application is doing:

1. create 2 imp devices for 2 RTP endpoints
2. create 2 voice devices for play/record functions
3. start media bothway of 2 IP endpoints (first endpoint sends data over IP to second endpoint, loop over IP)
4. listen on second endpoint
5. start recording on voice device 2
6. play wave file on vocie device 1

I don't understand why play is successful, I haven't connected the voice1 channel with the ipm1 channel, why is it working?

Recording doesn't work. If you want to try on your machine, just change the ip addresses.

Thank you.

Best regards.

↧
↧

RE: HMP 4.1: how to record voice from IP?

March 1, 2016, 7:14 am
$
0
0

Hello,

The voice device will play with no errors, whether it is connected to any listener or not. Please try to add ipm_Listen(ipm_dev1, sc_tsinfo_vox1) before starting playing, and it should start working. All the rest looks good.

↧

RE: SIP Instant Messaging via Dialogic HMP

March 1, 2016, 7:26 am
$
0
0

This method can be used from the board level device, or from channel device what is involved in the call. If you use GCTGT_GCLIB_CHAN, the board handle must be specified. For in-call IMs you should use GCTGT_GCLIB_CRN as a target, and provide a real CRN for that call. Also, please check if  

virtBoards[0].E_SIP_MESSAGE_Access = ENUM_Enabled;

is set for gc_Start

↧

RE: HMP 4.1: how to record voice from IP?

March 2, 2016, 4:13 am
$
0
0

Hello,

I have tried to add ipm_Listen(ipm_dev1, sc_tsinfo_vox1) before starting playing but it doesn't help, I'm still recording only silence.

I still don't understand how play can work: how is the dev_vox1 connected to ipm_dev1? How does HMP know that voice sent from dev_vox1 has to be sent over IP via ipm_dev1?

Thanks.

↧
↧

RE: HMP Linux 64 Bit Version

March 2, 2016, 4:28 am
$
0
0

At the moment, you have to install the 32-bit standard libs (like libc) to be able to run HMP on a 64-bit architecture.

I'm also surprised that in 2016 we can still find frameworks (like HMP) which require performance and not natively run in 64-bits!

Please, Dialogic, wake up...

↧

RE: HMP 4.1: how to record voice from IP?

March 3, 2016, 6:53 am
$
0
0

Ok, just to chime in here, you should not be mixing dev_connect with xx_listen APIs on the same devices for routing purposes. It should be one method or the other, not both.  

Also from reading the down from the beginning of the chain, you cannot have a single device being routed in hairpin mode and also perform a play/record at the same time. As that device can only listen to one timeslot at a time. You need an extra resource to accomplish that task.

Thus if you want to IP legs to be listening to each other, you can not also play and record to those same streams as they are only connected together at the IPM level.

Meaning hair-pinned would be:

ipm_getxmitslot (ipmB1C1 tsinfo1)

ipm_getxmitslot(ipmB1C2, tsinfo2)

listen (ipmB1C1, tsinfo2)

listen (ipmB1C2, tsinfo1)

If you need to play or record to those devices, then you would have to unlisten the IPM channel in order to connect to voice device.

The only way of which you can have two legs connected together and then also play file to be heard, all three devices would need to be in a conference.

For the record side you would have to use a transaction record (where you pass both tsinfo of ipmB1C1, and B1C2 timeslots) to the dx_rec call. It would not be listening to the ipm channels via a listen call, as it does it internally.

Jeff

↧

RE: HMP Linux 64 Bit Version

March 3, 2016, 8:52 am
$
0
0

Yea, right now all 32-bit equivalent rpm's for such things like libstdc/c++, glibc, gcc, etc need to be installed as part of linux 64-bit O/S install such that applications can compile and run in 32-bit mode. Support for full 64-bit support libs (at HMP level) is not available right now (HMP only has built fwl and driver at 64-bit currently). Overall, this has been a topic of discussion for a while now, but there are no official plans currently to add 64 lib support. But that does not mean we will not eventually do it.

Jeff

↧
Search

RE: Start pending on Windows 7

March 3, 2016, 10:49 am
$
0
0

I am not sure older vfx board are supported on the newer OS lines from windows. They may have been EOL'ed (end of life) prior to release of win 7 itself and newer releases like 2008 or 2012. As that model would have been replaced by newer HW at the time (likes of D/4pciuf for example). So it may not have been tested at all, not sure though.  What is the specific model number of the board and serial number (two letters followed by 4 digits (and I can try and check).

Jeff

↧
↧

RE: HMP and DNI: number of devices doesn't reflect the license

March 3, 2016, 1:16 pm
$
0
0

Ok, the 2 physical boards refer to:

Brd1 (HMP device) which is allocated features of your license

You should see 37 or 38 dxxx VB in this case to get to 150. Meaning dxxxB1C1 thru dxxxB38C2 (if I did that right).

Brd2: (DNI board) which is only DTI channels.

If the HMP services are started, you can always run devmapdump from DOS prompt and redirect output to a file. That will show you all the ipm and dxx and dti devices enumerated.

Jeff

↧

RE: HMP 4.1: how to record voice from IP?

March 3, 2016, 10:44 pm
$
0
0

I think you have misunderstood what I would like to do. I don't need hairpin mode, the 2 IPM devices are not connected together.

The first IPM device (on the first host interface) send its data over IP to an external router, which routes back the IP traffic to the second IPM device (on the second host interface).

What I'm trying to do:

1. Connect a voice device to an IPM device 1 to be able to play voice, RTP is sent out to the external network over host interface 1 (this is working)

2. Connect a voice device to an IPM device 2 to be able to record voice, RTP is received from the external network over host interface 2

The second part doesn't work. Please have a look at my small code I have attached in my previous post (ipm_record.zip).

Thank you.

↧

RE: HMP and DNI: number of devices doesn't reflect the license

March 3, 2016, 10:58 pm
$
0
0

Thank you very much.

devmapdump shows me everything and it matches my license. I had an error in my application using the SRL functions.

↧

Max Digit Phone Number

March 4, 2016, 10:15 am
$
0
0

Hello All!

I'm having a problem when GLOBAL CALL API. Today I have a solution integrated with AVAYA and everytime DIALOGIC tries make a call avaya only receive the maximum of 12 digits, but I need send 13 to Avaya.

I tried analyze the pdk_us_ls_fxs_io.cdp file that I use, but I did not found any place to configure the max digits to dial. Does anyone have any suggestions?

Regards!

Rafael Neco

↧
↧

RE: SIP Instant Messaging via Dialogic HMP

March 6, 2016, 7:24 pm
$
0
0

You're right, the error was because I wasn't targeting the board level device.

Now I just need to get my request uri formatted properly.

Thanks!

↧

RE: something wrong with modify the RTP address

March 7, 2016, 10:22 am
$
0
0

In most cases I would check the system to make sure firewall is not blocking those specific ports used for RTP streaming. That being 49152 counting up by number ports *2 in your HMP license (rtp & rtcp).

Jeff

↧
Search

something wrong with modify the RTP address

March 6, 2016, 9:53 pm
$
0
0

I test the call,when I find the RTP flow cannot receive,I find that it should modify the RTP address of HMP.

the normal step is.

1.shutdown the ipmedia

2.modify the RTP address

3.start the ipmedia

as a matter of fact,I lost the step 1 and 3.I just modify the HMP-RTP-ADDRESS

so when I dlstop then dlstart .when HMP system cannot start normal.

the follow message:

Mar 6 11:51:03 MediaGateway 01_DM3: Calling /usr/dialogic/bin/dm3kload -f /usr/dialogic/data/hmp2_pdk.bin -g 1
Mar 6 11:51:03 MediaGateway DM3KLOAD[6117]: HMP Enabled Board(s) not found.
Mar 6 11:51:04 MediaGateway ct_intel: Calling /usr/dialogic/init.d/ctplatform/order/01_DM3 stopall
Mar 6 11:51:05 MediaGateway ct_intel: Stopping Telephony System Monitor :
Mar 6 11:51:05 MediaGateway ct_intel: killall -e /usr/dialogic/bin/dlgsysmonitorserver
Mar 6 11:51:05 MediaGateway ct_intel: Shutting Down Timeslot Doler
Mar 6 11:51:06 MediaGateway ct_intel: Shutting Down Timeslot Doler :
Mar 6 11:51:06 MediaGateway ct_intel: killall -e /usr/dialogic/bin/dlgtimeslotdolerserver
Mar 6 11:51:07 MediaGateway ct_intel: Shutting Down Device Mapper :
Mar 6 11:51:07 MediaGateway ct_intel: Calling /etc/redhat-lsb/lsb_killproc devmapserver
Mar 6 11:51:09 MediaGateway ct_intel: Shutting Down RTF Logging Server:
Mar 6 11:51:09 MediaGateway ct_intel: Calling /usr/dialogic/bin/RtfServer stop
Mar 6 11:51:10 MediaGateway ct_intel: Shutting Down OAM Event Service :
Mar 6 11:51:10 MediaGateway ct_intel: killall -e /usr/dialogic/bin/OAMEventService
Mar 6 11:51:53 MediaGateway ct_intel: Starting RTF Logging Server:
Mar 6 11:51:53 MediaGateway ct_intel: Calling /usr/dialogic/bin/RtfServer start
Mar 6 11:51:53 MediaGateway ct_intel: Starting OAM Event Service :
Mar 6 11:51:53 MediaGateway ct_intel: Calling /sbin/runuser -s /bin/bash - -c /usr/dialogic/bin/OAMEventService
Mar 6 11:51:57 MediaGateway ct_intel: Starting Device Mapper :
Mar 6 11:51:57 MediaGateway ct_intel: Calling /etc/redhat-lsb/lsb_start_daemon /usr/dialogic/bin/devmapserver -OAport 12003
Mar 6 11:51:57 MediaGateway ct_intel: Starting Timeslot Doler :
Mar 6 11:51:57 MediaGateway ct_intel: Calling /etc/redhat-lsb/lsb_start_daemon /usr/dialogic/bin/dlgtimeslotdolerserver -OAport 12005
Mar 6 11:51:58 MediaGateway ct_intel: Calling /usr/dialogic/bin/drvload
Mar 6 11:51:58 MediaGateway DM3KLOAD[6444]: HMP Enabled Board(s) not found.
Mar 6 11:51:59 MediaGateway ct_intel: Calling /usr/dialogic/bin/kmbc_load
Mar 6 11:52:00 MediaGateway ct_intel: Starting Telephony System Monitor :
Mar 6 11:52:00 MediaGateway ct_intel: Calling /sbin/runuser -s /bin/bash - -c /usr/dialogic/bin/dlgsysmonitorserver -OAport 12004
Mar 6 11:52:01 MediaGateway ct_intel: /usr/dialogic/bin/hmpd start
Mar 6 11:52:01 MediaGateway ssp_x86Linux_boot: LINOS: ERROR: Failed to open /dev/rtc, errno 2
Mar 6 11:52:11 MediaGateway ct_intel: Starting Board Manager Service :
Mar 6 11:52:11 MediaGateway ct_intel: Calling /sbin/runuser -s /bin/bash - -c /usr/dialogic/bin/bmserver -OAhost 127.0.0.1 -OAport 14000
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: LOGFRAMEWORK : BM_LOG_LEVEL set to Log and Info
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: BOARDMANAGER : Starting Board Manager Server
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: BM_Adaptor : BMProduct[ZVL]
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: BM_Adaptor : IPMSSoftwareVersion[hmp b118-4.1.-1]
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: Adaptor Parser : Processing Adaptor Product : ZVL Adaptor Form factor RMS
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: Adaptor Parser : Parsing Adaptor Configuration file /usr/dialogic/cfg/mitconfig/dalconfig.xml
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: SYSCONTROLLER-OS-Adaptor : Calling Adaptor Device Info Detector Init Method
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: Adaptor Parser : Processing Adaptor Product : ZVL Adaptor Form factor RMS
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: Adaptor Parser : Parsing Adaptor Configuration file /usr/dialogic/cfg/mitconfig/technologydal.xml
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: libdivaadaptor : Calling Adaptor Diva Device Adaptor Init Method
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: DivaAgent-Adaptor : File ipms_diva_devtable_cfg.xml already exists!
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: DivaAgent-Adaptor : Row size is 1
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: Diva Agent Device : Initialized object.
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: DivaAgent-Adaptor : The directory /usr/lib/opendiva/divas/registry/hw/ does not exist
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: DivaAgent-Adaptor : OS Error ID = 2 OS Error String=No such file or directory
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: DivaAgent-Adaptor : Diva- WriteProcFile - error - Can't open pci Driver for initial write
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: DivaAgent-Adaptor : WriteProcFile() Failed.
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: DivaAgent-Adaptor : The number of trunks are 0
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: DivaAgent-Adaptor : Generic failure
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: libdivaadaptor : Adaptor Diva Device Adaptor fail to initialize...
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: libdm3adaptor : Calling Adaptor DM3 Device Adaptor Init Method
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: DM3Agent-Adaptor : No DM3 device in the system
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: DM3Agent-Adaptor : DM3 Agent subsystem: Failed to detect devices
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: libdm3adaptor : Adaptor DM3 Device Adaptor fail to initialize...
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: DevInfo-Adaptor : Fail to get Board List
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: DevInfo-Adaptor : DM3 Agent subsystem: Failed to detect devices
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: SYSCONTROLLER-OS-Adaptor : Adaptor Device Info Detector fail to initialize...
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: SYSCONTROLLER-OS-Adaptor : match devinfo adaptor, check Gemini
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: SYSCONTROLLER-OS-Adaptor : Unable to retrieve adaptor who owns BMI_GROUP_HARDWARE_Dm3DEVINFO_TABLE group
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: SYSCONTROLLER-OS-Adaptor : Gemini is not in the system, not to load ipmi adaptor
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: SYSCONTROLLER-OS-Adaptor : Calling Adaptor Bridge Adaptor Init Method
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: Bridge-Adaptor : Initializing Bridge Adaptor.
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: Bridging&Streaming-Adaptor : Fail to get DEVICE INFO Adaptor in Init()
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: Bridge-Adaptor : Bridge subsystem: Ready
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: SYSCONTROLLER-OS-Adaptor : Adaptor Bridge Adaptor Ready...
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: SYSCONTROLLER-OS-Adaptor : Calling Adaptor License Adaptor Init Method
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: License-Adaptor : Failed to get devinfo adaptor
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: License-Adaptor : License subsystem: Get Adaptor failed
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: SYSCONTROLLER-OS-Adaptor : Adaptor License Adaptor fail to initialize...
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: SYSCONTROLLER-OS-Adaptor : Calling Adaptor TDM Adaptor Init Method
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: Tdmbus-Adaptor : Unable to retrieve adaptor who owns BMI_GROUP_HARDWARE_DEVINFO_TABLE group
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: Tdmbus-Adaptor : TDM H100/H110 Bus Adaptor Ready
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: SYSCONTROLLER-OS-Adaptor : Adaptor TDM Adaptor Ready...
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: SYSCONTROLLER-OS-Adaptor : Calling Adaptor DS1 Adaptor Init Method
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: DS1-Adaptor : Initializing DS1 Adaptor
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: DS1-Adaptor_CDS1DM3Manager : Unable to retrieve resolved table from data storage. Creating new table.
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: DS1-Adaptor_CDS1DM3Manager : GetBMTable: DS1ERROR: Unable to retrieve adaptor who owns group: 1900
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: DS1-Adaptor_CDS1DM3Manager : InitDM3DeviceCfg: DS1ERROR: Unable to retrieve BMI_GROUP_BM_TRUNKCAP_TABLE table.
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: DS1-Adaptor_CDS1DM3Manager : Init: DS1ERROR: Unable to initialize DM3 configuration
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: DS1-Adaptor : Init: DS1ERROR: Unable to initialize DM3 Device Manager.
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: DS1-Adaptor : Unable to initialize adaptor. [DS1 subsystem: Unable to retrieve adaptor pointer]
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: SYSCONTROLLER-OS-Adaptor : Adaptor DS1 Adaptor fail to initialize...
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: SYSCONTROLLER-OS-Adaptor : Calling Adaptor MIB2 OS Adaptor Init Method
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: MIB2::COffLoadBoardInfo : COffloadBoardInfo::mGetOBA() did not find Offload Board Adaptor
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: MIB2-OS-Adaptor : Offload Board Adaptor Not Detected
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: MIB2-OS-Adaptor : DS1 subsystem: HIB boards are not installed or not found - Can't Set DS1 interface offset
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: MIB2-OS-Adaptor : Kernel Version[2.6]
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: MIB2-OS-Adaptor : Failure at system routine GetAddrInfo()
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: MIB2-OS-Adaptor : 1 IPv6 address found for ifname=eth0
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: MIB2-OS-Adaptor : Failure at system routine GetAddrInfo()
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: MIB2-OS-Adaptor : 1 IPv6 address found for ifname=eth1
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: MIB2-OS-Adaptor : Failure at system routine GetAddrInfo()
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: MIB2-OS-Adaptor : 1 IPv6 address found for ifname=eth2
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: MIB2-OS-Adaptor : Failure at system routine GetAddrInfo()
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: MIB2-OS-Adaptor : 1 IPv6 address found for ifname=eth3
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: MIB2-OS-Adaptor : Ds1 ConfigTable empty
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: External-Interfaces-Types : CExtIfTypeImpl.cpp:126 Generic failure Can't Open Hardware Device hwconf file [0]
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: MIB2-OS-Adaptor : CMib2AdaptorImpl.cpp:3639 - Can't Find Interface Type based on Mac Address
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: MIB2-OS-Adaptor : CMib2AdaptorImpl.cpp:3639 - Can't Find Interface Type based on Mac Address
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: MIB2-OS-Adaptor : CMib2AdaptorImpl.cpp:3639 - Can't Find Interface Type based on Mac Address
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: MIB2-OS-Adaptor : CMib2AdaptorImpl.cpp:3639 - Can't Find Interface Type based on Mac Address
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: MIB2-OS-Adaptor : Start Link thread...
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: MIB2-OS-Adaptor : os[1][Redhat] arch[1][Open Architecture]
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: MIB2-OS-Adaptor : MIB2 subsystem: Ready
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: MIB2-OS-Adaptor LinkStatusThread : LinkStatus Thread started
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: SYSCONTROLLER-OS-Adaptor : Adaptor MIB2 OS Adaptor fail to initialize...
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: MIB2-OS-Adaptor LinkStatusThread : Interface Poll Interval[30000]
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: SYSCONTROLLER-OS-Adaptor : Calling Adaptor Media Adaptor Init Method
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: MIB2-OS-Adaptor LinkStatusThread : Adaptor not found - Can't retrieve DS1 Adaptor interfaces
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: MIB2-OS-Adaptor LinkStatusThread : MIB2 subsystem: Failed to find any system interfaces - No DS1 interfaces found
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: MIB2-OS-Adaptor : Failure at system routine GetAddrInfo()
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: MIB2-OS-Adaptor : 1 IPv6 address found for ifname=eth0
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: Media Adaptor : Get StartMode = 2 from DB
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: MSML-Adaptor : Register Group ID = 60100
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: MSML-Adaptor : Register Group ID = 60200
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: MSML-Adaptor : Register Group ID = 60800
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: MSML-Adaptor : MSML Adaptor Ready
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: Media-Adaptor : CMediaAdaptorImpl::fillRTPTable - Entry
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: MIB2-OS-Adaptor : Failure at system routine GetAddrInfo()
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: Media-Adaptor : RTP Active IP Address = 172.18.255.3
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: MIB2-OS-Adaptor : 1 IPv6 address found for ifname=eth1
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: Media-Adaptor : RTP Active IPv6 Address = fe80::29c:2ff:fe9a:e598
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: Media-Adaptor : RTP Active MAC Address = 00:9c:02:9a:e5:98
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: MIB2-OS-Adaptor : Failure at system routine GetAddrInfo()
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: MIB2-OS-Adaptor : 1 IPv6 address found for ifname=eth2
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: MIB2-OS-Adaptor : Failure at system routine GetAddrInfo()
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: MIB2-OS-Adaptor : 1 IPv6 address found for ifname=eth3
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: MIB2-OS-Adaptor : Ds1 ConfigTable empty
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: MIB2-OS-Adaptor LinkStatusThread : Send LinkStatus Event[LinkUP]-ifindex[1]
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: Media-Adaptor : Found RTP Active row with IPAddress = 172.18.255.3
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: Media-Adaptor : Register Group ID = 60000
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: MIB2-OS-Adaptor LinkStatusThread : Send LinkStatus Event[LinkUP]-ifindex[2]
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: CBMEvMgr : EVENT : IfLinkStatus [LINK UP] Interface IfIndex [1]
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: Media-Adaptor : Media subsystem: Ready
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: SYSCONTROLLER-OS-Adaptor : Unable to retrieve adaptor who owns BMI_GROUP_HARDWARE_Dm3DEVINFO_TABLE group
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: SYSCONTROLLER-OS-Adaptor : Adaptor Media Adaptor Ready...
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: SYSCONTROLLER-OS-Adaptor : Unable to retrieve adaptor who owns BMI_GROUP_HARDWARE_Dm3DEVINFO_TABLE group
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: MIB2-OS-Adaptor LinkStatusThread : Send LinkStatus Event[LinkUP]-ifindex[3]
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: CBMEvMgr : EVENT : SysRunStatus [INACTIVE]
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: SYSCONTROLLER-OS-Adaptor : IP Protocol Selection = 0 from DB
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: CBMEvMgr : EVENT : IfLinkStatus [LINK UP] Interface IfIndex [2]
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: MIB2-OS-Adaptor LinkStatusThread : Send LinkStatus Event[LinkUP]-ifindex[4]
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: CBMEvMgr : EVENT : IfLinkStatus [LINK UP] Interface IfIndex [3]
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: SYSCONTROLLER-OS-Adaptor : System Controller Adaptor Ready
Mar 6 11:52:12 MediaGateway BOARDMANAGER: From Component: CBMEvMgr : EVENT : IfLinkStatus [LINK UP] Interface IfIndex [4]
Mar 6 11:52:13 MediaGateway ct_intel: Starting SNMP Agent Service :
Mar 6 11:52:13 MediaGateway ct_intel: Calling /sbin/runuser -s /bin/bash - -c /usr/dialogic/bin/snmpagent -sp 16161 -st 162 -D 1 -d /usr/dialogic/ -l log/snmpagent.log
Mar 6 11:52:13 MediaGateway SNMPAGENT: From Component: LOGFRAMEWORK : BM_LOG_LEVEL set to Log and Info
Mar 6 11:52:13 MediaGateway SNMPAGENT: From Component: SNMPAGENT : SNMP Agent Started
Mar 6 11:52:13 MediaGateway SNMPAGENT: From Component: SNMP-SPL : Connecting to Backend Client...
Mar 6 11:52:13 MediaGateway SNMPAGENT: From Component: SNMP-SPL : Connection to backend client proxy object
Mar 6 11:52:13 MediaGateway SNMPAGENT: From Component: TIM : Setting Cache Time to 2 sec
Mar 6 11:52:13 MediaGateway SNMPAGENT: From Component: TIM : Setting Cache Time to 2 sec
Mar 6 11:52:13 MediaGateway SNMPAGENT: From Component: TIM : Setting Cache Time to 2 sec
Mar 6 11:52:13 MediaGateway SNMPAGENT: From Component: TIM : Setting Cache Time to 2 sec
Mar 6 11:52:13 MediaGateway SNMPAGENT: From Component: TIM : Setting Cache Time to 2 sec
Mar 6 11:52:13 MediaGateway SNMPAGENT: From Component: TIM : Setting Cache Time to 2 sec
Mar 6 11:52:13 MediaGateway SNMPAGENT: From Component: TIM : Setting Cache Time to 2 sec
Mar 6 11:52:13 MediaGateway SNMPAGENT: From Component: TIM : Setting Cache Time to 2 sec
Mar 6 11:52:13 MediaGateway SNMPAGENT: From Component: TIM : Setting Cache Time to 2 sec
Mar 6 11:52:13 MediaGateway SNMPAGENT: From Component: TIM : Setting Cache Time to 2 sec
Mar 6 11:52:13 MediaGateway SNMPAGENT: From Component: TIM : Setting Cache Time to 2 sec
Mar 6 11:52:13 MediaGateway SNMPAGENT: From Component: TIM : Setting Cache Time to 2 sec
Mar 6 11:52:13 MediaGateway SNMPAGENT: From Component: TIM : Setting Cache Time to 2 sec
Mar 6 11:52:13 MediaGateway SNMPAGENT: From Component: TIM : Setting Cache Time to 2 sec
Mar 6 11:52:13 MediaGateway SNMPAGENT: From Component: TIM : Setting Cache Time to 2 sec
Mar 6 11:52:13 MediaGateway SNMPAGENT: From Component: TIM : Setting Cache Time to 2 sec
Mar 6 11:52:13 MediaGateway SNMPAGENT: From Component: TIM : Setting Cache Time to 2 sec
Mar 6 11:52:13 MediaGateway SNMPAGENT: From Component: TIM : Setting Cache Time to 2 sec
Mar 6 11:52:13 MediaGateway SNMPAGENT: From Component: TIM : Setting Cache Time to 2 sec
Mar 6 11:52:13 MediaGateway SNMPAGENT: From Component: TIM : Setting Cache Time to 2 sec
Mar 6 11:52:13 MediaGateway SNMPAGENT: From Component: TIM : Setting Cache Time to 2 sec
Mar 6 11:52:13 MediaGateway SNMPAGENT: From Component: TIM : Setting Cache Time to 2 sec
Mar 6 11:52:13 MediaGateway SNMPAGENT: From Component: TIM : Setting Cache Time to 2 sec
Mar 6 11:52:13 MediaGateway SNMPAGENT: From Component: TIM : Setting Cache Time to 2 sec
Mar 6 11:52:13 MediaGateway SNMPAGENT: From Component: TIM : Setting Cache Time to 2 sec
Mar 6 11:52:13 MediaGateway SNMPAGENT: From Component: TIM : Setting Cache Time to 2 sec
Mar 6 11:52:13 MediaGateway SNMPAGENT: From Component: TIM : Setting Cache Time to 2 sec
Mar 6 11:52:13 MediaGateway SNMPAGENT: From Component: TIM : Setting Cache Time to 2 sec
Mar 6 11:52:13 MediaGateway SNMPAGENT: From Component: TIM : Setting Cache Time to 2 sec
Mar 6 11:52:13 MediaGateway SNMPAGENT: From Component: TIM : Setting Cache Time to 2 sec
Mar 6 11:52:13 MediaGateway SNMPAGENT: From Component: TIM : Setting Cache Time to 2 sec
Mar 6 11:52:13 MediaGateway SNMPAGENT: From Component: TIM : Setting Cache Time to 2 sec
Mar 6 11:52:13 MediaGateway SNMPAGENT: From Component: TIM : Setting Cache Time to 2 sec
Mar 6 11:52:13 MediaGateway SNMPAGENT: From Component: TIM : Setting Cache Time to 2 sec
Mar 6 11:52:13 MediaGateway SNMPAGENT: From Component: SNMP-SPL : Calling mInitMmaHwDeviceGroup()
Mar 6 11:52:13 MediaGateway SNMPAGENT: From Component: TIM : Setting Cache Time to 2 sec
Mar 6 11:52:13 MediaGateway SNMPAGENT: From Component: TIM : Setting Cache Time to 2 sec
Mar 6 11:52:13 MediaGateway SNMPAGENT: From Component: TIM : Setting Cache Time to 2 sec
Mar 6 11:52:13 MediaGateway SNMPAGENT: From Component: TIM : Setting Cache Time to 2 sec
Mar 6 11:52:13 MediaGateway SNMPAGENT: From Component: SNMPAGENT-ICL : Loaded HMP RTP SNMP Group
Mar 6 11:52:13 MediaGateway SNMPAGENT: From Component: SNMPAGENT-ICL : Registered Bridge System Event Callback function
Mar 6 11:52:13 MediaGateway SNMPAGENT: From Component: SNMPAGENT-ICL : Registered CT Bus Event Callback function
Mar 6 11:52:13 MediaGateway SNMPAGENT: From Component: SNMPAGENT : BM Product is ZIONSVILLE
Mar 6 11:52:14 MediaGateway ct_intel: Starting CLI Agent Service :
Mar 6 11:52:14 MediaGateway ct_intel: Calling /sbin/runuser -s /bin/bash - -c /usr/dialogic/bin/cliagent -ct 2323 -D 1 -d /usr/dialogic/ -l log/cliagent.log
Mar 6 11:52:14 MediaGateway CLIAGENT: From Component: LOGFRAMEWORK : BM_LOG_LEVEL set to Log and Info
Mar 6 11:52:14 MediaGateway CLIAGENT: From Component: CLI : @ Connected to Board Manager : BM_Handle[9418900] @
Mar 6 11:52:14 MediaGateway BOARDMANAGER: From Component: MIB2-OS-Adaptor : Failure at system routine GetAddrInfo()
Mar 6 11:52:14 MediaGateway BOARDMANAGER: From Component: MIB2-OS-Adaptor : 1 IPv6 address found for ifname=eth0
Mar 6 11:52:14 MediaGateway BOARDMANAGER: From Component: MIB2-OS-Adaptor : Failure at system routine GetAddrInfo()
Mar 6 11:52:14 MediaGateway BOARDMANAGER: From Component: MIB2-OS-Adaptor : 1 IPv6 address found for ifname=eth1
Mar 6 11:52:14 MediaGateway BOARDMANAGER: From Component: MIB2-OS-Adaptor : Failure at system routine GetAddrInfo()
Mar 6 11:52:14 MediaGateway BOARDMANAGER: From Component: MIB2-OS-Adaptor : 1 IPv6 address found for ifname=eth2
Mar 6 11:52:14 MediaGateway BOARDMANAGER: From Component: MIB2-OS-Adaptor : Failure at system routine GetAddrInfo()
Mar 6 11:52:14 MediaGateway BOARDMANAGER: From Component: MIB2-OS-Adaptor : 1 IPv6 address found for ifname=eth3
Mar 6 11:52:14 MediaGateway BOARDMANAGER: From Component: MIB2-OS-Adaptor : Ds1 ConfigTable empty
Mar 6 11:52:14 MediaGateway CLIAGENT: From Component: CLI : @#012 System initializing... @
Mar 6 11:52:14 MediaGateway CLIAGENT: From Component: CLI : #012@ Event [Link Status Change Registration] SUCCEEDED @
Mar 6 11:52:14 MediaGateway CLIAGENT: From Component: CLI : #012@ Event [DS1 Trunk Status Change Registration] SUCCEEDED @
Mar 6 11:52:14 MediaGateway CLIAGENT: From Component: CLI : #012@ Event [DS1 Alarm Trap Status Change Registration] SUCCEEDED @
Mar 6 11:52:14 MediaGateway CLIAGENT: From Component: CLI : #012@ Event [System Ready Registration] SUCCEEDED @
Mar 6 11:52:14 MediaGateway CLIAGENT: From Component: CLI : #012@ Event [System Run State Change Registration] SUCCEEDED @
Mar 6 11:52:14 MediaGateway CLIAGENT: From Component: CLI : #012@ Event [System Upgrade Registration] SUCCEEDED @
Mar 6 11:52:14 MediaGateway CLIAGENT: From Component: CLI : #012@ Event [System TCM Clock Switch Registration] SUCCEEDED @
Mar 6 11:52:14 MediaGateway CLIAGENT: From Component: CLI : #012@ Event [AMC Hotswap Registration] SUCCEEDED @
Mar 6 11:52:14 MediaGateway CLIAGENT: From Component: CLI : #012@ Event [AMC Run Status Change Registration] SUCCEEDED @
Mar 6 11:52:14 MediaGateway CLIAGENT: From Component: CLI : #012@ Event [Bridge Device Detected Registration] SUCCEEDED @
Mar 6 11:52:14 MediaGateway CLIAGENT: From Component: CLI : #012@ Event [MsML Startup Status Change Registration] SUCCEEDED @
Mar 6 11:52:14 MediaGateway CLIAGENT: From Component: CLI : #012@ Event [System Start Mode Change Registration] SUCCEEDED @
Mar 6 11:52:14 MediaGateway CLIAGENT: From Component: CLI : #012@ Event [MMA Device Upper Critical Temperature Registration] SUCCEEDED @
Mar 6 11:52:14 MediaGateway CLIAGENT: From Component: CLI : #012@ Event [MMA Device Upper Non-Recoverable Temperature Registration] SUCCEEDED @
Mar 6 11:52:14 MediaGateway CLIAGENT: From Component: CLI : #012@ Event [MMA Device Lower Critical Temperature Registration] SUCCEEDED @
Mar 6 11:52:14 MediaGateway CLIAGENT: From Component: CLI : #012@ Event [MMA Device Lower Non-Recoverable Temperature Registration] SUCCEEDED @
Mar 6 11:52:14 MediaGateway CLIAGENT: From Component: CLI : @ BM_Handle[9418900] Event Registation [SUCCEEDED] @
Mar 6 11:52:15 MediaGateway ct_intel: /usr/dialogic/bin/ssck 3
Mar 6 11:52:15 MediaGateway SSCK Monitoring Thread: From Component: LOGFRAMEWORK : BM_LOG_LEVEL set to Log and Info
Mar 6 11:52:15 MediaGateway SSCK Monitoring Thread: From Component: SSCK Monitoring Thread : Started SSCK monitoring thread
[root@MediaGateway log]#

I wanna get the help !Thank u:)

↧

RE: something wrong with modify the RTP address

March 10, 2016, 7:23 am
$
0
0

it casue by the ifcfg-ethX where service NetworkManager block the HMP detect the ethernet port ,stop the service and modify the NM_CONTROLLED=yes =>NM_CONTROLLED=no

↧
↧

RE: Max Digit Phone Number

March 11, 2016, 7:24 am
$
0
0

There may be a possibility to use GC send overlay digits method, but that depends on board in use (ie Springware vs DM3) and / or HMP/DNI?

What SR and board do you have in this case?

Jeff

↧

Configure HMP to save CDR information (Jitter, Delay and Packet Loss)

March 11, 2016, 1:53 pm
$
0
0

Hi

Is it posible to configure/write code to save all CDR information from all call to and from a HMP device?

We use HMP software for IVR functionality and I need to save CDR (Call Detail Records) especialy Jitter, Packet loss, and delay information. I can't find any information how to save this from HMP software, if it's possible.

Regards
Christian Enroth

↧

RE: Configure HMP to save CDR information (Jitter, Delay and Packet Loss)

March 14, 2016, 8:13 am
↧
Viewing all 1151 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>