modular messaging coverage path not working....

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • fsiddi
    Hot Shot
    • Nov 2012
    • 16

    modular messaging coverage path not working....

    Dear Friends,
    i have installed installed MM 5.2 (MSS/MAS/WCWSO) on hp dl 360 g7 as single server configuration..successfully ..and configured MSS and MAS ... i have added subscriber and make congfiguration at CM 5.2 like..hunt group, sip trunk, sip signaling group, aar table, public unknown numbering and coverage path... im able to dial hunt group extension like 7000 ...and get access to mail box number and successfully recorded greeting message to my extension number...but when i configure my IP station and configure coverage path...and dial from any other station...my calls doesnt go to the cover path ..continues bell ringing.....following is my station and coverage path settings.... please suggest the solution....

    station settings...
    ------------
    xtension: 1241 Lock Messages? n BCC: 0
    Type: 1608 Security Code: * TN: 1
    Port: S00408 Coverage Path 1: 99 COR: 4
    Name: Comm Admin Coverage Path 2: COS: 1
    Hunt-to Station:
    STATION OPTIONS
    Time of Day Lock Table:
    Loss Group: 1 Personalized Ringing Pattern: 1
    Message Lamp Ext: 7000
    Speakerphone: 2-way Mute Button Enabled? y
    Display Language: english
    Survivable GK Node Name:
    Survivable COR: internal Media Complex Ext:
    Survivable Trunk Dest? y IP SoftPhone? n

    xtension: 1241 Lock Messages? n BCC: 0
    Type: 1608 Security Code: * TN: 1
    Port: S00408 Coverage Path 1: 99 COR: 4
    Name: Comm Admin Coverage Path 2: COS: 1
    Hunt-to Station:
    STATION OPTIONS
    Time of Day Lock Table:
    Loss Group: 1 Personalized Ringing Pattern: 1
    Message Lamp Ext: 7000
    Speakerphone: 2-way Mute Button Enabled? y
    Display Language: english
    Survivable GK Node Name:
    Survivable COR: internal Media Complex Ext:
    Survivable Trunk Dest? y IP SoftPhone? n


    BUTTON ASSIGNMENTS
    1: call-appr 5:
    2: call-appr 6:
    3: call-appr 7:
    4: 8:
    voice-mail Number: 1241
    ========================
    coverage path settings..
    ========================
    COVERAGE PATH
    Coverage Path Number: 99
    Cvg Enabled for VDN Route-To Party? n Hunt after Coverage? n
    Next Path Number: Linkage
    COVERAGE CRITERIA
    Station/Group Status Inside Call Outside Call
    Active? n n
    Busy? y y
    Don't Answer? y y Number of Rings: 1
    All? n n
    DND/SAC/Goto Cover? y y
    Holiday Coverage? n n
    COVERAGE POINTS
    Terminate to Coverage Pts. with Bridged Appearances? n
    Point1: h99 Rng: Point2:
    Point3: Point4:
    Point5: Point6:
  • ebyh
    Hot Shot
    • Dec 2012
    • 12

    #2
    Hello, assuming you have verified that the PBX Extension field is populated correctly on the voicemail subscriber form... are you familiar with the CM 'list trace' command? (It doesn't work from GEDI, so you'll need to select terminal emulation if using Avaya Site Administration.) Type 'list trace station 7000' then call the number and see if you're then able to see the problem. I've come to find this feature to be a very helpful troubleshooting tool.

    Comment

    • ebyh
      Hot Shot
      • Dec 2012
      • 12

      #3
      Oops, sorry: 'list trace station 1241'

      As a side note, the Message Lamp Ext should match your phone number (1241) as that designates which phone's message light should be activated when a new message is received in mailbox 1241.

      Also, the 'voice-mail Number' field on page 4 of the station form is actually the message retrieval number, which in your case I think would be 7000.

      Comment

      • fsiddi
        Hot Shot
        • Nov 2012
        • 16

        #4
        Thanks ebyh....yeah i very well known of this command to troubleshoot....

        when dialing 7000 from 1241 ( 1st subscriber)
        10:31:34 SIP>INVITE sip:[email protected] SIP/2.0
        10:31:34 Setup digits 7000
        10:31:34 Calling Number & Name NO-CPNumber Test-Set
        10:31:34 SIP<SIP/2.0 100 Trying
        10:31:34 Proceed trunk-group 99 member 37 cid 0x3552
        10:31:34 SIP<SIP/2.0 180 Ringing
        10:31:34 SIP>PRACK sip:172.20.0.13:5061;transport=tls SIP/2.0
        10:31:34 Alert trunk-group 99 member 37 cid 0x3552
        10:31:34 SIP<SIP/2.0 200 OK
        10:31:34 SIP<SIP/2.0 200 OK
        10:31:34 SIP>ACK sip:172.20.0.13:5061;transport=tls SIP/2.0
        10:31:34 active trunk-group 99 member 37 cid 0x3552
        10:31:34 G711MU ss: off ps:20
        rgn:1 [172.20.0.13]:7000
        time data
        10:33:02 Setup digits 7000
        10:33:02 Calling Number & Name NO-CPNumber Comm Admin
        10:33:02 SIP<SIP/2.0 100 Trying
        10:33:02 Proceed trunk-group 99 member 38 cid 0x357a
        10:33:02 SIP<SIP/2.0 180 Ringing
        10:33:02 SIP>PRACK sip:172.20.0.13:5061;transport=tls SIP/2.0
        10:33:02 Alert trunk-group 99 member 38 cid 0x357a
        10:33:02 SIP<SIP/2.0 200 OK
        10:33:02 SIP<SIP/2.0 200 OK
        10:33:02 SIP>ACK sip:172.20.0.13:5061;transport=tls SIP/2.0
        10:33:02 active trunk-group 99 member 38 cid 0x357a
        10:33:02 G711MU ss: off ps:20
        rgn:1 [172.20.0.13]:7000
        rgn:1 [172.20.0.11]:2094
        10:33:02 xoip options: fax:T38 modem: off tty:US uid:0x50080
        xoip ip: [172.20.0.11]:2094
        rgn:1 [172.20.0.11]:2070
        time data
        10:33:02 SIP>INVITE sip:172.20.0.13:5061;transport=tls SIP/2.0
        10:33:02 SIP<SIP/2.0 100 Trying
        10:33:02 SIP<SIP/2.0 200 OK
        10:33:02 G711MU ssff ps:20
        rgn:1 [172.20.1.101]:33664
        rgn:1 [172.20.0.13]:7000
        10:33:02 SIP>ACK sip:172.20.0.13:5061;transport=tls SIP/2.0
        10:33:02 G711MU ss: off ps:20
        rgn:1 [172.20.0.13]:7000
        rgn:1 [172.20.1.101]:33664
        10:33:18 SIP>INVITE sip:172.20.0.13:5061;transport=tls SIP/2.0
        10:33:18 G711MU ss: off ps:20
        rgn:1 [172.20.1.101]:33664
        rgn:1 [172.20.0.11]:2068
        10:33:18 SIP<SIP/2.0 100 Trying
        10:33:18 SIP<SIP/2.0 200 OK

        Comment

        • fsiddi
          Hot Shot
          • Nov 2012
          • 16

          #5
          Thanks friends, i have done it....................issue resolved.........

          Comment

          • geronj
            Aspiring Member
            • May 2013
            • 2

            #6
            Hi,

            Can you please share to us how you did it? Thanks.

            Comment

            • hheart
              Aspiring Member
              • Jun 2013
              • 1

              #7
              please tell me what is solution

              Originally posted by fsiddi View Post
              Thanks friends, i have done it....................issue resolved.........
              Hi friend,

              Could you please tell me what you did exactly. Bcoz I m facing the same problem. ...appreciate if u will help

              Comment

              • fsiddi
                Hot Shot
                • Nov 2012
                • 16

                #8
                Originally posted by hheart View Post
                Hi friend,

                Could you please tell me what you did exactly. Bcoz I m facing the same problem. ...appreciate if u will help

                sorry friend replying very very late...well i found a document provided by avaya support and make some changes in my sip trunk group and route pattern.........

                Comment

                • ilalpatidar
                  Whiz
                  .
                  • Jan 2014
                  • 37

                  #9
                  What document you have referred can you share the same or link to it.

                  Comment

                  Loading