Skip to Content.
Sympa Menu

sip.edu - Re: [sip.edu] Re: Cisco 7960 and Avaya CCS 2.1 registration problem

Subject: SIP in higher education

List archive

Re: [sip.edu] Re: Cisco 7960 and Avaya CCS 2.1 registration problem


Chronological Thread 
  • From: Steve Blair <>
  • To:
  • Subject: Re: [sip.edu] Re: Cisco 7960 and Avaya CCS 2.1 registration problem
  • Date: Wed, 26 Jan 2005 19:06:11 -0500


Candace:

Right. For example. Say your phone config file has an
entry proxy1_address: harvard.edu. The phone boots,
checks it's tftp server for a config file. Downloads the
file and uses _sip._udp.<proxy1_address> as an SRV
service name. It attempts to resolve this into an A record
or CNAME.

In your case this works. If it were to fail then the phone
fails over to a certain DNS "lookup" sequence. I forget
what the sequence is but I think it is SRV, A, CNAME.

It repeats this process for each phoneX_config entry
in the phone configuration file.

I'm not sure if this helps

_Steve

Candace Holman wrote:

Yul,

I did try do it as you suggest, but I confirmed this doesn't work in the newer firmware versions (P0S3-06-3-00, P003-07-3-00). "Proxy*_address" on each line is not actually the sip proxy server address, it is the domain. I.e., for domain we use harvard.edu, you use hawaii.edu, Dennis uses mit.edu, - these are the domains but not the sip proxy server addresses.

Steve Blair's answer indicates that the DNS SRV (_sip._udp.bigu.edu) is what the phones use to find the sip proxy server address.

Candace

At 06:12 PM 1/26/2005, Yul Pyun wrote:

Candace,
Proxy server address is settable in three ways:
1) Manually configure it for each of the line, using the 79x0 phone's keypad
2) Set the Proxy1_address field in the SIPmac-addr.cnf file (probably in your TFTP server's sip_phone sub-directory) with the server's dotted IP address or FQDN
3) Set the Proxy1_address field in the SIPDefault.cnf file (probably in your TFTP server's root directory) with the server's dotted IP address or FQDN
hth,
-Yul

----- Original Message -----
From: Candace Holman
<mailto:>
To:


<mailto:>
Sent: Wednesday, January 26, 2005 12:26 PM
Subject: [sip.edu] Re: Cisco 7960 and Avaya CCS 2.1 registration
problem

Thanks Venky, Joseph, and others from Avaya. Although there is
no way to change the domain and realm on the Cisco endpoint, I
did get it to register after changing the proxy address from the
address of the sip proxy to the address of the domain.
This may seem like a strange question - how is the phone getting
the address of the sip proxy in order to register? Is it from
the SRV record in DNS?

Candace

At 11:56 PM 1/21/2005, Venkatesh Krishnaswamy wrote:

Candace,
Please see below for why you might be seeing the
registration problem.

Venky Krishnaswamy
Director, IP Communications Research,
Avaya Labs, Avaya Inc.
Lincroft, NJ 07738



<mailto:>

-------- Original Message --------
Subject: RE: [Fwd: [sip.edu] Cisco 7960 and Avaya CCS 2.1
registration problem]
Date: Fri, 21 Jan 2005 23:42:51 -0500
From: Mastrogiulio, Joseph (Joseph)

<>

<mailto:>
To: Krishnaswamy, Venkatesh (Venkatesh)
<>

<mailto:>,
Walker, William J (William)

<>

<mailto:>
CC: Zenner, Hal B (Hal)
<>

<mailto:>


Venky,


The registration is failing because the proxys domain and
realm is harvard.edu, and the endpoint is registering into
the mysipserver.harvard.edudomain. Notice that in the
WWW-Authenticate header of the 401 response from the proxy
the realmand domainvalues are both set to harvard.edu. This
tells me that the proxy is configured with harvard.eduas
domain and realm. The REGISTER request from the endpoint
specifies a mysipserver.harvard.eduas the domain. The
mismatch in domains is causing the registration to fail.


Make sure that the endpoint is configured with the same
domain and realm as the proxy. Also, make sure that the CCS
user and the phone are configured with the same password. However, this particular registration would fail because of
domain mismatch. So, reconfigure the endpoint with
harvard.edudomain and realm and the registration should succeed.


Joseph



-----Original Message-----
From: Krishnaswamy, Venkatesh (Venkatesh)
Sent: Thursday, January 20, 2005 5:08 PM
To: Walker, William J (William); Mastrogiulio, Joseph (Joseph)
Cc: Zenner, Hal B (Hal)
Subject: [Fwd: [sip.edu] Cisco 7960 and Avaya CCS 2.1
registration problem]


Bill, Joseph:
I came across this in the SIP.edu mailing list. Is the
configuration that they're talking about supported? If so -
any idea what the problem could be?
Venky


-------- Original Message --------

Subject:

[sip.edu] Cisco 7960 and Avaya CCS 2.1 registration problem

Date:

Thu, 20 Jan 2005 16:36:57 -0500

From:

Candace Holman
<>

<mailto:>

Reply-To:




<mailto:>

To:




<mailto:>



Hi,







I'm getting errors trying to register a Cisco 7960, firmware P0S3-06-3-00


with an Avaya CCS, version 2.1.0.0-35 There's a continuing auth


problem. The exchange of messages is listed below. Does anyone see the


problem here?







<REGISTER sip:mysipserver.harvard.edu SIP/2.0



Via: SIP/2.0/UDP myphoneipaddr:5060;branch=z9hG4bK29d84d0b



From:
sip:

<>



To:
sip:

<>



Call-ID:


<mailto:>



CSeq: 227 REGISTER



User-Agent: CSCO/6



Contact:
<sip:80550@myphoneipaddr:5060>



Content-Length: 0



Expires: 3600







, length=<357>







<SIP/2.0 401 Unauthorized



From:
sip:

<>



To:


sip:;tag=2C520912BDEF99F3DFFAD3DE1F6F188A110625677410312

<;tag=2C520912BDEF99F3DFFAD3DE1F6F188A110625677410312>



Call-ID:
003094c3-18c20002-237f53c2-2ff10850@myphoneipaddr



CSeq: 227 REGISTER



Via: SIP/2.0/UDP myphoneipaddr:5060;branch=z9hG4bK29d84d0b



Content-Length: 0



WWW-Authenticate: Digest


realm="harvard.edu",domain="harvard.edu",nonce="MTEwNjI1Njc3NDpTREZTZXJ2ZXJTZWNyZXRLZXk6MTUzMzk0MDgxNw==",algorithm=MD5



Server: Avaya Converged Communications Server



Organization: harvard.edu







, length=535







<REGISTER sip:mysipserver.harvard.edu SIP/2.0



Via: SIP/2.0/UDP myphoneipaddr:5060;branch=z9hG4bK4f5a0744



From:
sip:

<>



To:
sip:

<>



Call-ID:
003094c3-18c20002-237f53c2-2ff10850@myphoneipaddr



CSeq: 228 REGISTER



User-Agent: CSCO/6



Contact:
<sip:80550@myphoneipaddr:5060>



Authorization: Digest


username="80550",realm="harvard.edu",uri="sip:mysipserver.harvard.edu",response="cb7a0f964021ad9d60c5e312e887b17a",nonce="MTEwNjI1Njc3NDpTREZTZXJ2ZXJTZWNyZXRLZXk6MTUzMzk0MDgxNw==",algorithm=MD5



Content-Length: 0



Expires: 3600







, length=<571>







<SIP/2.0 500 Internal Server Error



From:
sip:

<>



To:


sip:;tag=2C520912BDEF99F3DFFAD3DE1F6F188A110625677410314

<;tag=2C520912BDEF99F3DFFAD3DE1F6F188A110625677410314>



Call-ID:
003094c3-18c20002-237f53c2-2ff10850@myphoneipaddr



CSeq: 228 REGISTER



Via: SIP/2.0/UDP myphoneipaddr:5060;branch=z9hG4bK4f5a0744



Content-Length: 0



Organization: harvard.edu



Server: Avaya Converged Communications Server







, length=398











=====================================================================



Candace Holman



617-384-6665







Harvard University Information Systems



60 Oxford Street



Cambridge, MA 02138












Archive powered by MHonArc 2.6.16.

Top of Page