[cisco-voip] CCM - Attendant console and multi-tenant

[Vincent De Keyzer]

Well, something else about this (since all my questions got answered so far,
I'd better keep going :-)...

I have created a pilot point and put my extension in the associated hunt
group. When I call the hunt pilot, I first get the MOH for a few seconds
(which is fine) - but at that time I see nothing on the attendant console.
After that, my phone starts ringing, and only then I see the call in the
"call control" window of the AC.

If I place a second call while the first one is ringing, the same behaviour
happens: nothing while the MOH plays, then little bell when the call is
ringing.

Shouldn't I be seeing the queued calls on the attendant console *before*
they start ringing? 

Am I having the same firewall/NAT problem as for the line status?

Vincent


> -----Original Message-----
> From: Wes Sisk [mailto:wsisk at cisco.com]
> Sent: mercredi 17 août 2005 17:37
> To: Vincent De Keyzer; 'Kevin Thorngren'
> Cc: cisco-voip at puck.nether.net
> Subject: RE: [cisco-voip] CCM - Attendant console and multi-tenant
> 
> gotcha. yeah, no nat fixup for RMI.  /Wes
> 
> -----Original Message-----
> From: Vincent De Keyzer [mailto:vincent at dekeyzer.net]
> Sent: Wednesday, August 17, 2005 11:30 AM
> To: 'Wes Sisk'; 'Kevin Thorngren'
> Cc: cisco-voip at puck.nether.net
> Subject: RE: [cisco-voip] CCM - Attendant console and multi-tenant
> 
> 
> The problem is not the port, the problem is the IP address.
> 
> I can only force an inside IP address on the client, and this inside IP
> address does not make any sense on the server (because it's outside).
> 
> One solution is to assign an outside address to the client (although it's
> inside). Ugly, but I might go for something like that if the customer
> really
> wants the client to be "inside" the firewall.
> 
> Vincent
> 
> 
> > -----Original Message-----
> > From: Wes Sisk [mailto:wsisk at cisco.com]
> > Sent: mercredi 17 août 2005 17:25
> > To: Vincent De Keyzer; 'Kevin Thorngren'
> > Cc: cisco-voip at puck.nether.net
> > Subject: RE: [cisco-voip] CCM - Attendant console and multi-tenant
> >
> > configure a static xlation for 1 UDP port, force the client to always
> use
> > the same port number.  This should work, no?
> >
> > /Wes
> >
> > -----Original Message-----
> > From: Vincent De Keyzer [mailto:vincent at dekeyzer.net]
> > Sent: Wednesday, August 17, 2005 11:21 AM
> > To: 'Wes Sisk'; 'Kevin Thorngren'
> > Cc: cisco-voip at puck.nether.net
> > Subject: RE: [cisco-voip] CCM - Attendant console and multi-tenant
> >
> >
> > Thanks Wes,
> >
> > > When you do a search in
> > > the directory window, acclient sends a subscribe message to ACServer
> to
> > > receive linestate updates for the lines in the directory search result
> > > set.
> > > ACServer then sends linestate updates down to the client in UDP
> packets.
> > >
> > > The client selects an ephemeral port to receive LSS updates by default
> > but
> > > can be configured to use a static port.  on the clent, settings,
> > advanced,
> > > local host ip address (for line state)
> > >
> > > ACClient subscrption shows up in ACServer traces as:
> > > ServerClient subscribelinestate: inet address: 172.18.120.120 Port:
> 1818
> > >
> > > if any LSS updates are available ACServer sends those down:
> > > Sending 0 linestate(s) sent to client: 172.18.120.120
> >
> > So I understand there is no way to get this working through a NATting
> > firewall: the attendant console has an inside address, which is NATted
> to
> > a
> > outside address for the outgoing TCP session to the server; but UDP
> > packets
> > are sent to the inside address - which does not make any sense outside
> of
> > the firewall.
> >
> > I have tried to configure an outside address on the client, but it won't
> > accept it since the outside address does not appear on any of its NICs.
> >
> > I'll place the machine outside of the firewall.
> >
> > Thanks for the insight
> >
> > Vincent