LanScape Support Forum: Connecting to Cisco Call Manager

		Active Topics Member List Search Help Register Login

SIP Proxy and Media Proxy - Pre-Sales Technical Support
LanScape Support Forum -> SIP Proxy and Media Proxy - Pre-Sales Technical Support

Topic: Connecting to Cisco Call Manager

Author

Message

<< Prev Topic | Next Topic >>

nshoe18
Intermediate

Joined: May 01 2007
Location: United States
Posts: 15

Posted: May 01 2007 at 8:34pm \| IP Logged

We have a paging appliance that we can register to the proxy server but cannot do any paging. Is there a setup that needs to be done when you are communicating with a SIP Trunk from call manager?

support
Administrator

Joined: January 26 2005
Location: United States
Posts: 1666

Posted: May 02 2007 at 7:33am \| IP Logged

Hi nshoe18,

Thanks for posting your questions to this forum.

We are sorry but you will have to be more specific with your question. Take a moment to tell us about your application and how it is deployed in the network and what you are trying to accomplish. Otherwise we simply end up guessing at this end and our “blathering” probably won’t help you.

We will reply as soon as we can get additional info.

Thanks,

Support

nshoe18
Intermediate

Joined: May 01 2007
Location: United States
Posts: 15

Posted: May 02 2007 at 8:40am \| IP Logged

I am sorry it was a long night. I work with Genesta in Dallas and you had one of our Cyberdata speakers working last week with your Proxy Server product, playing Led Zepplin in our office. I am using a Cyberdata paging server, I will attach the link for the product page, connecting to Call Manager 4.2. I have the Proxy server loaded and running on the same server as the Call Manager Subscriber. I have a SIP trunk crested in Call Manager pointing via port 5060 to the Proxy server. In the event log I get the message about an IP Port conflict on port 5060 with Call Manager. The Proxy Server is then connected via a WAN connection to the CyberData Paging Appliance. We were using port 5061 for the Port on the Proxy Server and the Paging Appliance. The Paging Appliance registers to the Proxy Server and all looks fine. We have setup 8000 as the number to call to access the Paging Appliance. When we dial the number we just get silence.

I hope you can make some kinds of head or tails of my rambling...we were up working on problems until 5:45 this morning so I am kind of out of it. Please call me on my phone at (214) 762-2648 and we can discuss further. Thank you.

-Nik Shoemaker

http://www.cyberdata.net/products/voip/pdf/VoipPagingServer. pdf

support
Administrator

Joined: January 26 2005
Location: United States
Posts: 1666

Posted: May 02 2007 at 9:26am \| IP Logged

Hi Nik,

Ahhhh, an all nighter – been there, done that, got the T-shirt.

Ok. I will regurgitate what you have said to make sure we are on the same page:

1)
Cisco Call Manager Subscriber and LanScape Centrex (SIP) Proxy Server running on the same host machine.

2)
Cisco Call Manager is using SIP port 5060.

3)
LanScape Centrex (SIP) Proxy Server is configured to use SIP port 5061.

4)
CyberData Paging appliance is using SIP port 5061.

5)
Call Manager’s SIP trunk will terminate (points to/forwards Sip traffic) to the LanScape Centrex Proxy Server.

What to do now:

1)
For my purposes, please answer the following:
What’s the IP address of the Call Manager?
What’s the IP address of the Centrex Proxy Server?
What’s the IP address of the CyberData paging appliance?

2)
Enable the SIP log capability in the Centrex Proxy Server. See “SIP Logging” in the proxy server settings dialog.

3)
Place another phone call to extension 8000. Wait 10 seconds then terminate the call.

4)
Shut down the Centrex Proxy Server.

5)
Post the SIP log from the LanScape Centrex Proxy to this support forum thread. We will look at its contents to locate the problem.

Support

nshoe18
Intermediate

Joined: May 01 2007
Location: United States
Posts: 15

Posted: May 02 2007 at 9:34am \| IP Logged

For my purposes, please answer the following:
What’s the IP address of the Call Manager? 172.17.227.21
What’s the IP address of the Centrex Proxy Server? 172.17.227.21
What’s the IP address of the CyberData paging appliance? 10.238.7.10

I will get the log stuff you are looking for in just a bit. Have to wait for someone to get here. I will get those posted for you.

nshoe18
Intermediate

Joined: May 01 2007
Location: United States
Posts: 15

Posted: May 02 2007 at 10:26am \| IP Logged

Here are both SIP and Eventlogs. Also, for temporary testing we are using my computer for the Proxy Server because we thought maybe we couldn't have it loaded on the same computer.

