" /> Can you view the currently registered SIP extensions in CCPulse? - Genesys CTI User Forum

Author Topic: Can you view the currently registered SIP extensions in CCPulse?  (Read 2494 times)

Offline nonny

  • Full Member
  • ***
  • Posts: 218
  • Karma: 2
Advertisement
Is there any way within CCPulse to view which SIP end points have registered?  We have a number of SIP end points using SIP Server solely for telephony, not URS/Routing.  Obviously where agents are concerned we can see the Place and agent status.  How can I view what SIP extensions are currently actively registered (Bria etc)?  I don't just mean which are enabled/disabled in CME :)

Offline cavagnaro

  • Administrator
  • Hero Member
  • *****
  • Posts: 7641
  • Karma: 56330
Re: Can you view the currently registered SIP extensions in CCPulse?
« Reply #1 on: March 25, 2015, 12:20:06 AM »
??? ???
To register agains SIP Server you use a CME DN number.
You monitor these on CCPulse not as Place but as Extension inside Switch objects.

Offline nonny

  • Full Member
  • ***
  • Posts: 218
  • Karma: 2
Re: Can you view the currently registered SIP extensions in CCPulse?
« Reply #2 on: March 25, 2015, 10:27:48 AM »
Yes I've gotten that far but what else do I need to do to be able to see in CCPulse if the SIP phone (Bria etc) has actually started and registered against that DN?

Offline Kubig

  • Hero Member
  • *****
  • Posts: 2755
  • Karma: 44
Re: Can you view the currently registered SIP extensions in CCPulse?
« Reply #3 on: March 25, 2015, 10:31:06 AM »
You are not able to monitor if the SIP phone is just registered against Genesys SIP, with except deployment where the SIP publish function is used (because with register is the EventAgentLogin generated). You can just monitor if the agent is logged into the DN/Place

Offline nonny

  • Full Member
  • ***
  • Posts: 218
  • Karma: 2
Re: Can you view the currently registered SIP extensions in CCPulse?
« Reply #4 on: March 25, 2015, 10:34:22 AM »
Thanks Kubig I was hoping that wasn't the case but expected it to be.