Greetings! We are having a problem sending faxes to a specific number in the Cleveland OH metro area from downtown Cleveland. All 9 fax machines send and receive faxes to every other destination without a problem, but constantly fail to this one. The destination's fax tone is heard, then it stops and our machines indicate they are waiting to attempt a redial. We have tried from every fax machine and from analog ports on the VG224 [24FXS-SCCP] and from ports on the EVM-HD-8FXS/DID-SCCP card in the Cisco 3845 [rev 1.0] [Cisco 3800 Software C3845-SPSERVICESK9-M, Version 12.4T3, Release Software [fc2]] gateway, running H.323, all with the same result. But when using a standard POTS line, the faxes complete without a problem. Additionally, faxes sent to this same destination from another node in Cleveland running the same physical and logical configurations complete without a problem. Finally, the tech at the destination says they are receiving faxes from many others and have heard no other complaints.
I have built a specific dial peer to provide more testing capability without disrupting other fax traffic: [DNs partially x'd out]
peer type = voice, system default peer = FALSE, information type = voice,
Here is a debug of one of the calls: [I have x'd the last 7 digits of the DNs]
Feb 27 21:38:18.461: ISDN Se0/2/0:23 Q931: TX -> SETUP pd = 8 callref = 0x7B6B Bearer Capability i = 0x8090A2 Standard = CCITT Transfer Capability = Speech Transfer Mode = Circuit Transfer Rate = 64 kbit/s Channel ID i = 0xA98397 Exclusive, Channel 23 Calling Party Number i = 0x2183, '216xxxxxxx' Plan:ISDN, Type:National Called Party Number i = 0xA1, '1330xxxxxxx' Plan:ISDN, Type:National Feb 27 21:38:18.525: ISDN Se0/2/0:23 Q931: RX <- CALL_PROC pd = 8 callref = 0xFB6B Channel ID i = 0xA98397 Exclusive, Channel 23
Feb 27 21:38:20.961: ISDN Se0/2/0:23 Q931: RX <- ALERTING pd = 8 callref = 0xFB6B Progress Ind i = 0x8488 - In-band info or appropriate now available
Feb 27 21:38:23.157: ISDN Se0/2/0:23 Q931: RX <- CONNECT pd = 8 callref = 0xFB6B Feb 27 21:38:23.969: %SYS-3-MSGLOST: 1 messages lost because of queue overflow Feb 27 21:38:23.157: %ISDN-6-CONNECT: Interface Serial0/2/0:22 is now connected to 1330xxxxxxx N/A
Feb 27 21:39:03.941: ISDN Se0/2/0:23 Q931: TX -> DISCONNECT pd = 8 callref = 0x7B6B Cause i = 0x8090 - Normal call clearing Feb 27 21:39:04.125: ISDN Se0/2/0:23 Q931: RX <- RELEASE pd = 8 callref = 0xFB6B Feb 27 21:39:04.129: ISDN Se0/2/0:23 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x7B6B
Does anyone see anything strange here or have any suggestions for other configurations that would resolve this issue? It seems to be a problem with the handshake between the machines, but we have several brands, models and ages of equipment at the site, and none of them work.
Does your provider require you to dial a 7 digit or 10 digit number if its a local call? I've seen issues in Texas where the carrier was very particular when dialing metro numbers. And they never accepted a 1 in the front.
I'm not able to access my old voice mail messages all of a sudden. The recording says something like 'the message is currently not available'. This has never happened before in all the years I have been using this system. I have t...
If you have 2 ISR routers, one acting as Failover, do we need to have both the same number of SRST licenses on the 2 routers?
No. You will only need the SRST licenses on the primary router. Because this feature...