Can someone help with a Cisco 3640 IOS (12.2(2).XT3) acting as a VOIP gateway, connected to a Nortel Meridian option 81C. Direct PRI to the Meridian. 3640 configured as user side, switch type DMS 100, Meridian setup as Network side switch type s100. Receiving the following Debug q931 messages:
Not sure how the 3640 is setup but from the debugs it looks like you get connect message from the gateway and immedeatly after tht we receive release from pbx. Is there a direct-inward-dial under the incoming dial-peer ? or do you want to configure this gateway as 2 stage dialing.
Its a possiblity that the pbx may want to see alert before connect so sends release after connect.
Found the fix for this issu. Apparently when the PBX is setup for DID and not TIE we receive the error messages seen. Here is a blurp from the documentation and email I have sent out.
PBX to NI2 User
Cisco to primary-NI Network
Nortel Meridian 1 Option 81C operation set for User side under LD 17, layers 2 & 3 protocol side are set for the user side.
The Cisco 3640 router set to the network
This will allow the 3640 to accept any number length
If the 3640 has an issue with Network side, lets switch them after testing.
When set to primary-ni (network side), the Cisco 3640 router ***accepts dialed numbers of less than 10 digits provided the trunk type is set for
TIE, (TKTP=TIE under LD 16 & 14). *** The PBX is sending 4 digits.
***When the trunk type is set for DID, "the Nortel PBX must send at least 10 digits" for the Cisco 3640 to properly route the call. Otherwise, the Cisco 3640 router sends back a Release message containing a release cause of Invalid Number Format.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.