#Rec#2#21:34:50 05/01/07#***************************** Centrex Proxy Session Start *****************************
#Rec#2#21:34:50 05/01/07#LanScape Centrex Proxy® Starting...
#Rec#2#21:34:50 05/01/07#LanScape Centrex Proxy® running. Configuration settings follow:
#Rec#2#21:34:50 05/01/07#Server Name: LanScape Centrex Proxy/3.42.1.6
#Rec#2#21:34:50 05/01/07#Private IP: 10.238.2.192
#Rec#2#21:34:50 05/01/07#WAN IP: 10.238.2.192
#Rec#2#21:34:50 05/01/07#Server Port: 5060
#Rec#2#21:34:50 05/01/07#Domain: ssg.petsmart.com
#Rec#2#21:34:50 05/01/07#Authentication: off
#Rec#2#21:34:50 05/01/07#Authentication Realm: MyCompany.com
#Rec#2#21:34:50 05/01/07#Call Routing: DISABLED
#Rec#2#21:34:50 05/01/07#Proxy Ready
#Rec#2#21:35:53 05/01/07#Terminating proxy functions...
#Rec#2#21:35:53 05/01/07#Terminating local authentication database.
#Rec#2#21:35:54 05/01/07#LanScape Centrex Proxy® Terminated.
#Rec#2#21:35:54 05/01/07#***************************** Centrex Proxy Session End *******************************
#Rec#2#21:35:54 05/01/07#***************************** Centrex Proxy Session Start *****************************
#Rec#2#21:35:54 05/01/07#LanScape Centrex Proxy® Starting...
#Rec#2#21:35:54 05/01/07#LanScape Centrex Proxy® running. Configuration settings follow:
#Rec#2#21:35:54 05/01/07#Server Name: LanScape Centrex Proxy/3.42.1.6
#Rec#2#21:35:54 05/01/07#Private IP: 10.238.2.192
#Rec#2#21:35:54 05/01/07#WAN IP: 10.238.2.192
#Rec#2#21:35:54 05/01/07#Server Port: 5060
#Rec#2#21:35:54 05/01/07#Domain: ssg.petsmart.com
#Rec#2#21:35:54 05/01/07#Authentication: on
#Rec#2#21:35:54 05/01/07#Authentication Realm: ssg.petsmart.com
#Rec#2#21:35:54 05/01/07#Initializing local authentication database.
#Rec#2#21:35:54 05/01/07#SIP protocol log file name: CentrexProxySipLog.log
#Rec#2#21:35:54 05/01/07#Call Routing: DISABLED
#Rec#2#21:35:54 05/01/07#Proxy Ready
#Rec#8#21:39:11 05/01/07#REGISTER 8000@10.238.7.10:5060 (3600 sec)    Received from: 10.238.7.10:5060    Registering UA/Contact: 10.238.7.10:5060
#Rec#8#22:27:19 05/01/07#REGISTER 8000@10.238.7.10:5060 (3600 sec)    Received from: 10.238.7.10:5060    Registering UA/Contact: 10.238.7.10:5060
#Rec#2#22:49:02 05/01/07#Terminating proxy functions...
#Rec#2#22:49:02 05/01/07#Terminating local authentication database.
#Rec#2#22:49:03 05/01/07#LanScape Centrex Proxy® Terminated.
#Rec#2#22:49:04 05/01/07#***************************** Centrex Proxy Session End *******************************
#Rec#2#22:49:04 05/01/07#***************************** Centrex Proxy Session Start *****************************
#Rec#2#22:49:04 05/01/07#LanScape Centrex Proxy® Starting...
#Rec#2#22:49:04 05/01/07#LanScape Centrex Proxy® running. Configuration settings follow:
#Rec#2#22:49:04 05/01/07#Server Name: LanScape Centrex Proxy/3.42.1.6
#Rec#2#22:49:04 05/01/07#Private IP: 10.238.2.192
#Rec#2#22:49:04 05/01/07#WAN IP: 10.238.2.192
#Rec#2#22:49:04 05/01/07#Server Port: 5060
#Rec#2#22:49:04 05/01/07#Domain: ssg.petsmart.com
#Rec#2#22:49:04 05/01/07#Authentication: on
#Rec#2#22:49:04 05/01/07#Authentication Realm: ssg.petsmart.com
#Rec#2#22:49:04 05/01/07#Initializing local authentication database.
#Rec#2#22:49:04 05/01/07#SIP protocol log file name: CentrexProxySipLog.log
#Rec#2#22:49:04 05/01/07#Call Routing: DISABLED
#Rec#2#22:49:04 05/01/07#Proxy Ready
#Rec#2#22:49:56 05/01/07#Terminating proxy functions...
#Rec#2#22:49:56 05/01/07#Terminating local authentication database.
#Rec#2#22:49:56 05/01/07#LanScape Centrex Proxy® Terminated.
#Rec#2#22:49:56 05/01/07#***************************** Centrex Proxy Session End *******************************
#Rec#2#22:49:56 05/01/07#***************************** Centrex Proxy Session Start *****************************
#Rec#2#22:49:56 05/01/07#LanScape Centrex Proxy® Starting...
#Rec#2#22:49:56 05/01/07#LanScape Centrex Proxy® running. Configuration settings follow:
#Rec#2#22:49:56 05/01/07#Server Name: LanScape Centrex Proxy/3.42.1.6
#Rec#2#22:49:56 05/01/07#Private IP: 10.238.2.192
#Rec#2#22:49:56 05/01/07#WAN IP: 10.238.2.192
#Rec#2#22:49:56 05/01/07#Server Port: 5060
#Rec#2#22:49:56 05/01/07#Domain: ssg.petsmart.com
#Rec#2#22:49:56 05/01/07#Authentication: on
#Rec#2#22:49:56 05/01/07#Authentication Realm: ssg.petsmart.com
#Rec#2#22:49:56 05/01/07#Initializing local authentication database.
#Rec#2#22:49:56 05/01/07#SIP protocol log file name: CentrexProxySipLog.log
#Rec#2#22:49:56 05/01/07#Call Routing: DISABLED
#Rec#2#22:49:56 05/01/07#Proxy Ready
#Rec#2#23:03:35 05/01/07#Terminating proxy functions...
#Rec#2#23:03:35 05/01/07#Terminating local authentication database.
#Rec#2#23:03:36 05/01/07#LanScape Centrex Proxy® Terminated.
#Rec#2#23:03:36 05/01/07#***************************** Centrex Proxy Session End *******************************
#Rec#2#10:12:33 05/02/07#***************************** Centrex Proxy Session Start *****************************
#Rec#2#10:12:33 05/02/07#LanScape Centrex Proxy® Starting...
#Rec#2#10:12:33 05/02/07#LanScape Centrex Proxy® running. Configuration settings follow:
#Rec#2#10:12:33 05/02/07#Server Name: LanScape Centrex Proxy/3.42.1.6
#Rec#2#10:12:33 05/02/07#Private IP: 10.238.2.192
#Rec#2#10:12:33 05/02/07#WAN IP: 10.238.2.192
#Rec#2#10:12:33 05/02/07#Server Port: 5060
#Rec#2#10:12:33 05/02/07#Domain: ssg.petsmart.com
#Rec#2#10:12:33 05/02/07#Authentication: on
#Rec#2#10:12:33 05/02/07#Authentication Realm: ssg.petsmart.com
#Rec#2#10:12:33 05/02/07#Initializing local authentication database.
#Rec#2#10:12:33 05/02/07#SIP protocol log file name: CentrexProxySipLog.log
#Rec#2#10:12:33 05/02/07#Call Routing: DISABLED
#Rec#2#10:12:34 05/02/07#Proxy Ready
#Rec#8#10:17:24 05/02/07#REGISTER 8000@10.238.7.10:5060 (3600 sec)    Received from: 10.238.7.10:5060    Registering UA/Contact: 10.238.7.10:5060
#Rec#2#10:18:33 05/02/07#Terminating proxy functions...
#Rec#2#10:18:33 05/02/07#Terminating local authentication database.
#Rec#2#10:18:34 05/02/07#LanScape Centrex Proxy® Terminated.
#Rec#2#10:18:34 05/02/07#***************************** Centrex Proxy Session End *******************************

<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 10.238.7.10:5060) <<<<
REGISTER sip:10.238.2.192:5060 SIP/2.0
Via: SIP/2.0/UDP 10.238.7.10:5060;rport;branch=z9hG4bK1052444514
From: <sip:8000@10.238.2.192>;tag=1297737753
To: <sip:8000@10.238.2.192>
Call-ID: 941106630@10.238.7.10
CSeq: 1 REGISTER
Contact: <sip:8000@10.238.7.10:5060>
Max-Forwards: 5
User-Agent: SipReg v1.0
Expires: 3600
Content-Length: 0

>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 10.238.7.10:5060) >>>>
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 10.238.7.10:5060;rport=5060;branch=z9hG4bK1052444514;receive d=10.238.7.10
From: <sip:8000@10.238.2.192>;tag=1297737753
To: <sip:8000@10.238.2.192>
Call-ID: 941106630@10.238.7.10
CSeq: 1 REGISTER
WWW-Authenticate: Digest realm="ssg.petsmart.com", nonce="f2a22b6d729fd361b6cb6f708171c48d", opaque="576d61915e0176c27f2e0b24d0f0799c"
Server: LanScape Centrex Proxy/3.42.1.6 (www.LanScapeCorp.com)
Content-Length: 0

<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 10.238.7.10:5060) <<<<
REGISTER sip:10.238.2.192:5060 SIP/2.0
Via: SIP/2.0/UDP 10.238.7.10:5060;rport;branch=z9hG4bK72113362
From: <sip:8000@10.238.2.192>;tag=1297737753
To: <sip:8000@10.238.2.192>
Call-ID: 941106630@10.238.7.10
CSeq: 2 REGISTER
Contact: <sip:8000@10.238.7.10:5060>
Authorization: Digest username="8000", realm="ssg.petsmart.com", nonce="f2a22b6d729fd361b6cb6f708171c48d", uri="sip:10.238.2.192:5060", response="e8a65e7be269a33ce0d47a4be57241b0", algorithm=MD5, opaque="576d61915e0176c27f2e0b24d0f0799c"
Max-Forwards: 5
User-Agent: SipReg v1.0
Expires: 3600
Content-Length: 0

>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 10.238.7.10:5060) >>>>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.238.7.10:5060;rport=5060;branch=z9hG4bK72113362;received= 10.238.7.10
From: <sip:8000@10.238.2.192>;tag=1297737753
To: <sip:8000@10.238.2.192>;tag=41
Call-ID: 941106630@10.238.7.10
CSeq: 2 REGISTER
Contact: <sip:8000@10.238.7.10:5060>;expires=3600
Expires: 3600
Server: LanScape Centrex Proxy/3.42.1.6 (www.LanScapeCorp.com)
Content-Length: 0

nshoe18
Intermediate

Joined: May 01 2007
Location: United States
Posts: 15

Posted: May 02 2007 at 10:33am \| IP Logged

Also, after about 6 seconds I get a busy signal. Forgot to add that. Not enough coffee this morning.

support
Administrator

Joined: January 26 2005
Location: United States
Posts: 1666

Posted: May 02 2007 at 11:20am \| IP Logged

