Presence and IntComm WG

[Steve Blair <>]

Ben:

  I agree. The PALs domain hijacking is what prompted me to send
my original message. Whether or not there is an interdomain problem
would depend upon two things. Will the PALs domain hijack'd model
be expected to work with domain and sub-domain models and
will domain and sub-domain models correctly relay invites between
themselves.

  I know I will have to enable relaying between  our 
"voice-over-ip-for-Centrex"
proxy users and SIP.edu proxy users but that "connection" does not exist
today.

  I was just wondering if others had experienced this issue or not. Candace
and I had taken the conversation offline but I think we agreed that the
current issue is unique to situations with PALs in the loop.

Thanks,Steve

Ben Teitelbaum wrote:

> Steve,
>
> The problem you point out is occurring only because of the strange
> "domain hijacking" that PALS does.  This made sense for the member
> meeting trials, where we were offering service to all attendees,
> regardless of home institution, but I can't see how it would make
> sense in a campus setting.  If you take PALS out of the picture and
> look only at domain and sub-domain interaction, is there an
> interdomain problem?
>
> -- ben
>
> Steve Blair 
> <>
>  writes:
>
>  
>
> > Candace:
> >
> >  Based on past conversations about SIP.edu I use the SRV name
> > _sip._udp.upenn.edu. This is not the domain name in my email
> > address (which is used by PALs) nor is it the domain name for
> > our VoIP proxy. That is kinda why I am asking. It just seems to
> > me that the domain names should "line up" at some point to make
> > cross-environment SIP routing work.
> >
> > -Steve
> >
> > Candace Holman wrote:
> >
> >    
> >
> > > It's the SRV record that makes the domains work.  You can have a SRV
> > > record without an A record.  It doesn't have to be resolvable as an
> > > A record.  Your SRV record is _sip._udp.isc.upenn.edu  Are you using
> > > something different for sip.edu?  I may be misunderstanding the
> > > issue, just ignore me if so.
> > >
> > > Candace
> > >
> > > At 03:51 PM 2/11/2005, Steve Blair wrote:
> > >
> > >      
> > >
> > > > Has anyone thought about the impact of domain names on
> > > > SIP routing, especially inter-institution?
> > > >
> > > > I noticed that eyebeam, and others, append the locally configured
> > > > SIP domain name to an outgoing "called number". This is fine
> > > > if that domain name is "resolvable". What happens when local
> > > > SIP proxies, SIP.edu proxies and now the PALs proxy all
> > > > interact?
> > > >
> > > > During the test call with Candace I noticed some missed calls
> > > > to 
> > > >
> > > >  and outbound calls had this same domain
> > > > name appended. This domain name is not resolvable.
> > > >
> > > > Our SIP.edu domain is trying to follow the architectural direction
> > > > of using <userid>@<institution-name>.edu. Our VoIP proxy is
> > > > known by yet another domain and PALs uses my email address.
> > > >
> > > >  I know we can use the alias command in SER to handle domain
> > > > names as long as userids are understood. I am just curious what
> > > > others think about this issue?
> > > >
> > > > -Steve
> > > >        
> >    
>
>  

--
 
ISC Network Engineering
The University of Pennsylvania
3401 Walnut Street, Suite 221A
Philadelphia, PA 19104  


voice: 215-573-8396 

      215-746-8001

fax: 215-898-9348    

sip: