Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

BLF over SCN 2

Status
Not open for further replies.

kolob4all

Vendor
Sep 13, 2010
143
US
500 v8.0.18 both sites
SCN is up and running.
Have no issues dialing each site.
Can add users from different sites to hunt groups.
When trying to set up User button only local users are available.
Checked docs. Features available over SCN:
"Monitoring of user status only. The ability to use additional features such as call pickup via a USER button will differ depending on whether the monitored user is local or remote."

Are there any trick to see BLF over SCN?
 
Pick what you need:

Code:
Port	Protocol		Function
è  25*	SMTP	TCP	Email system alarms from the IP Office to SMTP server. For IP Office 4.2 also used for Voicemail Email on Embedded Voicemail.
è  37	Time	UDP	Time requests from the IP Office to a Time Server (RFC868)
ç  53	DNS	UDP	Domain Name Service responses
ç  67	BOOTP/DHCP	UDP	DHCP Server Operation
è  68	BOOTP/DHCP	UDP	DHCP Client Operation
ç  69	TFTP	UDP	File requests to the IP Office.
è  69	TFTP	UDP	File requests by the IP Office.
ç  80	HTTP	TCP	HTTP File requests.
ç  161*	SNMP	UDP	From SNMP applications.
è  162*	SNMP Trap	UDP	To addresses set in the IP Office configuration.
è  389*	LDAP	TCP	Lightweight Directory Access Protocol.
ç  500	IKE	UDP	Key exchange for IPSec protocol.
è  520	RIP	UDP	"To and from the IP Office to other RIP devices. For RIP1 and RIP2 (RIP1 compatible) the destination address is a subnet
broadcast, eg. 192.168.42.255. For RIP2 Multicast the destination address is 224.0.0.9."
ç  520	RIP	UDP	
ç  1701	L2TP	UDP	Layer 2 Tunneling protocol
ç  1718	H.323	UDP	H.323 Discovery
ç  1719	H.323 RAS	UDP	H.323 Status. VoIP device registering with the IP Office.
è  1720	H.323/H.245	UDP	H.323 Signalling. Data to a registered VoIP device.
è  2127	(UDP) 	UDP	PC Wallboard to CCC Wallboard Server.
è  3478	SIP	UDP	Port used for STUN requests from the IP Office to the SIP provider
ç  5005	RTCPMon	UDP	RTCP Monitoring information from Avaya H323 phones.
çè  5060	SIP	UDP/TCP*	SIP Line Signalling
è  8080	HTTP	TCP	Browser access to the Delta Server application.
è  8089	Enconf	UDP	From the IP Office to the Conferencing Center Server Service.  User access to the conference center is direct via HTTP sessions.
è  8888	HTTP	TCP	Browser access to the IP Office ContactStore (VRL) application.
"çè
49152 to 53247*"	RTP/RTCP	UDP	Dynamically allocated ports used during VoIP calls for RTP and RTCP traffic. The port range can be adjusted through the System | Gatekeeper tab.
è  50791	IPO Voicemail	UDP	To voicemail server address.
ç  50793	IPO Solo Voicemail	UDP	From IP Office TAPI PC with Wave drive user support.
ç  50794	IPO Monitor	UDP	From the IP Office Monitor application.
ç  50795	IPO Voice Networking	UDP	Small Community Network signalling (AVRIP) and BLF updates.  Each system does a broadcast every 30 seconds. BLF updates are sent required up a maximum of every 5 seconds.
ç  50796	IPO PCPartner	UDP	From an IP Office application (for example Phone Manager or SoftConsole). Used to initiate a session between the IP Office and the application.
ç  50797	IPO TAPI	UDP	From an IP Office TAPI user PC.
è  50798	(UDP) 	UDP	IP Office Manager and Upgrade Wizard
è  50799	IPO BLF	UDP	Broadcast to the IP Office LAN and the first 10 IP addresses registered from other subnets.
è  50800	IPO License Dongle	UDP	To the License Server IP Address set in the IP Office config.
ç   50801	Econf	UDP	Conference Center Service to IP Office.
ç   50802	Discovery	TCP	IP Office discovery from Manager.
ç  50804*	"Service Access
Protocol"	TCP	IP Office configuration settings access.
ç  50805*		TCP	TLS Secure"
ç  50808*		TCP	IP Office system status access.
ç  50812*		TCP	IP Office security settings access.
ç  50813*		TCP	TLS Secure"
• CDR/SMDR from the IP Office is sent to the port number and IP address defined during configuration and using either TCP or UDP as selected.			
Application Specifc			
IP Office Application Server			
Port	Component		
"7070
22"	"HTTP/HTTP Access
SFTP Access"		
IP Office Manager			
Port	Component		Location - %ProgramFiles%\Avaya\IP Office"TCP 50802
TCP 50804
TCP 50812
UDP 50798"	IP Office Manager		Manager\manager.exe
SoftConsole			
Port	Component		Location - %ProgramFiles%\Avaya\IP Office"UDP 50796
UDP 50799"	"SoftConsole
"		SoftConsole\SoftConsole.exe
Phone Manager			
Port	Component		Location - %ProgramFiles%\Avaya\IP Office"UDP 50796
UDP 50799"	Phone Manager		Phone Manager\PhoneManager.exe
"UDP 1719
UDP 1720"	Phone Manager VOIP Server		Phone Manager\iClaritySvr.exe
Contact Store			
Port	Component		Location - %ProgramFiles%\Avaya\IP Office"TCP 8888
UDP 50791
UDP 50795"	Contact Store		Witness\tomcat5024\bin\tomcat5.exe
System Monitor			
Port	Component		Location - %ProgramFiles%\Avaya\IP OfficeUDP 50794	System Monitor		Monitor\sysmonitor.exe
TAPI2			
Port	Component		Location - %ProgramFiles%\Avaya\IP OfficeUDP 50797	TAPI2		TAPI\tspi2w.tsp
Voicemail Pro Service			
Port	Description		
TCP 25	Used to listen for SMTP connections.		
UDP 37 	Used to receive time requests (RFC 868).		
TCP 143 	Used to service IMAP4 requests.		
UDP 50791 	Used to receive requests from IP Office PBX.		
TCP 50791 	Used to receive requests fromone-X Portal for IP Office.		
TCP 50791 	Used to receive connections from Voicemail Pro client.		
			