Hi Nik,

Thanks for the info. Its OK, you do not need to clean the SIP logs for us unless you want to hide an IP:port for security purposes. We can read the raw SIP logs like a book :).

We will delete the cleaned log post for now to save space in the forum support database.

…well, the CyberData device is registering OK. Good.

From the LanScape proxy Sip log, it seems that Call Manager never sent the call INVITE to our proxy. If it did, we should see a SIP INVITE coming from the Cisco Call Manager. You probably have to do some additional configuration on the call manager side to get him to send the call to extension 8000 to the LanScape proxy. My guess is that call manager has sent it to the wrong IP address or port instead of the Ip and port the LanScape sip proxy is using.

Get the call manager to send the INVITE to the LanScape proxy and post another SIP log from the LanScape proxy.

Support

nshoe18
Intermediate

Joined: May 01 2007
Location: United States
Posts: 15

Posted: May 02 2007 at 12:33pm \| IP Logged

what does the 401 unauthorized mean in the log?

nshoe18
Intermediate

Joined: May 01 2007
Location: United States
Posts: 15

Posted: May 02 2007 at 12:52pm \| IP Logged

Do you have any examples of a Call Manager Trunk that has been previously used to do what we are attempting? Please call if you can. number is above.

support
Administrator

Joined: January 26 2005
Location: United States
Posts: 1666

Posted: May 02 2007 at 1:05pm \| IP Logged

The SIP “401 Unauthorized” in the LanScape Sip proxy log tells the CyberData device that it must authenticate its registration. This is normal and functioning OK.

I’m sorry, we do not have any examples of configuring a Call Manager Sip trunk. :(
I would hope that this is covered in the Cisco Call Manager setup/config guide. Maybe call Cisco support about this.

If I may suggest this to your group: You may want to enter into a support contract with us so we can help you with all of your SIP and VOIP needs. We do this for other customers. That way we can cut an NDA, share project requirements and help you spec out and configure systems. It works pretty well.

Repost as needed,

Support

nshoe18
Intermediate

Joined: May 01 2007
Location: United States
Posts: 15

Posted: May 02 2007 at 3:14pm \| IP Logged

We are now talking to the Call Manager here are our logs:

<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 10.238.7.10:5060) <<<<
REGISTER sip:172.17.227.21:5060 SIP/2.0
Via: SIP/2.0/UDP 10.238.7.10:5060;rport;branch=z9hG4bK1245311929
From: <sip:8000@172.17.227.21>;tag=1803735256
To: <sip:8000@172.17.227.21>
Call-ID: 45275417@10.238.7.10
CSeq: 1 REGISTER
Contact: <sip:8000@10.238.7.10:5060>
Max-Forwards: 5
User-Agent: SipReg v1.0
Expires: 3600
Content-Length: 0

>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 10.238.7.10:5060) >>>>
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 10.238.7.10:5060;rport=5060;branch=z9hG4bK1245311929;receive d=10.238.7.10
From: <sip:8000@172.17.227.21>;tag=1803735256
To: <sip:8000@172.17.227.21>
Call-ID: 45275417@10.238.7.10
CSeq: 1 REGISTER
WWW-Authenticate: Digest realm="ssg.petsmart.com", nonce="f1a7ca8be486b9995fbebaca2d12be59", opaque="8ffe4e26d5e43bb5387f4f0b7bdacb45"
Server: LanScape Centrex Proxy/3.42.1.6 (www.LanScapeCorp.com)
Content-Length: 0

<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 10.238.7.10:5060) <<<<
REGISTER sip:172.17.227.21:5060 SIP/2.0
Via: SIP/2.0/UDP 10.238.7.10:5060;rport;branch=z9hG4bK1138829277
From: <sip:8000@172.17.227.21>;tag=1803735256
To: <sip:8000@172.17.227.21>
Call-ID: 45275417@10.238.7.10
CSeq: 2 REGISTER
Contact: <sip:8000@10.238.7.10:5060>
Authorization: Digest username="8000", realm="ssg.petsmart.com", nonce="f1a7ca8be486b9995fbebaca2d12be59", uri="sip:172.17.227.21:5060", response="b2740fac38c4bf7ec6be8c1fd4ddb7b5", algorithm=MD5, opaque="8ffe4e26d5e43bb5387f4f0b7bdacb45"
Max-Forwards: 5
User-Agent: SipReg v1.0
Expires: 3600
Content-Length: 0

>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 10.238.7.10:5060) >>>>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.238.7.10:5060;rport=5060;branch=z9hG4bK1138829277;receive d=10.238.7.10
From: <sip:8000@172.17.227.21>;tag=1803735256
To: <sip:8000@172.17.227.21>;tag=41
Call-ID: 45275417@10.238.7.10
CSeq: 2 REGISTER
Contact: <sip:8000@10.238.7.10:5060>;expires=3600
Expires: 3600
Server: LanScape Centrex Proxy/3.42.1.6 (www.LanScapeCorp.com)
Content-Length: 0

