Good Morning Gentlemen,
We have a sucessfully intergrated a DMG 1000 with our 2000PBX and an asterisks server!
It works GREAT!!! i am pleased... But we have One problem...
When we call a NEC extention from a SIP phone.. it works great.. Hang up the call.... About 10 -20 minutes later we get a call from the previous called extention... with no one on the line... Its quite random... Phanthom calls.....
We followed the dialogic setup for matworks.. and ect.. I can provide ANY LOGS or anyother details... I just need some help getting to the bottom of this problem...
Thanks
Jaron
So the IP phone you placed the call from is getting a callback from the originally called TDM port? I'd like to see a DMG trace of that if you can catch it. The first thing that came to mind was maybe the TDM user you called from the IP phone is able to see who called somehow (MWI light, or display), and they are calling it back? However you would have voice if they stayed on the call (maybe they are hanging up?).
Was the TDM side busy when you called it from the IP phone the first time? Maybe they have some type of automatic callback on busy or NA stations enabled?
The trace should tell me if the DMG is doing it on its own or if it is being told to do so by the PBX for some reason. Enable tel-event, tel-code, tel-prot, and voip-prot trace masks and try to catch this if you can!
The Log is attached.... It just happened.. I hope you can see something! I got a random call from NEC extension 1067
Thanks so MUCH
Bump.... Can someone please take a look at my logs... and give me some ideas......
Well I just did another test... I routed the gateway to bridge the tdm.... to NEC TO NEC extension using the dialogic...... I GOT a phantom call again! so we can cross asterisks off the list... I need help PLEASE!
So what i am seeing this trace is that the DMG sees a lamp change on call appearance 60:
508:44.756 [Tel-5 ] Event EVT-Lamp 60:CallApp0:0 OFF->FLASH_ALT
DMG gets a display update for the call and knows its a fwd all call coming in from 1067;
508:44.760 [Tel-5 ] Event 2:20:40 | FDA 8061 1067 Rob Wood | 508:44.760 [Tel-5 ] Code phePrcCpid() 1067,->8061, (fwd-all)
508:44.760 [Tel-5 ] Code phePrcCpid() 1067,->8061, (fwd-all)
DMG sends an Invite to admin@10.0.32.5:
508:44.782 [VoIP ] Prot <----INVITE sip:admin@10.0.32.5 SIP/2.0508:44.782 [VoIP ] Prot From:<sip:1067;phone-context=admin@10.0.0.4:5060;user=phone>;vnd.pimg.port=5;tag=06D6324631353641000DD01F508:44.782 [VoIP ] Prot To:"admin"<sip:admin@10.0.32.5>508:44.782 [VoIP ] Prot Diversion: <tel:8061>;reason=unconditional508:44.782 [VoIP ] Prot Content-Type:application/sdp
The eventually sends a BUSY Here:
508:44.914 [VoIP ] Prot ---->SIP/2.0 486 Busy Here508:44.914 [VoIP ] Prot Via: SIP/2.0/UDP 10.0.0.4:5060;branch=z9hG4bK27F5476C12F0BE7A92BBB4394D9DD217;received=10.0.0.4508:44.914 [VoIP ] Prot From: <sip:1067;phone-context=admin@10.0.0.4:5060;user=phone>;vnd.pimg.port=5;tag=06D6324631353641000DD01F508:44.914 [VoIP ] Prot To: "admin"<sip:admin@10.0.32.5>;tag=as6a90d34a508:44.914 [VoIP ] Prot Call-ID: 01B2286E2E814000000016D5@10.0.0.4 Call is never answered and goes Idle. 508:44.938 [Tel-5 ] Code pheIdleLine() already onhook.508:44.938 [Tel-5 ] Code pheSetCallIdle 9161d0 User Busy508:44.940 [Tel-5 ] Code pheChangeCallState() 9161d0 IDLE So to me this looks like a legit forwarded call from 1067...the last two from 1067 look strange in the fact the call seems to be coming in on Button 76 appearance 16. How do you have the DMG configured as far as TDM>Digital Set is concerned? Is it NEC_NEAX? To me, it looks like either DMG is configured for the wrong protocol, or the actual ports plugged into the DMG are programmed incorrectly. Not sure why calls are coming in on another line appearance. Should only be EVT-Lamp 60:CallApp0. Hope this helps.
508:44.914 [VoIP ] Prot ---->SIP/2.0 486 Busy Here508:44.914 [VoIP ] Prot Via: SIP/2.0/UDP 10.0.0.4:5060;branch=z9hG4bK27F5476C12F0BE7A92BBB4394D9DD217;received=10.0.0.4508:44.914 [VoIP ] Prot From: <sip:1067;phone-context=admin@10.0.0.4:5060;user=phone>;vnd.pimg.port=5;tag=06D6324631353641000DD01F508:44.914 [VoIP ] Prot To: "admin"<sip:admin@10.0.32.5>;tag=as6a90d34a508:44.914 [VoIP ] Prot Call-ID: 01B2286E2E814000000016D5@10.0.0.4
Call is never answered and goes Idle.
508:44.938 [Tel-5 ] Code pheIdleLine() already onhook.508:44.938 [Tel-5 ] Code pheSetCallIdle 9161d0 User Busy508:44.940 [Tel-5 ] Code pheChangeCallState() 9161d0 IDLE So to me this looks like a legit forwarded call from 1067...the last two from 1067 look strange in the fact the call seems to be coming in on Button 76 appearance 16. How do you have the DMG configured as far as TDM>Digital Set is concerned? Is it NEC_NEAX? To me, it looks like either DMG is configured for the wrong protocol, or the actual ports plugged into the DMG are programmed incorrectly. Not sure why calls are coming in on another line appearance. Should only be EVT-Lamp 60:CallApp0.
508:44.938 [Tel-5 ] Code pheIdleLine() already onhook.508:44.938 [Tel-5 ] Code pheSetCallIdle 9161d0 User Busy508:44.940 [Tel-5 ] Code pheChangeCallState() 9161d0 IDLE
So to me this looks like a legit forwarded call from 1067...the last two from 1067 look strange in the fact the call seems to be coming in on Button 76 appearance 16. How do you have the DMG configured as far as TDM>Digital Set is concerned? Is it NEC_NEAX? To me, it looks like either DMG is configured for the wrong protocol, or the actual ports plugged into the DMG are programmed incorrectly. Not sure why calls are coming in on another line appearance. Should only be EVT-Lamp 60:CallApp0.
Hope this helps.
Yes the DMG TDM is configured to NEC_NEAX
Do you think its a possibility MWI (message waiting indicator) toggle could be triggering this..?
DAVE you are a lifesaver... Your tip lead us to find our problem...
NEC side.. extensions used for NEC between dialogic had a speeddial mapping from a previous setup before my time... We removed them... And things seem peachy
Thanks again! Dialogic is a GREAT company, couldn't be more pleased
Jaron,
I'm about to embark on connecting our 2007 OCS R2 with our NEAX 2000 IPS, would you care to share some of your experiences?
I have a Dialogic DMG 2000 setup and ready.
John
What protocol are you planning to use with the DMG2000? If you have any questions let us know.
The Dialogic box is currently handling our integration to our OCS 2007 R2 from our Sip Trunk provider. It's just converting the TCP to UDP and back, as our provider does not support TCP. So currently it's just handling VOIP for my external people. All my internal people are still using the old Neax 2000 IPC system. The problem is that in order to transfer calls we have to transfer to their OCS numbers instead of an extension, and there is no real integration between the two systems.
[EDIT] Our external people used to have the DTermIP phones, but it was always a mess having the VPN router etc. setup and getting our people supported, that's why we went the OCS route. The Neax 2000 IPS have two "Ethernet" cards used for the old IP Phones, not sure if they can be used for anything.
I was looking at the DMG 2000 and it has a port for a T1 hookup, which I thought I could hook up to the Neax 2000 IPS system. I've looked everywhere online and talked to our phone provider without any luck.
Any help is greatly appreciated.
I'm thinking that if that NEAX has a T1 card installed, you could very well connect that to the DMG2000 using NI2 protocol (if the PBX supports it). Not sure what other protocols the PBX supports (or if it even has a T1). CAS may be an option too depending on what the PBX can do. You could then forward your internal TDM phones over the "T" to the DMG to OCS....or even have OCS simul ring / forward to the TDM extensions. This sounds like it could be interesting! Keep us posted!
Thanks Dave!
This that's why I was asking Jaron if he had some advice. I assume his Neax 2000 is hooked up to the Dialogic somehow.
Yep. He was using a DMG1008DNI and integrating using digital NEC DTERM III ports I believe. The Problem with using that with OCS, is that the outbound call will always look like it is coming from the port that is making the call. so if port 1 connected to the DMG was extension 200, outbound calls from OCS to the TDM side will always look like they are coming from extension 200. Nothing you can do on the DMG side to avoid that. Its just how the port is programmed in the PBX. (Analog DMG1008LS would probably be the same). T1 would be best if we can do that...Have a great night.