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 SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Web Client and Multicsat 1

Status
Not open for further replies.

pdulfo

Technical User
Aug 21, 2003
467
0
0
US
I am setting up the webclient and cannot get the realtime display working. The book says to use the Icertdtrace command. Can somebody let me know what to expect as working output. I get the following from the client:

C:\Program Files\Nortel Networks\WClient\Server>icertdtrace -r ipsend 234.5.6.2
adapter 0 - 172.16.3.29
adapter 0 - 172.16.3.29
adapter 0 - 172.16.3.29
adapter 0 - 172.16.3.29
adapter 0 - 172.16.3.29
adapter 0 - 172.16.3.29
adapter 0 - 172.16.3.29
adapter 0 - 172.16.3.29
adapter 0 - 172.16.3.29
adapter 0 - 172.16.3.29
adapter 0 - 172.16.3.29
adapter 0 - 172.16.3.29


---------------------------------
PDulfo aka pdiddy
 
No multicast being sent out (or received, anyway) on 234.5.6.2. Check the multicast send address on the Symposium -- is it set at 234.5.6.2, or is it something like 230.0.0.1?
 
Thanks sandyml.

I am havin great fun with this bit.

On our Symposium Server the Mutlicats is set to 230.0.0.1

So on the Appserver I have set the ipreceive to 230.0.0.1 and the ipsend to 234.5.6.2.

Now if I use the following command :
icertdtrace -s symposium 230.0.0.1
I get
application ** scheme=Interval To Date,records=29
skillset ** scheme=Interval To Date,records=24
IVR queues ** scheme=Interval To Date,records=3
Route ** scheme=Interval To Date,records=11
Nodal ** scheme=Interval To Date


Bur using the -r option I get as in the first post. I must say that the installation manaul leaves a lot out.




---------------------------------
PDulfo aka pdiddy
 
I am having an issue with the real time displays over a WAN connection and only the real time displays from the web client. The WAN connection is two T1's with load balancing setup between two Cisco routers. I suspect the problem is coming from the load balancing on the routers. I have multicasting enabled on all the routers.

Any ideas?
 
For Cisco Users read the following excerpt. Its wordy but basicly change the default address in the 4.2 server. If you need to discuss with the network folks youll need all of this.

Real-Time Display timeouts,- The SWC RTD will timeout on clients PC (SWC is ok). You will see the display go to “0” and then come back, and go back out.

The 6800 switch where the servers reside was sending out the following error messages:

mdf2> (enable) 2003 May 30 11:17:50 PDT -07:00 %MCAST-2-IGMP_ADDRAL:IGMP: Address Aliasing for 01-00-5e-00-00-01
2003 May 30 11:17:50 PDT -07:00 %MCAST-2-IGMP_FALLBACK:IGMP: Running in FALL BACK mode
2003 May 30 11:23:06 PDT -07:00 %MCAST-2-IGMP_ADDRAL:IGMP: Address Aliasing for 01-00-5e-00-00-01
Summary:
The Multicast IP Address are reserved on the Cisco Switch. We had to change our Address to be out of this range to resolve the problem. (New Addresses 225.123.95.15, 225.123.95.16)
224.0.0.* through 239.0.0.*
224.128.0.* through 239.128.0.*
My concern is 230.0.0.1 & 230.0.0.2 is default for the SCCS & SWC.


Cisco Configuration Guidelines and Restrictions for Multicast Addresses:
IP MMLS Configuration Restrictions
IP MMLS does not perform multilayer switching for an IP multicast flow in the following situations:
• If IP MMLS is disabled on the RPF interface for the flow (using the no mls ip multicast interface configuration command).
• For IP multicast groups that fall into these ranges (where * is in the range 0-255):
224.0.0.* through 239.0.0.*
224.128.0.* through 239.128.0.*


Note Groups in the 224.0.0.* range are reserved for routing control packets and must be flooded to all forwarding interfaces of the VLAN. All these addresses map to the multicast MAC address range 01-00-5E-00-00-xx, where xx is in the range 0-0xFF.

For PIM auto-RP multicast groups (IP multicast group addresses 224.0.1.39 and 224.0.1.40)
 
Thanks MarkDvoracek

We just went to Symposium 4.2 with 2 sites networked with an NCC. We also put in Web server but the install technicians programmed 230.0.0.1 in the 4.2 server. Since we have Cisco routers our network guys asked them to change it to an IP they provided but now Nortel and Bell tells us that it cannot happen till they get PEP 13 which is still BETA. Could you let me know if you had this issue with changing Multicast IP on Symposium Call Centre Server 4.2. We currently have PEP/SUP 12

Thanks
 
I have reconfigured the Multicast IP on numerous occasions on the fly during business hours on SCCS 4.2 SU11 and SU12 with no problems. All you need to do is change the address using the RSMConfg.exe utility, then stop and restart the SDP service.

Regards,

Michael
 
Pdulfo

look in aour Host Tabell from WINNT\system32\drivers\etc
Remove all entries that forward to localhost

for Exampel

ping sccsswc ( hostname )
reply was 127.0.0.1

This is the Problem
 
When you say to remove the entries in the localhost table on the client desktop of 127.0.0.1 the SWC RDT data will present itself to the clients all the time and not "0" out?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top