<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 172.20.66.21:5060) <<<<
INVITE sip:8000@172.17.227.21:5060 SIP/2.0
Via: SIP/2.0/UDP 172.20.66.21:5060;branch=z9hG4bK1c27384e
From: "Mark Figor" <sip:5598@172.20.66.21>;tag=33579569
To: <sip:8000@172.17.227.21>
Date: Wed, 02 May 2007 19:52:17 GMT
Call-ID: a0167400-1dd116e9-80-154214ac@172.20.66.21
Supported: timer
Min-SE: 1800
User-Agent: Cisco-CCM4.1
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK
CSeq: 101 INVITE
Max-Forwards: 70
Remote-Party-ID: "Mark Figor" <sip:5598@172.20.66.21>;party=calling;screen=no;privac y=off
Contact: <sip:5598@172.20.66.21:5060>
Expires: 180
Allow-Events: telephone-event
Content-Type: application/sdp
Content-Length: 227

v=0
o=CiscoSystemsCCM-SIP 2000 1000 IN IP4 172.20.66.21
s=SIP Call
c=IN IP4 172.20.66.21
t=0 0
m=audio 31166 RTP/AVP 0 101
a=sendrecv
a=rtpmap:0 PCMU/8000
a=ptime:20
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15

>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 172.20.66.21:5060) >>>>
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 172.20.66.21:5060;branch=z9hG4bK1c27384e;rport=5060;received =172.20.66.21
From: "Mark Figor" <sip:5598@172.20.66.21>;tag=33579569
To: <sip:8000@172.17.227.21>
Call-ID: a0167400-1dd116e9-80-154214ac@172.20.66.21
CSeq: 101 INVITE
Server: LanScape Centrex Proxy/3.42.1.6 (www.LanScapeCorp.com)
Content-Length: 0

>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 172.20.66.21:5060) >>>>
SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP 172.20.66.21:5060;branch=z9hG4bK1c27384e;rport=5060;received =172.20.66.21
From: "Mark Figor" <sip:5598@172.20.66.21>;tag=33579569
To: <sip:8000@172.17.227.21>
Call-ID: a0167400-1dd116e9-80-154214ac@172.20.66.21
CSeq: 101 INVITE
Proxy-Authenticate: Digest realm="ssg.petsmart.com", nonce="f1a7ca8be486b9995fbebaca2d12be59", opaque="42daa77119f3ec582ce4e6395b89cec6"
Server: LanScape Centrex Proxy/3.42.1.6 (www.LanScapeCorp.com)
Content-Length: 0

<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 172.20.66.21:5060) <<<<
ACK sip:8000@172.17.227.21:5060 SIP/2.0
Via: SIP/2.0/UDP 172.20.66.21:5060;branch=z9hG4bK1c27384e
From: "Mark Figor" <sip:5598@172.20.66.21>;tag=33579569
To: <sip:8000@172.17.227.21>
Date: Wed, 02 May 2007 19:52:17 GMT
Call-ID: a0167400-1dd116e9-80-154214ac@172.20.66.21
Max-Forwards: 70
CSeq: 101 ACK
Content-Length: 0

<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 172.20.66.21:5060) <<<<
INVITE sip:8000@172.17.227.21:5060 SIP/2.0
Via: SIP/2.0/UDP 172.20.66.21:5060;branch=z9hG4bK17fa2ff4
From: "Mark Figor" <sip:5598@172.20.66.21>;tag=33579580
To: <sip:8000@172.17.227.21>
Date: Wed, 02 May 2007 19:58:46 GMT
Call-ID: 87f32480-1dd116ea-81-154214ac@172.20.66.21
Supported: timer
Min-SE: 1800
User-Agent: Cisco-CCM4.1
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK
CSeq: 101 INVITE
Max-Forwards: 70
Remote-Party-ID: "Mark Figor" <sip:5598@172.20.66.21>;party=calling;screen=no;privac y=off
Contact: <sip:5598@172.20.66.21:5060>
Expires: 180
Allow-Events: telephone-event
Content-Type: application/sdp
Content-Length: 227

v=0
o=CiscoSystemsCCM-SIP 2000 1000 IN IP4 172.20.66.21
s=SIP Call
c=IN IP4 172.20.66.21
t=0 0
m=audio 31172 RTP/AVP 0 101
a=sendrecv
a=rtpmap:0 PCMU/8000
a=ptime:20
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15

>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 172.20.66.21:5060) >>>>
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 172.20.66.21:5060;branch=z9hG4bK17fa2ff4;rport=5060;received =172.20.66.21
From: "Mark Figor" <sip:5598@172.20.66.21>;tag=33579580
To: <sip:8000@172.17.227.21>
Call-ID: 87f32480-1dd116ea-81-154214ac@172.20.66.21
CSeq: 101 INVITE
Server: LanScape Centrex Proxy/3.42.1.6 (www.LanScapeCorp.com)
Content-Length: 0

>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 172.20.66.21:5060) >>>>
SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP 172.20.66.21:5060;branch=z9hG4bK17fa2ff4;rport=5060;received =172.20.66.21
From: "Mark Figor" <sip:5598@172.20.66.21>;tag=33579580
To: <sip:8000@172.17.227.21>
Call-ID: 87f32480-1dd116ea-81-154214ac@172.20.66.21
CSeq: 101 INVITE
Proxy-Authenticate: Digest realm="ssg.petsmart.com", nonce="f1a7ca8be486b9995fbebaca2d12be59", opaque="0827f14d0e666ac6419d7bb2ef36e266"
Server: LanScape Centrex Proxy/3.42.1.6 (www.LanScapeCorp.com)
Content-Length: 0

