SCN troubleshooting

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
  • brunem
    Member
    • Aug 2012
    • 9
    #1

    SCN troubleshooting

    Good Morning

    I updated IP Office 500 V2 from 6.0 to 9.0 ( I upgraded from 6 to 7 to 8 to 9 by inserting immediately upgrade license.)

    Both machines have licensed four-channel voice network and the other machine is a preferred edition with a voice mail pro working perfectly.

    I try to connect the 2 machine with H323 trunk and SCN , but the machine i have update with system status show messsage small community network :not enable.

    Runs H323 IP trunks, routing calls with the function codes I can make calls between extensions, but the services related to scn do not work

    The two PABX are connected to a company vpn ,from any of the two locations I can see the two PABX and access manager with no problems.

    1- usually all the problems related to scn are due to network problems

    I think make trace with Monitor >Routing and enable AVRIP Tx & AVRIP Rx to analyze if Port 50795 (IPO Voice Networking): Small Community Network signalling (AVRIP) and BLF updates. working or maybe firewall block the traffic.

    2- any suggestion are appreciate , to make troubleshooting ?



    Thanks Mas
    Tags: None
  • ista4
    Legend
    • May 2011
    • 403
    #2
    Are both the IPO's on 9.0? they need to be.
    The difference between the two can be max 1 release.
    So if one is on 9.0 then the other must be on 8.1 at least.

    The other option which i have had myself is to recreate the SCN trunk.
    I have seen that the SCN trunk was not working while everything else was correct.
    Try to remove it on the upgraded system, reboot and recreate it and reboot again.
    If that fails then it on both systems.

    Comment

    • brunem
      Member
      • Aug 2012
      • 9
      #3
      I have two IP 500 V2 9.0.0.0 build 829 with license IP 500 Voice Networking Channels 4
      with COMBO CARD both system:

      configuration is this

      System A
      IP Address 192.168.2.80 IP Mask 255.255.255.0 Primary Trans.IP Address 0.0.0.0
      IP Route IP Address 0.0.0.0 IP Mask 0.0.0.0 Gateway IP Address 192.168.2.1 Destination LAN1
      Gateway IP Address 192.168.40.48
      Code Selection : System Default
      Services : IP Office SCN
      Allow Direct Media Path
      Line Number of Channels 10
      Outgoing Group ID : 1


      System B
      IP Address 192.168.40.48 IP Mask 255.255.255.0 Primary Trans.IP Address 0.0.0.0
      IP Route IP Address 0.0.0.0 IP Mask 0.0.0.0 Gateway IP Address 192.168.40.1 Destination LAN1
      Gateway IP Address 192.168.2.80
      Code Selection : System Default
      Services : IP Office SCN
      Allow Direct Media Path
      Line Number of Channels 10
      Outgoing Group ID : 1

      Yes i have VPN between IP Office , but i dnt know what type of router because other people watch network.

      And this real log

      SYSTEM A

      ********** SysMonitor v9.0.0.0 build 829 [connected to 192.168.2.80 ] **********
      ********** Reconnect Selected **********
      ********** contact lost with 192.168.2.80 at 11:22:59 5/8/2014 - reselect = 0 ************************************************** **************************
      ********** SysMonitor v9.0.0.0 build 829 **********
      ********** contact made with 192.168.2.80 at 11:23:00 5/8/2014 **********
      ********** System (192.168.2.80) has been up and running for 7mins and 4secs(424270mS) **********
      ********** Warning: TEXT File Logging selected **********

      ********** Warning: TEXT Logging to C:\Program Files\Avaya\IP Office\Monitor\\TMP1.$$$ File: STARTED on 5/8/2014 11:23:00 ********** 424270mS PRN: Monitor Started IP=192.168.2.104 IP 500 V2 9.0.0.0 build 829 StarterKit (IP Office: Supports Unicode, System Locale is default) 424270mS PRN: LAW=A PRI=0, BRI=2, ALOG=4, VCOMP=20, MDM=0, WAN=0, MODU=0 LANM=0 CkSRC=1 VMAIL=1(VER=3 TYP=1) 1-X=0 CALLS=0(TOT=0) 428270mS PRN: +++ START OF UDP MONITOR CLIENT DUMP +++ 428270mS PRN: CLIENT: IPAddress=192.168.2.104 UDPPort=56676 LastReceived=424278(3992) LastSent=428270(0) LastOldUpdate=424270(4000) SentPackets=9 MissedPackets=0 OldSentPackets=0 OldMissedPackets=0 428270mS PRN: ++++ END OF UDP MONITOR CLIENT DUMP ++++ 431122mS AVRIP Tx: v=192.168.40.48 send=0 receive=0 requiresvoicemail 0 operational 1 version 3 recordsupported 1 IPaddr 255.255.255.255 hops=0 voice=128 441122mS AVRIP Tx: v=192.168.40.48 send=0 receive=0 requiresvoicemail 0 operational 1 version 3 recordsupported 1 IPaddr 255.255.255.255 hops=0 voice=128 451122mS AVRIP Tx: v=192.168.40.48 send=0 receive=0 requiresvoicemail 0 operational 1 version 3 recordsupported 1 IPaddr 255.255.255.255 hops=0 voice=128 461122mS AVRIP Tx: v=192.168.40.48 send=0 receive=0 requiresvoicemail 0 operational 1 version 3 recordsupported 1 IPaddr 255.255.255.255 hops=0 voice=128 471122mS AVRIP Tx: v=192.168.40.48 send=0 receive=0 requiresvoicemail 0 operational 1 version 3 recordsupported 1 IPaddr 255.255.255.255 hops=0 voice=128 481122mS AVRIP Tx: v=192.168.40.48 send=0 receive=0 requiresvoicemail 0 operational 1 version 3 recordsupported 1 IPaddr 255.255.255.255 hops=0 voice=128
      ********** SysMonitor v9.0.0.0 build 829 [connected to 192.168.2.80 ] ********** 491122mS AVRIP Tx: v=192.168.40.48 send=0 receive=0 requiresvoicemail 0 operational 1 version 3 recordsupported 1 IPaddr 255.255.255.255 hops=0 voice=128 501123mS AVRIP Tx: v=192.168.40.48 send=0 receive=0 requiresvoicemail 0 operational 1 version 3 recordsupported 1 IPaddr 255.255.255.255 hops=0 voice=128
      SYSTEM B

      ********** Reconnect Selected **********
      ********** contact lost with 192.168.40.48 at 11:19:19 5/8/2014 - reselect = 0 ************************************************** **************************
      ********** SysMonitor v9.0.0.0 build 829 **********
      ********** contact made with 192.168.40.48 at 11:19:19 5/8/2014 **********
      ********** System (192.168.40.48) has been up and running for 4mins and 25secs(265991mS) **********
      ********** Warning: TEXT File Logging selected **********

      ********** Warning: TEXT Logging to C:\Program Files\Avaya\IP Office\Monitor\\TMP1.$$$ File: STARTED on 5/8/2014 11:19:19 ********** 265991mS PRN: 265991mS PRN: 269991mS PRN: +++ START OF UDP MONITOR CLIENT DUMP +++ 269991mS PRN: CLIENT: IPAddress=192.168.2.104 UDPPort=56676 LastReceived=266021(3970) LastSent=269991(0) LastOldUpdate=265991(4000) SentPackets=7 MissedPackets=0 OldSentPackets=0 OldMissedPackets=0 269991mS PRN: ++++ END OF UDP MONITOR CLIENT DUMP ++++
      ********** SysMonitor v9.0.0.0 build 829 [connected to 192.168.40.48 ] **********
      ********** Warning: Missed 1 packet(s) Total late 1 packet(s) ********** 275645mS AVRIP Tx: v=192.168.2.80 send=0 receive=0 requiresvoicemail 1 operational 0 version 0 recordsupported 0 IPaddr 255.255.255.255 hops=0 voice=128
      ********** Warning: Missed 1 packet(s) Total late 1 packet(s) ********** 285645mS AVRIP Tx: v=192.168.2.80 send=0 receive=0 requiresvoicemail 1 operational 0 version 0 recordsupported 0 IPaddr 255.255.255.255 hops=0 voice=128
      ********** Warning: Missed 1 packet(s) Total late 1 packet(s) ********** 295645mS AVRIP Tx: v=192.168.2.80 send=0 receive=0 requiresvoicemail 1 operational 0 version 0 recordsupported 0 IPaddr 255.255.255.255 hops=0 voice=128
      ********** Warning: Missed 1 packet(s) Total late 1 packet(s) ********** 305645mS AVRIP Tx: v=192.168.2.80 send=0 receive=0 requiresvoicemail 1 operational 0 version 0 recordsupported 0 IPaddr 255.255.255.255 hops=0 voice=128
      ********** SysMonitor v9.0.0.0 build 829 [connected to 192.168.40.48 ] **********
      ********** Warning: Missed 1 packet(s) Total late 1 packet(s) ********** 315645mS AVRIP Tx: v=192.168.2.80 send=0 receive=0 requiresvoicemail 1 operational 0 version 0 recordsupported 0 IPaddr 255.255.255.255 hops=0 voice=128
      ********** Warning: Missed 1 packet(s) Total late 1 packet(s) ********** 325645mS AVRIP Tx: v=192.168.2.80 send=0 receive=0 requiresvoicemail 1 operational 0 version 0 recordsupported 0 IPaddr 255.255.255.255 hops=0 voice=128
      ********** Warning: Missed 1 packet(s) Total late 1 packet(s) ********** 335645mS AVRIP Tx: v=192.168.2.80 send=0 receive=0 requiresvoicemail 1 operational 0 version 0 recordsupported 0 IPaddr 255.255.255.255 hops=0 voice=128
      ********** Warning: Missed 1 packet(s) Total late 1 packet(s) ********** 345645mS AVRIP Tx: v=192.168.2.80 send=0 receive=0 requiresvoicemail 1 operational 0 version 0 recordsupported 0 IPaddr 255.255.255.255 hops=0 voice=128
      ********** Warning: Missed 1 packet(s) Total late 1 packet(s) ********** 355645mS AVRIP Tx: v=192.168.2.80 send=0 receive=0 requiresvoicemail 1 operational 0 version 0 recordsupported 0 IPaddr 255.255.255.255 hops=0 voice=128
      ********** Warning: Missed 1 packet(s) Total late 1 packet(s) ********** 365645mS AVRIP Tx: v=192.168.2.80 send=0 receive=0 requiresvoicemail 1 operational 0 version 0 recordsupported 0 IPaddr 255.255.255.255 hops=0 voice=128
      ********** Warning: Missed 1 packet(s) Total late 1 packet(s) ********** 375645mS AVRIP Tx: v=192.168.2.80 send=0 receive=0 requiresvoicemail 1 operational 0 version 0 recordsupported 0 IPaddr 255.255.255.255 hops=0 voice=128 385645mS AVRIP Tx: v=192.168.2.80 send=0 receive=0 requiresvoicemail 1 operational 0 version 0 recordsupported 0 IPaddr 255.255.255.255 hops=0 voice=128
      ********** SysMonitor v9.0.0.0 build 829 [connected to 192.168.40.48 ] **********
      ********** Warning: Missed 1 packet(s) Total late 1 packet(s) ********** 395645mS AVRIP Tx: v=192.168.2.80 send=0 receive=0 requiresvoicemail 1 operational 0 version 0 recordsupported 0 IPaddr 255.255.255.255 hops=0 voice=128

      And there is possible wrong configuration with H323 Trunk because i have 20 Channels ( 10 Outgoing Channels ) in all system ?

      I try delete H323 Trunks both system > Reboot > create again H323 system > Reboot again , but SCN still not enable

      any suggestion ?

      thanks
      Last edited by brunem; 08-05-2014, 11:43 AM.

      Comment

      • bejarj
        Aspiring Member
        • Feb 2014
        • 1
        #4
        the small comunty configuratio n change

        On Trunk lines select wit rigth click IP Office Line


        Once its create, verify on transport type "Propietary" amd Networking Level SCN.


        Configure the facilities on SCN back up Options.


        Terminar la configuración de manera acostumbrada y probar la conectividad realizando llamadas.

        Enabling Small Community Networking
        The process below adds an IP Office Line to the system configuration. It is assumed that data routing between the systems has already been configured and tested. Adding Small Community Network connections between systems can also be done using Manager's Small Community Network Management mode.
        Parent topic: Configuring Small Community Networking
        Setup the VoIP Line from System A to System B
        About this task
        Receive the system configuration for System A. Prepare the system for addition to the Small Community Network:
        1. Change all extensions numbers and names to values that will be unique within the multi-site network.
        o For users and extensions this can be done using the Extension Renumber tool. That will adjust all users and extension and all items using those numbers, for example hunt group memberships and incoming call routes.
        o For hunt groups, each hunt group must be change individually.
        2. Click Line to display a list of existing lines.
        3. Right-click on the displayed list and select New and then IP Office Line.
        4. Select the Line tab and set the following:
        o In the Transport Type field, select Proprietary.
        o In the Networking Level field, select SCN.
        o In the Description field, enter a description of the link. For example System B Small Community Network.
        o Set the Outgoing Group ID to a unique value. For example match the automatically assigned Line Number value.
        5. Under Gateway, set the following:
        o For the Gateway IP Address, enter the IP address of the remote System B.
        o Use of IP Office SCN - Fallback is detailed in Small Community Network Fallback.
        6. Click the VoIP Settings tab.
        o
        o Select the preferred Compression Mode. The same mode must be used by all VoIP lines and extensions within the network.
        o The other option can be configured as required but must be matched by the other IP Office Lines in the network. For example the Silence Suppression settings on all the network trunks must match.
        7. Select System | Voicemail.
        a. Only one system should have its Voicemail Type set to Voicemail Pro/Lite.
        The Voicemail IP Address will be the IP address of the central voicemail server PC.
        b. Any other system with its own Voicemail Pro server PC should have its Voicemail Type set to Distributed Voicemail.
        The Voicemail IP Address should be the IP address of the distributed voicemail server PC. The Voicemail Destination should be set to the Outgoing Group ID used for the Small Community Network line to the system that is set as Voicemail Pro/Lite.
        c. All other systems should have their Voicemail Type set to Centralized Voicemail.
        The Voicemail Destination should be set to the Outgoing Group ID used for the Small Community Network line to the system that is set as Voicemail Pro/Lite.
        Save the configuration and reboot System A.
        Next Steps
        Set up the IP Office Line from B to A.
        Setup the VoIP Line from System B to System A
        1. On the remote system, repeat the previous steps to create an IP Office Line to System A. As stated above, where possible the line settings, especially the VoIP settings, must match those used for other IP Office Lines in the network.
        2. Load the configuration and reboot the remote system.
        Next Steps
        Test by making calls between extensions on the different systems

        Comment

        • havel3
          Guru
          • Nov 2012
          • 148
          #5
          First things first, if you have a license for four channels then do not allocate more then four channels.
          The outgoing Line IDs must have a unique number within the SCN, otherwise call route optimalisation will not work.
          Can you call extensions on the other site using shortcodes?:
          SC= 3xx (extensions othe site) TN=3N LineID=H323 trunk outgoing ID Action=Dial
          Use wireshark to see if SCN packets arrive from the remote site, if not then check firewall ( number one in failure of SCN )
          Upgrade IP Office to the latest R9 version, the one you use is a first time release and may/will have bugs which may interfere a proper working

          Comment

          Previous template Next
          Loading