Quote:
Originally Posted by
blackrageous
Are you sure the number you calling into has DID (direct inward dial) capability, in other words can you make a call to that number (where mgetty is) from the outside and have it answer?
Hey, thanks for the reply..
Yes, I have one line coming out of the ATA and going into a splitter and from that splitter one end goes into the PC running mgetty and the other end goes into a dumb phone that has caller ID. And when I make the call I can see the dumb phone ringing with the correct caller ID number as well as I can see mgetty Ringing while watching the log file.
So both my laptop and the PC running Mgetty both have DID numbers assigned to them.
Also, if I call the mgetty PC from my cell phone, I can see my cell number on the dumb phone's Caller ID but mgetty shows it as "none"...
Thanks Again,
Matt
---------- Post updated at 04:46 PM ---------- Previous update was at 03:51 PM ----------
Ahh crap....
So other then the
15 Zoom USB modems I already purchased for a project, I have 2 or 3 TrendNET USB Modems...
So I shutdown mgetty, unplugged the Zoom modem and connected the TrendNET modem, then restarted mgetty. I did NOT change any of the init-string
stuff or any configuration data and this time when I called from my cell phone, the correct caller-id number showed instantly in the mgetty log file... I really hope
this is not an issue with all the Zoom modems or else I'm SOL.
I was wondering if it was the Caller-ID's AT Command I'm sending to the modem as part of mgetty's config, which is
AT+VCID=1, the
1 simply means to show
formatted CID information. So I changed it to
AT+VCID=2, which means to use unformatted CID information, but that didn't seem to change anything
in terms of receiving any CID information from an outside caller...
Any advice or suggestions??
Thanks Again,
Matt
---------- Post updated at 05:44 PM ---------- Previous update was at 04:46 PM ----------
******** UPDATE ********
So I just tried something else...
I connected the same USB Modem to my Windows XP VM and started Putty Serial connection for the USB Modem. Then the ONLY AT command that I sent to the
Modem was the Caller-ID Command, which is
AT+VCID=1. Then I called the USB Modem connected to the Windows XP machine from an internal extension and got the
4-digit extension as expected in the Caller-ID information. So I hung up that call and called the full DID number from my cell phone this time and Putty then
displayed the FULL, correct Caller-ID information...
So it looks like it might be an issue with mgetty. Any ideas what it could possibly be, I'm at a bit of a loss here..?
Thanks again and sorry for the consecutive posts.
Thanks,
Matt