<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 172.20.66.21:5060) <<<<
ACK sip:8000@172.17.227.21:5060 SIP/2.0
Via: SIP/2.0/UDP 172.20.66.21:5060;branch=z9hG4bK17fa2ff4
From: "Mark Figor" <sip:5598@172.20.66.21>;tag=33579580
To: <sip:8000@172.17.227.21>
Date: Wed, 02 May 2007 19:58:46 GMT
Call-ID: 87f32480-1dd116ea-81-154214ac@172.20.66.21
Max-Forwards: 70
CSeq: 101 ACK
Content-Length: 0

<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 172.20.66.21:5060) <<<<
INVITE sip:8000@172.17.227.21:5060 SIP/2.0
Via: SIP/2.0/UDP 172.20.66.21:5060;branch=z9hG4bK52bda57a
From: "Mark Figor" <sip:5598@172.20.66.21>;tag=33579584
To: <sip:8000@172.17.227.21>
Date: Wed, 02 May 2007 19:58:57 GMT
Call-ID: 8e819c00-1dd116ea-82-154214ac@172.20.66.21
Supported: timer
Min-SE: 1800
User-Agent: Cisco-CCM4.1
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK
CSeq: 101 INVITE
Max-Forwards: 70
Remote-Party-ID: "Mark Figor" <sip:5598@172.20.66.21>;party=calling;screen=no;privac y=off
Contact: <sip:5598@172.20.66.21:5060>
Expires: 180
Allow-Events: telephone-event
Content-Type: application/sdp
Content-Length: 227

v=0
o=CiscoSystemsCCM-SIP 2000 1000 IN IP4 172.20.66.21
s=SIP Call
c=IN IP4 172.20.66.21
t=0 0
m=audio 31174 RTP/AVP 0 101
a=sendrecv
a=rtpmap:0 PCMU/8000
a=ptime:20
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15

>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 172.20.66.21:5060) >>>>
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 172.20.66.21:5060;branch=z9hG4bK52bda57a;rport=5060;received =172.20.66.21
From: "Mark Figor" <sip:5598@172.20.66.21>;tag=33579584
To: <sip:8000@172.17.227.21>
Call-ID: 8e819c00-1dd116ea-82-154214ac@172.20.66.21
CSeq: 101 INVITE
Server: LanScape Centrex Proxy/3.42.1.6 (www.LanScapeCorp.com)
Content-Length: 0

>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 172.20.66.21:5060) >>>>
SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP 172.20.66.21:5060;branch=z9hG4bK52bda57a;rport=5060;received =172.20.66.21
From: "Mark Figor" <sip:5598@172.20.66.21>;tag=33579584
To: <sip:8000@172.17.227.21>
Call-ID: 8e819c00-1dd116ea-82-154214ac@172.20.66.21
CSeq: 101 INVITE
Proxy-Authenticate: Digest realm="ssg.petsmart.com", nonce="f1a7ca8be486b9995fbebaca2d12be59", opaque="64c85933e3d38c5358d2a9fba2e6f8dc"
Server: LanScape Centrex Proxy/3.42.1.6 (www.LanScapeCorp.com)
Content-Length: 0

<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 172.20.66.21:5060) <<<<
ACK sip:8000@172.17.227.21:5060 SIP/2.0
Via: SIP/2.0/UDP 172.20.66.21:5060;branch=z9hG4bK52bda57a
From: "Mark Figor" <sip:5598@172.20.66.21>;tag=33579584
To: <sip:8000@172.17.227.21>
Date: Wed, 02 May 2007 19:58:57 GMT
Call-ID: 8e819c00-1dd116ea-82-154214ac@172.20.66.21
Max-Forwards: 70
CSeq: 101 ACK
Content-Length: 0

<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 172.20.66.21:5060) <<<<
INVITE sip:8000@172.17.227.21:5060 SIP/2.0
Via: SIP/2.0/UDP 172.20.66.21:5060;branch=z9hG4bK7170e2e0
From: "DC38 Wireless" <sip:8506@172.20.66.21>;tag=33579588
To: <sip:8000@172.17.227.21>
Date: Wed, 02 May 2007 20:02:03 GMT
Call-ID: fd5ef500-1dd116ea-83-154214ac@172.20.66.21
Supported: timer
Min-SE: 1800
User-Agent: Cisco-CCM4.1
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK
CSeq: 101 INVITE
Max-Forwards: 70
Remote-Party-ID: "DC38 Wireless" <sip:8506@172.20.66.21>;party=calling;screen=no;privac y=off
Contact: <sip:8506@172.20.66.21:5060>
Expires: 180
Allow-Events: telephone-event
Content-Type: application/sdp
Content-Length: 227

v=0
o=CiscoSystemsCCM-SIP 2000 1000 IN IP4 172.20.66.21
s=SIP Call
c=IN IP4 172.20.66.21
t=0 0
m=audio 31176 RTP/AVP 0 101
a=sendrecv
a=rtpmap:0 PCMU/8000
a=ptime:20
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15

>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 172.20.66.21:5060) >>>>
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 172.20.66.21:5060;branch=z9hG4bK7170e2e0;rport=5060;received =172.20.66.21
From: "DC38 Wireless" <sip:8506@172.20.66.21>;tag=33579588
To: <sip:8000@172.17.227.21>
Call-ID: fd5ef500-1dd116ea-83-154214ac@172.20.66.21
CSeq: 101 INVITE
Server: LanScape Centrex Proxy/3.42.1.6 (www.LanScapeCorp.com)
Content-Length: 0

