Bogen TAMB2 system (PAGING)



So I got a request to look at the paging over an intercom system and look at why the system was not ringing when they would forward calls to the paging system.


They use Bogen TAMB2 and on this system


You can see the connectors for the system on the back. The "green" farthest left is the station trunk.  When connecting back to the voice gateway you would connect these back on the "tip" and "ring" essentially a loopstart connection.


For this voice port associated to it we can configure the loopstart connection :



Router#sh voice port summary

            - This will show all voice ports



Router#sh voice port 1/0/0
 Voice card specific Info Follows:
 Signal Type is loopStart
 Ring Frequency is 25 Hz
 Hook Status is On Hook
 Ring Active Status is inactive
 Ring Ground Status is inactive
 Tip Ground Status is inactive
 Digit Duration Timing is set to 100 ms
 InterDigit Duration Timing is set to 100 ms
 Hookflash-in Timing is set to max=1000 ms, min=150 ms
 Hookflash-out Timing is set to 400 ms
 No disconnect acknowledge
 Ring Cadence is defined by CPTone Selection
 Ring Cadence are [20 40] * 100 msec
 Ringer Equivalence Number is set to 1

               - At the bottom you will get Voice Card Specifics and can see the Signal Type is loopStart

Also to see all the dial-peers associated to the device we can look through the dial peer patterns by doing the following :

               Router#sh dial-peer voice summary


OR

               Router#debug dialpeer 

This will allow us to be able debug the dialpeer being used as we dial the devices specific number. So for example if I call 612-555-5555 it will show me the dial peer that is being used to go to the device.





BACK TO CONFIGURATION OF LOOPSTART :

    Router(config)#voice-port 1/0/0
    Router(config-voiceport)#
    Router(config-voiceport)#signal loopStart


After configuring the interface for loopStart make sure you reset the interface:
    Router(config)#voice-port 1/0/0
    Router(config-voiceport)#shutdown
    Router(config-voiceport)#no shutdown


There were some other tidbits that ended up fixing the entire situation like an AMP replacement and tracking of the directory number used in Cisco Unified Communications Manager. Result now though.... is they are up and running!





Comments

Popular posts from this blog

HULC LED PROCESS - 3750 High CPU

%PLATFORM_UCAST-4-PREFIX: --------- TCAM 3750 Switch