Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

FOP2 Community Forum

  1. Home
  2. Feedback
  3. SCCP phones support

SCCP phones support

Scheduled Pinned Locked Moved Feedback
13 Posts 3 Posters 182 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • N
    N
    nicolas
    wrote on last edited by
    #2

    I do not know if skinny fires any event for a phone being on or off line. As I do not have any phones myself to test I cannot tell you either, but you can run fop2 in debug mode and capture events, so I can look into them and see if there is anything that can be done.

    service fop2 stop
    cd /usr/local/fop2
    script capture.log
    ./fop2_server -X 1
    (log into fop2, then make a phone available or unavailable)
    ctrl-C
    exit
    service fop2 start

    At that point you have the capture.log file with AMI events related to your environment. You can send that to me telling me what phone got offline or online that was not shown in the fop2 display, so I can trace for related events and see if this can be added as a new feature or not (lack of events means fop2 won't be able to tell the change of status)

    Best regards,

    1 Reply Last reply
    0
    • C
      C
      coobic
      wrote on last edited by
      #3

      Events after off phone 1342:

      127.0.0.1 <- Event: PeerStatus
      127.0.0.1 <- Privilege: call,all
      127.0.0.1 <- Timestamp: 1384775220.353184
      127.0.0.1 <- ChannelType: SCCP
      127.0.0.1 <- ChannelObjectType: DeviceLine
      127.0.0.1 <- PeerStatus: DETACHED
      127.0.0.1 <- SCCPDevice: SEP1CAA07E2A4D7
      127.0.0.1 <- SCCPLine: 1342
      127.0.0.1 <- SCCPLineName: �ени� ��ликов
      127.0.0.1 <- SubscriptionId:
      127.0.0.1 <- SubscriptionName:
      127.0.0.1 <- Server: 0

      127.0.0.1 <- Event: DeviceStatus
      127.0.0.1 <- Privilege: call,all
      127.0.0.1 <- Timestamp: 1384775220.353880
      127.0.0.1 <- ChannelType: SCCP
      127.0.0.1 <- ChannelObjectType: Device
      127.0.0.1 <- DeviceStatus: UNREGISTERED
      127.0.0.1 <- SCCPDevice: SEP1CAA07E2A4D7
      127.0.0.1 <- Server: 0

      127.0.0.1 <- Event: ExtensionStatus
      127.0.0.1 <- Privilege: call,all
      127.0.0.1 <- Timestamp: 1384775220.358130
      127.0.0.1 <- Exten: 1342
      127.0.0.1 <- Context: ext-local
      127.0.0.1 <- Hint: SCCP/1342&Custom:DND1342
      127.0.0.1 <- Status: 4
      127.0.0.1 <- Server: 0

      Events after on phone: 1342

      127.0.0.1 <- Event: DeviceStatus
      127.0.0.1 <- Privilege: call,all
      127.0.0.1 <- Timestamp: 1384775367.905977
      127.0.0.1 <- ChannelType: SCCP
      127.0.0.1 <- ChannelObjectType: Device
      127.0.0.1 <- DeviceStatus: PREREGISTERED
      127.0.0.1 <- SCCPDevice: SEP1CAA07E2A4D7
      127.0.0.1 <- Server: 0

      127.0.0.1 <- Event: PeerStatus
      127.0.0.1 <- Privilege: call,all
      127.0.0.1 <- Timestamp: 1384775368.887042
      127.0.0.1 <- ChannelType: SCCP
      127.0.0.1 <- ChannelObjectType: DeviceLine
      127.0.0.1 <- PeerStatus: ATTACHED
      127.0.0.1 <- SCCPDevice: SEP1CAA07E2A4D7
      127.0.0.1 <- SCCPLine: 1342
      127.0.0.1 <- SCCPLineName: �ени� ��ликов
      127.0.0.1 <- SubscriptionId:
      127.0.0.1 <- SubscriptionName:
      127.0.0.1 <- Server: 0

      127.0.0.1 <- Event: ExtensionStatus
      127.0.0.1 <- Privilege: call,all
      127.0.0.1 <- Timestamp: 1384775368.887237
      127.0.0.1 <- Exten: 1342
      127.0.0.1 <- Context: ext-local
      127.0.0.1 <- Hint: SCCP/1342&Custom:DND1342
      127.0.0.1 <- Status: 0
      127.0.0.1 <- Server: 0

      127.0.0.1 <- Event: DeviceStatus
      127.0.0.1 <- Privilege: call,all
      127.0.0.1 <- Timestamp: 1384775369.125328
      127.0.0.1 <- ChannelType: SCCP
      127.0.0.1 <- ChannelObjectType: Device
      127.0.0.1 <- DeviceStatus: REGISTERED
      127.0.0.1 <- SCCPDevice: SEP1CAA07E2A4D7
      127.0.0.1 <- Server: 0

      1 Reply Last reply
      0
      • N
        N
        nicolas
        wrote on last edited by
        #4

        Strange, as any PeerStatus that is not "Registered" or "Reachable" is marked as unregistered. I have added "ATTACHED" to the "ok" states, but the detached status should fall into the unregistered/notok events as it is not either registered or reachable, and thus the button should be grayed out.

        1 Reply Last reply
        0
        • N
          N
          nicolas
          wrote on last edited by
          #5

          Unless the PeerStatus is not fired when the phone is unplugged, but when you request status...

          1 Reply Last reply
          0
          • C
            C
            coobic
            wrote on last edited by
            #6

            I have added "ATTACHED" to the "ok" states,
            Where i can download latest version of FOP2 for check this (we use 2.26 from official site).

            Unless the PeerStatus is not fired when the phone is unplugged, but when you request status...
            Im wait this messages on console output and dont click anything after phone on/off.

            What additional information needed for resolve this?

            1 Reply Last reply
            0
            • N
              N
              nicolas
              wrote on last edited by
              #7

              http://download.fop2.com/fop2-2.27j-centos-i386.tgz
              http://download.fop2.com/fop2-2.27j-centos-x86_64.tgz

              I do not need more information... anyways, without the ATTACHED addition, the PeerStatus with DETACHED should result in a greyed out button anyways. Not sure why it did not work in your case. You can try the above version and see how it goes. If there are still problems, you will have to capture complete output when running fop2_server in debug level 1 and send that to me so I can rerun those events through and see how fop2 reacts to them.

              Best regards,

              1 Reply Last reply
              0
              • C
                C
                coobic
                wrote on last edited by
                #8

                Thanks for reply!

                Im upgrade 2.26->2.27j (x86_64) and nothing changed. Because im cannot find how to attach the debug output here, i put it on online storage:
                [url:3t852f4o]http://rapidshare.com/share/4BB2F210D5B5DB0D87FBBCD7E5F31410[/url:3t852f4o]

                Some comments to debug (-X 1):
                phone 1384 off and never on - incorrectly show in FOP2
                phone 1342 off and on then debug is collected (comments marked in log OFF and ON).

                Also (im already read other topics) UTF-8 (russian language support) in my configuration is broken after upgrade. Phone labels is showing as: label=Бехер Вера instead of Russian characters. Im attached screenshot to debug logs.
                Its perfectly work in 2.26 without SET NAMES and other 'hacks'. UTF-8 in my configuration stored in FreePBX database with default settings (collate latin-1) and correctly showed by fop2. Im try different things (SET NAMES and other), but cannot find the solution (i can create another topic if needed).

                Many thanks for future reply.

                1 Reply Last reply
                0
                • C
                  C
                  coobic
                  wrote on last edited by
                  #9

                  Sorry for trouble you Nicolás!

                  Have you any updates relatively to this issue?

                  1 Reply Last reply
                  0
                  • N
                    N
                    nicolas
                    wrote on last edited by
                    #10

                    I cannot make any updaes as I do not have SCCP phones, for what I see on your events, fop2 should work correctly. The problem is that I do not know if those events happen when they are supposed to happen (when you unplug or turn onn/off a phone). contact me via the live help, as the only way to know that is by working on your actual system. I am online now if you want to chat.

                    Best regards,

                    1 Reply Last reply
                    0
                    • C
                      C
                      coobic
                      wrote on last edited by
                      #11

                      Many thanks for Online Chat.

                      Problem is resolved and i think these changes will be included in next stable version.

                      1 Reply Last reply
                      0
                      • I
                        I
                        innatetech
                        wrote on last edited by
                        #12

                        If it would be of use in FOP2 development, I'd happily contribute a SCCP deskset for testing, etc. My intention is to keep our SCCP extensions on CME, but support in FOP2 for SCCP presence info is quite desirable.

                        1 Reply Last reply
                        0
                        • N
                          N
                          nicolas
                          wrote on last edited by
                          #13

                          If it would be of use in FOP2 development, I'd happily contribute a SCCP deskset for testing, etc. My intention is to keep our SCCP extensions on CME, but support in FOP2 for SCCP presence info is quite desirable.

                          SCCP registration/presence support was tweaked/fixed already. You can install FOP 2.27 and see extension buttons greyed out if they are not plugged in/registered into asterisk. I do not have any idea on how to integrate that with CME? I do not think FOP2 will work besides or outside the asterisk manager (AMI), as FOP2 does not talk sccp, it just talks to asterisk via AMI.

                          Best regards,

                          1 Reply Last reply
                          0

                          Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                          Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                          With your input, this post could be even better 💗

                          Register Login
                          Reply
                          • Reply as topic
                          Log in to reply
                          • Oldest to Newest
                          • Newest to Oldest
                          • Most Votes


                          • Login

                          • Don't have an account? Register

                          • Login or register to search.
                          Powered by NodeBB Contributors
                          • First post
                            Last post
                          0
                          • Categories
                          • Recent
                          • Tags
                          • Popular
                          • World
                          • Users
                          • Groups