>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 172.20.66.21:5060) >>>>
SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP 172.20.66.21:5060;branch=z9hG4bK7170e2e0;rport=5060;received =172.20.66.21
From: "DC38 Wireless" <sip:8506@172.20.66.21>;tag=33579588
To: <sip:8000@172.17.227.21>
Call-ID: fd5ef500-1dd116ea-83-154214ac@172.20.66.21
CSeq: 101 INVITE
Proxy-Authenticate: Digest realm="ssg.petsmart.com", nonce="f1a7ca8be486b9995fbebaca2d12be59", opaque="2d11fa2c2f0b412b1e44e829f71c2fc2"
Server: LanScape Centrex Proxy/3.42.1.6 (www.LanScapeCorp.com)
Content-Length: 0

<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 172.20.66.21:5060) <<<<
ACK sip:8000@172.17.227.21:5060 SIP/2.0
Via: SIP/2.0/UDP 172.20.66.21:5060;branch=z9hG4bK7170e2e0
From: "DC38 Wireless" <sip:8506@172.20.66.21>;tag=33579588
To: <sip:8000@172.17.227.21>
Date: Wed, 02 May 2007 20:02:03 GMT
Call-ID: fd5ef500-1dd116ea-83-154214ac@172.20.66.21
Max-Forwards: 70
CSeq: 101 ACK
Content-Length: 0

<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 172.20.66.21:5060) <<<<
INVITE sip:8000@172.17.227.21:5060 SIP/2.0
Via: SIP/2.0/UDP 172.20.66.21:5060;branch=z9hG4bKa90152
From: "DC38 Wireless" <sip:8506@172.20.66.21>;tag=33579600
To: <sip:8000@172.17.227.21>
Date: Wed, 02 May 2007 20:04:45 GMT
Call-ID: 5dee3200-1dd116eb-84-154214ac@172.20.66.21
Supported: timer
Min-SE: 1800
User-Agent: Cisco-CCM4.1
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK
CSeq: 101 INVITE
Max-Forwards: 70
Remote-Party-ID: "DC38 Wireless" <sip:8506@172.20.66.21>;party=calling;screen=no;privac y=off
Contact: <sip:8506@172.20.66.21:5060>
Expires: 180
Allow-Events: telephone-event
Content-Type: application/sdp
Content-Length: 227

v=0
o=CiscoSystemsCCM-SIP 2000 1000 IN IP4 172.20.66.21
s=SIP Call
c=IN IP4 172.20.66.21
t=0 0
m=audio 31180 RTP/AVP 0 101
a=sendrecv
a=rtpmap:0 PCMU/8000
a=ptime:20
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15

>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 172.20.66.21:5060) >>>>
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 172.20.66.21:5060;branch=z9hG4bKa90152;rport=5060;received=1 72.20.66.21
From: "DC38 Wireless" <sip:8506@172.20.66.21>;tag=33579600
To: <sip:8000@172.17.227.21>
Call-ID: 5dee3200-1dd116eb-84-154214ac@172.20.66.21
CSeq: 101 INVITE
Server: LanScape Centrex Proxy/3.42.1.6 (www.LanScapeCorp.com)
Content-Length: 0

>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 172.20.66.21:5060) >>>>
SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP 172.20.66.21:5060;branch=z9hG4bKa90152;rport=5060;received=1 72.20.66.21
From: "DC38 Wireless" <sip:8506@172.20.66.21>;tag=33579600
To: <sip:8000@172.17.227.21>
Call-ID: 5dee3200-1dd116eb-84-154214ac@172.20.66.21
CSeq: 101 INVITE
Proxy-Authenticate: Digest realm="ssg.petsmart.com", nonce="f1a7ca8be486b9995fbebaca2d12be59", opaque="4663e760d62460cc431c0bdbe6e7f964"
Server: LanScape Centrex Proxy/3.42.1.6 (www.LanScapeCorp.com)
Content-Length: 0

<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 172.20.66.21:5060) <<<<
ACK sip:8000@172.17.227.21:5060 SIP/2.0
Via: SIP/2.0/UDP 172.20.66.21:5060;branch=z9hG4bKa90152
From: "DC38 Wireless" <sip:8506@172.20.66.21>;tag=33579600
To: <sip:8000@172.17.227.21>
Date: Wed, 02 May 2007 20:04:45 GMT
Call-ID: 5dee3200-1dd116eb-84-154214ac@172.20.66.21
Max-Forwards: 70
CSeq: 101 ACK
Content-Length: 0

<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 172.20.66.21:5060) <<<<
INVITE sip:8000@172.17.227.21:5060 SIP/2.0
Via: SIP/2.0/UDP 172.20.66.21:5060;branch=z9hG4bK4e6d9cda
From: "DC38 Wireless" <sip:8506@172.20.66.21>;tag=33579606
To: <sip:8000@172.17.227.21>
Date: Wed, 02 May 2007 20:08:23 GMT
Call-ID: dfde5b00-1dd116eb-85-154214ac@172.20.66.21
Supported: timer
Min-SE: 1800
User-Agent: Cisco-CCM4.1
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK
CSeq: 101 INVITE
Max-Forwards: 70
Remote-Party-ID: "DC38 Wireless" <sip:8506@172.20.66.21>;party=calling;screen=no;privac y=off
Contact: <sip:8506@172.20.66.21:5060>
Expires: 180
Allow-Events: telephone-event
Content-Type: application/sdp
Content-Length: 227

