In this case you need to preserve the configuration using the following method.
This is documented in the system configuration guide:
3.6 Preserving Data in User Configuration Files
www.dialogic.com/.../system_config_v5.pdf
Or the following technote:
www.dialogic.com/.../pm_hmp_lin
At that point you can then change the start of the RTP port range in this case.
Regards,
Jeff
In this case, HMP requires at least one of the Network interface names be "ethX" where X is some number (typically 0). In VMs this is common to be named something else, and required to be changed to ethx.
I suspect that is the difference between the 6.9 system and the 7.6 system you referenced.
Regards,
Jeff
i know it is an old post, but what did you do to solved it?
i have the same problem
hey' i know it's an old post, but how did yo solved it? we have the same problem.
Thank you Jeff. It works.
Regards,
Roberto
Thank you for that, I changed the naming of the Network interfaces to eth0 and eth1 and now the HMP finds the interfaces successfully.
Regards
Colin
Hi,
Running a server 20008 R2 with D/600 card and suddenly after reboot of server i get
Power Requirement was not met but the user had the power override on, for board in slot 0, bus 4, Power Required is 25, and actual power provided is 0
And i cant start the card from Configuration Manager.
Please Advise
Kristoffer
Sound like the dx_getxmitslot call is getting a bad handle in this case. I know I have used that demo on HMP in the past but it was still in context of HMP with DNI (for pstn), not SIP. I know it was originally written for both PSTN (JCT/DM3) and SIP (DMIP/PMAC) boards on SR 6.x baseline. But not sure how much more work was done on HMP as it was very old back then (as I recall) and the project source is probably just as old.
What actual line in the cfg file (outbound or inbound) are you running in this case?
Jeff M.
Whoa. More acronyms and history I don't have reference for.
You are telling me HMP is old? What is current?
You mentioned SR 6.x. Does SR = Standard Runtime Library? If so, the latest PDFs on www.dialogic.com/.../hmp30win say they are V5. What is this 6.x?
To answer your question:
I'm attempting to use the provided inbound.cmd with this line uncommented
sr6callp mode=inbound type=JctAnalog protocol=pdk_na_an_io vox=dxxxB1C1 dropOnConnected=0 playFileName=SitNoCircuit.vox
I'm being told that HMP is the layer over PSTN and IP.
No, HMP is not old, the SR 6.x (system release 6.0 PCI software) was a different older animal of which the demo you are using was meant for. Thus the name sr6callp. What I said was I don't recall if is was meant for HMP usage itself, I know it has IP capabilities but like I said that was for DM3 board that had IP caps, like the DMIP and IPT (ie pmac). this is all older hw no longer sold by dialogic.
Moving forward.... the line you have here from the inbound config file is wrong as its looking for analog JCT board (like C120jct), this is not anything you would use with HMP. it references the SR 6.0 release as I mentioned prior.
sr6callp mode=inbound type=JctAnalog protocol=pdk_na_an_io vox=dxxxB1C1 dropOnConnected=0 playFileName=SitNoCircuit.vox
That is why you get the switching error in this case then. You need to use one of the SIP config lines I suspect.
Jeff
so in the various demos that I have seen there are API calls with "sr_" prefix. Is that System Release or Standard Runtime that the prefix is referring to? I had been assuming Standard Runtime as that seemed to be the PDF API with applicable hits when searching.
So what is this "system release 6.0 PCI software"? What is the history? I'm not grasping what that is or if it is an "is".
Don't confuse the SRL API (standard runtime library) used for event processing between host library and firmware communications with that of SR (system release software) in this case.
In anycase, the 6.0 software and all board based products were sold off to Sangoma last year and no longer own by dialogic. So if you were really looking to use that going forward you would have to contact them for more information.
But I suspect that is not really the case. Overall, I feel it might be worthy for you to have some conversation with a dialogic field (FAE) sales rep to get you in the right direction.
If you PM me your information i can see if that is a possibility...
Let me talk internally here first. It sounds like I've been given an impossible task. Build a layer that allows for Sip (new stuff) and PSTN (stuff in field).
I don't think the task would be "impossible", I just think you may need some pointers to provide the background on getting you to the point of where you need to be. And that type of conversation would typically be something more elaborate than what would be discussed in the forums...
Overall, it sounds like some type of porting effort is involved here in this case.
Jeff
I need help learning how to figure out problems as I dig into developing an HMP layer for our system. I've download several demos, worked for days to get them to compile in VS 2017, and then found other road blocks keeping me from proving the demo code actually works.
Using demo - Sr6Callp
The current problem is
dx_getxmitslot error=0x6a Invalid Switching Handler Bus Mode
What does that mean? I ask myself.
So I go to https://www.dialogic.com/manuals/hmp/hmp30win and open the Global Call API Library reference because …… that has the API calls, right? I do a search for dx_getxmitslot and it shows up as a comment for gc_getxmitslot stating to use dx_ for voice resources. Ok. This HMP demo code appears to be doing that. It says right in the code file for that code block // Get voice device transmit timeslot.
So I did a search for "Invalid Switching Handler Bus Mode" and returned results were a very small number. Even smaller when focused on dx_getxmitslot also. The few entries didn't seem helpful.
I've spent days reading so many PDFs and it hasn't helped get me down the right path.
How do I break this message down and figure out what is going on?
Hi all,
I have a strange behaviour with a new HMP 4.1 installation (SU 272). Installation completed successfully, and ipmedia starts with the standard demo license. Anyway with a permanent purchased license, ipmedia fails to start, although the license would be deployed correctly.
This is not my first HMP installation, and I never met this kind of error before.
The only difference concern with the server network interfaces. In this installation I have the following network IF:
PrivateTeam: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
ether 98:4b:e1:05:fa:d0 txqueuelen 1000 (Ethernet)
RX packets 1941 bytes 1276418 (1.2 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1294 bytes 222434 (217.2 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
PublicTeam: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
ether 98:4b:e1:05:fa:d2 txqueuelen 1000 (Ethernet)
RX packets 2420 bytes 1052997 (1.0 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 733 bytes 2122667 (2.0 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
brPrivate: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet xxx.xxx.xxx.xxx netmask 255.255.255.0 broadcast a.b.c.d
inet6 fe80::9d28:5f2:537e:3124 prefixlen 64 scopeid 0x20<link>
ether 98:4b:e1:05:fa:d0 txqueuelen 1000 (Ethernet)
RX packets 1658 bytes 1094433 (1.0 MiB)
RX errors 0 dropped 684 overruns 0 frame 0
TX packets 352 bytes 31422 (30.6 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
brPublic: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet yyy.yyy.yyy.yyy netmask 255.255.255.224 broadcast e.f.g.h
inet6 fe80::9095:1467:ef3d:bdcf prefixlen 64 scopeid 0x20<link>
ether 98:4b:e1:05:fa:d2 txqueuelen 1000 (Ethernet)
RX packets 2324 bytes 1028122 (1004.0 KiB)
RX errors 0 dropped 684 overruns 0 frame 0
TX packets 733 bytes 2122667 (2.0 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
enp3s0f0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
ether 98:4b:e1:05:fa:d0 txqueuelen 1000 (Ethernet)
RX packets 1981 bytes 1311698 (1.2 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1293 bytes 227523 (222.1 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
enp3s0f1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
ether 98:4b:e1:05:fa:d2 txqueuelen 1000 (Ethernet)
RX packets 2417 bytes 1094855 (1.0 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1914 bytes 2194436 (2.0 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
enp4s0f0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
ether 98:4b:e1:05:fa:d0 txqueuelen 1000 (Ethernet)
RX packets 1470 bytes 1107668 (1.0 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
enp4s0f1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
ether 98:4b:e1:05:fa:d2 txqueuelen 1000 (Ethernet)
RX packets 1189 bytes 1003375 (979.8 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
ens2f0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 00:26:55:db:2d:4e txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 44 memory 0xfbfe0000-fc000000
ens2f1: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 00:26:55:db:2d:4f txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 46 memory 0xfbfa0000-fbfc0000
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1 (Local Loopback)
RX packets 802 bytes 78384 (76.5 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 802 bytes 78384 (76.5 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255
ether 52:54:00:d7:43:c4 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
virbr0-nic: flags=4098<BROADCAST,MULTICAST> mtu 1500
ether 52:54:00:d7:43:c4 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
vnet0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::fc54:ff:fe70:aa62 prefixlen 64 scopeid 0x20<link>
ether fe:54:00:70:aa:62 txqueuelen 1000 (Ethernet)
RX packets 1221 bytes 207182 (202.3 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1941 bytes 1242639 (1.1 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
My license has been generated with the MAC 98:4b:e1:05:fa:d2.
Do you know guys about problem with bonding and or bridge IF (the server has KVM installed also)?
Any help/suggest will be appreciated.
Thanks.
Roberto
From q quick look there is a requirement from the FlexLm (licensing) level that NIC must be named EthX (where x is a number) for license activation to work correctly. I see that since this is a VM, you will need to make sure that requirement is met.
Jeff
Hi Jeff,
The problem can't be this one, because on some other VMs I have ensXX interfaces and the system works.
Roberto.
I am not sure about Linux, but I know on windows HMP side the same flex version does not support teaming. So the NIC has to be on a NIC that is not part of the team. You can then use any other adapter set afterwards for the actual streaming of RTP. It could be the Linux side has the same restrictions, but I have not tried that in the past.
Just speculation.
Are the other systems configured the same way? What is the license bond to in that case, which NIC?
Jeff