You may have to put some commas ( , ) after your dialing string. Some modems are still negotiating EC protocols when the next CR is sent by WUG. If that is the case, the modem will hang-up before EC is negotiated. There also may be a part of your INIT string that will disable the EC protocol for 2400 bps.
But I have always fixed it by adding the commas. Yours would be ATDT4087144,,, (each comma usually makes the negotiation take 2 seconds longer.) Good luck... trial and error sometimes it the rule with notifications. Matt ----- Original Message ----- From: "Diego Costa" <[EMAIL PROTECTED]> To: "WhatsUp Forum" <[EMAIL PROTECTED]> Sent: Thursday, April 11, 2002 1:35 PM Subject: [WhatsUp Forum] Pager Notification > I've got a problem with the pager notification in WhatsUP Gold 6.02. When I > try to send a pager notification test this is what the debug log shows: > > Sending message to 2532 via 4087144 on COM1 > sending "ATE0Q0V1X4 > " > waiting for completion > returned " > OK > " > sending "ATDT4087144 > " > waiting for completion > returned " > CARRIER 2400 > " > sending " > " > returned " > NO CARRIER > " > sending "+++" > sending "ATH0 > " > waiting for completion > returned " > OK > " > > Then ... the program says "Failed to Send Pager Message" > > I'm using a 56K Rockwell Esternal Modem with ATE0Q0V1X4 in the > initialization string. The pager works with TAP. > > I just can't make it work, you have any idea of what can I do to solve it ? > > Thanks! > > > Please visit http://www.ipswitch.com/support/mailing-lists.html > to be removed from this list. > > An Archive of this list is available at: > http://www.mail-archive.com/whatsup_forum%40list.ipswitch.com/ > > Please visit http://www.ipswitch.com/support/mailing-lists.html to be removed from this list. An Archive of this list is available at: http://www.mail-archive.com/whatsup_forum%40list.ipswitch.com/