v=0
o=CiscoSystemsCCM-SIP 2000 1000 IN IP4 172.20.66.21
s=SIP Call
c=IN IP4 172.20.66.21
t=0 0
m=audio 31182 RTP/AVP 0 101
a=sendrecv
a=rtpmap:0 PCMU/8000
a=ptime:20
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15

>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 172.20.66.21:5060) >>>>
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 172.20.66.21:5060;branch=z9hG4bK4e6d9cda;rport=5060;received =172.20.66.21
From: "DC38 Wireless" <sip:8506@172.20.66.21>;tag=33579606
To: <sip:8000@172.17.227.21>
Call-ID: dfde5b00-1dd116eb-85-154214ac@172.20.66.21
CSeq: 101 INVITE
Server: LanScape Centrex Proxy/3.42.1.6 (www.LanScapeCorp.com)
Content-Length: 0

>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 172.20.66.21:5060) >>>>
SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP 172.20.66.21:5060;branch=z9hG4bK4e6d9cda;rport=5060;received =172.20.66.21
From: "DC38 Wireless" <sip:8506@172.20.66.21>;tag=33579606
To: <sip:8000@172.17.227.21>
Call-ID: dfde5b00-1dd116eb-85-154214ac@172.20.66.21
CSeq: 101 INVITE
Proxy-Authenticate: Digest realm="ssg.petsmart.com", nonce="f1a7ca8be486b9995fbebaca2d12be59", opaque="de524e0a06f1d96d55a8543cc56f736a"
Server: LanScape Centrex Proxy/3.42.1.6 (www.LanScapeCorp.com)
Content-Length: 0

<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 172.20.66.21:5060) <<<<
ACK sip:8000@172.17.227.21:5060 SIP/2.0
Via: SIP/2.0/UDP 172.20.66.21:5060;branch=z9hG4bK4e6d9cda
From: "DC38 Wireless" <sip:8506@172.20.66.21>;tag=33579606
To: <sip:8000@172.17.227.21>
Date: Wed, 02 May 2007 20:08:23 GMT
Call-ID: dfde5b00-1dd116eb-85-154214ac@172.20.66.21
Max-Forwards: 70
CSeq: 101 ACK
Content-Length: 0

Will it cause us issues if the proxy server is loaded on the same server as call manager?

support
Administrator

Joined: January 26 2005
Location: United States
Posts: 1666

Posted: May 02 2007 at 3:33pm \| IP Logged

Hi Nik,

Cool. That’s what we need! Good SIP log. Way to go.

Now at least Call Manager is sending the call to the LanScape Centrex Proxy Server (LS proxy).

I can see that the SIP INVITE is being challenged by the LS proxy. The Cisco Call Manager however is not subsequently responding with another INVITE with authentication credentials.

So we can progress further, this is what you must do:

Turn off authentication at the LS proxy so that we can go further to test call processing. If you can do this, then we may actually be able to get the LS proxy to vector the call to the CyberData paging server yet today.

Note:
At a later time you can configure Call Manager to respond to authentication challenges on the “SIP trunk” from the LS proxy. You are on your own here – not sure how to configure this in call manager but it should be straight forward. Configure Call Manager with the same authentication credentials you set up on the LS Proxy for user 8000:

User name: 8000
Realm: ssg.petsmart.com
password: whatever you defined at the LS proxy

After you turn off authentication at the LS proxy, test the call again and post the SIP log from the LS proxy just as you did above.

Support

support
Administrator

Joined: January 26 2005
Location: United States
Posts: 1666

Posted: May 02 2007 at 3:35pm \| IP Logged

Hi Nik,

<<< you
Will it cause us issues if the proxy server is loaded on the same server as call manager?

Support >>>
It should not but Lets keep your configuration the way it is until we get the call processing performing the way we want.

Support

nshoe18
Intermediate

Joined: May 01 2007
Location: United States
Posts: 15

Posted: May 02 2007 at 7:22pm \| IP Logged

all is good. all is running. thank you for your help.

support
Administrator

Joined: January 26 2005
Location: United States
Posts: 1666

Posted: May 02 2007 at 7:30pm \| IP Logged

Hi Nik,

Do you mean that call processing has worked as expected?

If so, that is terrific. Now we would like to ask a favor of you…

Could you please post a SIP log file from our LanScape Centrex Proxy Server????

We are very interested in the SIP transaction that takes place between the Cisco Call manager and our Proxy for the redirected call to your CyberData paging server from the Cisco Call Manager SIP trunk.

Thanks in advance,

Support

support
Administrator

Joined: January 26 2005
Location: United States
Posts: 1666

Posted: May 08 2007 at 6:58pm \| IP Logged

Hi Nik,

When you get a moment, please post a Proxy generated SIP log of the call coming from the Call Manager SIP trunk.

Thank you,

Support

If you wish to post a reply to this topic you must first login
If you are not already registered you must first register

Printable version

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot delete your posts in this forum
You cannot edit your posts in this forum
You cannot create polls in this forum
You cannot vote in polls in this forum