One X Portal 			
Port	Description		
4560	This port is used by log4j socket appender.		
5222	This port is used for XMPP client/server communication.		
5269	This port is used for server to server federation. This port federates with the External XMPP servers or XMPP enabled servers such as GTalk, Yahoo, and MSN.		
5269	This port is used for XMPP server to server federation. If the customer is not intending to federate with external XMPP servers then this port does not need to be opened on the firewall.		
8005	Used by the Tomcat shutdown listener.		
8080	Default HTTP browser access port. This port number can be changed during installation.		
8082	The database component of the one-X Portal for IP Office uses this port.		
8086	This port is used for HTTPS access to MyBuddy.		
8443	Used for HTTPS access to one-X Portal for IP Office (Only for Windows installation of the one-X Portal for IP Office).		
8444	This port is used for initial communication between the mobility client (Android/iPhone) and the one-X Portal for IP Office. If customer is NOT using the mobility client or is only using it on the internal WiFi network, then this port does not need to be opened on the firewall.		
8666	This port is used by the JVMX component of the one-X Portal for IP Office. This port number can be changed during installation.		
9094	This port is used for OpenFire XML RPC (Remote Procedure Call) and administration console.		
9095	This port is used by the OpenFire admin console (https).		
8080-to- 8090	"To allow the one-X Call Assistant to communicate through a specific TCP port 
"


BAZINGA!

I'm not insane, my mother had me tested!

 
the users don't auto populate on the remote end in the drop down box, you have to manually add the names in,

Kevin Wing
ACSS Small and Medium Enterprise (SME) Communications
ACS- Implement IP Office
ACA- Implement IP Office
Carousel Industries
 
AND like mentioned before allow broadcast traffic on your routing devices for port 50799 so that the BLF information comes to you. it is a UDP broadcasted only, not sent to specific users with that user as a button.

Joe W.

FHandw, ACSS
 
I have had luck just entering the extension number under the user button. It seems to work. That way you don't have to go and change buttons on remote systems every time you change a name.

"When you do things right, people won't be sure you have done anything at all.
 
Was there nothing in it?
Because a user button will auto fill when you enter the extension number.


BAZINGA!

I'm not insane, my mother had me tested!

 
Thanks all for replies.
There is no problems with VPN and broadcast is passing over and I had no issues at all.
Tried suggestion from "Shortcode" and it worked like a sharm ))
Created User button, and for extension just put ext. number.
It doesn't replace it with Name but works the way you need it.

So Star goes to .................Shortcode ))))
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top