RADIUS Interface for Cisco SPS - Cisco - Global Home … Documentation Organization viii RADIUS...

RADIUS Interface for Cisco SPS

Corporate HeadquartersCisco Systems, Inc.170 West Tasman DriveSan Jose, CA 95134-1706 USAhttp://www.cisco.comTel: 408 526-4000

800 553-NETS (6387)Fax: 408 526-4100

http://www.cisco.com

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

RADIUS Interface for Cisco SPSCopyright © 2005 Cisco Systems, Inc. All rights reserved.

CCSP, the Cisco Square Bridge logo, Follow Me Browsing, and StackWise are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, and iQuick Study are service marks of Cisco Systems, Inc.; and Access Registrar, Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, FormShare, GigaDrive, GigaStack, HomeLink, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, LightStream, Linksys, MeetingPlace, MGX, the Networkers logo, Networking Academy, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, ProConnect, RateMUX, ScriptShare, SlideCast, SMARTnet, StrataView Plus, SwitchProbe, TeleRouter, The Fastest Way to Increase Your Internet Quotient, TransPath, and VCO are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.

All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0501R)

C O N T E N T S

Preface vii

Scope vii

Overview vii

Audience vii

Documentation Organization viii

Document Conventions viii

Obtaining Documentation x

Cisco.com x

Documentation CD-ROM x

Ordering Documentation xi

Documentation Feedback xi

Obtaining Technical Assistance xi

Cisco TAC Website xi

Opening a TAC Case xii

TAC Case Priority Definitions xii

Obtaining Additional Publications and Information xii

RADIUS Accounting for Cisco SPS 1

RADIUS Accounting for Cisco SPS Overview 1

RADUIS Server Accounting 2

RADIUS Client Accounting 4

sip-hdr VSA 6

RADIUS Data Format 7

Code 7

Identifier 7

Length 7

Authenticator 8

Request Authenticator 8

Response Authenticator 8

Attributes 8

Standard Attributes 8

Vendor-Specific Attributes 10

iiiRADIUS Interface for Cisco SPS

Contents

Correlating Accounting Records from Cisco SPS 12

Re-INVITEs 12

Server-Side and Client-Side Accounting Records 12

Duplicate Accounting Records Caused by Proxy Sending to Itself 13

Configuring RADIUS Accounting 13

Accounting Module Directives 15

Accounting-Related SIP Server Core Directives 16

Configuration Tips 17

Configurations Example and Call Flows with Debugging Enabled 18

Successful Call, Server-Side Accounting Enabled 18

Call Flow 19

Unsuccessful Call, Server-Side Accounting Enabled, Unsuccessful Accounting Enabled 20

Configuration 20

Call Flow 21

Forked Call; Server- and Client-Side Accounting Enabled; Unsuccessful Accounting Enabled 21

Configuration 21

Call Flow 22

RADIUS Authentication for Cisco SPS 25

RADIUS Authentication for Cisco SPS Overview 25

RADIUS Access-Request Format 26

Code 26

Identifier 27

Length 27

Authenticator 27



Attributes 28


Vendor-Specific Attributes 29

Configuring RADIUS Authentication 30

Authentication Module Directives 30

Authentication-Related SIP Server Core Directives 32

Configuration Example and Call Flows with Debugging Enabled 33

REGISTER-Accepted Scenario 33

Configuring the REGISTER-Accepted Scenario 33

Call Flow 35

ivRADIUS Interface for Cisco SPS

Contents

REGISTER Rejected Scenario 35

Configuring the REGISTER-Rejected Scenario 35

Call Flow 35

INVITE-Accepted Scenario 36

Configuring the INVITE-Accepted Scenario 36

Call Flow 36

INVITE Rejected 37

Configuration 37

Call Flow 37

RADIUS Preauthentication for Cisco SPS 39

RADIUS Preauthentication for Cisco SPS Overview 39

RADIUS Access-Request Format 40

Code 40

Identifier 40

Length 41

Authenticator 41



Attributes 41


Vendor Specific Attributes 42

Configuring RADIUS Preauthentication 43

RPMS Module Directives 45

Preauthentication-Related SIP Server Core Directives 45

Configuration Example and Call Flows with Debugging Enabled 46

INVITE-Accepted Scenario 46

Configuring the INVITE-Accepted Scenario 46

Call Flow 47

RADIUS Debugging File 48

Cisco SPS error_log File 48

INVITE-Rejected Scenario 48

Configuration 48

Call Flow 48

vRADIUS Interface for Cisco SPS

Contents

Cisco SPS Interface Reference Appendix 49

Accounting Configuration Screens 50

Authentication Configuration Screens 56

Preauthentication Configuration Screens 59

RADIUS Interface for Cisco SPS Scenario Output Appendix 61

RADIUS Accounting Message Listings 62

Successful Call, Server-Side Accounting Enabled 62

RADIUS Start and Stop Records 62

RADIUS Debugging file 63

Cisco SPS error_log file 65

Unsuccessful Call, Server-Side Accounting Enabled, Unsuccessful Accounting Enabled 77



Cisco SPS error_log file 79

Forked Call; Server- and Client-Side Accounting Enabled; Unsuccessful Accounting Enabled 84




RADIUS Authentication Message Listings 129

REGISTER-Accepted Scenario Messages 129



REGISTER-Rejected Scenario Messages 135



INVITE-Accepted Scenario Messages 140



INVITE-Rejected Scenario Messages 148



RADIUS Preauthentication Message Listings 154

INVITE-Rejected Scenario Messages 154



I N D E X

viRADIUS Interface for Cisco SPS

Preface

ScopeRADIUS Interface for Cisco SPS is based on Cisco Session Initiation Protocol (SIP) Proxy Server (SPS) Version 2.1. Subsequent releases of Cisco SPS support the same interface. The examples involve integration with the FreeRADIUS Remote Authentication Dial-In User Service (RADIUS) server, Version 0.9.1. Additional information about FreeRADIUS is available at http://www.freeradius.org/.

You can configure and integrate Cisco SPS with a RADIUS server for:

• Accounting

• Authentication

• Preauthentication

OverviewCisco SPS acts as an RFC 2865- and RFC 2866-compliant RADIUS client interfacing to an RFC 2865- and RFC 2866-compliant RADIUS server. In some cases, additional functionality not covered by these RFCs is required on behalf of the RADIUS server for the desired results to occur. These cases, and a detailed description of the requirements, are highlighted in this document.

RADIUS is an Internet Engineering Task Force (IETF) protocol based on the User Datagram Protocol (UDP). RADIUS functions by exchanging a set of attribute/value pairs between the client and server. For accounting, Cisco SPS acts as a RADIUS client sending Accounting-Request packets with the corresponding attribute value (AV) pairs to a RADIUS server to provide the necessary information for the server to form Call Detail Records (CDR). For authentication, Cisco SPS acts as a RADIUS client sending Access-Request packets with the corresponding AV pairs to a RADIUS server to facilitate the validation of a user’s credentials. For preauthentication, Cisco SPS acts as a RADIUS client sending Access-Request packets with the corresponding AV pairs to a RADIUS server to enforce service-level agreements (SLA).

AudienceThis document is intended for Cisco internal, customer and partner network support engineers, and network managers responsible for planning, designing, implementing, or integrating Cisco SPS to a RADIUS server.

viiRADIUS Interface for Cisco SPS

http://www.freeradius.org/

PrefaceDocumentation Organization

Documentation OrganizationThis document includes the following chapters:

• “RADIUS Accounting for Cisco SPS”—Describes the specifics of the accounting interface.

• “RADIUS Authentication for Cisco SPS”—Describes the specifics of the authentication interface.

• “RADIUS Preauthentication for Cisco SPS”—Describes the specifics of the preauthentication interface.

Document ConventionsWithin Cisco IOS software documentation, the term router is generally used to refer to a variety of Cisco products (for example, routers, access servers, and switches). Routers, access servers, and other networking devices that support Cisco IOS software are shown interchangeably within examples. These products are used only for illustrative purposes; that is, an example that shows one product does not necessarily indicate that other products are not supported.

The following conventions are used in Cisco IOS documentation:

Command syntax descriptions use the following conventions:

Nested sets of square brackets or braces indicate optional or required choices within optional or required elements. For example:

Convention Description

^ and Ctrl The ^ and Ctrl symbols represent the Control key. For example, the key combination ^D or Ctrl-D means press the Control key and D keys simultaneously. Keys are indicated in capital letters but are not case sensitive.

String A string is a nonquoted set of characters shown in italics. For example, when setting an SNMP community string to the public, do not use quotation marks around the string, or the string will include the quotation marks.


Bold Text in bold indicates commands and keywords that you enter literally as shown.

Italics Text in italics indicates arguments for which you supply values.

[x] Square brackets enclose an optional element (keyword or argument).

| A vertical line indicates a choice within an optional or required set of keywords or arguments.

[x | y] Square brackets enclosing keywords or arguments separated by a vertical line indicate an optional choice.

{x | y} Braces enclosing keywords or arguments separated by a vertical line indicate a required choice.


[x {y | z}] Braces and a vertical line within square brackets indicate a required choice within an optional element.

viiiRADIUS Interface for Cisco SPS

http://lbj/push_targets1/ucdit/cc/td/doc/product/voice/sipproxy/radiusps/radacc.htm

http://lbj/push_targets1/ucdit/cc/td/doc/product/voice/sipproxy/radiusps/radauth.htm

http://lbj/push_targets1/ucdit/cc/td/doc/product/voice/sipproxy/radiusps/radpreau.htm

PrefaceDocument Conventions

Examples use the following conventions:

IP addresses and telephone numbers use the following conventions:


screen Examples of information displayed on the screen are set in Courier font.

boldface screen Examples of text that you must enter are set in Courier bold font.

< > Angle brackets enclose text that is not printed on the screen, such as passwords.

! An exclamation point at the beginning of a line indicates a comment line. (Exclamation points are also displayed by the Cisco IOS software for certain processes.)

[ ] Square brackets enclose default responses to system prompts.


The letter a used in the high-order address range for an IP V4-formatted address.

Example: a.23.10.224

Represents a public Class A Internet address or network. These are used for illustrative purposes in place of public numbers.

The letter b used in the high-order address range for an IP V4-formatted address.

Example: b.23.10.224

Represents a public Class B Internet address or network. These are used for illustrative purposes in place of public numbers.

The letters x and y used within phone numbers

Example: xxx.yyy.1234

Represents the area code and prefix for a telephone number. These are used for illustrative purposes in place of public numbers.

ixRADIUS Interface for Cisco SPS

PrefaceObtaining Documentation

Caution Means reader be careful. In this situation, you might do something that could result in equipment damage or loss of data.

Note Means reader take note. Notes contain helpful suggestions or references to materials not contained in this manual.

Timesaver Means the described action saves time. You can save time by performing the action described in the paragraph.

Obtaining DocumentationCisco provides several ways to obtain documentation, technical assistance, and other technical resources. These sections explain how to obtain technical information from Cisco Systems.

Cisco.comYou can access the most current Cisco documentation on the World Wide Web at this URL:

http://www.cisco.com/univercd/home/home.htm

You can access the Cisco website at this URL:


International Cisco websites can be accessed from this URL:

http://www.cisco.com/public/countries_languages.shtml

Documentation CD-ROMCisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which may have shipped with your product. The Documentation CD-ROM is updated regularly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual or quarterly subscription.

Registered Cisco.com users can order a single Documentation CD-ROM (product number DOC-CONDOCCD=) through the Cisco Ordering tool:

http://www.cisco.com/en/US/partner/ordering/ordering_place_order_ordering_tool_launch.html

All users can order annual or quarterly subscriptions through the online Subscription Store:

http://www.cisco.com/go/subscription

xRADIUS Interface for Cisco SPS

http://www.cisco.com/univercd/home/home.htm


http://www.cisco.com/public/countries_languages.shtml

http://www.cisco.com/en/US/partner/ordering/ordering_place_order_ordering_tool_launch.html


PrefaceObtaining Technical Assistance

Ordering DocumentationYou can find instructions for ordering documentation at this URL:

http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm

You can order Cisco documentation in these ways:

• Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from the Networking Products MarketPlace:

http://www.cisco.com/en/US/partner/ordering/index.shtml

• Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco Systems Corporate Headquarters (California, USA.) at 408 526-7208 or, elsewhere in North America, by calling 800 553-NETS (6387).

Documentation FeedbackYou can submit comments electronically on Cisco.com. On the Cisco Documentation home page, click Feedback at the top of the page.

You can send your comments in e-mail to [email protected].

You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address:

Cisco SystemsAttn: Customer Document Ordering170 West Tasman DriveSan Jose, CA 95134-9883

We appreciate your comments.

Obtaining Technical AssistanceFor all customers, partners, resellers, and distributors who hold valid Cisco service contracts, the Cisco Technical Assistance Center (TAC) provides 24-hour, award-winning technical support services, online and over the phone. Cisco.com features the Cisco TAC website as an online starting point for technical assistance.

Cisco TAC WebsiteThe Cisco TAC website (http://www.cisco.com/tac) provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The Cisco TAC website is available 24 hours a day, 365 days a year.

Accessing all the tools on the Cisco TAC website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a login ID or password, register at this URL:

http://tools.cisco.com/RPF/register/register.do

xiRADIUS Interface for Cisco SPS


http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm

http://www.cisco.com/en/US/partner/ordering/index.shtml

http://www.cisco.com/tac


PrefaceObtaining Additional Publications and Information

Opening a TAC CaseThe online TAC Case Open Tool (http://www.cisco.com/tac/caseopen) is the fastest way to open P3 and P4 cases. (Your network is minimally impaired or you require product information). After you describe your situation, the TAC Case Open Tool automatically recommends resources for an immediate solution. If your issue is not resolved using these recommendations, your case will be assigned to a Cisco TAC engineer.

For P1 or P2 cases (your production network is down or severely degraded) or if you do not have Internet access, contact Cisco TAC by telephone. Cisco TAC engineers are assigned immediately to P1 and P2 cases to help keep your business operations running smoothly.

To open a case by telephone, use one of the following numbers:

Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227) EMEA: +32 2 704 55 55 USA: 1 800 553-2447

For a complete listing of Cisco TAC contacts, go to this URL:

http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml

TAC Case Priority DefinitionsTo ensure that all cases are reported in a standard format, Cisco has established case priority definitions.

Priority 1 (P1)—Your network is “down” or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.

Priority 2 (P2)—Operation of an existing network is severely degraded, or significant aspects of your business operation are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.

Priority 3 (P3)—Operational performance of your network is impaired, but most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.

Priority 4 (P4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.

Obtaining Additional Publications and InformationInformation about Cisco products, technologies, and network solutions is available from various online and printed sources.

• The Cisco Product Catalog describes the networking products offered by Cisco Systems, as well as ordering and customer support services. Access the Cisco Product Catalog at this URL:

http://www.cisco.com/en/US/products/products_catalog_links_launch.html

• Cisco Press publishes a wide range of networking publications. Cisco suggests these titles for new and experienced users: Internetworking Terms and Acronyms Dictionary, Internetworking Technology Handbook, Internetworking Troubleshooting Guide, and the Internetworking Design Guide. For current Cisco Press titles and other information, go to Cisco Press online at this URL:

http://www.ciscopress.com

xiiRADIUS Interface for Cisco SPS


http://www.cisco.com/tac/caseopen

http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml

http://www.cisco.com/en/US/products/products_catalog_links_launch.html



• Packet magazine is the Cisco quarterly publication that provides the latest networking trends, technology breakthroughs, and Cisco products and solutions to help industry professionals get the most from their networking investment. Included are networking deployment and troubleshooting tips, configuration examples, customer case studies, tutorials and training, certification information, and links to numerous in-depth online resources. You can access Packet magazine at this URL:

http://www.cisco.com/go/packet

• iQ Magazine is the Cisco bimonthly publication that delivers the latest information about Internet business strategies for executives. You can access iQ Magazine at this URL:

http://www.cisco.com/go/iqmagazine

• Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in designing, developing, and operating public and private internets and intranets. You can access the Internet Protocol Journal at this URL:

http://www.cisco.com/en/US/about/ac123/ac147/about_cisco_the_internet_protocol_journal.html

• Training—Cisco offers world-class networking training. Current offerings in network training are listed at this URL:

http://www.cisco.com/en/US/learning/index.html

xiiiRADIUS Interface for Cisco SPS


http://www.cisco.com/go/packet

http://www.cisco.com/go/iqmagazine

http://www.cisco.com/en/US/about/ac123/ac147/about_cisco_the_internet_protocol_journal.html

http://www.cisco.com/en/US/learning/index.html


xivRADIUS Interface for Cisco SPS

RADIUS Accounting for Cisco SPS

You can configure Cisco SPS to send Accounting-Request packets to a RADIUS server that correspond to the SIP transactions that the server processes. The Accounting-Request packets are start and stop records that contain a combination of standard RADIUS attributes and Cisco-defined vendor-specific attributes (VSAs).

RADIUS Accounting for Cisco SPS OverviewCisco SPS generates Accounting-Request packets for all branches of each INVITE and BYE transaction. This facilitates start and stop records being sent to a RADIUS server for all call attempts, including all branches of forked call-attempts, whether successful, unsuccessful, or canceled. All Accounting-Request packets for the same call contain the same Call ID, and the RADIUS server, or a billing server working with the RADIUS server, must be able to correlate Accounting-Request packets based on this Call ID. The high-level diagram in Figure 1 shows a SIP call from one SIP phone to another through Cisco SPS and the corresponding RADIUS Accounting-Request packet sent by Cisco SPS to the RADIUS server. In this example, the RADIUS server forms a call detail record (CDR) from the Accounting-Request packet and forwards the CDR to the billing server for correlation.

Figure 1 Accounting Components

The configuration options in the Cisco SPS allow the customization of accounting triggers. To upstream entities, Cisco SPS appears as a server side entity that handles requests. To downstream entities, Cisco SPS appears as a client side entity that initiates requests. Configuration options enable accounting for call attempts on the server side or client side, as well as for successful and/or unsuccessful call attempts. The call flow in Figure 2 demonstrates the various accounting records that can be generated for a call.

IP

Cisco SPSSIP

SIP

SIP Domain

RADIUS/Accounting Domain

RADIUSaccounting request CDR

RADIUSserver

Billingserver

1178

99

IP

IP

1RADIUS Interface for Cisco SPS

RADIUS Accounting for Cisco SPSRADIUS Accounting for Cisco SPS Overview

Figure 2 Accounting Call Flow

The following numbered process describes the call-flow protocol outlined in Figure 2:

1. User A wants to call User B. User A sends an INVITE for User B to Cisco SPS.

2. User B has registered at both B1 and B2.

3. Cisco SPS sends the INVITE to both B1 and B2.

4. B2 is busy and returns 486. Cisco SPS sends client side unsuccessful Stop.

5. User B has a Call Forward Busy contact set to B3, so Cisco SPS forwards INVITE to B3.

6. The INVITE to B1 times out. Cisco SPS generates an internal 408 and sends client side unsuccessful Stop.

7. B3 answers the call and returns 200. Cisco SPS sends client side Start.

8. Cisco SPS forwards 200 to User A and sends server side Start.

9. User A sends an ACK

10. Cisco SPS forwards the ACK to User B.

11. User A sends the BYE to Cisco SPS.

12. Cisco SPS forwards the BYE to B3.

13. Cisco SPS receives the 200 for the BYE from B3 and sends client side successful Stop.

14. Cisco SPS forwards the 200 for the BYE to User A and sends server side successful Stop

RADUIS Server AccountingFor a successful server-side call attempt, a Start record is sent when a 200 final response for the INVITE is returned upstream. A Stop record is sent when a final response is sent for the BYE.

1179

00

1

2345

6

789

1011

1213

14

200BYE

ACK

408-1

200-3

INVITE-3486-2

INVITE-2INVITE-1

INVITE

Cisco 7961Server

side

Cisco SPSClientside 99023126 Cisco 7905(I)

Cisco 7905(II)

200-3ACK

BYE

200



The Start record contains an h323-start-time, which is the time the INVITE was received, and an h323-connect-time, which is the time the 200 was sent. The h323-call-origin is set to answer, indicating this is a server-side accounting record. The sip-status-code VSA is set to 200, which is the value of the final response for the INVITE. A text representation of the Start, complete with all standard RADIUS attributes and Cisco-defined VSAs, is as follows:

NAS-IP-Address = a.4.61.72NAS-Port-Type = VirtualUser-Name = “1230”Service-Type = Login-UserAcct-Status-Type = StartAcct-Session-Id = “[email protected]”Called-Station-Id = “<sip:[email protected]:5060>”Calling-Station-Id = “<sip:[email protected]:9090>”Vendor-Specific-9-25 = “h323-setup-time=21:31:14.578 GMT Mon Apr 14 2003”Vendor-Specific-9-28 = “h323-connect-time=21:31:24.692 GMT Mon Apr 14 2003”Vendor-Specific-9-26 = “h323-call-origin=answer”Vendor-Specific-9-27 = “h323-call-type=VoIP”Vendor-Specific-9-1 = “sip-status-code=200”Vendor-Specific-9-1 = “session-protocol=sip”Vendor-Specific-9-1 = “[email protected]”Vendor-Specific-9-1 = “method=INVITE”Vendor-Specific-9-1 = “prev-hop-via=SIP/2.0/UDP a.4.61.70:9090”Vendor-Specific-9-1 = “prev-hop-ip=a.4.61.70:9090”Vendor-Specific-9-1 = “incoming-req-uri=sip:[email protected]:5060”Vendor-Specific-9-1 = “outgoing-req-uri=sip:[email protected]:5060”Vendor-Specific-9-1 = “next-hop-ip=a.4.106.19:5060”

The Stop record contains an h323-disconnect-time, which is the time the BYE was received. The h323-call-origin is set to answer, indicating this is a server-side accounting record. The h323-disconnect-cause is not used; instead, the sip-status-code VSA is added and set to the value of the final response for the BYE. For this reason, the Stop is not sent until the final response for the BYE has been sent. A text representation of the Stop, complete with all standard RADIUS attributes and Cisco-defined VSAs, is as follows:

NAS-IP-Address = a.4.61.72NAS-Port-Type = VirtualUser-Name = “1230”Service-Type = Login-UserAcct-Status-Type = StopAcct-Session-Id = “[email protected]”Called-Station-Id = “<sip:[email protected]:5060>;tag=1F37F280-21AD”Calling-Station-Id = “<sip:[email protected]:9090>”Vendor-Specific-9-29 = “h323-disconnect-time=21:31:44.770 GMT Mon Apr 14 2003"Vendor-Specific-9-26 = “h323-call-origin=answer”Vendor-Specific-9-27 = “h323-call-type=VoIP”Vendor-Specific-9-1 = “sip-status-code=200”Vendor-Specific-9-1 = “session-protocol=sip”Vendor-Specific-9-1 = “[email protected]”Vendor-Specific-9-1 = “method=BYE”Vendor-Specific-9-1 = “prev-hop-via=SIP/2.0/UDP a.4.61.70:9090”Vendor-Specific-9-1 = “prev-hop-ip=a.4.61.70:9090”Vendor-Specific-9-1 = “incoming-req-uri=sip:[email protected]:5060”Vendor-Specific-9-1 = “outgoing-req-uri=sip:[email protected]:5060”Vendor-Specific-9-1 = “next-hop-ip=a.4.106.19:5060”

For an unsuccessful server-side call attempt, there is no Start record. A Stop record is sent when the best non-200 response for the INVITE is returned upstream, including the CANCEL scenario in which Cisco SPS waits for the 487 from the downstream and returns it upstream. The Stop record contains an h323-start-time, which is the time the INVITE message was received, and an h323-disconnect-time,



which is the time the final response was sent. The h323-call-origin is set to answer, indicating this is a server-side accounting record. The sip-status-code VSA is set to the value of the final response for the INVITE. A text representation of the Stop, complete with all standard RADIUS attributes and Cisco-defined VSAs, is as follows:

NAS-IP-Address = a.4.61.72NAS-Port-Type = VirtualUser-Name = “1230”Service-Type = Login-UserAcct-Status-Type = StopAcct-Session-Id = “[email protected]”Called-Station-Id = “<sip:[email protected]:5060>;tag=1F37F280-21AD”Calling-Station-Id = “<sip:[email protected]:9090>”Vendor-Specific-9-25 = "h323-setup-time=21:31:14.578 GMT Mon Apr 14 2003"Vendor-Specific-9-29 = "h323-disconnect-time=21:31:44.770 GMT Mon Apr 14 2003"Vendor-Specific-9-26 = “h323-call-origin=answer”Vendor-Specific-9-27 = “h323-call-type=VoIP”Vendor-Specific-9-1 = “sip-status-code=487”Vendor-Specific-9-1 = “session-protocol=sip”Vendor-Specific-9-1 = “[email protected]”Vendor-Specific-9-1 = “method=INVITE”Vendor-Specific-9-1 = “prev-hop-via=SIP/2.0/UDP a.4.61.70:9090”Vendor-Specific-9-1 = “prev-hop-ip=a.4.61.70:9090”Vendor-Specific-9-1 = “incoming-req-uri=sip:[email protected]:5060”Vendor-Specific-9-1 = “outgoing-req-uri=sip:[email protected]:5060”Vendor-Specific-9-1 = “next-hop-ip=a.4.106.19:5060”

RADIUS Client AccountingFor the client-side accounting, Accounting-Request packets (Starts or Stops) are sent on behalf of each branch when a final response is received on that branch. If the final response is a 200 for an INVITE, a Start record is sent for that client-side branch. The corresponding Stop record is sent when the final response is received or generated for the BYE. If the final response for the INVITE is a non-200 response, a Stop is generated for the given client-side branch when the final response is received or generated.

For a successful client-side call, the Start record contains an h323-start-time, which is the time the INVITE was sent, and an h323-connect-time, which is the time the 200 was received. The h323-call-origin is set to originate indicating this is a client-side accounting record. The sip-status-code VSA is set to 200, which is the value of the final response for the INVITE. A text representation of a sample Start, complete with all standard RADIUS attributes and Cisco defined VSAs, is as follows:

NAS-IP-Address = a.4.61.72NAS-Port-Type = VirtualUser-Name = “1230”Service-Type = Login-UserAcct-Status-Type = StartAcct-Session-Id = “[email protected]”Called-Station-Id = “<sip:[email protected]:5060>”Calling-Station-Id = “<sip:[email protected]:9090>”Vendor-Specific-9-25 = "h323-setup-time=21:31:14.578 GMT Mon Apr 14 2003"Vendor-Specific-9-28 = "h323-connect-time=21:31:24.692 GMT Mon Apr 14 2003"Vendor-Specific-9-26 = “h323-call-origin=originate”Vendor-Specific-9-27 = “h323-call-type=VoIP”Vendor-Specific-9-1 = “sip-status-code=200”Vendor-Specific-9-1 = “session-protocol=sip”Vendor-Specific-9-1 = “[email protected]”Vendor-Specific-9-1 = “method=INVITE”



Vendor-Specific-9-1 = “prev-hop-via=SIP/2.0/UDP a.4.61.70:9090”Vendor-Specific-9-1 = “prev-hop-ip=a.4.61.70:9090”Vendor-Specific-9-1 = “incoming-req-uri=sip:[email protected]:5060”Vendor-Specific-9-1 = “outgoing-req-uri=sip:[email protected]:5060”Vendor-Specific-9-1 = “next-hop-ip=a.4.106.19:5060”

When a final response for a BYE is received or generated, a Stop record is sent on behalf of the client. The Stop record contains an h323-disconnect-time, which is the time the final response was received or generated. The h323-call-origin is set to originate, indicating this is a client-side accounting record. The h323-disconnect-cause is not used; instead, the sip-status-code VSA is added and set to the value of the final response for the BYE. For this reason, the Stop is not sent until the final response for the BYE has been received. A text representation of a sample Stop, complete with all standard RADIUS attributes and Cisco defined VSAs, is as follows:

NAS-IP-Address = a.4.61.72NAS-Port-Type = VirtualUser-Name = “1230”Service-Type = Login-UserAcct-Status-Type = StopAcct-Session-Id = “[email protected]”Called-Station-Id = “<sip:[email protected]:5060>;tag=1F37F280-21AD”Calling-Station-Id = “<sip:[email protected]:9090>”Vendor-Specific-9-29 = "h323-disconnect-time=21:31:44.770 GMT Mon Apr 14 2003"Vendor-Specific-9-26 = “h323-call-origin=originate”Vendor-Specific-9-27 = “h323-call-type=VoIP”Vendor-Specific-9-1 = “sip-status-code=200”Vendor-Specific-9-1 = “session-protocol=sip”Vendor-Specific-9-1 = “[email protected]”Vendor-Specific-9-1 = “method=BYE”Vendor-Specific-9-1 = “prev-hop-via=SIP/2.0/UDP a.4.61.70:9090”Vendor-Specific-9-1 = “prev-hop-ip=a.4.61.70:9090”Vendor-Specific-9-1 = “incoming-req-uri=sip:[email protected]:5060”Vendor-Specific-9-1 = “outgoing-req-uri=sip:[email protected]:5060”Vendor-Specific-9-1 = “next-hop-ip=a.4.106.19:5060”

An unsuccessful Stop record is generated for any client-side branch for which a non-200 response for the INVITE is received or generated. When a CANCEL is sent down a branch, Cisco SPS waits for the 487, for the corresponding INVITE from downstream to send a Stop record, indicating this branch was cancelled. The Stop record contains an h323-start-time, which is the time the INVITE was sent, and an h323-disconnect-time, which is the time the final response was received or generated. The h323-call-origin is set to originate indicating this is a client accounting record. The sip-status-code VSA is set to the value of the final response for the INVITE. A text representation of a sample Stop, complete with all standard RADIUS attributes and Cisco defined VSAs, is as follows:

NAS-IP-Address = a.4.61.72NAS-Port-Type = VirtualUser-Name = “1230”Service-Type = Login-UserAcct-Status-Type = StopAcct-Session-Id = “[email protected]”Called-Station-Id = “<sip:[email protected]:5060>;tag=1F37F280-21AD”Calling-Station-Id = “<sip:[email protected]:9090>”Vendor-Specific-9-25 = "h323-setup-time=21:31:14.578 GMT Mon Apr 14 2003"Vendor-Specific-9-29 = "h323-disconnect-time=21:31:44.770 GMT Mon Apr 14 2003"Vendor-Specific-9-26 = “h323-call-origin=originate”Vendor-Specific-9-27 = “h323-call-type=VoIP”Vendor-Specific-9-1 = “sip-status-code=487”Vendor-Specific-9-1 = “session-protocol=sip”Vendor-Specific-9-1 = “[email protected]”Vendor-Specific-9-1 = “method=INVITE”



Vendor-Specific-9-1 = “prev-hop-via=SIP/2.0/UDP a.4.61.70:9090”Vendor-Specific-9-1 = “prev-hop-ip=a.4.61.70:9090”Vendor-Specific-9-1 = “incoming-req-uri=sip:[email protected]:5060”Vendor-Specific-9-1 = “outgoing-req-uri=sip:[email protected]:5060”Vendor-Specific-9-1 = “next-hop-ip=a.4.106.19:5060”

sip-hdr VSACisco SPS provides configuration options with which you can specify any SIP headers to be sent in VSA 1 (AVPair) within RADIUS Accounting-Request packets. The headers included in the various requests are extracted from SIP messages as follows:

• Server-side Start: 200 for the INVITE returned upstream

• Server-side Stop (unsuccessful call): 3xx-6xx for the INVITE returned upstream

• Server-side Stop (successful call): Final response for the BYE received or generated

• Client-side Start: 200 for INVITE received from downstream branch

• Client-side Stop (unsuccessful branch): 3xx-6xx for the INVITE received (or generated)

• Client-side Stop (successful branch): Final response for the BYE that was sent

A text representation of a sample Start in which Cisco SPS has been configured to include the CSeq and Contact headers, complete with all standard RADIUS attributes and Cisco defined VSAs, is as follows (note that the sip-hdr attributes appear in bold for illustrative purposes):

NAS-IP-Address = a.4.61.72NAS-Port-Type = VirtualUser-Name = "1230"Service-Type = Login-UserAcct-Status-Type = StartAcct-Session-Id = "[email protected]"Called-Station-Id = "<sip:[email protected]:5060>"Calling-Station-Id = "<sip:[email protected]:9090>"Vendor-Specific-9-25 = "h323-setup-time=21:31:14.578 GMT Mon Apr 14 2003"Vendor-Specific-9-28 = "h323-connect-time=21:31:24.692 GMT Mon Apr 14 2003"Vendor-Specific-9-26 = "h323-call-origin=answer"Vendor-Specific-9-27 = "h323-call-type=VoIP"Vendor-Specific-9-1 = "sip-status-code=200"Vendor-Specific-9-1 = "session-protocol=sip"Vendor-Specific-9-1 = "[email protected]"Vendor-Specific-9-1 = "method=INVITE"Vendor-Specific-9-1 = "prev-hop-via=SIP/2.0/UDP a.4.61.70:9090"Vendor-Specific-9-1 = "prev-hop-ip=a.4.61.70:9090"Vendor-Specific-9-1 = "incoming-req-uri=sip:[email protected]:5060"Vendor-Specific-9-1 = "outgoing-req-uri=sip:[email protected]:5060"Vendor-Specific-9-1 = "next-hop-ip=a.4.106.19:5060"Vendor-Specific-9-1 = "sip-hdr=Contact: <sip:[email protected]:5060>"Vendor-Specific-9-1 = "sip-hdr=CSeq: 101 INVITE"


RADIUS Accounting for Cisco SPSRADIUS Data Format

RADIUS Data FormatA summary of the RADIUS data format, as defined in RFC 2866 follows. The RADIUS accounting record fields are transmitted from left to right.

0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Code | Identifier | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | | Authenticator | | | | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Attributes ... +-+-+-+-+-+-+-+-+-+-+-+-+-

The following sections describe the specific fields that make up the accounting record.

CodeThe Code field is one octet and identifies the type of RADIUS packet. RADIUS accounting codes (decimal) are assigned as follows:

4—Accounting-Request code (used in Start and Stop requests sent by Cisco SPS)

5—Accounting-Response code (used in Start and Stop responses returned by the RADIUS server)

Upon receipt of an Accounting-Request packet, the RADIUS server must transmit an Accounting-Response packet reply if the server successfully records the accounting packet—and must not transmit any reply if the server fails to record the accounting packet.

IdentifierThe Identifier field is one octet and aids in matching requests and replies. The RADIUS server can detect a duplicate request if the server has the same client source IP address and source UDP port and Identifier field within a short span of time. Cisco SPS changes the Identifier field whenever the content of the Attributes field changes and whenever a valid reply has been received for a previous request. For retransmissions where the contents are identical, the Identifier field remains unchanged. Cisco SPS uses monotonically increasing identifiers that wrap around to 1 once they reach 254.

LengthThe Length field is two octets and indicates the length of the packet including the Code, Identifier, Length, Authenticator, and Attribute fields. Octets outside the range of the Length field must be treated as padding and ignored on reception. If a packet is shorter than the Length field indicates, the packet must be silently discarded. The minimum length of the RADIUS Accounting Record packet is 20 and maximum length is 4095. If Cisco SPS is configured to include more headers than fit within the maximum length, the Accounting-Request packet is truncated.



AuthenticatorThe Authenticator field is sixteen (16) octets. The most significant octet is transmitted first. The Authenticator field value is used to authenticate the messages between the client and the RADIUS accounting server.

Request Authenticator

In Accounting-Request packets, the Authenticator value is a 16-octet Message Digest 5 (MD5) checksum, which is called the Request Authenticator. Cisco SPS and the RADIUS server share a configurable secret. The Request Authenticator field in Accounting-Request packets contains a one-way MD5 hash calculated over a stream of octets, consisting of the Code + Identifier + Length + 16 zero octets + request attributes + shared secret (where + indicates concatenation). The 16-octet MD-hash value is stored in the Authenticator field of the Accounting-Request packet. The shared secret is configured on Cisco SPS as described in “Accounting Module Directives” section on page 15.

Response Authenticator

The Authenticator field in an that is Accounting-Response packet is called the Response Authenticator, and contains a one-way MD5 hash that is calculated over a stream of octets, consisting of the Accounting-Response Code, Identifier, Length, the Request Authenticator field from the Accounting-Request packet being replied to, and the response attributes if any, followed by the shared secret. The resulting 16-octet MD5-hash value is stored in the Authenticator field of the Accounting-Response packet. The shared secret that is configured on the RADIUS server must match the shared secret that is configured on Cisco SPS.

AttributesThe Attributes field is variable in length and contains a list of Attributes fields. Attributes may have multiple instances. The end of the list of attributes is indicated by the Length field of the RADIUS packet. A summary of the attribute format follows. The fields are transmitted from left to right.

0 1 2 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type | Length | Value ... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Standard Attributes

The standard RADIUS attributes in RFC 2865 and RFC 2866 that are included in Accounting-Request packets from Cisco SPS are listed in Table 1. The Attribute column is for illustrative purposes only because it is not a field in the actual attributes that are included in the request. The Length field is in octets and is 1 (for the Type field) + 1 (for the Length field) + length of the Value field.



Table 1 Standard Attributes for Accounting-Request Packets

Attribute TypeLength (octets) Value

User Name 1 3-254 User part of the URL in the “From” SIP header or user in “Proxy-Authorization” SIP header, if present. This value is controlled by a configuration directive (OrigUserNameSource).

If the RadiusUserNameAttrAddDomain directive is On, the domain in the “From” header will be appended to the User Name and the User Name attribute will be in the name@domain format.

The User Name can be expanded to a fully expanded E164 number. If the user name is taken from the “From” header, the expansion is dependent on the user type and the NumericUserNameInterpretation directive. If the user name is taken from the “Proxy-Authorization” header, the expansion is dependent on the NumExpandAuthUserName directive. The expansion is based on the number expansion rules, which are defined in the number expansion module.

Example: “5000”

Example: “+1xxxyyy1212”

Example: “[email protected]”

NAS IP 4 6 IP address of Cisco SPS.

Example: a.22.76.1

Service-Type 6 6 1, which stands for Login.

Example: 1

Vendor-Specific 26 7-254 See Table 2 for the complete set.

Called-Station-Id 30 3-254 “To” SIP header value of the request.

Example: "<sip:[email protected]>; tag=c3943000dd3-ba2b824”

Calling-Station-Id 31 3-254 “From” SIP header value of the request.

Example: “<sip:[email protected]>;tag=c1234567dd3-ab2b248”

Acct-Status-Type 40 6 1 for Start, 2 for Stop.

Example: 1

Acct-Session-Id 44 3-254 “Call-Id” SIP header value of the request.

Example: "[email protected]"

NAS Port Type 61 6 5 stands for Virtual. Virtual refers to a connection by the client to Cisco SPS via a transport protocol. In this case, SIP is used, instead of a physical port.

Example: 5



Vendor-Specific Attributes

A summary of the vendor-specific attribute (VSA) format is as follows:

0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type | Length | Vendor-ID +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Vendor-ID (cont) | Vendor-Type | Vendor-Length| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Vendor-Data ... +-+-+-+-+-+-+-+-+-+-+-+-+-

The values of these fields for Accounting-Request packets from Cisco SPS are the following:

• Type = 26 (indicating Vendor-Specific)

• Length = 7-254 octets

• Vendor-ID = 9 (Cisco’s Vendor-ID for all VSAs used by Cisco SPS)

• Vendor-Type, Vendor-Length, and Vendor-Data take various values as summarized in Table 2.

The Attribute column is for illustrative purposes only because it is not a field in the actual attributes that are included in the request. The Vendor-Length field is in octets and is 1 (for the Vendor-Type field) + 1 (for the Vendor-Length field) + length of the Vendor-Data field. For additional details on all Cisco VSAs, see http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/vapp_dev/vsaig3.htm#27593.

Table 2 Cisco VSAs for Accounting Request packets

Attribute Vendor TypeVendor Length (octets) Vendor Data

h323-conf-id 24 Less than or equal to 247

“cisco-GUID” SIP header value of the request. If this header is not present in the SIP request, this VSA is omitted from the accounting request.

Example: “h323-conf-id=2176014509-3094090198-2164699425-3804311776”

h323-call-setup-time 25 Less than or equal to 247

Time the SIP INVITE was processed; GMT format. This VSA is omitted if the accounting request is not for a SIP INVITE.

Example: “h323-setup-time=21:31:14.578 GMT Mon Apr 14 2003"

h323-call-origin 26 Less than or equal to 247

answer for server side, or originate of client side.

Example: “h323-call-origin=answer”

h323-call-type 27 Less than or equal to 247

VoIP.

Example: “h323-call-type=VoIP”

h323-connect-time 28 Less than or equal to 247

Time the response for SIP INVITE was processed; GMT format. This VSA is included in Start requests only.

Example: “h323-connect-time=21:31:24.692 GMT Mon Apr 14 2003"


http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/vapp_dev/vsaig3.htm#27593


h323-disconnect-time

29 Less than or equal to 247

Time the response was processed for call-ending request; this may be a non-200 response for an INVITE or a response for a BYE. This VSA is included in Stop requests only.

Example: “h323-disconnect-time=21:31:44.770 GMT Mon Apr 14 2003"

session-protocol 1 Less than or equal to 247

sip.

Example: “session-protocol=sip”

Call-id 1 Less than or equal to 247

“Call-Id” SIP header value.


Method 1 Less than or equal to 247

Method name given in the request line which may be INVITE or BYE. Start requests always have INVITE, but Stop requests have either INVITE (for an unsuccessful call attempt) or BYE.

Example: “method=INVITE”

incoming-req-uri 1 Less than or equal to 247

Request URI of the incoming SIP request.

Example: “incoming-req-uri=sip:[email protected]”

prev-hop-ip 1 Less than or equal to 247

Previous hop IP address as seen by the proxy.

Example: “prev-hop-ip=a.22.76.38:5060”

prev-hop-via 1 Less than or equal to 247

The topmost “Via” header when the SIP request is received by Cisco SPS.

Example: “prev-hop-via=SIP/2.0/UDP a.22.76.38:5060;received=a.22.76.38”

outgoing-req-uri 1 Less than or equal to 247

Request URI of the outgoing SIP request sent by Cisco SPS.

Example: “outgoing-req-uri=sip:[email protected]:5060”

next-hop-ip 1 Less than or equal to 247

IP to which the SIP request is forwarded by Cisco SPS.

Example: "next-hop-ip=a.22.76.104:5060"

next-hop-dn 1 Less than or equal to 247

Domain name or fully qualified domain name where the SIP request is forwarded by Cisco SPS. This VSA is omitted if the next-hop domain name or fully qualified domain name is not known.

Example: "next-hop-dn=cisco.com"

sip-hdr 1 Less than or equal to 247

An arbitrary SIP header found in the SIP request received by Cisco SPS (complete header line). Inclusion of any given header is controlled by a configuration directive AcctIncludeSIPHeader.

Example: “sip-hdr=CSeq: 101 INVITE”

Example: “sip-hdr=Via: SIP/2.0/UDP b.19.174.99:5060;branch=363e586d-e1529570-dad25df7-49a3df73-1,SIP/2.0/UDP a.22.76.38:5060;received=a.22.76.38”

Table 2 Cisco VSAs for Accounting Request packets

Attribute Vendor TypeVendor Length (octets) Vendor Data


RADIUS Accounting for Cisco SPSCorrelating Accounting Records from Cisco SPS

Correlating Accounting Records from Cisco SPSIf both server-side and client-side accounting are enabled, all successful calls result in a Start and a Stop being sent for both the server side and the client side. Enabling server-side and client-side accounting also results in 0 or more Stops being sent for any client-side branches which were not successful. All unsuccessful calls result in a Stop being sent for the server side, and a Stop being sent for any client-side branches. It is possible that there are no client-side branches (such as when a translation phase yields no destinations for the call). All Starts and Stops corresponding to the same call can be correlated based on the fact they all contain the same Call-Id. The Call-Id appears in the Start and Stop as both the Acct-Session-Id (see Table 1) and the call-id VSA (see Table 2).

Accounting-Request packets for individual client side branches may be distinguished by examining the “To” tag, which is contained in the Called-Station-Id attribute (see Table 1) associated with each record.

Called-Station-Id = “<sip:[email protected]:5060>;tag=1F37F280-21AD”

In the example above, the tag value is 1F37F280-21AD. Any record for a specific client-side branch has the same tag in addition to having the same Call-Id. For successful calls, a single client-side Stop has the same tag in the Called-Station-Id attribute as the previously sent client-side Start. The server side Start and Stop share this same tag. Because the BYE request may be sent from either side of the call, the “To” tag of the Start may instead match the “From” tag, which is contained in the Calling-Station-Id attribute (see Table 1) of the Stop.

Called-Station-Id = “<sip:[email protected]:5060>;tag=1F37F280-21AD”

Therefore, if the “To” tag of the Stop does not match the “To” tag of any Starts, the “From” tag of the Stop must be matched against the “To” tag of the Starts as well.

Re-INVITEsA re-INVITE for the same call results in another set of Accounting-Request packets with the same Call-Id. In order to distinguish the original INVITE from each re-INVITE, the CSeq header may be included in the accounting records as a sip-hdr VSA (see Table 2).

Vendor-Specific-9-1 = “sip-hdr=CSeq: 101 INVITE”

The CSeq value is different and increases for each re-INVITE. For example, the Starts for the original INVITE could all have CSeq equal to 101. The Starts for the first re-INVITE would have CSeq equal to 102. The Starts for the next re-INVITE would have CSeq equal to 103. This continues until the call ends with a BYE message when the Stops are sent with CSeq equal to the last re-INVITE plus one, or 104. Optionally, the extra Start records for any re-INVITEs can be dismissed as duplicates.

Server-Side and Client-Side Accounting RecordsThe value of the h323-call-origin VSA (see Table 2) distinguishes server-side accounting requests from client-side accounting requests.

Vendor-Specific-9-26 = “h323-call-origin=answer”

The h323-call origin VSA has the value of answer for the server side and originate for the client side.


RADIUS Accounting for Cisco SPSConfiguring RADIUS Accounting

Duplicate Accounting Records Caused by Proxy Sending to ItselfLogic exists in Cisco SPS blocking accounting requests when Cisco SPS receives and sends accounting requests from or to itself in order to avoid generating duplicate Accounting-Request packets. This logic includes Cisco SPS recognizing SIP messages from and to the IP address associated with any farm member as being from or to itself.

Configuring RADIUS AccountingYou can configure Cisco SPS to send Accounting-Request packets to up to two RADIUS servers. For initial testing, it may be more convenient to set up a single RADIUS server only; but in a production environment, using a pair of RADIUS servers for redundancy is strongly recommended.

Cisco SPS has multiple SIP message-handling processes (sipds). Each process handles individual SIP messages. In the event the given SIP message is one that requires accounting, it is the responsibility of the sipd handling the message to send the corresponding Accounting-Request packet. The Accounting-Request packet is generated and sent after the SIP message processing has been completed. This means that SIP request processing is not delayed or dependent on accounting.

The algorithm by which the sipd selects a RADIUS server to which to send the Accounting-Request packet is shown in Figure 3.



Figure 3 RADIUS Request State Machine

The values of the various retransmission timers and counters, as well as the configuration of the primary and the secondary RADIUS servers, are described in two sections:

No

Yes

No

Yes

No

Response

Yes

Wait

No

Yes

New request

Waitreceived

Ignore

RadiusRetryTimer expires

Clear RadiusRetry-AfterFail

Is RadiusRetryAfter-FailureCounter >

RadiusRetryAfter-Failure

Set CurrentRadiusServer to LastGoodRadiusServer

Send request to CurrentRadiusServer and start

RadiusRetransInterval timer

Set LastGoodServer to CurrentRadiusServer, clear all counters, stop all timers except RadiusRetryTimer

Increment RadiusRetransCounter

RadiusRetransTimerexpires

Is > Radius- RetransCount?

Is CurrentRadiusServer

the Secondary?

Increment RadiusRetry- AfterFailureCounter

Set LastGoodServer to Primary, clear all counters except

RadiusRetryAfter-Failure, and start

RadiusRetryTimer

Is > RadiusRetrans- AfterFailureCount?

1179

01

Set Current-RadiusServer to Secondary


Set LastGood-RadiusServer to

Primary RadiusRetransInterval

timer



• Accounting Module Directives, page 15

• Accounting-Related SIP Server Core Directives, page 16.

Accounting Module DirectivesThe following directives are specific to the Cisco SPS accounting module. Reasonable default values are assigned when possible; however, it is advisable to carefully set and review the values of all these directives.

Note Complete details regarding viewing and editing Cisco SPS directives are beyond the scope of RADIUS Interface for Cisco SPS. Please refer to the Cisco SIP Proxy Server Administrator Guide for comprehensive configuration information. See the following URL: http://www.cisco.com/univercd/cc/td/doc/product/voice/sipproxy/admingd/index.htm

The following notes summarize how directives are used and how to choose appropriate values for each directive within the context of a RADIUS-based environment:

• Accounting—Turns on or off Cisco SPS accounting requests. Valid values are On and Off. When Off, no accounting requests are sent and all the subsequent directives are ignored. The default is Off. For accounting to work properly, this directive must be set to On.

• AccountingServerSide—Turns on or off server-side accounting requests for successful calls. Valid values are On and Off. The default is On.

• AccountingClientSide—Turns on or off client-side accounting requests for successful calls. Valid values are On and Off. The default is Off.

• AccountingUnsuccessful—Turns on or off accounting requests for unsuccessful calls. Valid values are On and Off.

When the flag is On, this directive is interpreted in conjunction with the AccountingServerSide and AccountingClientSide directives.

If the AccountingServerSide and this flag are both On, accounting requests are sent for server-side unsuccessful calls.

If the AccountingClientSide and this flag are both On, accounting records are sent for client-side unsuccessful calls.

When the flag is Off, no accounting requests are sent for unsuccessful calls, regardless of the setting for the AccountingServerSide or AccountingClientSide flags.

The default is Off.

• AccountingRecordFormat—Record format used for accounting. Currently, RADIUS is the only valid option.

• AccountingTimeFormat—Timestamps are in GMT format.

• PrimaryRadiusAcctIp—IP address or host name of the primary RADIUS server to be used for accounting. The default address is 127.0.0.1. For accounting to work properly, the address must be set to an IP address of a functioning RADIUS server.

• PrimaryRadiusAcctPort—Destination port number of the primary RADIUS server to be used for accounting. The well-known RADIUS server port for accounting is 1813. The default is 0. For accounting to work properly, set this directive to the port on which the primary RADIUS server is listening for Accounting-Request packets.


http://www.cisco.com/univercd/cc/td/doc/product/voice/sipproxy/admingd/index.htm


• PrimaryRadiusAcctSecret—Secret text string shared between Cisco SPS and the primary RADIUS accounting server. This is used to compute the Authenticator field of the Accounting-Request packets as described in the “Request Authenticator” section on page 8. For accounting to work properly, set this directive to the same value that is configured on the RADIUS server.

• SecondaryRadiusAcctIp—IP address or host name of the secondary RADIUS server to be used for accounting. The default is 127.0.0.1. For accounting to work properly, set this directive to IP address of a functioning RADIUS server.

• SecondaryRadiusAcctPort—Destination port number of the secondary RADIUS server to be used for accounting. The well known RADIUS server port for accounting is 1813. The default port value is 0. For accounting to work properly, set this directive to the port on which the secondary RADIUS server is listening for Accounting-Request packets.

• SecondaryRadiusAcctSecret—Secret text string shared between Cisco SPS and the secondary RADIUS accounting server. This text string is used to compute the Authenticator field of the Accounting-Request packets as described in “Request Authenticator” section on page 8. For accounting to work properly, set this directive to the same value that is configured on the RADIUS server.

• AcctIncludeSIPHeader—SIP header to be sent as a sip-hdr VSA (see Table 2) within RADIUS Accounting-Request packets. You can configure a maximum of 50 headers.

Accounting-Related SIP Server Core DirectivesThe following directives reside in the SIP server core module, but these directives affect the accounting operation of Cisco SPS. These directives are shared across the accounting, authentication, and preauthentication modules. Reasonable default values are assigned when possible; however, it is advisable to carefully set and review the values of all these directives.


The following notes summarize how directives are used and how to choose appropriate values for each within the context of a RADIUS-based environment:

• StatefulServer—Determines whether Cisco SPS is a transaction-stateful or transaction-stateless server. A transaction includes the following: received request, request or requests (if forked) forwarded downstream, responses received from downstream hosts, and best response returned upstream. Valid values are as follows:

– On (stateful)—Cisco SPS remembers incoming and outgoing requests, provides reliable retransmission of proxied requests, and returns the best final responses.

– Off (stateless)—Cisco SPS forgets all information once a request or response has been processed. Cisco SPS forwards requests and responses.

The default is On. If you change the value of this directive, you must restart the server. For accounting to work properly, set this directive to On. If Off, Accounting will still be performed, but not all the attributes are written in the individual accounting requests. The StatefulServer directive is assumed to be On for all subsequent configuration requirements described in RADIUS Interface for Cisco SPS.




• ServerType—Determines whether Cisco SPS functions as a proxy server or as a redirect server. A proxy server processes and routes SIP requests. A redirect server provides contact information by means of SIP redirect (3xx) responses. Valid values are Proxy and Redirect. The default is Proxy. For client-side accounting to work properly, set this directive to Proxy. If ServerType is set to Redirect, only server-side accounting is performed.

• OrigUserNameSource—Origin of the User Name attribute (see to Table 1 on page 9) in Accounting-Request packets. Valid values are From and Auth. If the value is From, the user part of the URL in the From SIP header is used to populate the User Name attribute. If the value is Auth, the user provided for authentication in the Authorization or Proxy-Authorization header is used instead. If no Proxy-Authorization header is present, the user is taken from the From header regardless of the setting of this directive. The default is Auth. A relevant configuration for this directive is one where all the IP phones authenticating themselves to Cisco SPS share a common user and password for authentication purposes. For example, Bob and Mary both work for Cisco and populate the From header with Bob and Mary respectively. However, they authenticate themselves to Cisco SPS by using a common username of cisco and a common password. The OrigUserNameSource provides to ability to choose whether to have Bob or Mary versus cisco as the User-Name in Accounting-Request packets.

• AddRecordRoute—Adds the Record-Route header to an initial SIP INVITE message. The Record-Route header field contains a globally reachable Request-URI that identifies the proxy server that added it. When a proxy server adds a Record-Route header in a SIP INVITE request, the proxy server is kept in the path of subsequent requests for the same call (such as re-INVITEs, ACK, BYE). Valid values are On (add) and Off (do not add). The default is Off. ServerType must be set to Proxy for this directive to apply. For accounting to work correctly, set this directive to On.

• RadiusRetransmissionInterval—Time (in milliseconds) between retransmissions to the RADIUS server. The default is 2000.

• RadiusRetransmissionCount—Number of times to retransmit the current RADIUS request before deciding that a given RADIUS server is unreachable and trying the other RADIUS server. The default is 2.

• RadiusRetransmissionAfterFailure—Number of times to try the entire procedure for sending a RADIUS request if all attempts to send the previous request failed. The default is 0.

• RadiusRetryTime—Time (in seconds) before retrying the primary RADIUS server if it is out of service, or before trying to send requests to any RADIUS server. The default is 300 (5 minutes).

Configuration TipsSome general accounting scenarios, and the corresponding configurations, are as follows:

• To only bill for completed calls, set AccountingServerSide On, and set AccountingClientSide and AccountingUnsuccessful Off.

• To bill for features, such as forking, turn AccountingClientSide On.

• To gather statistics, measure quality of service, or detect potential network problems, turn AccountingServerSide, AccountingClientSide, and AccountingUnsuccessful On.


RADIUS Accounting for Cisco SPSConfigurations Example and Call Flows with Debugging Enabled

Configurations Example and Call Flows with Debugging Enabled

The following sections illustrate various call scenarios and the associated SIP and RADIUS messaging for each scenario:

• Successful Call, Server-Side Accounting Enabled, page 18

• Unsuccessful Call, Server-Side Accounting Enabled, Unsuccessful Accounting Enabled, page 20

• Forked Call; Server- and Client-Side Accounting Enabled; Unsuccessful Accounting Enabled, page 21

The components involved in the scenarios are listed in Table 3:

Successful Call, Server-Side Accounting EnabledThis scenario illustrates a successful call between two registered users, Cisco 7961 and Cisco 7905, through their proxy Cisco SPS. In this scenarios, Cisco SPS has server-side accounting enabled for a single RADIUS server and sends Start and Stop records for the call to the RADIUS server. Table 4 provides a summary of the required modifications to the default directives (organized by relevant configuration option tab) to support this RADIUS-based scenario. Please refer to the “Cisco SPS Interface Reference Appendix” for screen examples showing configuration options for RADIUS-implementation related directives.

Table 3 Call-Scenario Components

Component Name IP Address Hostname

Cisco SIP Proxy Server Cisco SPS b.19.174.239 vvs-vitra

FreeRADIUS Server FreeRADIUS b.19.174.128 n/a

IP Phone (Cisco 7905) Cisco 7905 a.22.76.60 n/a


IP Phone (Cisco 7907) Cisco 7907 b.23.252.22 n/a


Table 4 Cisco SPS Directives Modifications for RADIUS-based Implementation for the Successful

Call Scenario

Cisco SPS Configuration Option Screen Cisco SPS Directive Default Value Modified Value

SIP Server Core Configuration AddRecordRoute Off On

Accounting Accounting Off On

Unsuccessful Off On

PrimaryRadiusServer Not set Set to IP, port, and secret of the Free RADIUS server


http://www.cisco.com/univercd/cc/td/doc/product/voice/sipproxy/radiusps/radspsui.htm



Call Flow

The call flow for this scenario as shown in Figure 4.

Figure 4 Basic Successful Call

The following list summarizes the call process outlined in Figure 4:

1. Cisco 7961 wants to call Cisco 7905. Cisco 7961 sends INVITE for Cisco 7905 to Cisco SPS.

2. Cisco SPS forwards the INVITE to Cisco 7905.

3. Cisco 7905 answers the call and returns 200.

4. Cisco SPS forwards 200 to Cisco 7961 and sends server side Start.

5. Cisco 7961 sends the ACK to Cisco SPS.

6. Cisco SPS forwards the ACK to Cisco 7905.

7. Cisco 7961 sends BYE to Cisco SPS.

8. Cisco SPS forwards the BYE to Cisco 7905.

9. Cisco SPS receives the 200 for the BYE from Cisco 7905.

Debugs and Logs StateMachine Off On

Radius Off On

LogLevel warn debug

Table 4 Cisco SPS Directives Modifications for RADIUS-based Implementation for the Successful

Call Scenario


1179

06

1

2

345

6

789

10

200BYE

ACK

200

INVITE

INVITE

Cisco 7961Server

side

Cisco SPSClientside Cisco 7905

200ACK

BYE

200



10. Cisco SPS forwards the 200 for the BYE to Cisco 7961 and sends server side successful Stop.

Note For complete listings of records, debug output and error logs related to the RADIUS interface Cisco SPS implementation, please refer to “RADIUS Interface for Cisco SPS Scenario Output Appendix”.

Unsuccessful Call, Server-Side Accounting Enabled, Unsuccessful Accounting Enabled

This scenario illustrates an unsuccessful call from a registered user (Cisco 7961) to an unregistered and unknown user (in this scenario named Cisco 7000) through the Cisco SPS (serving as a proxy for Cisco 7961). The Cisco SPS has server-side accounting enabled and sends a Stop record for the unsuccessful call attempt to the FreeRADIUS server.

Configuration

Cisco SPS is configured the same as described in the “Successful Call, Server-Side Accounting Enabled” section on page 18.


http://www.cisco.com/univercd/cc/td/doc/product/voice/sipproxy/radiusps/raderr.htm


Call Flow

Figure 5 illustrates an unsuccessful call flow.

Figure 5 Basic Unsuccessful Call

The process illustrated in Figure 5 is as follows:

1. Cisco 7961 wants to call (unregistered user) Cisco 7000. Cisco 7961 sends an INVITE for Cisco 7000 to Cisco SPS.

2. 7000 is not a registered user, so Cisco SPS returns 404 and sends server side unsuccessful Stop.


Forked Call; Server- and Client-Side Accounting Enabled; Unsuccessful Accounting Enabled

This scenario illustrates a successful call between two registered users, Cisco 7961 and Cisco 7905, through their proxy, Cisco SPS. Cisco 7905 is registered as both Cisco 7905 and Cisco 7906. Cisco 7906 does not respond, resulting in a 408 (time-out). Cisco 7905 responds with 486 (busy), resulting in Call Forward Busy to Cisco 7907. Cisco 7907 answers, resulting in a successful call.

Configuration

Cisco SPS is configured with server- and client-side accounting enabled to a single RADIUS server, as well as with call forward busy enabled for Cisco 7905 to Cisco 7907. Unsuccessful accounting is enabled as well. In order to facilitate the correlation of the various server- and client side Accounting-Request packets, Cisco SPS is configured to include the To, From, and CSeq SIP headers in the Accounting-Request packets. This is accomplished by modifying the default configuration with which Cisco SPS was first installed as described in this section. Table 5 provides a summary of the required modifications (organized by relevant configuration option tab or screen) to support this RADIUS-based scenario. Please refer to the “Cisco SPS Interface Reference Appendix” for screen examples illustrating configuration options for specifying RADIUS-implementation related options.

1179

07

1INVITE

2404

Cisco 7961Server

side

Cisco SPSClientside Cisco 7905





Call Flow

The call flow in Figure 6 is the same as the one shown in Figure 4, except that the endpoints have changed.

Table 5 Cisco SPS Modifications for RADIUS-based Implementation for Forked-Call Scenario


SIP Server Core Configuration AddRecordRoute Off On

Accounting Accounting Off On

Unsuccessful Off On

PrimaryRadiusServer Not set Set to IP, port, and secret of the Free RADIUS server

SIP Headers Not set Added from, to, CSeq

Call Forward Busy Off On

Diversion Header Name CC-Diversion Diversion (This is an optional change.)

Subscribers Not applicable Added a new subscriber, Cisco 7905, with call forward busy (CFB) to Cisco 7907

Debug and Logs State Machine Off On

Radius Off On

LogLevel warn debug



Figure 6 Forked Call-Flow77

The following process stages summarize the protocol illustrated in Figure 6.

1. Cisco 7961 wants to call Cisco 7905. Cisco 7961 sends INVITE for Cisco 7905 to Cisco SPS.

2. Cisco SPS forks the INVITE and INVITE is sent to Cisco 7905 (registration is implied).

3. Cisco SPS forks the INVITE and INVITE is sent to Cisco 7906 (registration is implied).

4. Cisco 7905 is busy and returns 486. Cisco SPS sends client side unsuccessful Stop.

5. Cisco 7905 has a Call Forward Busy contact set to Cisco 7907, so Cisco SPS forwards INVITE to Cisco 7907.

6. INVITE to Cisco 7906 times out. Cisco SPS generates internal 408 and sends client side unsuccessful Stop.

7. Cisco 7907 answers the call, returning 200. Cisco SPS sends client side Start.

8. Cisco SPS forwards 200 to Cisco 7961 and sends server side Start.

9. Cisco 7961 sends ACK.

10. Cisco SPS forwards the ACK to Cisco 7907.

11. Cisco 7961 sends BYE to Cisco SPS.

12. Cisco SPS forwards the BYE to Cisco 7907.

13. Cisco SPS receives the 200 for the BYE from Cisco 7907 and sends client side successful Stop.

14. Cisco SPS forwards the 200 for the BYE to Cisco 7961 and sends server side successful Stop.


1179

14

1

2345

6

789

1011

1213

14

200BYE

ACK

408-1

200-3

INVITE-3486-2

INVITE-2INVITE-1

INVITE

Cisco 7961Server

side

Cisco SPSClientside Cisco 7907 Cisco 7905 Cisco 7906

200-3ACK

BYE

200



RADIUS Authentication for Cisco SPS

You can configure Cisco SPS to send RADIUS Access-Request packets to a RADIUS server that correspond to the SIP REGISTER and SIP INVITE requests that the RADIUS server receives. Access-Request packets are as defined in RFC 2865, with the additional syntax and semantics defined in RADIUS Extension for Digest Authentication (Cisco Systems draft-sterman-aaa-sip-01.txt). Based on the responses received from the RADIUS server for the Access-Request packets, the SIP requests are either accepted or rejected by Cisco SPS.

The authentication scheme used by Cisco SPS may be either HTTP Digest or HTTP Basic, as defined in RFC 2617 and RFC 3261; however, the use of HTTP Basic as a SIP authentication mechanism has been deprecated by RFC 3261. Only HTTP Digest is described in this document. SIP messaging that is associated with the authentication occurs between Cisco SPS and the originator of the SIP request; but the actual validation of the user’s identification and password may occur at Cisco SPS or at a RADIUS server. The configuration which occurs at the RADIUS server is the only configuration within the scope of this document.

RADIUS Authentication for Cisco SPS OverviewCisco SPS can generate Access-Request packets for REGISTER and INVITE requests as a means of authenticating any request that has not yet passed the configured access-control mechanisms. The high-level diagram in Figure 7 shows a SIP REGISTER which is assumed to contain the user’s credentials from a SIP phone to Cisco SPS, as well as the corresponding RADIUS Access-Request packet sent by Cisco SPS to the RADIUS server. In this example, the RADIUS server queries an external database to retrieve the user’s password and validate the credentials. Further processing of the REGISTER by Cisco SPS is dependant on the response Cisco SPS receives from the RADIUS server.


RADIUS Authentication for Cisco SPSRADIUS Access-Request Format

Figure 7 Authentication Components

A user password is stored in the RADIUS server, or in some database that is accessible by the RADIUS server. The user identification, as found in the Authorization header (for REGISTER requests) or the Proxy-Authorization header (for INVITE requests), is passed as one of the attribute value pairs from the Cisco SPS to the RADIUS server in an Access-Request. You can configure Cisco SPS to add any SIP headers as VSAs in the authentication request to the RADIUS server.

The username can be expanded by Cisco SPS before being passed to the RADIUS server. This enables phone numbers to be expanded to fully expanded E.164 numbers before processing.

If the virtual proxy host feature is enabled, the username@domain (username found in the Authorization/Proxy-Authorization header and the domain name found in either the Authorization/Proxy-Authorization header if present, otherwise in the From header) can be passed as one of the attribute value pairs from Cisco SPS to the RADIUS server. This attribute value pair can then be used as the key for the user.

RADIUS Access-Request FormatThe following summary describes the format of the RADIUS data packet. The data fields defined in the format for the Access-Request packet are transmitted from left to right.


CodeThe Code field is one octet and identifies the type of RADIUS packet. RADIUS access codes (decimal) are assigned as follows:

1. Access-Request code (request sent by Cisco SPS)

IP

Cisco SPS

SIP

SIP domain

RADIUS/Authentication Domain

RADIUSaccess request

RADIUSserver

Passworddatabase

1179

15

IP

IP



2. Access-Accept code (returned by the RADIUS server if the SIP request is accepted)

3. Access-Reject code (returned by the RADIUS server if the SIP request is rejected)

Upon receipt of an Access-Request packet, the RADIUS server must transmit an Access-Accept or Access-Reject reply. If all Attribute values received in an Access-Request packet are acceptable then the RADIUS server must transmit a packet with the Code field set to 2 (Access-Accept). If any value of the received Attributes is not acceptable, then the RADIUS server must transmit a packet with the Code field set to 3 (Access-Reject).

IdentifierThe Identifier field is one octet and aids in matching requests and replies. The RADIUS server can detect a duplicate request if the server sees the same client source IP address and source UDP port and Identifier field within a short span of time. Cisco SPS changes the Identifier field whenever the content of the Attributes field change and whenever a valid reply has been received for a previous request. For retransmissions where the contents are identical, the Identifier field remains unchanged. Cisco SPS uses monotonically increasing identifiers that wrap around to 1 once they reach 254.

LengthThe Length field is two octets and indicates the length of the packet including the Code, Identifier, Length, Authenticator and Attribute fields. Octets outside the range of the Length field are treated as padding and ignored on reception. If a packet is shorter than the Length field indicates, the packet must be silently discarded. The minimum Length field value is 20 and maximum is 4095. If Cisco SPS is configured to include more headers than fit within the maximum length, the Access-Request packet is truncated.

AuthenticatorThe Authenticator field is 16 octets. The most significant octet is transmitted first. The Authenticator field value is used to authenticate the messages between the client and the RADIUS access server.


In Access-Request packets, the Authenticator value is a 16-octet random number, which is called the Request Authenticator. The value is unpredictable and unique over the lifetime of a shared secret between the Cisco SPS and the RADIUS server because repetition of a request value with the same secret permits an attacker to reply with a previously intercepted response. The shared secret is configured on Cisco SPS as described in the “Authentication Module Directives” section on page 30.


The Authenticator field in an Access-Accept and Access-Reject packet is called the Response Authenticator and contains a one-way MD5 hash that is calculated over a stream of octets, consisting of the RADIUS packet, beginning with the Code field, including the Identifier, the Length, the Request Authenticator field from the Access-Request packet, and the response Attributes, followed by the shared



secret. That is, ResponseAuth = MD5 (Code+ID+Length+RequestAuth+Attributes+Secret) where + denotes concatenation. The shared secret configured that is on the RADIUS server must match the one configured on Cisco SPS.

On reception of an Access-Accept, the Response Authenticator field must contain the correct response for the pending access request. Invalid packets are discarded by Cisco SPS, and an error is logged in the error_log file.

AttributesThe Attributes field is variable in length and contains a list of attributes. Attributes may have multiple instances. The end of the list of attributes is indicated by the Length field of the RADIUS packet. The following is a summary of the attribute format. The fields are transmitted from left to right.


Standard Attributes

The standard RADIUS attributes in RFC 2865 that are included in Access-Request packets from Cisco SPS are listed in Table 6. The Attribute column is for illustrative purposes only because it is not a field in the actual attributes included in the request. The Length field is in octets and is 1 (for the Type field) + 1 (for the Length field) + length of the Value field.

Table 6 Standard Attributes for Access-Request Packets

Attribute Type Length (octets) Value

User Name 1 3-254 User part of the URL in the “From” SIP header or user in “Proxy-Authorization” SIP header, if present. This value is controlled by a configuration directive (OrigUserNameSource).

If the RadiusUserNameAttrAddDomain directive is On, the domain in the “From” header will be appended to the User Name and the User Name attribute will be in the name@domain format.

The User Name can be expanded to a fully expanded E164 number. If the user name is taken from the “From” header, the expansion is dependent on the user type and the NumericUserNameInterpretation directive. If the user name is taken from the “Proxy-Authorization” header, the expansion is dependent on the NumExpandAuthUserName directive. The expansion is based on the number expansion rules, which are defined in the number expansion module.

Example: “5000”



NAS IP 4 6 IP address of Cisco SPS.

Example: a.22.76.1

Vendor-Specific 26 7-254 See Table 2 on page 10 for the complete set.


http://www.cisco.com/univercd/cc/td/doc/product/voice/sipproxy/radiusps/radacc.htm#wp1015272


Vendor-Specific Attributes

The following is a summary of the VSA format:

0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type | Length | Vendor-Id +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Vendor-Id (cont) | Vendor-Type | Vendor-Length| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Vendor-Data ... +-+-+-+-+-+-+-+-+-+-+-+-+-

The values of these fields for Accounting-Requests from Cisco SPS are:


• Length = 7 to 254 octets


• Vendor-Type, Vendor-Length, and Vendor-Data take various values as summarized in Table 2 on page 10.

The Attribute column is for illustrative purposes only because it is not a field in the actual attributes that are included in the request. The Vendor-Length field is in octets and is 1 (for the Vendor-Type field) + 1 (for the Vendor-Length field) + length of the Vendor-Data field. Table 7 presents the relevant Cisco VSA.

For additional details on all Cisco VSAs, see http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/vapp_dev/vsaig3.htm#27593.

NAS Port Type 61 6 5 stands for Virtual. Virtual refers to a connection by the client to Cisco SPS via a transport protocol. In this case, SIP is used, instead of a physical port.

Example: 5

Digest-Response 206 34 String that proves the user knows a password. The String field is 32 octets long and contains a hexadecimal representation of a 16 octet digest value that is received by Cisco SPS in the corresponding SIP request’s Authorization (REGISTER) or Proxy-Authorization (INVITE) header.

Example: “aafe4bf36a7b5887cdb9383f57887ee6”

Digest-Attributes 207 5-254 Contains subattributes that indicate the values contained in a Digest (Proxy) Authorization header together with other information that is necessary to calculate the correct digest-response value. The Digest-Attributes attribute is only used in Access-Request packets. There can be multiple Digest-Attributes attributes contained in one Access-Request packet. In this case the RADIUS server must interpret a concatenation of their values as if those values came in one attribute. For additional details see RADIUS Extension for Digest Authentication (Cisco Systems draft-sterman-aaa-sip-01.txt).


Attribute Type Length (octets) Value





RADIUS Authentication for Cisco SPSConfiguring RADIUS Authentication

Configuring RADIUS AuthenticationYou can configure Cisco SPS to send Access-Request packets to two RADIUS servers. For initial testing, it may be more convenient to set-up a single RADIUS server only; but in a production environment, using a pair of RADIUS servers for redundancy is strongly recommended.

Cisco SPS has multiple SIP message-handling processes (sipds); each process handles individual SIP messages. In the event the given SIP message is one that requires authentication, it is the responsibility of the sipd handling the message to send the corresponding Access-Request packet. The Access-Request packet is generated and sent prior to accepting the SIP request as a valid request, and if no response is received, the request will simply time-out. This means that SIP-request processing is dependent on RADIUS authentication.

The algorithm by which the sipd selects a RADIUS server to which to send the Access-Request packet is the same as for the Accounting-Request.

The values of the various retransmission timers and counters, as well as the configuration of the primary and the secondary RADIUS servers, are described in the “Authentication Module Directives” section on page 30 and in the “Authentication-Related SIP Server Core Directives” section on page 32.

Authentication Module DirectivesThe following directives are specific to the authentication module for Cisco SPS. Reasonable default values are assigned when possible; however, it is advisable to carefully set and review the values of all these directives. The mechanisms for viewing and editing these directives are described in Cisco SIP Proxy Server Administrator Guide. See the following URL:


The follow describes how each directive is used and how to choose appropriate values:

• Authentication—Specifies whether users must be authenticated before their transactions are processed. Valid values are On (authentication required) and Off (authentication not required). The default is Off. For authentication to occur, this directive must be set to On.

User authentication does not occur in the following case because access control is already satisfied:

– Access Control is set to On

– Host name or IP address of the sender is covered by a corresponding Allow from the directive

Table 7 Cisco VSAs for Access-Request Packets

AttributeVendor Type

Vendor Length (octets) Vendor Data

sip-hdr 1 Less than or equal to 247

An arbitrary SIP header found in the SIP request received by Cisco SPS (complete header line). Inclusion of any given header is controlled by a configuration directive AcctIncludeSIPHeader.

Example: “sip-hdr=CSeq: 101 INVITE”

Example: “sip-hdr=Via: SIP/2.0/UDP b.19.174.99:5060;branch=363e586d-e1529570-dad25df7-49a3df73-1,SIP/2.0/UDP a.22.76.38:5060;received=a.22.76.38”




– Satisfy directive is set to Any instead of All

For additional information on Access Control, see Cisco SIP Proxy Server Administrator Guide at the following location:


• AuthRealm—Realm used in authentication response headers. The default is CISCO.

• AuthServer—Server on which user authentication takes place. Valid values are Radius and Proxy. The default is Proxy. For Access-Request packets to be sent to the RADIUS server, this must be set to Radius.

• AuthScheme—Type of authentication method to be used when users are required to obtain authentication before receiving service from the Cisco SPS. Valid values are HTTP_Digest and HTTP_Basic. The default is HTTP_Digest. HTTP_Basic for use with SIP has been deprecated in RFC 3261, so HTTP_Digest is all that is covered in this document.

• AuthDigestQop—QOP value for digest authentication challenge. Indicates the quality of protection supported. Valid values are Auth (qop= “auth”, authentication only), Auth-Int (qop= “auth-int”, authentication and integrity), and Both (qop= “auth, auth-int”, allows the client to choose). The default is Auth.

The use of the value Both results in value “auth, auth-int” being sent in the challenge to the SIP client. The client then responds with either “auth” or “auth-int”, and this is the value included in the QOP subattribute of the Digest-Attributes attribute.

• AuthDigestAlgorithm—Value of the algorithm value to be included in a Digest Challenge to the user. This value is used in Authentication Response headers. Valid values are MD5 (algorithm=”MD5”) and MD5-sess (algorithm=”MD5-sess”). The default is MD5.

• AuthConsumeProxyAuth—Enables Cisco SPS to consume the Proxy-Authorization header before the request is forwarded downstream to the next hop. Valid values are On (consume header) and Off (pass header downstream). The default is On.

• AuthAllow3rdPartyRegistration—Allows unauthorized redirection of calls by a third-party registration. If the value of this directive is set to Off, the username in the To header is matched with the username in the From or Authorization header. If the user names in these two headers do not match, registration is rejected. If the value is On, third-party registrations are allowed. This is independent of the authentication scheme. The default is Off.

• AuthAllow3rdPartyInvite—Allows third-party INVITEs. Valid values are On (user in the From header can differ from user used for authentication) and Off (user in the From header must match user used for authentication). The default is On.

• RadiusAuthSkew—Time (in seconds) for which a nonce included by Cisco SPS in a digest challenge is valid. The default is 30.

• PrimaryRadiusAuthIp—IP address or host name of the primary RADIUS server to be used for authentication. By default it is set to 127.0.0.1. For authentication to work properly, this value must be set to the IP address of a functioning RADIUS server.

• PrimaryRadiusAuthPort—Destination port number of the primary RADIUS server to be used for authentication. The well known RADIUS server port for authentication is 1812. By default it is set to 0. For authentication to work properly, this value must be set to the port on which the primary RADIUS server is listening for Access-Request packets.

• PrimaryRadiusAuthSecret—Secret text string shared between Cisco SPS and the primary RADIUS authentication server. This attribute is used to compute the Authenticator field of the Access-Request packets as described in the “Response Authenticator” section on page 27. For authentication to work properly, this value must be set to the same value configured on the RADIUS server.




• SecondaryRadiusAuthIp—IP address or host name of the secondary RADIUS server to be used for authentication. By default it is set to 127.0.0.1. For authentication to work properly, this value must be set to IP address of a functioning RADIUS server.

• SecondaryRadiusAuthPort—Destination port number of the secondary RADIUS server to be used for authentication. The well known RADIUS server port for authentication is 1812. By default it is set to 0. For authentication to work properly, this value must be set to the port on which the secondary RADIUS server is listening for Access-Request packets.

• SecondaryRadiusAuthSecret—Secret text string shared between Cisco SPS and the secondary RADIUS authentication server. This is used to compute the Authenticator field of the Access-Request packets as described in the“Response Authenticator” section on page 27. For authentication to work properly, this value must be set to the same value configured on the RADIUS server.

• AuthIncludeSIPHeader—SIP header to be sent as a sip-hdr VSA (see Table 7 on page 30) within RADIUS Access-Request packets. You can configure a maximum of 50 headers.

Authentication-Related SIP Server Core DirectivesThe following directives reside in the SIP Server Core module, but they affect the authentication operation of Cisco SPS. These directives are shared across the accounting, authentication, and pre-authentication modules. Reasonable default values are assigned when possible; however, it is advisable to carefully set and/or review the values of all these directives.


The following notes summarize how directives are used and how to choose appropriate values for each within the context of a RADIUS-based environment:

• StatefulServer—Determines whether Cisco SPS is a transaction-stateful or transaction-stateless server. A transaction includes the following: received request, request or requests (if forked) forwarded downstream, responses received from downstream hosts, and best response returned upstream. Valid values are as follows:



• OrigUserNameSource—Origin of the User Name attribute (see Table 6 on page 28) in Accounting-Request packets. Valid values are From and Auth. If the value is From, the user part of the URL in the From SIP header is used to populate the User Name attribute. If the value is Auth, the user provided for authentication in the Authorization or Proxy-Authorization header is used instead. If no Proxy-Authorization header is present, the user is taken from the From header regardless of the setting of this directive. The default is Auth. A relevant configuration for this directive is one where all the IP phones authenticating themselves to Cisco SPS share a common user and password for authentication purposes. For example, Bob and Mary both work for Cisco and populate the From header with Bob and Mary respectively. However, they authenticate themselves



RADIUS Authentication for Cisco SPSConfiguration Example and Call Flows with Debugging Enabled

to Cisco SPS by using a common username of cisco and a common password. The OrigUserNameSource provides to ability to choose whether to have Bob or Mary versus cisco as the User-Name in Accounting-Request packets.


• RadiusRetransmissionCount—Number of times to retransmit the current RADIUS request before deciding that a given RADIUS server is unreachable and trying the other RADIUS server. The default is 2.

• RadiusRetransmissionAfterFailure—Number of times to try the entire procedure for sending a RADIUS request if all attempts to send the previous request failed. The default is 0.

• RadiusRetryTime—Time (in seconds) before retrying the primary RADIUS server if it is out of service, or before trying to send requests to any RADIUS server. The default is 300 (5 minutes).

Configuration Example and Call Flows with Debugging EnabledThe following sections illustrate various call scenarios and the associated SIP and RADIUS messaging for each scenario:

• REGISTER-Accepted Scenario, page 33

• REGISTER Rejected Scenario, page 35

• INVITE-Accepted Scenario, page 36

• INVITE Rejected, page 37

The components involved in the scenarios are listed in Table 8:

REGISTER-Accepted ScenarioIn this scenario, Cisco 7905 is registering with Cisco SPS. The credentials provided by Cisco 7905 match those at the RADIUS server, so the registration is accepted.

Configuring the REGISTER-Accepted Scenario

Cisco SPS is configured with authentication via RADIUS enabled for a single RADIUS server. This is accomplished by modifying the default configuration with which Cisco SPS was initially installed. Table 9 provides a summary of the required modifications to the default configuration. Please refer to the “Cisco SPS Interface Reference Appendix” for screen examples showing configuration options for RADIUS-implementation.

Table 8 Call-Scenario Components

Component Name IP Address Hostname


FreeRADIUS Server FreeRADIUS b.19.174.128 n/a






Table 9 Cisco SPS Directives Modifications for RADIUS-based Implementation for the

REGISTER-Accepted Scenario


Authentication Authentication Off On

AuthenticationServer Proxy Radius

PrimaryRadiusServer Not Set Set IP address, port, and secret of FreeRADIUS server

SecondaryRadiusServer Not Set Set IP address, port, and secret of FreeRADIUS server

In the scenario presented, this could have been left with the default values, but instead the same values were used as for the primary server.

AuthSIPHeaders Not Set For this scenario, From, Proxy-Authorization, and Authorization were added.

The addition of these values are optional and was done for illustrative purposes.

According to the RADIUS Extension for Digest Authentication, these headers are legal but will be ignored by the RADIUS server.

Debugs and Logs StateMachine Off On

Radius Off On

Authentication Off On

LogLevel warn debug



Call Flow

The call flow is shown in Figure 8.

Figure 8 REGISTER Accepted


REGISTER Rejected ScenarioIn this example, Cisco 7905 is registering with Cisco SPS. The credentials provided by Cisco 7905 do not match those at the RADIUS server, so the registration is rejected.

Configuring the REGISTER-Rejected Scenario

Same as the“Configuring the REGISTER-Accepted Scenario” section on page 33.

Call Flow


1179

19

REGISTER

401

ACK

REGISTERwith propercredentials

Access requestwith propercredentials

Access-accept200

SIP RADIUS

IP

Cisco SPSCisco 7905RADIUSserver

IP




Figure 9 REGISTER Rejected


INVITE-Accepted ScenarioIn this example, Cisco 7963 is calling Cisco 7905 through Cisco SPS. The credentials provided by Cisco 7963 match those at the FreeRADIUS server, so the INVITE is accepted and the call succeeds.

Configuring the INVITE-Accepted Scenario

Same as the “Configuring the REGISTER-Accepted Scenario” section on page 33.

Call Flow


1179

20

REGISTER

401

ACK

REGISTERwith propercredentials

Access requestwith wrongcredentials

Access-reject200

ACK

SIP RADIUS

IP

Cisco SPSCisco 7905RADIUSserver

IP




Figure 10 INVITE Accepted


INVITE RejectedIn this example, Cisco 7905 is calling Cisco 7963 through Cisco SPS. The credentials provided by Cisco 7905 do not match those at the FreeRADIUS server, so the INVITE is rejected.

Configuration

Same as the“Configuring the REGISTER-Accepted Scenario” section on page 33.

Call Flow


1179

21

INVITE

407

ACK

INVITEwith propercredentials


Access-accept

200

INVITE180200

ACKACK

SIP RADIUS

IP

Cisco SPSCisco 7963

RADIUSserver

IP

Cisco 7905

IP




Figure 11 INVITE Rejected


1179

22

INVITE

407

ACK

INVITEwith propercredentials


Access-reject407

ACK

SIP RADIUS

IP

Cisco SPSCisco 7905

RADIUSserver

IP

Cisco 7963

IP



RADIUS Preauthentication for Cisco SPS

Preauthentication is a process in which Cisco SPS sends a preauthentication query in the form of an Access-Request packet to a Resource Policy Management System (RPMS) to check policy limits of the matching customer. If RPMS determines that the customer limits will not be exceeded on accepting this call, RPMS sends an Access-Accept response to Cisco SPS. On the other hand, if RPMS detects that accepting this call violates the policy agreement, RPMS sends an Access-Reject response to Cisco SPS.

RADIUS Preauthentication for Cisco SPS OverviewYou can configure Cisco SPS to send RADIUS Access-Request packets that correspond to SIP INVITE requests that are received from a configurable set of previous-hop devices. RPMS maps the previous-hop IP address to a entity with a specified service-level agreements (SLA). The SIP INVITE is either accepted or rejected by Cisco SPS based on the response it receives from RPMS. This allows Cisco SPS to be used to offload downstream gateways by proactively rejecting calls that would ultimately fail due to SLAs being exceeded. These calls are then redirected without expending gateway resources. The high-level diagram in Figure 12 shows a SIP INVITE from a previous hop for which preauthentication is required by Cisco SPS, as well as by the corresponding RADIUS Access-Request packet sent by Cisco SPS to RPMS. Forwarding the INVITE to the appropriate downstream gateway or proxy by Cisco SPS depends on the response Cisco SPS receives from RPMS.

Figure 12 Preauthentication Components

Preauthentication, when enabled, is performed on INVITEs before any user authentication is performed by Cisco SPS. RPMS appears as a standard RADIUS server to Cisco SPS. All preauthentication Access-Request packets go to RPMS, but all user authentication Access-Request packets and

Cisco SPS

Upstreamgateway or proxy

Downstreamgateway or proxy

SIP INVITE

RADIUS/Preauthentication Domain

RADIUSaccess request

RPMS

1179

24

VV

IP


RADIUS Preauthentication for Cisco SPSRADIUS Access-Request Format

Accounting records are sent to the configured authentication and accounting RADIUS servers as if preauthentication were not enabled. If the preauthentication query fails (Accept-Reject message received from RPMS), Cisco SPS sends a 480 response back upstream. If it succeeds (Accept-Accept message received from RPMS), Cisco SPS proceeds with normal processing and eventually forwards the INVITE to the appropriate next hop.

RADIUS Access-Request FormatA summary of the RADIUS data format, as defined in RFC 2865 and RADIUS Extension for Digest Authentication follows. The fields are transmitted from left to right.


CodeThe Code field is one octet and identifies the type of RADIUS packet. RADIUS access codes (decimal) are assigned as follows:

1. Access-Request code (request sent by Cisco SPS)

2. Access-Accept code (returned by RADIUS server if SIP request should be accepted)

3. Access-Reject code (returned by RADIUS server if SIP request should be rejected)

Upon receipt of an Access-Request packet, the RADIUS server must transmit an Access-Accept or Access-Reject reply. If all attribute values received in an Access-Request packet are acceptable, then the RADIUS server must transmit a packet with the Code field set to 2 (Access-Accept). If any value of the received Attributes is not acceptable, then the RADIUS server must transmit a packet with the Code field set to 3 (Access-Reject).

IdentifierThe Identifier field is one octet and aids in matching requests and replies. The RADIUS server can detect a duplicate request if it has the same client source IP address and source UDP port and Identifier field value within a short span of time. Cisco SPS changes the Identifier field whenever the content of the Attributes field change, and whenever a valid reply has been received for a previous request. For retransmissions where the contents are identical, the Identifier field value remains unchanged. Cisco SPS uses monotonically increasing identifiers that wrap around to 1 once they reach 254.



LengthThe Length field is two octets and indicates the length of the packet including the Code, Identifier, Length, Authenticator, and Attribute fields. Octets outside the range of the Length field are treated as padding and ignored on reception. If a packet is shorter than the Length field indicates, it must be silently discarded. The minimum value for the Length field is 20 and maximum value is 4095. If Cisco SPS is configured to include more headers than fit within the maximum length, the Access-Request packet is truncated.

AuthenticatorThe Authenticator field is sixteen (16) octets. The most significant octet is transmitted first. The Authenticator value is used to authenticate the messages between the client and the RADIUS access server.


In Access-Request packets, the Authenticator value is a 16 octet random number, called the Request Autheticator. The value is unpredictable and unique over the lifetime of aa shared secret between Cisco SPS and the RADIUS server because repetition of a request value with the same secret permits an attacker to reply with a previously intercepted response. The shared secret is configured on Cisco SPS as described in the “Authentication Module Directives” section on page 30.


The Authenticator field in an Access-Accept and Access-Reject packet is called the Response Authenticator and contains a one-way MD5 hash calculated over a stream of octets, consisting of the RADIUS packet that begins with the Code field, including the Identifier, the Length, the Request Authenticator field from the Access-Request packet, and the response Attributes, followed by the shared secret. That is, ResponseAuth = MD5 (Code+ID+Length+RequestAuth+Attributes+Secret) where + denotes concatenation. The shared secret that is configured on the RADIUS server must match the one that is configured on Cisco SPS.

On reception of an Access-Accept packet, the Response Authenticator field must contain the correct response for the pending Access-Request packet. Invalid packets are discarded by Cisco SPS and an error is logged in the error_log file.

AttributesThe Attributes field is variable in length and contains a list of attributes. Attributes may have multiple instances. The end of the list of attributes is indicated by the Length field of the RADIUS packet. The following is a summary of the Attribute field format. The fields are transmitted from left to right.



http://www.cisco.com/univercd/cc/td/doc/product/voice/sipproxy/radiusps/radauth.htm#wp1007702


Standard Attributes

The standard RADIUS attributes in RFC 2865 included in Access-Request packets from Cisco SPS are listed in Table 10. The Attribute column is for illustrative purposes only because it is not a field in the actual attributes that are included in the request. The Length field is in octets and is 1 (for the Type field) + 1 (for the Length field) + length of the Value field.

Vendor Specific Attributes

A summary of the VSA format is as follows:

0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type | Length | Vendor-Id


Attribute TypeLength(octets) Value

User Name 1 3-254 User part of the URL in the “From” SIP header or user in “Proxy-Authorization” SIP header, if present. This is controlled by a configuration directive (OrigUserNameSource).

If the RadiusUserNameAttrAddDomain directive is On, the domain in the “From” header is appended to the User Name attribute and the User Name attribute is in the name@domain format.

The UserName can be expanded to a fully expanded E164 number. If the user name is taken from the “From” header, the expansion is dependent on the user type and the NumericUserNameInterpretation directive. If the User Name is taken from the “Proxy-Authorization” header, the expansion is dependent on the NumExpandAuthUserName directive. Expansion is based on the number expansion rules which are defined in the number expansion module.

Example: “5000”



Service-Type 6 6 Cisco SPS always sets it to 10 (Call-Check), indicating to RPMS that this is a preauthentication request.

Example: “10”

Vendor-Specific 26 7-254 See Table 2 on page 10 for the complete set.

Called-Station-ID 30 3-254 “To” SIP header value of the request.

Example: “<sip:[email protected]>”

Acct-Session-ID 44 3-254 “Call-Id” SIP header value of the request.




RADIUS Preauthentication for Cisco SPSConfiguring RADIUS Preauthentication

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Vendor-Id (cont) | Vendor-Type | Vendor-Length| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Vendor-Data ... +-+-+-+-+-+-+-+-+-+-+-+-+-

The values of these fields for Accounting-Request packets from Cisco SPS are:


• Length = 7-254 octets


• Vendor-Type, Vendor-Length, and Vendor-Data take various values as summarized in Table 2 on page 10.

The Attribute column is for illustrative purposes only because it is not a field in the actual attributes that are included in the request. The Vendor-Length field is in octets and is 1 (for the Vendor-Type field) + 1 (for the Vendor-Length field) + length of the Vendor-Data field. For additional details on all Cisco VSAs, see http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/vapp_dev/vsaig3.htm#27593.

Configuring RADIUS PreauthenticationYou can configure Cisco SPS to send preauthentication Access-Request packets to 10 RPMS servers. For initial testing, it may be more convenient to set-up a single RPMS server only; but, in a production environment, using at least two RPMS servers for redundancy is strongly recommended.

Cisco SPS has multiple SIP message-handling processes (sipds); each process handles individual SIP messages. In the event the given INVITE is one that requires preauthentication, it is the responsibility of the sipd handling the INVITE to send the corresponding Access-Request packet. The Access-Request packet is generated and sent prior to accepting the INVITE as a valid request. In the event no response is received from any RPMS server, Cisco SPS processes the INVITE as if an Access-Accept had been received. The algorithm by which the sipd selects a RADIUS server to which to send the Access-Request packet is shown in Figure 13.

Table 11 Cisco VSAs for Access-Request Packets

AttributeVendor Type

Vendor-Length(octets) Vendor Data

prev-hop-ip 1 Less than or equal to 247

Previous hop IP address as seen by the proxy.

Example: “prev-hop-ip=a.22.76.38:5060”

resource-service 1 Less than or equal to 247

Set to query to indicate that this is a preauthentication query (from a proxy), rather than an actual preauthentication request (from a gateway). There are no resources reserved as the result of a query.

Example: “resource-service=query”

call-id 1 Less than or equal to 247

“Call-ID” SIP header value.







Figure 13 RPMS Request State Machine

No

Yes

No

Yes

No

Response

Yes

Wait

No

Yes

New request

Waitreceived

IgNore

RadiusRetryTimer expires

Clear RadiusRetry-AfterFail

Is RadiusRetryAfter-FailureCounter >

RadiusRetryAfter-Failure

Set CurrentRadiusServer to LastGoodRadiusServer

Send request to CurrentRadiusServer and start


Set LastGoodServer to CurrentRadiusServer, clear all counters, stop all timers except RadiusRetryTimer

Increment RadiusRetransCounter

RadiusRetransTimerexpires

Is > Radius- RetransCount?

Have all RPMS servers been tried?

Increment RadiusRetry- AfterFailureCounter

Set LastGoodServer to first server, clear all

counters except RadiusRetryAfter-Failure, and start

RadiusRetryTimer

Is > RadiusRetrans- AfterFailureCount?

1179

25

Set Current-RadiusServer to next server


Set LastGood-RadiusServer to first

server RadiusRetransInterval

timer



The values of the various retransmission timers and counters, as well as the configuration of the RPMS servers, are described in “RPMS Module Directives” section on page 45 and in “Preauthentication-Related SIP Server Core Directives” section on page 45.

RPMS Module DirectivesThe following directives are specific to the RPMS module for Cisco SPS. Reasonable default values are assigned when possible; however, it is advisable to carefully set and review the values of all these directives. The mechanisms for viewing and editing these directives are described in the Cisco SIP Proxy Server Administrator Guide. The following notes provide additional descriptions of how the directives are used and how to choose appropriate values for each directive:

• PreAuthorization—Preauthorizes new INVITE requests. Valid values are On and Off. Default is Off. For preauthentication to occur, the value must be On.

• PreAuthRequestType—Preauthentication request type. The only valid value with this release is Query.

• RPMS_ServerIpPortSecret—List of RPMS IP addresses, port numbers, and secrets (passwords) for up to 10 servers. By default, none are specified. Values for at least one RPMS must be added for preauthentication to work properly.

• PreAuthPreviousHop—IP address, hostname, or domain for up to 100 different hops, or the keyword ALL. The format of an entry is the same as that for an access list entry. For for information, see the Cisco SIP Proxy Server Administrator Guide. By default, the list is empty. For preauthentication to occur, at least one PreAuthPreviousHop must be defined.

Preauthentication-Related SIP Server Core DirectivesThe following directives reside in the SIP server core module, but these directives affect the authentication operation of Cisco SPS. These directives are shared across the accounting, authentication, and preauthentication modules. Reasonable default values are assigned when possible; however, it is advisable to carefully set and/or review the values of all these directives. The mechanisms for viewing and editing these directives are described in the Cisco SIP Proxy Server Administrator Guide. Additional descriptions of how the directives are used and how to choose appropriate values for each of them follow:

• StatefulServer—Determines whether Cisco SPS is a transaction-stateful or transaction-stateless server. A transaction includes received request, request or requests (if forked) forwarded downstream, responses received from downstream hosts, and best response returned upstream. Valid values are:



The default is On. If you change the value of this directive, you must restart the server. For preauthentication to work properly, this directive must be set to On.


• RadiusRetransmissionCount—Number of times to retransmit the current RADIUS request before deciding that a given RADIUS server is unreachable and trying the other RADIUS server. Default is 2.






RADIUS Preauthentication for Cisco SPSConfiguration Example and Call Flows with Debugging Enabled

• RadiusRetransmissionAfterFailure—Number of retransmission attempts to send the RADIUS request if all attempts to send the previous request failed. The default is 0.

• RadiusRetryTime—Time (in seconds) before retrying the first RPMS server if the server is out of service, or before trying to send a request to any RPMS server. The default is 300 (5 minutes).

Configuration Example and Call Flows with Debugging EnabledThe following sections illustrate various call scenarios and the associated SIP and RADIUS messaging for each scenario:

• INVITE-Accepted Scenario, page 46

• INVITE-Rejected Scenario, page 48

The components involved in the scenarios are listed in Table 12.

INVITE-Accepted ScenarioIn this example, Cisco 7963 calls a Cisco 7905 through Cisco SPS. The IP address of Cisco 7963 corresponds to the customer for whom the SLAs have not been exceeded. The INVITE is accepted, and the call succeeds.

Configuring the INVITE-Accepted Scenario

Cisco SPS is configured with preauthentication enabled for a single RPMS server. This is accomplished by modifying the default configuration with which Cisco SPS was initially installed. Table 13 provides a summary of the required modifications to the default configuration. Please refer to the “Cisco SPS Interface Reference Appendix” for screen examples showing configuration options for RADIUS-implementation.

Table 12 Call Scenario Components

Component Names IP Address Hostname


FreeRadius RADIUS Server FreeRADIUS b.19.174.128 n/a







Call Flow

The call flow is as shown in Figure 14.

Figure 14 INVITE-Accepted Call Flow

Table 13 Cisco SPS Directives Modifications for RADIUS-based Implementation for the

INVITE-Accepted Scenario


RPMS Preauthentication Off On

ServerIpPortSecret Not Set Added a row with the IP address, port, and secret of the RPMS server.

PreviousHop Not Set Added a row with all, specifying preauthentication should be done for INVITEs from all IP addresses.

Debug and Logs StateMachine Off On

Radius Off On

RPMS Off On

LogLevel warn debug

1179

28

INVITE

INVITE

180

200

ACK

200

ACK

Access request

Access accept

SIP RADIUS

IP

Cisco SPSCisco 7963

RPMSserver

IP

Cisco 7905

IP



RADIUS Debugging File

FreeRADIUS server does not support preauthentication. There is no example for this case.

Cisco SPS error_log File

FreeRADIUS server does not support preauthentication. There is no example for this case.

INVITE-Rejected ScenarioIn this example, Cisco 7963 is calling Cisco 7905 through Cisco SPS. The IP address of Cisco 7963 corresponds to the customer for which the SLAs have been exceeded, so the INVITE is rejected.

Configuration

Same as the “Configuring the INVITE-Accepted Scenario” section on page 46.

Call Flow


Figure 15 INVITE Rejected

1179

29

INVITE

480

ACK

Access request

Access reject

SIP RADIUS

IP

Cisco SPSCisco 7963

RPMSserver

IP

Cisco 7905

IP


Cisco SPS Interface Reference Appendix

The following figures illustrate examples of Cisco SPS screens used for modifying RADIUS-related configuration options as described in RADIUS Interface for Cisco SPS.

These are organized to align with the chapters of this publication:

• Accounting Configuration Screens, page 50

• Authentication Configuration Screens, page 56

• Preauthentication Configuration Screens, page 59

Note The values provided in these example screen displays are for illustrative purposes.


Cisco SPS Interface Reference AppendixAccounting Configuration Screens

Accounting Configuration ScreensFigure 16 SIP Server Core Configuration (1 of 2)



Figure 17 SIP Server Core Configuration (2 of 2)



Figure 18 Accounting



Figure 19 Debug and Logs



Figure 20 Call Forward



Figure 21 Subscribers


Cisco SPS Interface Reference AppendixAuthentication Configuration Screens

Authentication Configuration ScreensFigure 22 Authentication (1 of 2)



Figure 23 Authentication (2 of 2)


Cisco SPS Interface Reference AppendixPreauthentication Configuration Screens

Preauthentication Configuration ScreensFigure 25 RPMS


Cisco SPS Interface Reference AppendixPreauthentication Configuration Screens



RADIUS Interface for Cisco SPS Scenario Output Appendix

This appendix provides start and stop, debug, and error log listings relevant to the accounting, authentication, and preauthentication scenarios presented in RADIUS Interface for Cisco SPS.

The following output examples are divided between the three main chapters:

• RADIUS Accounting Message Listings, page 62

• RADIUS Authentication Message Listings, page 129

• RADIUS Preauthentication Message Listings, page 154


RADIUS Interface for Cisco SPS Scenario Output AppendixRADIUS Accounting Message Listings

RADIUS Accounting Message ListingsThe following output examples are organized by scenario:

• Successful Call, Server-Side Accounting Enabled, page 62

• Unsuccessful Call, Server-Side Accounting Enabled, Unsuccessful Accounting Enabled, page 77

• Forked Call; Server- and Client-Side Accounting Enabled; Unsuccessful Accounting Enabled, page 84

Successful Call, Server-Side Accounting Enabled

RADIUS Start and Stop Records

The following are accounting records from a FreeRADIUS server with default accounting configuration:

Mon Oct 13 14:11:41 2003NAS-IP-Address = b.19.174.239NAS-Port-Type = VirtualUser-Name = “7961”Service-Type = Login-UserAcct-Status-Type = StartAcct-Session-Id = “[email protected]”Called-Station-Id = “<sip:7905@vvs-vitra>”Calling-Station-Id = ““(vvs-vitra)7961” <sip:7961@vvs-vitra>;tag=003094c450f000033ee9695f-7653f7b6”h323-setup-time = “h323-setup-time=21:17:07.687 GMT Mon Oct 13 2003"h323-connect-time = “h323-connect-time=21:17:09.788 GMT Mon Oct 13 2003"h323-call-origin = "h323-call-origin=answer"h323-call-type = "h323-call-type=VoIP"Cisco-AVPair = "sip-status-code=200"Cisco-AVPair = "session-protocol=sip"Cisco-AVPair = "[email protected]"Cisco-AVPair = "method=INVITE"Cisco-AVPair = "prev-hop-via=SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248"Cisco-AVPair = "prev-hop-ip=a.22.77.248:5060"Cisco-AVPair = "incoming-req-uri=sip:7905@vvs-vitra"Cisco-AVPair = "outgoing-req-uri=sip:[email protected]:5060;user=phone;transport=udp"Cisco-AVPair = "next-hop-ip=a.22.76.60:5060"Client-IP-Address = b.19.174.239Acct-Unique-Session-Id = "e9b70bb607c440e3"Timestamp = 1066079501

Mon Oct 13 14:11:46 2003NAS-IP-Address = b.19.174.239NAS-Port-Type = VirtualUser-Name = "7961"Service-Type = Login-UserAcct-Status-Type = StopAcct-Session-Id = "[email protected]"Called-Station-Id = "<sip:7905@vvs-vitra>;tag=4134181333"Calling-Station-Id = ""(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f000033ee9695f-7653f7b6"h323-disconnect-time = "h323-disconnect-time=21:17:14.33 GMT Mon Oct 13 2003"h323-call-origin = "h323-call-origin=answer"h323-call-type = "h323-call-type=VoIP"Cisco-AVPair = "sip-status-code=200"Cisco-AVPair = "session-protocol=sip"Cisco-AVPair = "[email protected]"



Cisco-AVPair = "method=BYE"Cisco-AVPair = "prev-hop-via=SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248"Cisco-AVPair = "prev-hop-ip=a.22.77.248:5060"Cisco-AVPair = "incoming-req-uri=sip:7905@vvs-vitra:5060"Cisco-AVPair = "outgoing-req-uri=sip:[email protected]:5060;user=phone"Cisco-AVPair = "next-hop-ip=a.22.76.60:5060"Client-IP-Address = b.19.174.239Acct-Unique-Session-Id = "e9b70bb607c440e3"Timestamp = 1066079506

RADIUS Debugging file

The following debug output is from a FreeRADIUS server with default accounting configuration:

Listening on IP address b.19.174.128, ports 1812/udp and 1813/udp, with proxy on 1814/udp.Ready to process requests.rad_recv: Accounting-Request packet from host b.19.174.239:35361, id=1, length=775 NAS-IP-Address = b.19.174.239 NAS-Port-Type = Virtual User-Name = "7961" Service-Type = Login-User Acct-Status-Type = Start Acct-Session-Id = "[email protected]" Called-Station-Id = "<sip:7905@vvs-vitra>" Calling-Station-Id = ""(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f000033ee9695f-7653f7b6" h323-setup-time = "h323-setup-time=21:17:07.687 GMT Mon Oct 13 2003" h323-connect-time = "h323-connect-time=21:17:09.788 GMT Mon Oct 13 2003" h323-call-origin = "h323-call-origin=answer" h323-call-type = "h323-call-type=VoIP" Cisco-AVPair = "sip-status-code=200" Cisco-AVPair = "session-protocol=sip" Cisco-AVPair = "[email protected]" Cisco-AVPair = "method=INVITE" Cisco-AVPair = "prev-hop-via=SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248" Cisco-AVPair = "prev-hop-ip=a.22.77.248:5060" Cisco-AVPair = "incoming-req-uri=sip:7905@vvs-vitra" Cisco-AVPair = "outgoing-req-uri=sip:[email protected]:5060;user=phone;transport=udp" Cisco-AVPair = "next-hop-ip=a.22.76.60:5060"modcall: entering group preacct modcall[preacct]: module "preprocess" returns noop rlm_realm: No '@' in User-Name = "7961", looking up realm NULL rlm_realm: No such realm "NULL" modcall[preacct]: module "suffix" returns noop acct_users: Matched DEFAULT at 7 modcall[preacct]: module "files" returns okmodcall: group preacct returns okmodcall: entering group accountingrlm_acct_unique: WARNING: Attribute NAS-Port-Id was not found in request, unique ID MAY be inconsistentrlm_acct_unique: Hashing ',Client-IP-Address = b.19.174.239,NAS-IP-Address = b.19.174.239,Acct-Session-Id = "[email protected]",User-Name = "7961"'rlm_acct_unique: Acct-Unique-Session-ID = "e9b70bb607c440e3". modcall[accounting]: module "acct_unique" returns okradius_xlat: '/usr/local/var/log/radius/radacct/b.19.174.239/detail-20031013'rlm_detail: /usr/local/var/log/radius/radacct/%{Client-IP-Address}/detail-%Y%m%d expands to /usr/local/var/log/radius/radacct/b.19.174.239/detail-20031013 modcall[accounting]: module "detail" returns ok modcall[accounting]: module "unix" returns noopradius_xlat: '/usr/local/var/log/radius/radutmp'radius_xlat: '7961'



rlm_radutmp: No NAS-Port seen. Cannot do anything. rlm_radumtp: WARNING: checkrad will probably not work! modcall[accounting]: module "radutmp" returns noopmodcall: group accounting returns okradius_xlat: '/path/to/exec/acct/start'Exec-Program: /path/to/exec/acct/startSending Accounting-Response of id 1 to b.19.174.239:35361Finished request 0Going to the next request--- Walking the entire request list ---Cleaning up request 0 ID 1 with timestamp 3f8b150dNothing to do. Sleeping until we see a request.--- Walking the entire request list ---Nothing to do. Sleeping until we see a request.rad_recv: Accounting-Request packet from host b.19.174.239:35356, id=2, length=724 NAS-IP-Address = b.19.174.239 NAS-Port-Type = Virtual User-Name = "7961" Service-Type = Login-User Acct-Status-Type = Stop Acct-Session-Id = "[email protected]" Called-Station-Id = "<sip:7905@vvs-vitra>;tag=4134181333" Calling-Station-Id = ""(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f000033ee9695f-7653f7b6" h323-disconnect-time = "h323-disconnect-time=21:17:14.33 GMT Mon Oct 13 2003" h323-call-origin = "h323-call-origin=answer" h323-call-type = "h323-call-type=VoIP" Cisco-AVPair = "sip-status-code=200" Cisco-AVPair = "session-protocol=sip" Cisco-AVPair = "[email protected]" Cisco-AVPair = "method=BYE" Cisco-AVPair = "prev-hop-via=SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248" Cisco-AVPair = "prev-hop-ip=a.22.77.248:5060" Cisco-AVPair = "incoming-req-uri=sip:7905@vvs-vitra:5060" Cisco-AVPair = "outgoing-req-uri=sip:[email protected]:5060;user=phone" Cisco-AVPair = "next-hop-ip=a.22.76.60:5060"modcall: entering group preacct modcall[preacct]: module "preprocess" returns noop rlm_realm: No '@' in User-Name = "7961", looking up realm NULL rlm_realm: No such realm "NULL" modcall[preacct]: module "suffix" returns noop acct_users: Matched DEFAULT at 10 modcall[preacct]: module "files" returns okmodcall: group preacct returns okmodcall: entering group accountingrlm_acct_unique: WARNING: Attribute NAS-Port-Id was not found in request, unique ID MAY be inconsistentrlm_acct_unique: Hashing ',Client-IP-Address = b.19.174.239,NAS-IP-Address = b.19.174.239,Acct-Session-Id = "[email protected]",User-Name = "7961"'rlm_acct_unique: Acct-Unique-Session-ID = "e9b70bb607c440e3". modcall[accounting]: module "acct_unique" returns okradius_xlat: '/usr/local/var/log/radius/radacct/b.19.174.239/detail-20031013'rlm_detail: /usr/local/var/log/radius/radacct/%{Client-IP-Address}/detail-%Y%m%d expands to /usr/local/var/log/radius/radacct/b.19.174.239/detail-20031013 modcall[accounting]: module "detail" returns ok modcall[accounting]: module "unix" returns noopradius_xlat: '/usr/local/var/log/radius/radutmp'radius_xlat: '7961' rlm_radutmp: No NAS-Port seen. Cannot do anything. rlm_radumtp: WARNING: checkrad will probably not work! modcall[accounting]: module "radutmp" returns noopmodcall: group accounting returns okradius_xlat: '/path/to/exec/acct/stop'



Exec-Program: /path/to/exec/acct/stopSending Accounting-Response of id 2 to b.19.174.239:35356Finished request 1Going to the next request--- Walking the entire request list ---Cleaning up request 1 ID 2 with timestamp 3f8b1512Nothing to do. Sleeping until we see a request.

Cisco SPS error_log file

[Mon Oct 13 21:17:07 2003] sip_protocol.c(5393) Received 657 bytes UDP packet from a.22.77.248:50432 INVITE sip:7905@vvs-vitra SIP/2.0Via: SIP/2.0/UDP a.22.77.248:5060From: "(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f000033ee9695f-7653f7b6To: <sip:7905@vvs-vitra>Call-ID: [email protected]: 101 INVITEUser-Agent: CSCO/4Contact: <sip:[email protected]:5060>Expires: 180Content-Type: application/sdpContent-Length: 247Accept: application/sdp

v=0o=Cisco-SIPUA 13140 11398 IN IP4 a.22.77.248s=SIP Callc=IN IP4 a.22.77.248t=0 0m=audio 31856 RTP/AVP 0 8 18 101a=rtpmap:0 PCMU/8000a=rtpmap:8 PCMA/8000a=rtpmap:18 G729/8000a=rtpmap:101 telephone-event/8000a=fmtp:101 0-15

[Mon Oct 13 21:17:07 2003] sip_sm.c(998) Sent 286 bytes UDP packet to a.22.77.248:5060 SIP/2.0 100 TryingVia: SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248Call-ID: [email protected]: "(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f000033ee9695f-7653f7b6To: <sip:7905@vvs-vitra>CSeq: 101 INVITEContent-Length: 0

[Mon Oct 13 21:17:07 2003] mod_sip_acct.c(630) Accounting event type: INVITE received from upstream, subtype: none

[Mon Oct 13 21:17:07 2003] sip_sm.c(828) TCB_PROXIED_STATE_TIMER : 180 seconds.[Mon Oct 13 21:17:07 2003] sip_sm.c(2057) Translation yielded 1 URLs :<sip:[email protected]:5060;user=phone;transport=udp>[Mon Oct 13 21:17:07 2003] sip_dns.c(787) "A" Query for a.22.76.60 successful, Got 1 IP addresses[Mon Oct 13 21:17:07 2003] sip_dns.c(136) A Record : a.22.76.60[Mon Oct 13 21:17:07 2003] sip_sm.c(998) Sent 893 bytes UDP packet to a.22.76.60:5060 INVITE sip:[email protected]:5060;user=phone;transport=udp SIP/2.0Via: SIP/2.0/UDP b.19.174.239:5060;branch=e330f109-4cc4e882-ab239539-e8b2e93-1



Record-Route: <sip:[email protected]:5060;maddr=b.19.174.239>Via: SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248From: "(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f000033ee9695f-7653f7b6To: <sip:7905@vvs-vitra>Call-ID: [email protected]: 101 INVITEUser-Agent: CSCO/4Contact: <sip:[email protected]:5060>Expires: 180Content-Type: application/sdpContent-Length: 247Accept: application/sdp


[Mon Oct 13 21:17:07 2003] mod_sip_acct.c(424) client side accounting disabled[Mon Oct 13 21:17:07 2003] sip_protocol.c(5393) Received 485 bytes UDP packet from a.22.76.60:5060 SIP/2.0 100 TryingVia: SIP/2.0/UDP b.19.174.239:5060;branch=e330f109-4cc4e882-ab239539-e8b2e93-1Via: SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248From: "(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f000033ee9695f-7653f7b6To: <sip:7905@vvs-vitra>;tag=4134181333Call-ID: [email protected]: 101 INVITEServer: Cisco-CP7905/1.01-030512AAllow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTERContent-Length: 0

[Mon Oct 13 21:17:07 2003] sip_sm.c(4820) Found existing TCB 0xf680b698[Mon Oct 13 21:17:07 2003] sip_protocol.c(5393) Received 486 bytes UDP packet from a.22.76.60:5060 SIP/2.0 180 RingingVia: SIP/2.0/UDP b.19.174.239:5060;branch=e330f109-4cc4e882-ab239539-e8b2e93-1Via: SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248From: "(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f000033ee9695f-7653f7b6To: <sip:7905@vvs-vitra>;tag=4134181333Call-ID: [email protected]: 101 INVITEServer: Cisco-CP7905/1.01-030512AAllow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTERContent-Length: 0

[Mon Oct 13 21:17:07 2003] sip_sm.c(4820) Found existing TCB 0xf680b698[Mon Oct 13 21:17:07 2003] sip_sm.c(998) Sent 406 bytes UDP packet to a.22.77.248:5060 SIP/2.0 180 Ringing Via: SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248From: "(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f000033ee9695f-7653f7b6



To: <sip:7905@vvs-vitra>;tag=4134181333Call-ID: [email protected]: 101 INVITEServer: Cisco-CP7905/1.01-030512AAllow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTERContent-Length: 0

[Mon Oct 13 21:17:09 2003] sip_protocol.c(5393) Received 878 bytes UDP packet from a.22.76.60:5060 SIP/2.0 200 OKVia: SIP/2.0/UDP b.19.174.239:5060;branch=e330f109-4cc4e882-ab239539-e8b2e93-1Via: SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248Record-Route: <sip:[email protected]:5060;maddr=b.19.174.239>From: "(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f000033ee9695f-7653f7b6To: <sip:7905@vvs-vitra>;tag=4134181333Call-ID: [email protected]: 101 INVITEContact: <sip:[email protected]:5060;user=phone;transport=udp>Server: Cisco-CP7905/1.01-030512AAllow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTERContent-Length: 201Content-Type: application/sdp

v=0o=7905 31664 31664 IN IP4 a.22.76.60s=Cisco 7905 SIP Callc=IN IP4 a.22.76.60t=0 0m=audio 16384 RTP/AVP 0 101a=rtpmap:0 PCMU/8000/1a=rtpmap:101 telephone-event/8000a=fmtp:101 0-15

[Mon Oct 13 21:17:09 2003] sip_sm.c(4820) Found existing TCB 0xf680b698[Mon Oct 13 21:17:09 2003] mod_sip_acct.c(424) client side accounting disabled[Mon Oct 13 21:17:09 2003] sip_sm.c(998) Sent 760 bytes UDP packet to a.22.77.248:5060 SIP/2.0 200 OK Via: SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248Record-Route: <sip:7905@vvs-vitra:5060;maddr=b.19.174.239>From: "(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f000033ee9695f-7653f7b6To: <sip:7905@vvs-vitra>;tag=4134181333Call-ID: [email protected]: 101 INVITEContact: <sip:[email protected]:5060;user=phone;transport=udp>Server: Cisco-CP7905/1.01-030512AAllow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTERContent-Length: 201Content-Type: application/sdp




[Mon Oct 13 21:17:09 2003] mod_sip_acct.c(630) Accounting event type: 200 to INVITE sent upstream, subtype: response received from downstream

[Mon Oct 13 21:17:09 2003] sip_radius.c(675) Building attr - NAS-IP-Address b.19.174.239

[Mon Oct 13 21:17:09 2003] [debug] sip_radius.c(806): Attr built as 4 () 4 - NAS-IP-Address 6 bytes

[Mon Oct 13 21:17:09 2003] [debug] sip_radius.c(594): 04 06 ac 13 ae ef [Mon Oct 13 21:17:09 2003] sip_radius.c(675) Building attr - NAS-Port-Type 5

[Mon Oct 13 21:17:09 2003] [debug] sip_radius.c(806): Attr built as 61 () 2 - NAS-Port-Type 6 bytes

[Mon Oct 13 21:17:09 2003] [debug] sip_radius.c(594): 3d 06 00 00 00 05 [Mon Oct 13 21:17:09 2003] sip_radius.c(675) Building attr - User-Name 7961

[Mon Oct 13 21:17:09 2003] [debug] sip_radius.c(806): Attr built as 1 () 1 - User-Name 6 bytes

[Mon Oct 13 21:17:09 2003] [debug] sip_radius.c(594): 01 06 37 39 36 31 [Mon Oct 13 21:17:09 2003] sip_radius.c(675) Building attr - Service-Type 1

[Mon Oct 13 21:17:09 2003] [debug] sip_radius.c(806): Attr built as 6 () 2 - Service-Type 6 bytes

[Mon Oct 13 21:17:09 2003] [debug] sip_radius.c(594): 06 06 00 00 00 01 [Mon Oct 13 21:17:09 2003] sip_radius.c(675) Building attr - Acct-Status-Type 1

[Mon Oct 13 21:17:09 2003] [debug] sip_radius.c(806): Attr built as 40 () 2 - Acct-Status-Type 6 bytes

[Mon Oct 13 21:17:09 2003] [debug] sip_radius.c(594): 28 06 00 00 00 01 [Mon Oct 13 21:17:09 2003] sip_radius.c(675) Building attr - Acct-Session-Id [email protected]

[Mon Oct 13 21:17:09 2003] [debug] sip_radius.c(806): Attr built as 44 () 1 - Acct-Session-Id 50 bytes

[Mon Oct 13 21:17:09 2003] [debug] sip_radius.c(594): 2c 32 30 30 33 30 39 34 63 34 2d 35 30 66 30 30 30 32 32 2d 34 36 33 33 39 62 64 35 2d 34 61 66 31 36 66 34 64 40 31 30 2e 32 32 2e 37 37 2e 32 34 38 [Mon Oct 13 21:17:09 2003] sip_radius.c(675) Building attr - Called-Station-Id <sip:7905@vvs-vitra>

[Mon Oct 13 21:17:09 2003] [debug] sip_radius.c(806): Attr built as 30 () 1 - Called-Station-Id 22 bytes

[Mon Oct 13 21:17:09 2003] [debug] sip_radius.c(594): 1e 16 3c 73 69 70 3a 37 39 30 35 40 76 76 73 2d 76 69 74 72 61 3e [Mon Oct 13 21:17:09 2003] sip_radius.c(675) Building attr - Calling-Station-Id "(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f000033ee9695f-7653f7b6

[Mon Oct 13 21:17:09 2003] [debug] sip_radius.c(806): Attr built as 31 () 1 - Calling-Station-Id 78 bytes



[Mon Oct 13 21:17:09 2003] [debug] sip_radius.c(594): 1f 4e 22 28 76 76 73 2d 76 69 74 72 61 29 37 39 36 31 22 20 3c 73 69 70 3a 37 39 36 31 40 76 76 73 2d 76 69 74 72 61 3e 3b 74 61 67 3d 30 30 33 30 39 34 63 34 35 30 66 30 30 30 30 33 33 65 65 39 36 39 35 66 2d 37 36 35 33 66 37 62 36 [Mon Oct 13 21:17:09 2003] sip_radius.c(675) Building attr - h323-setup-time= 21:17:07.687 GMT Mon Oct 13 2003

[Mon Oct 13 21:17:09 2003] [debug] sip_radius.c(806): Attr built as 25 (VSA) 11 - h323-setup-time= 56 bytes

[Mon Oct 13 21:17:09 2003] [debug] sip_radius.c(594): 1a 38 00 00 00 09 19 32 68 33 32 33 2d 73 65 74 75 70 2d 74 69 6d 65 3d 32 31 3a 31 37 3a 30 37 2e 36 38 37 20 47 4d 54 20 4d 6f 6e 20 4f 63 74 20 31 33 20 32 30 30 33 [Mon Oct 13 21:17:09 2003] sip_radius.c(675) Building attr - h323-connect-time= 21:17:09.788 GMT Mon Oct 13 2003

[Mon Oct 13 21:17:09 2003] [debug] sip_radius.c(806): Attr built as 28 (VSA) 11 - h323-connect-time= 58 bytes

[Mon Oct 13 21:17:09 2003] [debug] sip_radius.c(594): 1a 3a 00 00 00 09 1c 34 68 33 32 33 2d 63 6f 6e 6e 65 63 74 2d 74 69 6d 65 3d 32 31 3a 31 37 3a 30 39 2e 37 38 38 20 47 4d 54 20 4d 6f 6e 20 4f 63 74 20 31 33 20 32 30 30 33 [Mon Oct 13 21:17:09 2003] sip_radius.c(675) Building attr - h323-call-origin= answer

[Mon Oct 13 21:17:09 2003] [debug] sip_radius.c(806): Attr built as 26 (VSA) 11 - h323-call-origin= 31 bytes

[Mon Oct 13 21:17:09 2003] [debug] sip_radius.c(594): 1a 1f 00 00 00 09 1a 19 68 33 32 33 2d 63 61 6c 6c 2d 6f 72 69 67 69 6e 3d 61 6e 73 77 65 72 [Mon Oct 13 21:17:09 2003] sip_radius.c(675) Building attr - h323-call-type= VoIP

[Mon Oct 13 21:17:09 2003] [debug] sip_radius.c(806): Attr built as 27 (VSA) 11 - h323-call-type= 27 bytes

[Mon Oct 13 21:17:09 2003] [debug] sip_radius.c(594): 1a 1b 00 00 00 09 1b 15 68 33 32 33 2d 63 61 6c 6c 2d 74 79 70 65 3d 56 6f 49 50 [Mon Oct 13 21:17:09 2003] sip_radius.c(675) Building attr - sip-status-code= 200

[Mon Oct 13 21:17:09 2003] [debug] sip_radius.c(806): Attr built as 1 (VSA) 11 - sip-status-code= 27 bytes

[Mon Oct 13 21:17:09 2003] [debug] sip_radius.c(594): 1a 1b 00 00 00 09 01 15 73 69 70 2d 73 74 61 74 75 73 2d 63 6f 64 65 3d 32 30 30 [Mon Oct 13 21:17:09 2003] sip_radius.c(675) Building attr - session-protocol= sip

[Mon Oct 13 21:17:09 2003] [debug] sip_radius.c(806): Attr built as 1 (VSA) 11 - session-protocol= 28 bytes

[Mon Oct 13 21:17:09 2003] [debug] sip_radius.c(594): 1a 1c 00 00 00 09 01 16 73 65 73 73 69 6f 6e 2d 70 72 6f 74 6f 63 6f 6c 3d 73 69 70 [Mon Oct 13 21:17:09 2003] sip_radius.c(675) Building attr - call-id= [email protected]



[Mon Oct 13 21:17:09 2003] [debug] sip_radius.c(806): Attr built as 1 (VSA) 11 - call-id= 64 bytes

[Mon Oct 13 21:17:09 2003] [debug] sip_radius.c(594): 1a 40 00 00 00 09 01 3a 63 61 6c 6c 2d 69 64 3d 30 30 33 30 39 34 63 34 2d 35 30 66 30 30 30 32 32 2d 34 36 33 33 39 62 64 35 2d 34 61 66 31 36 66 34 64 40 31 30 2e 32 32 2e 37 37 2e 32 34 38

[Mon Oct 13 21:17:09 2003] sip_radius.c(675) Building attr - method= INVITE

[Mon Oct 13 21:17:09 2003] [debug] sip_radius.c(806): Attr built as 1 (VSA) 11 - method= 21 bytes

[Mon Oct 13 21:17:09 2003] [debug] sip_radius.c(594): 1a 15 00 00 00 09 01 0f 6d 65 74 68 6f 64 3d 49 4e 56 49 54 45 [Mon Oct 13 21:17:09 2003] sip_radius.c(675) Building attr - prev-hop-via= SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248

[Mon Oct 13 21:17:09 2003] [debug] sip_radius.c(806): Attr built as 1 (VSA) 11 - prev-hop-via= 72 bytes

[Mon Oct 13 21:17:09 2003] [debug] sip_radius.c(594): 1a 48 00 00 00 09 01 42 70 72 65 76 2d 68 6f 70 2d 76 69 61 3d 53 49 50 2f 32 2e 30 2f 55 44 50 20 31 30 2e 32 32 2e 37 37 2e 32 34 38 3a 35 30 36 30 3b 72 65 63 65 69 76 65 64 3d 31 30 2e 32 32 2e 37 37 2e 32 34 38 [Mon Oct 13 21:17:09 2003] sip_radius.c(675) Building attr - prev-hop-ip= a.22.77.248:5060

[Mon Oct 13 21:17:09 2003] [debug] sip_radius.c(806): Attr built as 1 (VSA) 11 - prev-hop-ip= 37 bytes

[Mon Oct 13 21:17:09 2003] [debug] sip_radius.c(594): 1a 25 00 00 00 09 01 1f 70 72 65 76 2d 68 6f 70 2d 69 70 3d 31 30 2e 32 32 2e 37 37 2e 32 34 38 3a 35 30 36 30 [Mon Oct 13 21:17:09 2003] sip_radius.c(675) Building attr - incoming-req-uri= sip:7905@vvs-vitra

[Mon Oct 13 21:17:09 2003] [debug] sip_radius.c(806): Attr built as 1 (VSA) 11 - incoming-req-uri= 43 bytes

[Mon Oct 13 21:17:09 2003] [debug] sip_radius.c(594): 1a 2b 00 00 00 09 01 25 69 6e 63 6f 6d 69 6e 67 2d 72 65 71 2d 75 72 69 3d 73 69 70 3a 37 39 30 35 40 76 76 73 2d 76 69 74 72 61 [Mon Oct 13 21:17:09 2003] sip_radius.c(675) Building attr - outgoing-req-uri= sip:[email protected]:5060;user=phone;transport=udp

[Mon Oct 13 21:17:09 2003] [debug] sip_radius.c(806): Attr built as 1 (VSA) 11 - outgoing-req-uri= 75 bytes

[Mon Oct 13 21:17:09 2003] [debug] sip_radius.c(594): 1a 4b 00 00 00 09 01 45 6f 75 74 67 6f 69 6e 67 2d 72 65 71 2d 75 72 69 3d 73 69 70 3a 37 39 30 35 40 31 30 2e 32 32 2e 37 36 2e 36 30 3a 35 30 36 30 3b 75 73 65 72 3d 70 68 6f 6e 65 3b 74 72 61 6e 73 70 6f 72 74 3d 75 64 70 [Mon Oct 13 21:17:09 2003] sip_radius.c(675) Building attr - next-hop-ip= a.22.76.60:5060

[Mon Oct 13 21:17:09 2003] [debug] sip_radius.c(806): Attr built as 1 (VSA) 11 - next-hop-ip= 36 bytes



[Mon Oct 13 21:17:09 2003] [debug] sip_radius.c(594): 1a 24 00 00 00 09 01 1e 6e 65 78 74 2d 68 6f 70 2d 69 70 3d 31 30 2e 32 32 2e 37 36 2e 36 30 3a 35 30 36 30 [Mon Oct 13 21:17:09 2003] sip_radius.c(1115) Radius: max number of servers to use is 2.[Mon Oct 13 21:17:09 2003] sip_radius.c(1120) Radius: Start with server 1.[Mon Oct 13 21:17:09 2003] sip_radius.c(852) Radius: The RA is:[Mon Oct 13 21:17:09 2003] [debug] sip_radius.c(594): a6 d0 87 1d 5f aa 30 e6 a4 a4 10 cf 3f 5b a4 e1

[Mon Oct 13 21:17:09 2003] sip_radius.c(1222) Radius: To send 775 bytes in request to b.19.174.128:1813.[Mon Oct 13 21:17:09 2003] [debug] sip_radius.c(594): 04 01 03 07 a6 d0 87 1d 5f aa 30 e6 a4 a4 10 cf 3f 5b a4 e1 04 06 ac 13 ae ef 3d 06 00 00 00 05 01 06 37 39 36 31 06 06 00 00 00 01 28 06 00 00 00 01 2c 32 30 30 33 30 39 34 63 34 2d 35 30 66 30 30 30 32 32 2d 34 36 33 33 39 62 64 35 2d 34 61 66 31 36 66 34 64 40 31 30 2e 32 32 2e 37 37 2e 32 34 38 1e 16 3c 73 69 70 3a 37 39 30 35 40 76 76 73 2d 76 69 74 72 61 3e 1f 4e 22 28 76 76 73 2d 76 69 74 72 61 29 37 39 36 31 22 20 3c 73 69 70 3a 37 39 36 31 40 76 76 73 2d 76 69 74 72 61 3e 3b 74 61 67 3d 30 30 33 30 39 34 63 34 35 30 66 30 30 30 30 33 33 65 65 39 36 39 35 66 2d 37 36 35 33 66 37 62 36 1a 38 00 00 00 09 19 32 68 33 32 33 2d 73 65 74 75 70 2d 74 69 6d 65 3d 32 31 3a 31 37 3a 30 37 2e 36 38 37 20 47 4d 54 20 4d 6f 6e 20 4f 63 74 20 31 33 20 32 30 30 33 1a 3a 00 00 00 09 1c 34 68 33 32 33 2d 63 6f 6e 6e 65 63 74 2d 74 69 6d 65 3d 32 31 3a 31 37 3a 30 39 2e 37 38 38 20 47 4d 54 20 4d 6f 6e 20 4f 63 74 20 31 33 20 32 30 30 33 1a 1f 00 00 00 09 1a 19 68 33 32 33 2d 63 61 6c 6c 2d 6f 72 69 67 69 6e 3d 61 6e 73 77 65 72 1a 1b 00 00 00 09 1b 15 68 33 32 33 2d 63 61 6c 6c 2d 74 79 70 65 3d 56 6f 49 50 1a 1b 00 00 00 09 01 15 73 69 70 2d 73 74 61 74 75 73 2d 63 6f 64 65 3d 32 30 30 1a 1c 00 00 00 09 01 16 73 65 73 73 69 6f 6e 2d 70 72 6f 74 6f 63 6f 6c 3d 73 69 70 1a 40 00 00 00 09 01 3a 63 61 6c 6c 2d 69 64 3d 30 30 33 30 39 34 63 34 2d 35 30 66 30 30 30 32 32 2d 34 36 33 33 39 62 64 35 2d 34 61 66 31 36 66 34 64 40 31 30 2e 32 32 2e 37 37 2e 32 34 38 1a 15 00 00 00 09 01 0f 6d 65 74 68 6f 64 3d 49 4e 56 49 54 45 1a 48 00 00 00 09 01 42 70 72 65 76 2d 68 6f 70 2d 76 69 61 3d 53 49 50 2f 32 2e 30 2f 55 44 50 20 31 30 2e 32 32 2e 37 37 2e 32 34 38 3a 35 30 36 30 3b 72 65 63 65 69 76 65 64 3d 31 30 2e 32 32 2e 37 37 2e 32 34 38 1a 25 00 00 00 09 01 1f 70 72 65 76 2d 68 6f 70 2d 69 70 3d 31 30 2e 32 32 2e 37 37 2e 32 34 38 3a 35 30 36 30 1a 2b 00 00 00 09 01 25 69 6e 63 6f 6d 69 6e 67 2d 72 65 71 2d 75 72 69 3d 73 69 70 3a 37 39 30 35 40 76 76 73 2d 76 69 74 72 61 1a 4b 00 00 00 09 01 45 6f 75 74 67 6f 69 6e 67 2d 72 65 71 2d 75 72 69 3d 73 69 70 3a 37 39 30 35 40 31 30 2e 32 32 2e 37 36 2e 36 30 3a 35 30 36 30 3b 75 73 65 72 3d 70 68 6f 6e 65 3b 74 72 61 6e 73 70 6f 72 74 3d 75 64 70 1a 24 00 00 00 09 01 1e 6e 65 78 74 2d 68 6f 70 2d 69 70 3d 31 30 2e 32 32 2e 37 36 2e 36 30 3a 35 30 36 30



[Mon Oct 13 21:17:09 2003] sip_radius.c(1300) Radius: read 20 bytes in response from b.19.174.128:1813.[Mon Oct 13 21:17:09 2003] [debug] sip_radius.c(594): 05 01 00 14 fb 6e 5e 7a ef dc bd 5d f4 19 1e 59 c3 dd fe 3e [Mon Oct 13 21:17:09 2003] sip_radius.c(1410) Radius: server 1 responded with Accept. Mark it for next time use.[Mon Oct 13 21:17:09 2003] sip_protocol.c(5393) Received 360 bytes UDP packet from a.22.77.248:50432 ACK sip:7905@vvs-vitra:5060 SIP/2.0Via: SIP/2.0/UDP a.22.77.248:5060From: "(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f000033ee9695f-7653f7b6To: <sip:7905@vvs-vitra>;tag=4134181333Call-ID: [email protected]: 101 ACKUser-Agent: CSCO/4Route: <sip:[email protected]:5060;user=phone>Content-Length: 0

[Mon Oct 13 21:17:09 2003] sip_sm.c(3952) Found existing TCB 0xf680b698[Mon Oct 13 21:17:09 2003] sip_dns.c(787) "A" Query for a.22.76.60 successful, Got 1 IP addresses[Mon Oct 13 21:17:09 2003] sip_dns.c(136) A Record : a.22.76.60[Mon Oct 13 21:17:09 2003] sip_sm.c(998) Sent 503 bytes UDP packet to a.22.76.60:5060 ACK sip:[email protected]:5060;user=phone SIP/2.0Via: SIP/2.0/UDP b.19.174.239:5060;branch=e330f109-4cc4e882-ab239539-e8b2e93Record-Route: <sip:7905.e330f109-4cc4e882-ab239539-e8b2e93@vvs-vitra:5060;maddr=b.19.174.239>Via: SIP/2.0/UDP a.22.77.248:5060From: "(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f000033ee9695f-7653f7b6To: <sip:7905@vvs-vitra>;tag=4134181333Call-ID: [email protected]: 101 ACKUser-Agent: CSCO/4Content-Length: 0

[Mon Oct 13 21:17:14 2003] sip_protocol.c(5393) Received 360 bytes UDP packet from a.22.77.248:50432 BYE sip:7905@vvs-vitra:5060 SIP/2.0Via: SIP/2.0/UDP a.22.77.248:5060From: "(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f000033ee9695f-7653f7b6To: <sip:7905@vvs-vitra>;tag=4134181333Call-ID: [email protected]: 102 BYEUser-Agent: CSCO/4Content-Length: 0Route: <sip:[email protected]:5060;user=phone>

[Mon Oct 13 21:17:14 2003] sip_sm.c(998) Sent 298 bytes UDP packet to a.22.77.248:5060 SIP/2.0 100 TryingVia: SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248Call-ID: [email protected]: "(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f000033ee9695f-7653f7b6To: <sip:7905@vvs-vitra>;tag=4134181333CSeq: 102 BYEContent-Length: 0



[Mon Oct 13 21:17:14 2003] mod_sip_acct.c(630) Accounting event type: BYE received from upstream, subtype: none

[Mon Oct 13 21:17:14 2003] sip_dns.c(787) "A" Query for a.22.76.60 successful, Got 1 IP addresses[Mon Oct 13 21:17:14 2003] sip_dns.c(136) A Record : a.22.76.60[Mon Oct 13 21:17:14 2003] sip_sm.c(998) Sent 430 bytes UDP packet to a.22.76.60:5060 BYE sip:[email protected]:5060;user=phone SIP/2.0Via: SIP/2.0/UDP b.19.174.239:5060;branch=4800fdff-b455bb2-3d29e94a-e910bb79-1Via: SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248From: "(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f000033ee9695f-7653f7b6To: <sip:7905@vvs-vitra>;tag=4134181333Call-ID: [email protected]: 102 BYEUser-Agent: CSCO/4Content-Length: 0

[Mon Oct 13 21:17:14 2003] mod_sip_acct.c(424) client side accounting disabled[Mon Oct 13 21:17:14 2003] sip_protocol.c(5393) Received 478 bytes UDP packet from a.22.76.60:5060 SIP/2.0 200 OKVia: SIP/2.0/UDP b.19.174.239:5060;branch=4800fdff-b455bb2-3d29e94a-e910bb79-1Via: SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248From: "(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f000033ee9695f-7653f7b6To: <sip:7905@vvs-vitra>;tag=4134181333Call-ID: [email protected]: 102 BYEServer: Cisco-CP7905/1.01-030512AAllow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTERContent-Length: 0

[Mon Oct 13 21:17:14 2003] sip_sm.c(4820) Found existing TCB 0xf680c5d0[Mon Oct 13 21:17:14 2003] mod_sip_acct.c(424) client side accounting disabled[Mon Oct 13 21:17:14 2003] sip_sm.c(998) Sent 398 bytes UDP packet to a.22.77.248:5060 SIP/2.0 200 OK Via: SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248From: "(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f000033ee9695f-7653f7b6To: <sip:7905@vvs-vitra>;tag=4134181333Call-ID: [email protected]: 102 BYEServer: Cisco-CP7905/1.01-030512AAllow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTERContent-Length: 0

[Mon Oct 13 21:17:14 2003] mod_sip_acct.c(630) Accounting event type: response to BYE sent upstream, subtype: response received from downstream















[Mon Oct 13 21:17:14 2003] [debug] sip_radius.c(594): 2c 32 30 30 33 30 39 34 63 34 2d 35 30 66 30 30 30 32 32 2d 34 36 33 33 39 62 64 35 2d 34 61 66 31 36 66 34 64 40 31 30 2e 32 32 2e 37 37 2e 32 34 38 [Mon Oct 13 21:17:14 2003] sip_radius.c(675) Building attr - Called-Station-Id <sip:7905@vvs-vitra>;tag=4134181333


[Mon Oct 13 21:17:14 2003] [debug] sip_radius.c(594): 1e 25 3c 73 69 70 3a 37 39 30 35 40 76 76 73 2d 76 69 74 72 61 3e 3b 74 61 67 3d 34 31 33 34 31 38 31 33 33 33 [Mon Oct 13 21:17:14 2003] sip_radius.c(675) Building attr - Calling-Station-Id "(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f000033ee9695f-7653f7b6


[Mon Oct 13 21:17:14 2003] [debug] sip_radius.c(594): 1f 4e 22 28 76 76 73 2d 76 69 74 72 61 29 37 39 36 31 22 20 3c 73 69 70 3a 37 39 36 31 40 76 76 73 2d 76 69 74 72 61 3e 3b 74 61 67 3d 30 30 33 30 39 34 63 34 35 30 66 30 30 30 30 33 33 65 65 39 36 39 35 66 2d 37 36 35 33 66 37 62 36 [Mon Oct 13 21:17:14 2003] sip_radius.c(675) Building attr - h323-disconnect-time= 21:17:14.33 GMT Mon Oct 13 2003

[Mon Oct 13 21:17:14 2003] [debug] sip_radius.c(806): Attr built as 29 (VSA) 11 - h323-disconnect-time= 60 bytes



[Mon Oct 13 21:17:14 2003] [debug] sip_radius.c(594): 1a 3c 00 00 00 09 1d 36 68 33 32 33 2d 64 69 73 63 6f 6e 6e 65 63 74 2d 74 69 6d 65 3d 32 31 3a 31 37 3a 31 34 2e 33 33 20 47 4d 54 20 4d 6f 6e 20 4f 63 74 20 31 33 20 32 30 30 33 [Mon Oct 13 21:17:14 2003] sip_radius.c(675) Building attr - h323-call-origin= answer











[Mon Oct 13 21:17:14 2003] sip_radius.c(675) Building attr - method= BYE


[Mon Oct 13 21:17:14 2003] [debug] sip_radius.c(594): 1a 12 00 00 00 09 01 0c 6d 65 74 68 6f 64 3d 42 59 45 [Mon Oct 13 21:17:14 2003] sip_radius.c(675) Building attr - prev-hop-via= SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248






[Mon Oct 13 21:17:14 2003] [debug] sip_radius.c(594): 1a 25 00 00 00 09 01 1f 70 72 65 76 2d 68 6f 70 2d 69 70 3d 31 30 2e 32 32 2e 37 37 2e 32 34 38 3a 35 30 36 30 [Mon Oct 13 21:17:14 2003] sip_radius.c(675) Building attr - incoming-req-uri= sip:7905@vvs-vitra:5060


[Mon Oct 13 21:17:14 2003] [debug] sip_radius.c(594): 1a 30 00 00 00 09 01 2a 69 6e 63 6f 6d 69 6e 67 2d 72 65 71 2d 75 72 69 3d 73 69 70 3a 37 39 30 35 40 76 76 73 2d 76 69 74 72 61 3a 35 30 36 30

[Mon Oct 13 21:17:14 2003] sip_radius.c(675) Building attr - outgoing-req-uri= sip:[email protected]:5060;user=phone

[Mon Oct 13 21:17:14 2003] [debug] sip_radius.c(806): Attr built as 1 (VSA) 11 - outgoing-req-uri= 61 bytes

[Mon Oct 13 21:17:14 2003] [debug] sip_radius.c(594): 1a 3d 00 00 00 09 01 37 6f 75 74 67 6f 69 6e 67 2d 72 65 71 2d 75 72 69 3d 73 69 70 3a 37 39 30 35 40 31 30 2e 32 32 2e 37 36 2e 36 30 3a 35 30 36 30 3b 75 73 65 72 3d 70 68 6f 6e 65 [Mon Oct 13 21:17:14 2003] sip_radius.c(675) Building attr - next-hop-ip= a.22.76.60:5060

[Mon Oct 13 21:17:14 2003] [debug] sip_radius.c(806): Attr built as 1 (VSA) 11 - next-hop-ip= 36 bytes

[Mon Oct 13 21:17:14 2003] [debug] sip_radius.c(594): 1a 24 00 00 00 09 01 1e 6e 65 78 74 2d 68 6f 70 2d 69 70 3d 31 30 2e 32 32 2e 37 36 2e 36 30 3a 35 30 36 30 [Mon Oct 13 21:17:14 2003] sip_radius.c(1115) Radius: max number of servers to use is 2.[Mon Oct 13 21:17:14 2003] sip_radius.c(1120) Radius: Start with server 1.[Mon Oct 13 21:17:14 2003] sip_radius.c(852) Radius: The RA is:[Mon Oct 13 21:17:14 2003] [debug] sip_radius.c(594): 63 94 9a 16 a5 bc f5 03 f8 66 51 4d 57 19 a0 d7

[Mon Oct 13 21:17:14 2003] sip_radius.c(1222) Radius: To send 724 bytes in request to b.19.174.128:1813.[Mon Oct 13 21:17:14 2003] [debug] sip_radius.c(594): 04 02 02 d4 63 94 9a 16 a5 bc f5 03 f8 66 51 4d 57 19 a0 d7 04 06 ac 13 ae ef 3d 06 00 00 00 05 01 06 37 39 36 31 06 06 00 00 00 01 28 06 00 00 00 02 2c 32 30 30 33 30 39 34 63 34 2d 35 30 66 30 30 30 32 32 2d 34 36 33 33 39 62 64 35 2d 34 61 66 31 36 66 34 64 40 31 30 2e 32 32 2e 37 37 2e 32 34 38 1e 25 3c 73 69 70 3a 37 39 30 35 40 76 76 73 2d 76 69 74 72 61 3e 3b 74 61 67 3d 34 31 33 34 31 38 31 33 33 33 1f 4e 22 28 76 76 73



2d 76 69 74 72 61 29 37 39 36 31 22 20 3c 73 69 70 3a 37 39 36 31 40 76 76 73 2d 76 69 74 72 61 3e 3b 74 61 67 3d 30 30 33 30 39 34 63 34 35 30 66 30 30 30 30 33 33 65 65 39 36 39 35 66 2d 37 36 35 33 66 37 62 36 1a 3c 00 00 00 09 1d 36 68 33 32 33 2d 64 69 73 63 6f 6e 6e 65 63 74 2d 74 69 6d 65 3d 32 31 3a 31 37 3a 31 34 2e 33 33 20 47 4d 54 20 4d 6f 6e 20 4f 63 74 20 31 33 20 32 30 30 33 1a 1f 00 00 00 09 1a 19 68 33 32 33 2d 63 61 6c 6c 2d 6f 72 69 67 69 6e 3d 61 6e 73 77 65 72 1a 1b 00 00 00 09 1b 15 68 33 32 33 2d 63 61 6c 6c 2d 74 79 70 65 3d 56 6f 49 50 1a 1b 00 00 00 09 01 15 73 69 70 2d 73 74 61 74 75 73 2d 63 6f 64 65 3d 32 30 30 1a 1c 00 00 00 09 01 16 73 65 73 73 69 6f 6e 2d 70 72 6f 74 6f 63 6f 6c 3d 73 69 70 1a 40 00 00 00 09 01 3a 63 61 6c 6c 2d 69 64 3d 30 30 33 30 39 34 63 34 2d 35 30 66 30 30 30 32 32 2d 34 36 33 33 39 62 64 35 2d 34 61 66 31 36 66 34 64 40 31 30 2e 32 32 2e 37 37 2e 32 34 38 1a 12 00 00 00 09 01 0c 6d 65 74 68 6f 64 3d 42 59 45 1a 48 00 00 00 09 01 42 70 72 65 76 2d 68 6f 70 2d 76 69 61 3d 53 49 50 2f 32 2e 30 2f 55 44 50 20 31 30 2e 32 32 2e 37 37 2e 32 34 38 3a 35 30 36 30 3b 72 65 63 65 69 76 65 64 3d 31 30 2e 32 32 2e 37 37 2e 32 34 38 1a 25 00 00 00 09 01 1f 70 72 65 76 2d 68 6f 70 2d 69 70 3d 31 30 2e 32 32 2e 37 37 2e 32 34 38 3a 35 30 36 30 1a 30 00 00 00 09 01 2a 69 6e 63 6f 6d 69 6e 67 2d 72 65 71 2d 75 72 69 3d 73 69 70 3a 37 39 30 35 40 76 76 73 2d 76 69 74 72 61 3a 35 30 36 30 1a 3d 00 00 00 09 01 37 6f 75 74 67 6f 69 6e 67 2d 72 65 71 2d 75 72 69 3d 73 69 70 3a 37 39 30 35 40 31 30 2e 32 32 2e 37 36 2e 36 30 3a 35 30 36 30 3b 75 73 65 72 3d 70 68 6f 6e 65 1a 24 00 00 00 09 01 1e 6e 65 78 74 2d 68 6f 70 2d 69 70 3d 31 30 2e 32 32 2e 37 36 2e 36 30 3a 35 30 36 30 [Mon Oct 13 21:17:14 2003] sip_radius.c(1300) Radius: read 20 bytes in response from b.19.174.128:1813.[Mon Oct 13 21:17:14 2003] [debug] sip_radius.c(594): 05 02 00 14 2c 1d 94 90 7b fd eb b8 b6 d7 db 37 24 48 ae 86 [Mon Oct 13 21:17:14 2003] sip_radius.c(1410) Radius: server 1 responded with Accept. Mark it for next time use.

Unsuccessful Call, Server-Side Accounting Enabled, Unsuccessful Accounting Enabled


The following are ccounting records from a FreeRADIUS server with default accounting configuration:

Mon Oct 13 14:37:07 2003 NAS-IP-Address = b.19.174.239 NAS-Port-Type = Virtual User-Name = "7961" Service-Type = Login-User Acct-Status-Type = Stop Acct-Session-Id = "[email protected]" Called-Station-Id = "<sip:7000@vvs-vitra>"



Calling-Station-Id = ""(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f00005375b5768-01bbe6f0" h323-setup-time = "h323-setup-time=21:42:35.707 GMT Mon Oct 13 2003" h323-disconnect-time = "h323-disconnect-time=21:42:35.713 GMT Mon Oct 13 2003" h323-call-origin = "h323-call-origin=answer" h323-call-type = "h323-call-type=VoIP" Cisco-AVPair = "sip-status-code=404" Cisco-AVPair = "session-protocol=sip" Cisco-AVPair = "[email protected]" Cisco-AVPair = "method=INVITE" Cisco-AVPair = "prev-hop-via=SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248" Cisco-AVPair = "prev-hop-ip=a.22.77.248:5060" Cisco-AVPair = "incoming-req-uri=sip:7000@vvs-vitra" Client-IP-Address = b.19.174.239 Acct-Unique-Session-Id = "e0ad66218005a903" Timestamp = 1066081027



rad_recv: Accounting-Request packet from host b.19.174.239:35455, id=1, length=667 NAS-IP-Address = b.19.174.239 NAS-Port-Type = Virtual User-Name = "7961" Service-Type = Login-User Acct-Status-Type = Stop Acct-Session-Id = "[email protected]" Called-Station-Id = "<sip:7000@vvs-vitra>" Calling-Station-Id = ""(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f00005375b5768-01bbe6f0" h323-setup-time = "h323-setup-time=21:42:35.707 GMT Mon Oct 13 2003" h323-disconnect-time = "h323-disconnect-time=21:42:35.713 GMT Mon Oct 13 2003" h323-call-origin = "h323-call-origin=answer" h323-call-type = "h323-call-type=VoIP" Cisco-AVPair = "sip-status-code=404" Cisco-AVPair = "session-protocol=sip" Cisco-AVPair = "[email protected]" Cisco-AVPair = "method=INVITE" Cisco-AVPair = "prev-hop-via=SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248" Cisco-AVPair = "prev-hop-ip=a.22.77.248:5060" Cisco-AVPair = "incoming-req-uri=sip:7000@vvs-vitra"modcall: entering group preacct modcall[preacct]: module "preprocess" returns noop rlm_realm: No '@' in User-Name = "7961", looking up realm NULL rlm_realm: No such realm "NULL" modcall[preacct]: module "suffix" returns noop acct_users: Matched DEFAULT at 10 modcall[preacct]: module "files" returns okmodcall: group preacct returns okmodcall: entering group accountingrlm_acct_unique: WARNING: Attribute NAS-Port-Id was not found in request, unique ID MAY be inconsistentrlm_acct_unique: Hashing ',Client-IP-Address = b.19.174.239,NAS-IP-Address = b.19.174.239,Acct-Session-Id = "[email protected]",User-Name = "7961"'rlm_acct_unique: Acct-Unique-Session-ID = "e0ad66218005a903". modcall[accounting]: module "acct_unique" returns okradius_xlat: '/usr/local/var/log/radius/radacct/b.19.174.239/detail-20031013'rlm_detail: /usr/local/var/log/radius/radacct/%{Client-IP-Address}/detail-%Y%m%d expands to /usr/local/var/log/radius/radacct/b.19.174.239/detail-20031013 modcall[accounting]: module "detail" returns ok modcall[accounting]: module "unix" returns noop



radius_xlat: '/usr/local/var/log/radius/radutmp'radius_xlat: '7961' rlm_radutmp: No NAS-Port seen. Cannot do anything. rlm_radumtp: WARNING: checkrad will probably not work! modcall[accounting]: module "radutmp" returns noopmodcall: group accounting returns okradius_xlat: '/path/to/exec/acct/stop'Exec-Program: /path/to/exec/acct/stopSending Accounting-Response of id 1 to b.19.174.239:35455Finished request 0Going to the next request--- Walking the entire request list ---Cleaning up request 0 ID 1 with timestamp 3f8b1b03Nothing to do. Sleeping until we see a request.

Cisco SPS error_log file

[Mon Oct 13 21:42:35 2003] sip_protocol.c(5393) Received 657 bytes UDP packet from a.22.77.248:50432 INVITE sip:7000@vvs-vitra SIP/2.0Via: SIP/2.0/UDP a.22.77.248:5060From: "(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f00005375b5768-01bbe6f0To: <sip:7000@vvs-vitra>Call-ID: [email protected]: 101 INVITEUser-Agent: CSCO/4Contact: <sip:[email protected]:5060>Expires: 180Content-Type: application/sdpContent-Length: 247Accept: application/sdp


[Mon Oct 13 21:42:35 2003] sip_sm.c(998) Sent 286 bytes UDP packet to a.22.77.248:5060 SIP/2.0 100 TryingVia: SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248Call-ID: [email protected]: "(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f00005375b5768-01bbe6f0To: <sip:7000@vvs-vitra>CSeq: 101 INVITEContent-Length: 0

[Mon Oct 13 21:42:35 2003] mod_sip_acct.c(630) Accounting event type: INVITE received from upstream, subtype: none

[Mon Oct 13 21:42:35 2003] sip_sm.c(828) TCB_PROXIED_STATE_TIMER : 180 seconds.[Mon Oct 13 21:42:35 2003] sip_sm.c(998) Sent 303 bytes UDP packet to a.22.77.248:5060 SIP/2.0 404 Not Found



Via: SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248Call-ID: [email protected]: "(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f00005375b5768-01bbe6f0To: <sip:7000@vvs-vitra>;tag=4c1d-360bCSeq: 101 INVITEContent-Length: 0

[Mon Oct 13 21:42:35 2003] mod_sip_acct.c(630) Accounting event type: non-200 to INVITE sent upstream, subtype: local response without branch













[Mon Oct 13 21:42:35 2003] [debug] sip_radius.c(594): 2c 32 30 30 33 30 39 34 63 34 2d 35 30 66 30 30 30 36 66 2d 35 37 33 34 61 33 33 34 2d 30 66 36 32 61 32 39 34 40 31 30 2e 32 32 2e 37 37 2e 32 34 38 [Mon Oct 13 21:42:35 2003] sip_radius.c(675) Building attr - Called-Station-Id <sip:7000@vvs-vitra>




[Mon Oct 13 21:42:35 2003] [debug] sip_radius.c(594): 1e 16 3c 73 69 70 3a 37 30 30 30 40 76 76 73 2d 76 69 74 72 61 3e [Mon Oct 13 21:42:35 2003] sip_radius.c(675) Building attr - Calling-Station-Id "(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f00005375b5768-01bbe6f0


[Mon Oct 13 21:42:35 2003] [debug] sip_radius.c(594): 1f 4e 22 28 76 76 73 2d 76 69 74 72 61 29 37 39 36 31 22 20 3c 73 69 70 3a 37 39 36 31 40 76 76 73 2d 76 69 74 72 61 3e 3b 74 61 67 3d 30 30 33 30 39 34 63 34 35 30 66 30 30 30 30 35 33 37 35 62 35 37 36 38 2d 30 31 62 62 65 36 66 30 [Mon Oct 13 21:42:35 2003] sip_radius.c(675) Building attr - h323-setup-time= 21:42:35.707 GMT Mon Oct 13 2003

[Mon Oct 13 21:42:35 2003] [debug] sip_radius.c(806): Attr built as 25 (VSA) 11 - h323-setup-time= 56 bytes

[Mon Oct 13 21:42:35 2003] [debug] sip_radius.c(594): 1a 38 00 00 00 09 19 32 68 33 32 33 2d 73 65 74 75 70 2d 74 69 6d 65 3d 32 31 3a 34 32 3a 33 35 2e 37 30 37 20 47 4d 54 20 4d 6f 6e 20 4f 63 74 20 31 33 20 32 30 30 33 [Mon Oct 13 21:42:35 2003] sip_radius.c(675) Building attr - h323-disconnect-time= 21:42:35.713 GMT Mon Oct 13 2003

[Mon Oct 13 21:42:35 2003] [debug] sip_radius.c(806): Attr built as 29 (VSA) 11 - h323-disconnect-time= 61 bytes

[Mon Oct 13 21:42:35 2003] [debug] sip_radius.c(594): 1a 3d 00 00 00 09 1d 37 68 33 32 33 2d 64 69 73 63 6f 6e 6e 65 63 74 2d 74 69 6d 65 3d 32 31 3a 34 32 3a 33 35 2e 37 31 33 20 47 4d 54 20 4d 6f 6e 20 4f 63 74 20 31 33 20 32 30 30 33 [Mon Oct 13 21:42:35 2003] sip_radius.c(675) Building attr - h323-call-origin= answer













[Mon Oct 13 21:42:35 2003] sip_radius.c(675) Building attr - method= INVITE


[Mon Oct 13 21:42:35 2003] [debug] sip_radius.c(594): 1a 15 00 00 00 09 01 0f 6d 65 74 68 6f 64 3d 49 4e 56 49 54 45 [Mon Oct 13 21:42:35 2003] sip_radius.c(675) Building attr - prev-hop-via= SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248




[Mon Oct 13 21:42:35 2003] [debug] sip_radius.c(594): 1a 25 00 00 00 09 01 1f 70 72 65 76 2d 68 6f 70 2d 69 70 3d 31 30 2e 32 32 2e 37 37 2e 32 34 38 3a 35 30 36 30 [Mon Oct 13 21:42:35 2003] sip_radius.c(675) Building attr - incoming-req-uri= sip:7000@vvs-vitra


[Mon Oct 13 21:42:35 2003] [debug] sip_radius.c(594): 1a 2b 00 00 00 09 01 25 69 6e 63 6f 6d 69 6e 67 2d 72 65 71 2d 75 72 69 3d 73 69 70 3a 37 30 30 30 40 76 76 73 2d 76 69 74 72 61 [Mon Oct 13 21:42:35 2003] sip_radius.c(1115) Radius: max number of servers to use is 2.[Mon Oct 13 21:42:35 2003] sip_radius.c(1120) Radius: Start with server 1.[Mon Oct 13 21:42:35 2003] sip_radius.c(852) Radius: The RA is:[Mon Oct 13 21:42:35 2003] [debug] sip_radius.c(594): 39 a4 56 d0 7f a3 a4 99 09 0e 2d ad 51 02 52 9a



[Mon Oct 13 21:42:35 2003] sip_radius.c(1222) Radius: To send 667 bytes in request to b.19.174.128:1813.[Mon Oct 13 21:42:35 2003] [debug] sip_radius.c(594): 04 01 02 9b 39 a4 56 d0 7f a3 a4 99 09 0e 2d ad 51 02 52 9a 04 06 ac 13 ae ef 3d 06 00 00 00 05 01 06 37 39 36 31 06 06 00 00 00 01 28 06 00 00 00 02 2c 32 30 30 33 30 39 34 63 34 2d 35 30 66 30 30 30 36 66 2d 35 37 33 34 61 33 33 34 2d 30 66 36 32 61 32 39 34 40 31 30 2e 32 32 2e 37 37 2e 32 34 38 1e 16 3c 73 69 70 3a 37 30 30 30 40 76 76 73 2d 76 69 74 72 61 3e 1f 4e 22 28 76 76 73 2d 76 69 74 72 61 29 37 39 36 31 22 20 3c 73 69 70 3a 37 39 36 31 40 76 76 73 2d 76 69 74 72 61 3e 3b 74 61 67 3d 30 30 33 30 39 34 63 34 35 30 66 30 30 30 30 35 33 37 35 62 35 37 36 38 2d 30 31 62 62 65 36 66 30 1a 38 00 00 00 09 19 32 68 33 32 33 2d 73 65 74 75 70 2d 74 69 6d 65 3d 32 31 3a 34 32 3a 33 35 2e 37 30 37 20 47 4d 54 20 4d 6f 6e 20 4f 63 74 20 31 33 20 32 30 30 33 1a 3d 00 00 00 09 1d 37 68 33 32 33 2d 64 69 73 63 6f 6e 6e 65 63 74 2d 74 69 6d 65 3d 32 31 3a 34 32 3a 33 35 2e 37 31 33 20 47 4d 54 20 4d 6f 6e 20 4f 63 74 20 31 33 20 32 30 30 33 1a 1f 00 00 00 09 1a 19 68 33 32 33 2d 63 61 6c 6c 2d 6f 72 69 67 69 6e 3d 61 6e 73 77 65 72 1a 1b 00 00 00 09 1b 15 68 33 32 33 2d 63 61 6c 6c 2d 74 79 70 65 3d 56 6f 49 50 1a 1b 00 00 00 09 01 15 73 69 70 2d 73 74 61 74 75 73 2d 63 6f 64 65 3d 34 30 34 1a 1c 00 00 00 09 01 16 73 65 73 73 69 6f 6e 2d 70 72 6f 74 6f 63 6f 6c 3d 73 69 70 1a 40 00 00 00 09 01 3a 63 61 6c 6c 2d 69 64 3d 30 30 33 30 39 34 63 34 2d 35 30 66 30 30 30 36 66 2d 35 37 33 34 61 33 33 34 2d 30 66 36 32 61 32 39 34 40 31 30 2e 32 32 2e 37 37 2e 32 34 38 1a 15 00 00 00 09 01 0f 6d 65 74 68 6f 64 3d 49 4e 56 49 54 45 1a 48 00 00 00 09 01 42 70 72 65 76 2d 68 6f 70 2d 76 69 61 3d 53 49 50 2f 32 2e 30 2f 55 44 50 20 31 30 2e 32 32 2e 37 37 2e 32 34 38 3a 35 30 36 30 3b 72 65 63 65 69 76 65 64 3d 31 30 2e 32 32 2e 37 37 2e 32 34 38 1a 25 00 00 00 09 01 1f 70 72 65 76 2d 68 6f 70 2d 69 70 3d 31 30 2e 32 32 2e 37 37 2e 32 34 38 3a 35 30 36 30 1a 2b 00 00 00 09 01 25 69 6e 63 6f 6d 69 6e 67 2d 72 65 71 2d 75 72 69 3d 73 69 70 3a 37 30 30 30 40 76 76 73 2d 76 69 74 72 61 [Mon Oct 13 21:42:35 2003] sip_radius.c(1300) Radius: read 20 bytes in response from b.19.174.128:1813.[Mon Oct 13 21:42:35 2003] [debug] sip_radius.c(594): 05 01 00 14 d8 c5 25 9a 93 90 dc ec 42 22 96 c5 86 6d 5a a9 [Mon Oct 13 21:42:35 2003] sip_radius.c(1410) Radius: server 1 responded with Accept. Mark it for next time use.[Mon Oct 13 21:42:35 2003] sip_protocol.c(5393) Received 287 bytes UDP packet from a.22.77.248:50531 ACK sip:7000@vvs-vitra SIP/2.0Via: SIP/2.0/UDP a.22.77.248:5060From: "(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f00005375b5768-01bbe6f0To: <sip:7000@vvs-vitra>;tag=4c1d-360bCall-ID: [email protected]: 101 ACKContent-Length: 0



Forked Call; Server- and Client-Side Accounting Enabled; Unsuccessful Accounting Enabled


The following accounting records are from a FreeRADIUS server with default accounting configuration:

Wed Oct 15 10:35:21 2003 NAS-IP-Address = b.19.174.239 NAS-Port-Type = Virtual User-Name = "7961" Service-Type = Login-User Acct-Status-Type = Stop Acct-Session-Id = "[email protected]" Called-Station-Id = "<sip:7905@vvs-vitra>" Calling-Station-Id = ""(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f0000f0b70ee8f-06e54737" h323-setup-time = "h323-setup-time=17:40:56.92 GMT Wed Oct 15 2003" h323-disconnect-time = "h323-disconnect-time=17:40:56.125 GMT Wed Oct 15 2003" h323-call-origin = "h323-call-origin=originate" h323-call-type = "h323-call-type=VoIP" Cisco-AVPair = "sip-status-code=486" Cisco-AVPair = "session-protocol=sip" Cisco-AVPair = "[email protected]" Cisco-AVPair = "method=INVITE" Cisco-AVPair = "prev-hop-via=SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248" Cisco-AVPair = "prev-hop-ip=a.22.77.248:5060" Cisco-AVPair = "incoming-req-uri=sip:7905@vvs-vitra" Cisco-AVPair = "outgoing-req-uri=sip:[email protected]:5060;user=phone;transport=udp" Cisco-AVPair = "next-hop-ip=a.22.76.60:5060" Cisco-AVPair = "sip-hdr=From: "(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f0000f0b70ee8f-06e54737" Cisco-AVPair = "sip-hdr=To: <sip:7905@vvs-vitra>;tag=1186552587" Cisco-AVPair = "sip-hdr=CSeq: 101 INVITE" Client-IP-Address = b.19.174.239 Acct-Unique-Session-Id = "b9b284f20f5f865e" Timestamp = 1066239321

Wed Oct 15 10:35:26 2003 NAS-IP-Address = b.19.174.239 NAS-Port-Type = Virtual User-Name = "7961" Service-Type = Login-User Acct-Status-Type = Stop Acct-Session-Id = "[email protected]" Called-Station-Id = "<sip:7905@vvs-vitra>" Calling-Station-Id = ""(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f0000f0b70ee8f-06e54737" h323-setup-time = "h323-setup-time=17:40:56.93 GMT Wed Oct 15 2003" h323-disconnect-time = "h323-disconnect-time=17:41:00.461 GMT Wed Oct 15 2003" h323-call-origin = "h323-call-origin=originate" h323-call-type = "h323-call-type=VoIP" Cisco-AVPair = "sip-status-code=408" Cisco-AVPair = "session-protocol=sip" Cisco-AVPair = "[email protected]" Cisco-AVPair = "method=INVITE" Cisco-AVPair = "prev-hop-via=SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248" Cisco-AVPair = "prev-hop-ip=a.22.77.248:5060" Cisco-AVPair = "incoming-req-uri=sip:7905@vvs-vitra" Cisco-AVPair = "outgoing-req-uri=sip:[email protected]:5060;user=phone;transport=udp"



Cisco-AVPair = "next-hop-ip=a.2.3.4:5060" Cisco-AVPair = "sip-hdr=From: "(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f0000f0b70ee8f-06e54737" Cisco-AVPair = "sip-hdr=To: <sip:7905@vvs-vitra>;tag=28b4-313c" Cisco-AVPair = "sip-hdr=CSeq: 101 INVITE" Client-IP-Address = b.19.174.239 Acct-Unique-Session-Id = "b9b284f20f5f865e" Timestamp = 1066239326

Wed Oct 15 10:35:34 2003 NAS-IP-Address = b.19.174.239 NAS-Port-Type = Virtual User-Name = "7961" Service-Type = Login-User Acct-Status-Type = Start Acct-Session-Id = "[email protected]" Called-Station-Id = "<sip:7905@vvs-vitra>" Calling-Station-Id = ""(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f0000f0b70ee8f-06e54737" h323-setup-time = "h323-setup-time=17:40:56.146 GMT Wed Oct 15 2003" h323-connect-time = "h323-connect-time=17:41:08.685 GMT Wed Oct 15 2003" h323-call-origin = "h323-call-origin=originate" h323-call-type = "h323-call-type=VoIP" Cisco-AVPair = "sip-status-code=200" Cisco-AVPair = "session-protocol=sip" Cisco-AVPair = "[email protected]" Cisco-AVPair = "method=INVITE" Cisco-AVPair = "prev-hop-via=SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248" Cisco-AVPair = "prev-hop-ip=a.22.77.248:5060" Cisco-AVPair = "incoming-req-uri=sip:7905@vvs-vitra" Cisco-AVPair = "outgoing-req-uri=sip:[email protected]" Cisco-AVPair = "next-hop-ip=b.23.252.22:5060" Cisco-AVPair = "sip-hdr=From: "(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f0000f0b70ee8f-06e54737" Cisco-AVPair = "sip-hdr=To: <sip:7905@vvs-vitra>;tag=CD0A90CC-20BC" Cisco-AVPair = "sip-hdr=CSeq: 101 INVITE" Client-IP-Address = b.19.174.239 Acct-Unique-Session-Id = "b9b284f20f5f865e" Timestamp = 1066239334

Wed Oct 15 10:35:34 2003 NAS-IP-Address = b.19.174.239 NAS-Port-Type = Virtual User-Name = "7961" Service-Type = Login-User Acct-Status-Type = Start Acct-Session-Id = "[email protected]" Called-Station-Id = "<sip:7905@vvs-vitra>" Calling-Station-Id = ""(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f0000f0b70ee8f-06e54737" h323-setup-time = "h323-setup-time=17:40:56.86 GMT Wed Oct 15 2003" h323-connect-time = "h323-connect-time=17:41:08.702 GMT Wed Oct 15 2003" h323-call-origin = "h323-call-origin=answer" h323-call-type = "h323-call-type=VoIP" Cisco-AVPair = "sip-status-code=200" Cisco-AVPair = "session-protocol=sip" Cisco-AVPair = "[email protected]" Cisco-AVPair = "method=INVITE" Cisco-AVPair = "prev-hop-via=SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248" Cisco-AVPair = "prev-hop-ip=a.22.77.248:5060" Cisco-AVPair = "incoming-req-uri=sip:7905@vvs-vitra" Cisco-AVPair = "outgoing-req-uri=sip:[email protected]" Cisco-AVPair = "next-hop-ip=b.23.252.22:5060"



Cisco-AVPair = "sip-hdr=From: "(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f0000f0b70ee8f-06e54737" Cisco-AVPair = "sip-hdr=To: <sip:7905@vvs-vitra>;tag=CD0A90CC-20BC" Cisco-AVPair = "sip-hdr=CSeq: 101 INVITE" Client-IP-Address = b.19.174.239 Acct-Unique-Session-Id = "b9b284f20f5f865e" Timestamp = 1066239334

Wed Oct 15 10:35:47 2003 NAS-IP-Address = b.19.174.239 NAS-Port-Type = Virtual User-Name = "7961" Service-Type = Login-User Acct-Status-Type = Stop Acct-Session-Id = "[email protected]" Called-Station-Id = "<sip:7905@vvs-vitra>;tag=CD0A90CC-20BC" Calling-Station-Id = ""(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f0000f0b70ee8f-06e54737" h323-disconnect-time = "h323-disconnect-time=17:41:21.605 GMT Wed Oct 15 2003" h323-call-origin = "h323-call-origin=originate" h323-call-type = "h323-call-type=VoIP" Cisco-AVPair = "sip-status-code=200" Cisco-AVPair = "session-protocol=sip" Cisco-AVPair = "[email protected]" Cisco-AVPair = "method=BYE" Cisco-AVPair = "prev-hop-via=SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248" Cisco-AVPair = "prev-hop-ip=a.22.77.248:5060" Cisco-AVPair = "incoming-req-uri=sip:7905@vvs-vitra:5060" Cisco-AVPair = "outgoing-req-uri=sip:[email protected]:5060" Cisco-AVPair = "next-hop-ip=b.23.252.22:5060" Cisco-AVPair = "sip-hdr=From: "(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f0000f0b70ee8f-06e54737" Cisco-AVPair = "sip-hdr=To: <sip:7905@vvs-vitra>;tag=CD0A90CC-20BC" Cisco-AVPair = "sip-hdr=CSeq: 102 BYE" Client-IP-Address = b.19.174.239 Acct-Unique-Session-Id = "b9b284f20f5f865e" Timestamp = 1066239347

Wed Oct 15 10:35:47 2003 NAS-IP-Address = b.19.174.239 NAS-Port-Type = Virtual User-Name = "7961" Service-Type = Login-User Acct-Status-Type = Stop Acct-Session-Id = "[email protected]" Called-Station-Id = "<sip:7905@vvs-vitra>;tag=CD0A90CC-20BC" Calling-Station-Id = ""(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f0000f0b70ee8f-06e54737" h323-disconnect-time = "h323-disconnect-time=17:41:21.601 GMT Wed Oct 15 2003" h323-call-origin = "h323-call-origin=answer" h323-call-type = "h323-call-type=VoIP" Cisco-AVPair = "sip-status-code=200" Cisco-AVPair = "session-protocol=sip" Cisco-AVPair = "[email protected]" Cisco-AVPair = "method=BYE" Cisco-AVPair = "prev-hop-via=SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248" Cisco-AVPair = "prev-hop-ip=a.22.77.248:5060" Cisco-AVPair = "incoming-req-uri=sip:7905@vvs-vitra:5060" Cisco-AVPair = "outgoing-req-uri=sip:[email protected]:5060" Cisco-AVPair = "next-hop-ip=b.23.252.22:5060" Cisco-AVPair = "sip-hdr=From: "(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f0000f0b70ee8f-06e54737" Cisco-AVPair = "sip-hdr=To: <sip:7905@vvs-vitra>;tag=CD0A90CC-20BC" Cisco-AVPair = "sip-hdr=CSeq: 102 BYE"



Client-IP-Address = b.19.174.239 Acct-Unique-Session-Id = "b9b284f20f5f865e" Timestamp = 1066239347



rad_recv: Accounting-Request packet from host b.19.174.239:36544, id=1, length=965 NAS-IP-Address = b.19.174.239 NAS-Port-Type = Virtual User-Name = "7961" Service-Type = Login-User Acct-Status-Type = Stop Acct-Session-Id = "[email protected]" Called-Station-Id = "<sip:7905@vvs-vitra>" Calling-Station-Id = ""(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f0000f0b70ee8f-06e54737" h323-setup-time = "h323-setup-time=17:40:56.92 GMT Wed Oct 15 2003" h323-disconnect-time = "h323-disconnect-time=17:40:56.125 GMT Wed Oct 15 2003" h323-call-origin = "h323-call-origin=originate" h323-call-type = "h323-call-type=VoIP" Cisco-AVPair = "sip-status-code=486" Cisco-AVPair = "session-protocol=sip" Cisco-AVPair = "[email protected]" Cisco-AVPair = "method=INVITE" Cisco-AVPair = "prev-hop-via=SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248" Cisco-AVPair = "prev-hop-ip=a.22.77.248:5060" Cisco-AVPair = "incoming-req-uri=sip:7905@vvs-vitra" Cisco-AVPair = "outgoing-req-uri=sip:[email protected]:5060;user=phone;transport=udp" Cisco-AVPair = "next-hop-ip=a.22.76.60:5060" Cisco-AVPair = "sip-hdr=From: "(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f0000f0b70ee8f-06e54737" Cisco-AVPair = "sip-hdr=To: <sip:7905@vvs-vitra>;tag=1186552587" Cisco-AVPair = "sip-hdr=CSeq: 101 INVITE"modcall: entering group preacct modcall[preacct]: module "preprocess" returns noop rlm_realm: No '@' in User-Name = "7961", looking up realm NULL rlm_realm: No such realm "NULL" modcall[preacct]: module "suffix" returns noop acct_users: Matched DEFAULT at 10 modcall[preacct]: module "files" returns okmodcall: group preacct returns okmodcall: entering group accountingrlm_acct_unique: WARNING: Attribute NAS-Port-Id was not found in request, unique ID MAY be inconsistentrlm_acct_unique: Hashing ',Client-IP-Address = b.19.174.239,NAS-IP-Address = b.19.174.239,Acct-Session-Id = "[email protected]",User-Name = "7961"'rlm_acct_unique: Acct-Unique-Session-ID = "b9b284f20f5f865e". modcall[accounting]: module "acct_unique" returns okradius_xlat: '/usr/local/var/log/radius/radacct/b.19.174.239/detail-20031015'rlm_detail: /usr/local/var/log/radius/radacct/%{Client-IP-Address}/detail-%Y%m%d expands to /usr/local/var/log/radius/radacct/b.19.174.239/detail-20031015 modcall[accounting]: module "detail" returns ok modcall[accounting]: module "unix" returns noopradius_xlat: '/usr/local/var/log/radius/radutmp'radius_xlat: '7961' rlm_radutmp: No NAS-Port seen. Cannot do anything. rlm_radumtp: WARNING: checkrad will probably not work! modcall[accounting]: module "radutmp" returns noopmodcall: group accounting returns ok



radius_xlat: '/path/to/exec/acct/stop'Exec-Program: /path/to/exec/acct/stopSending Accounting-Response of id 1 to b.19.174.239:36544Finished request 0Going to the next request--- Walking the entire request list ---Cleaning up request 0 ID 1 with timestamp 3f8d8559Nothing to do. Sleeping until we see a request.--- Walking the entire request list ---Nothing to do. Sleeping until we see a request.rad_recv: Accounting-Request packet from host b.19.174.239:36546, id=2, length=956 NAS-IP-Address = b.19.174.239 NAS-Port-Type = Virtual User-Name = "7961" Service-Type = Login-User Acct-Status-Type = Stop Acct-Session-Id = "[email protected]" Called-Station-Id = "<sip:7905@vvs-vitra>" Calling-Station-Id = ""(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f0000f0b70ee8f-06e54737" h323-setup-time = "h323-setup-time=17:40:56.93 GMT Wed Oct 15 2003" h323-disconnect-time = "h323-disconnect-time=17:41:00.461 GMT Wed Oct 15 2003" h323-call-origin = "h323-call-origin=originate" h323-call-type = "h323-call-type=VoIP" Cisco-AVPair = "sip-status-code=408" Cisco-AVPair = "session-protocol=sip" Cisco-AVPair = "[email protected]" Cisco-AVPair = "method=INVITE" Cisco-AVPair = "prev-hop-via=SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248" Cisco-AVPair = "prev-hop-ip=a.22.77.248:5060" Cisco-AVPair = "incoming-req-uri=sip:7905@vvs-vitra" Cisco-AVPair = "outgoing-req-uri=sip:[email protected]:5060;user=phone;transport=udp" Cisco-AVPair = "next-hop-ip=a.2.3.4:5060" Cisco-AVPair = "sip-hdr=From: "(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f0000f0b70ee8f-06e54737" Cisco-AVPair = "sip-hdr=To: <sip:7905@vvs-vitra>;tag=28b4-313c" Cisco-AVPair = "sip-hdr=CSeq: 101 INVITE"modcall: entering group preacct modcall[preacct]: module "preprocess" returns noop rlm_realm: No '@' in User-Name = "7961", looking up realm NULL rlm_realm: No such realm "NULL" modcall[preacct]: module "suffix" returns noop acct_users: Matched DEFAULT at 10 modcall[preacct]: module "files" returns okmodcall: group preacct returns okmodcall: entering group accountingrlm_acct_unique: WARNING: Attribute NAS-Port-Id was not found in request, unique ID MAY be inconsistentrlm_acct_unique: Hashing ',Client-IP-Address = b.19.174.239,NAS-IP-Address = b.19.174.239,Acct-Session-Id = "[email protected]",User-Name = "7961"'rlm_acct_unique: Acct-Unique-Session-ID = "b9b284f20f5f865e". modcall[accounting]: module "acct_unique" returns okradius_xlat: '/usr/local/var/log/radius/radacct/b.19.174.239/detail-20031015'rlm_detail: /usr/local/var/log/radius/radacct/%{Client-IP-Address}/detail-%Y%m%d expands to /usr/local/var/log/radius/radacct/b.19.174.239/detail-20031015 modcall[accounting]: module "detail" returns ok modcall[accounting]: module "unix" returns noopradius_xlat: '/usr/local/var/log/radius/radutmp'radius_xlat: '7961' rlm_radutmp: No NAS-Port seen. Cannot do anything. rlm_radumtp: WARNING: checkrad will probably not work! modcall[accounting]: module "radutmp" returns noopmodcall: group accounting returns ok



radius_xlat: '/path/to/exec/acct/stop'Exec-Program: /path/to/exec/acct/stopSending Accounting-Response of id 2 to b.19.174.239:36546Finished request 1Going to the next request--- Walking the entire request list ---Cleaning up request 1 ID 2 with timestamp 3f8d855eNothing to do. Sleeping until we see a request.--- Walking the entire request list ---Nothing to do. Sleeping until we see a request.rad_recv: Accounting-Request packet from host b.19.174.239:36551, id=3, length=944 NAS-IP-Address = b.19.174.239 NAS-Port-Type = Virtual User-Name = "7961" Service-Type = Login-User Acct-Status-Type = Start Acct-Session-Id = "[email protected]" Called-Station-Id = "<sip:7905@vvs-vitra>" Calling-Station-Id = ""(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f0000f0b70ee8f-06e54737" h323-setup-time = "h323-setup-time=17:40:56.146 GMT Wed Oct 15 2003" h323-connect-time = "h323-connect-time=17:41:08.685 GMT Wed Oct 15 2003" h323-call-origin = "h323-call-origin=originate" h323-call-type = "h323-call-type=VoIP" Cisco-AVPair = "sip-status-code=200" Cisco-AVPair = "session-protocol=sip" Cisco-AVPair = "[email protected]" Cisco-AVPair = "method=INVITE" Cisco-AVPair = "prev-hop-via=SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248" Cisco-AVPair = "prev-hop-ip=a.22.77.248:5060" Cisco-AVPair = "incoming-req-uri=sip:7905@vvs-vitra" Cisco-AVPair = "outgoing-req-uri=sip:[email protected]" Cisco-AVPair = "next-hop-ip=b.23.252.22:5060" Cisco-AVPair = "sip-hdr=From: "(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f0000f0b70ee8f-06e54737" Cisco-AVPair = "sip-hdr=To: <sip:7905@vvs-vitra>;tag=CD0A90CC-20BC" Cisco-AVPair = "sip-hdr=CSeq: 101 INVITE"modcall: entering group preacct modcall[preacct]: module "preprocess" returns noop rlm_realm: No '@' in User-Name = "7961", looking up realm NULL rlm_realm: No such realm "NULL" modcall[preacct]: module "suffix" returns noop acct_users: Matched DEFAULT at 7 modcall[preacct]: module "files" returns okmodcall: group preacct returns okmodcall: entering group accountingrlm_acct_unique: WARNING: Attribute NAS-Port-Id was not found in request, unique ID MAY be inconsistentrlm_acct_unique: Hashing ',Client-IP-Address = b.19.174.239,NAS-IP-Address = b.19.174.239,Acct-Session-Id = "[email protected]",User-Name = "7961"'rlm_acct_unique: Acct-Unique-Session-ID = "b9b284f20f5f865e". modcall[accounting]: module "acct_unique" returns okradius_xlat: '/usr/local/var/log/radius/radacct/b.19.174.239/detail-20031015'rlm_detail: /usr/local/var/log/radius/radacct/%{Client-IP-Address}/detail-%Y%m%d expands to /usr/local/var/log/radius/radacct/b.19.174.239/detail-20031015 modcall[accounting]: module "detail" returns ok modcall[accounting]: module "unix" returns noopradius_xlat: '/usr/local/var/log/radius/radutmp'radius_xlat: '7961' rlm_radutmp: No NAS-Port seen. Cannot do anything. rlm_radumtp: WARNING: checkrad will probably not work! modcall[accounting]: module "radutmp" returns noopmodcall: group accounting returns ok



radius_xlat: '/path/to/exec/acct/start'Exec-Program: /path/to/exec/acct/startSending Accounting-Response of id 3 to b.19.174.239:36551Finished request 2Going to the next request--- Walking the entire request list ---Cleaning up request 2 ID 3 with timestamp 3f8d8566Nothing to do. Sleeping until we see a request.--- Walking the entire request list ---Nothing to do. Sleeping until we see a request.rad_recv: Accounting-Request packet from host b.19.174.239:36551, id=4, length=940 NAS-IP-Address = b.19.174.239 NAS-Port-Type = Virtual User-Name = "7961" Service-Type = Login-User Acct-Status-Type = Start Acct-Session-Id = "[email protected]" Called-Station-Id = "<sip:7905@vvs-vitra>" Calling-Station-Id = ""(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f0000f0b70ee8f-06e54737" h323-setup-time = "h323-setup-time=17:40:56.86 GMT Wed Oct 15 2003" h323-connect-time = "h323-connect-time=17:41:08.702 GMT Wed Oct 15 2003" h323-call-origin = "h323-call-origin=answer" h323-call-type = "h323-call-type=VoIP" Cisco-AVPair = "sip-status-code=200" Cisco-AVPair = "session-protocol=sip" Cisco-AVPair = "[email protected]" Cisco-AVPair = "method=INVITE" Cisco-AVPair = "prev-hop-via=SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248" Cisco-AVPair = "prev-hop-ip=a.22.77.248:5060" Cisco-AVPair = "incoming-req-uri=sip:7905@vvs-vitra" Cisco-AVPair = "outgoing-req-uri=sip:[email protected]" Cisco-AVPair = "next-hop-ip=b.23.252.22:5060" Cisco-AVPair = "sip-hdr=From: "(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f0000f0b70ee8f-06e54737" Cisco-AVPair = "sip-hdr=To: <sip:7905@vvs-vitra>;tag=CD0A90CC-20BC" Cisco-AVPair = "sip-hdr=CSeq: 101 INVITE"modcall: entering group preacct modcall[preacct]: module "preprocess" returns noop rlm_realm: No '@' in User-Name = "7961", looking up realm NULL rlm_realm: No such realm "NULL" modcall[preacct]: module "suffix" returns noop acct_users: Matched DEFAULT at 7 modcall[preacct]: module "files" returns okmodcall: group preacct returns okmodcall: entering group accountingrlm_acct_unique: WARNING: Attribute NAS-Port-Id was not found in request, unique ID MAY be inconsistentrlm_acct_unique: Hashing ',Client-IP-Address = b.19.174.239,NAS-IP-Address = b.19.174.239,Acct-Session-Id = "[email protected]",User-Name = "7961"'rlm_acct_unique: Acct-Unique-Session-ID = "b9b284f20f5f865e". modcall[accounting]: module "acct_unique" returns okradius_xlat: '/usr/local/var/log/radius/radacct/b.19.174.239/detail-20031015'rlm_detail: /usr/local/var/log/radius/radacct/%{Client-IP-Address}/detail-%Y%m%d expands to /usr/local/var/log/radius/radacct/b.19.174.239/detail-20031015 modcall[accounting]: module "detail" returns ok modcall[accounting]: module "unix" returns noopradius_xlat: '/usr/local/var/log/radius/radutmp'radius_xlat: '7961' rlm_radutmp: No NAS-Port seen. Cannot do anything. rlm_radumtp: WARNING: checkrad will probably not work! modcall[accounting]: module "radutmp" returns noopmodcall: group accounting returns ok



radius_xlat: '/path/to/exec/acct/start'Exec-Program: /path/to/exec/acct/startSending Accounting-Response of id 4 to b.19.174.239:36551Finished request 3Going to the next request--- Walking the entire request list ---Cleaning up request 3 ID 4 with timestamp 3f8d8566Nothing to do. Sleeping until we see a request.--- Walking the entire request list ---Nothing to do. Sleeping until we see a request.rad_recv: Accounting-Request packet from host b.19.174.239:36544, id=5, length=913 NAS-IP-Address = b.19.174.239 NAS-Port-Type = Virtual User-Name = "7961" Service-Type = Login-User Acct-Status-Type = Stop Acct-Session-Id = "[email protected]" Called-Station-Id = "<sip:7905@vvs-vitra>;tag=CD0A90CC-20BC" Calling-Station-Id = ""(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f0000f0b70ee8f-06e54737" h323-disconnect-time = "h323-disconnect-time=17:41:21.605 GMT Wed Oct 15 2003" h323-call-origin = "h323-call-origin=originate" h323-call-type = "h323-call-type=VoIP" Cisco-AVPair = "sip-status-code=200" Cisco-AVPair = "session-protocol=sip" Cisco-AVPair = "[email protected]" Cisco-AVPair = "method=BYE" Cisco-AVPair = "prev-hop-via=SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248" Cisco-AVPair = "prev-hop-ip=a.22.77.248:5060" Cisco-AVPair = "incoming-req-uri=sip:7905@vvs-vitra:5060" Cisco-AVPair = "outgoing-req-uri=sip:[email protected]:5060" Cisco-AVPair = "next-hop-ip=b.23.252.22:5060" Cisco-AVPair = "sip-hdr=From: "(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f0000f0b70ee8f-06e54737" Cisco-AVPair = "sip-hdr=To: <sip:7905@vvs-vitra>;tag=CD0A90CC-20BC" Cisco-AVPair = "sip-hdr=CSeq: 102 BYE"modcall: entering group preacct modcall[preacct]: module "preprocess" returns noop rlm_realm: No '@' in User-Name = "7961", looking up realm NULL rlm_realm: No such realm "NULL" modcall[preacct]: module "suffix" returns noop acct_users: Matched DEFAULT at 10 modcall[preacct]: module "files" returns okmodcall: group preacct returns okmodcall: entering group accountingrlm_acct_unique: WARNING: Attribute NAS-Port-Id was not found in request, unique ID MAY be inconsistentrlm_acct_unique: Hashing ',Client-IP-Address = b.19.174.239,NAS-IP-Address = b.19.174.239,Acct-Session-Id = "[email protected]",User-Name = "7961"'rlm_acct_unique: Acct-Unique-Session-ID = "b9b284f20f5f865e". modcall[accounting]: module "acct_unique" returns okradius_xlat: '/usr/local/var/log/radius/radacct/b.19.174.239/detail-20031015'rlm_detail: /usr/local/var/log/radius/radacct/%{Client-IP-Address}/detail-%Y%m%d expands to /usr/local/var/log/radius/radacct/b.19.174.239/detail-20031015 modcall[accounting]: module "detail" returns ok modcall[accounting]: module "unix" returns noopradius_xlat: '/usr/local/var/log/radius/radutmp'radius_xlat: '7961' rlm_radutmp: No NAS-Port seen. Cannot do anything. rlm_radumtp: WARNING: checkrad will probably not work! modcall[accounting]: module "radutmp" returns noopmodcall: group accounting returns okradius_xlat: '/path/to/exec/acct/stop'



Exec-Program: /path/to/exec/acct/stopSending Accounting-Response of id 5 to b.19.174.239:36544Finished request 4Going to the next request--- Walking the entire request list ---Cleaning up request 4 ID 5 with timestamp 3f8d8573Nothing to do. Sleeping until we see a request.--- Walking the entire request list ---Nothing to do. Sleeping until we see a request.rad_recv: Accounting-Request packet from host b.19.174.239:36544, id=6, length=910 NAS-IP-Address = b.19.174.239 NAS-Port-Type = Virtual User-Name = "7961" Service-Type = Login-User Acct-Status-Type = Stop Acct-Session-Id = "[email protected]" Called-Station-Id = "<sip:7905@vvs-vitra>;tag=CD0A90CC-20BC" Calling-Station-Id = ""(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f0000f0b70ee8f-06e54737" h323-disconnect-time = "h323-disconnect-time=17:41:21.601 GMT Wed Oct 15 2003" h323-call-origin = "h323-call-origin=answer" h323-call-type = "h323-call-type=VoIP" Cisco-AVPair = "sip-status-code=200" Cisco-AVPair = "session-protocol=sip" Cisco-AVPair = "[email protected]" Cisco-AVPair = "method=BYE" Cisco-AVPair = "prev-hop-via=SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248" Cisco-AVPair = "prev-hop-ip=a.22.77.248:5060" Cisco-AVPair = "incoming-req-uri=sip:7905@vvs-vitra:5060" Cisco-AVPair = "outgoing-req-uri=sip:[email protected]:5060" Cisco-AVPair = "next-hop-ip=b.23.252.22:5060" Cisco-AVPair = "sip-hdr=From: "(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f0000f0b70ee8f-06e54737" Cisco-AVPair = "sip-hdr=To: <sip:7905@vvs-vitra>;tag=CD0A90CC-20BC" Cisco-AVPair = "sip-hdr=CSeq: 102 BYE"modcall: entering group preacct modcall[preacct]: module "preprocess" returns noop rlm_realm: No '@' in User-Name = "7961", looking up realm NULL rlm_realm: No such realm "NULL" modcall[preacct]: module "suffix" returns noop acct_users: Matched DEFAULT at 10 modcall[preacct]: module "files" returns okmodcall: group preacct returns okmodcall: entering group accountingrlm_acct_unique: WARNING: Attribute NAS-Port-Id was not found in request, unique ID MAY be inconsistentrlm_acct_unique: Hashing ',Client-IP-Address = b.19.174.239,NAS-IP-Address = b.19.174.239,Acct-Session-Id = "[email protected]",User-Name = "7961"'rlm_acct_unique: Acct-Unique-Session-ID = "b9b284f20f5f865e". modcall[accounting]: module "acct_unique" returns okradius_xlat: '/usr/local/var/log/radius/radacct/b.19.174.239/detail-20031015'rlm_detail: /usr/local/var/log/radius/radacct/%{Client-IP-Address}/detail-%Y%m%d expands to /usr/local/var/log/radius/radacct/b.19.174.239/detail-20031015 modcall[accounting]: module "detail" returns ok modcall[accounting]: module "unix" returns noopradius_xlat: '/usr/local/var/log/radius/radutmp'radius_xlat: '7961' rlm_radutmp: No NAS-Port seen. Cannot do anything. rlm_radumtp: WARNING: checkrad will probably not work! modcall[accounting]: module "radutmp" returns noopmodcall: group accounting returns okradius_xlat: '/path/to/exec/acct/stop'Exec-Program: /path/to/exec/acct/stop



Sending Accounting-Response of id 6 to b.19.174.239:36544Finished request 5Going to the next request


[Wed Oct 15 17:40:56 2003] sip_protocol.c(5393) Received 655 bytes UDP packet from a.22.77.248:50432 INVITE sip:7905@vvs-vitra SIP/2.0Via: SIP/2.0/UDP a.22.77.248:5060From: "(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f0000f0b70ee8f-06e54737To: <sip:7905@vvs-vitra>Call-ID: [email protected]: 101 INVITEUser-Agent: CSCO/4Contact: <sip:[email protected]:5060>Expires: 180Content-Type: application/sdpContent-Length: 245Accept: application/sdp


[Wed Oct 15 17:40:56 2003] sip_sm.c(998) Sent 286 bytes UDP packet to a.22.77.248:5060 SIP/2.0 100 TryingVia: SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248Call-ID: [email protected]: "(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f0000f0b70ee8f-06e54737To: <sip:7905@vvs-vitra>CSeq: 101 INVITEContent-Length: 0

[Wed Oct 15 17:40:56 2003] mod_sip_acct.c(630) Accounting event type: INVITE received from upstream, subtype: none

[Wed Oct 15 17:40:56 2003] sip_sm.c(828) TCB_PROXIED_STATE_TIMER : 180 seconds.[Wed Oct 15 17:40:56 2003] sip_sm.c(2057) Translation yielded 2 URLs :<sip:[email protected]:5060;user=phone;transport=udp>, <sip:[email protected]:5060;user=phone;transport=udp>[Wed Oct 15 17:40:56 2003] sip_dns.c(787) "A" Query for a.22.76.60 successful, Got 1 IP addresses[Wed Oct 15 17:40:56 2003] sip_dns.c(136) A Record : a.22.76.60[Wed Oct 15 17:40:56 2003] sip_sm.c(998) Sent 893 bytes UDP packet to a.22.76.60:5060 INVITE sip:[email protected]:5060;user=phone;transport=udp SIP/2.0Via: SIP/2.0/UDP b.19.174.239:5060;branch=f7ab66e0-a9f08f30-5b066032-b760acb8-1Record-Route: <sip:[email protected]:5060;maddr=b.19.174.239>Via: SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248From: "(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f0000f0b70ee8f-06e54737



To: <sip:7905@vvs-vitra>Call-ID: [email protected]: 101 INVITEUser-Agent: CSCO/4Contact: <sip:[email protected]:5060>Expires: 180Content-Type: application/sdpContent-Length: 245Accept: application/sdp


[Wed Oct 15 17:40:56 2003] mod_sip_acct.c(630) Accounting event type: INVITE sent downstream, subtype: none

[Wed Oct 15 17:40:56 2003] sip_dns.c(787) "A" Query for a.2.3.4 successful, Got 1 IP addresses[Wed Oct 15 17:40:56 2003] sip_dns.c(136) A Record : a.2.3.4[Wed Oct 15 17:40:56 2003] sip_sm.c(998) Sent 889 bytes UDP packet to a.2.3.4:5060 INVITE sip:[email protected]:5060;user=phone;transport=udp SIP/2.0Via: SIP/2.0/UDP b.19.174.239:5060;branch=f7ab66e0-a9f08f30-5b066032-b760acb8-2Record-Route: <sip:[email protected]:5060;maddr=b.19.174.239>Via: SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248From: "(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f0000f0b70ee8f-06e54737To: <sip:7905@vvs-vitra>Call-ID: [email protected]: 101 INVITEUser-Agent: CSCO/4Contact: <sip:[email protected]:5060>Expires: 180Content-Type: application/sdpContent-Length: 245Accept: application/sdp



[Wed Oct 15 17:40:56 2003] sip_protocol.c(5393) Received 486 bytes UDP packet from a.22.76.60:5060



SIP/2.0 100 TryingVia: SIP/2.0/UDP b.19.174.239:5060;branch=f7ab66e0-a9f08f30-5b066032-b760acb8-1Via: SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248From: "(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f0000f0b70ee8f-06e54737To: <sip:7905@vvs-vitra>;tag=1186552587Call-ID: [email protected]: 101 INVITEServer: Cisco-CP7905/1.01-030512AAllow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTERContent-Length: 0

[Wed Oct 15 17:40:56 2003] sip_sm.c(4820) Found existing TCB 0xf680b698[Wed Oct 15 17:40:56 2003] sip_protocol.c(5393) Received 489 bytes UDP packet from a.22.76.60:5060 SIP/2.0 486 Busy HereVia: SIP/2.0/UDP b.19.174.239:5060;branch=f7ab66e0-a9f08f30-5b066032-b760acb8-1Via: SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248From: "(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f0000f0b70ee8f-06e54737To: <sip:7905@vvs-vitra>;tag=1186552587Call-ID: [email protected]: 101 INVITEServer: Cisco-CP7905/1.01-030512AAllow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTERContent-Length: 0

[Wed Oct 15 17:40:56 2003] sip_sm.c(4820) Found existing TCB 0xf680b698[Wed Oct 15 17:40:56 2003] sip_sm.c(998) Sent 367 bytes UDP packet to a.22.76.60:5060 ACK sip:[email protected]:5060;user=phone;transport=udp SIP/2.0Via: SIP/2.0/UDP b.19.174.239:5060;branch=f7ab66e0-a9f08f30-5b066032-b760acb8-1Call-ID: [email protected]: "(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f0000f0b70ee8f-06e54737To: <sip:7905@vvs-vitra>;tag=1186552587CSeq: 101 ACKContent-Length: 0

[Wed Oct 15 17:40:56 2003] mod_sip_acct.c(630) Accounting event type: non-200 to INVITE received from downstream or locally generated, subtype: response received from downstream

[Wed Oct 15 17:40:56 2003] sip_radius.c(675) Building attr - NAS-IP-Address b.19.174.239

[Wed Oct 15 17:40:56 2003] [debug] sip_radius.c(806): Attr built as 4 () 4 - NAS-IP-Address 6 bytes

[Wed Oct 15 17:40:56 2003] [debug] sip_radius.c(594): 04 06 ac 13 ae ef [Wed Oct 15 17:40:56 2003] sip_radius.c(675) Building attr - NAS-Port-Type 5

[Wed Oct 15 17:40:56 2003] [debug] sip_radius.c(806): Attr built as 61 () 2 - NAS-Port-Type 6 bytes

[Wed Oct 15 17:40:56 2003] [debug] sip_radius.c(594): 3d 06 00 00 00 05 [Wed Oct 15 17:40:56 2003] sip_radius.c(675) Building attr - User-Name 7961

[Wed Oct 15 17:40:56 2003] [debug] sip_radius.c(806): Attr built as 1 () 1 - User-Name 6 bytes

[Wed Oct 15 17:40:56 2003] [debug] sip_radius.c(594):



01 06 37 39 36 31 [Wed Oct 15 17:40:56 2003] sip_radius.c(675) Building attr - Service-Type 1

[Wed Oct 15 17:40:56 2003] [debug] sip_radius.c(806): Attr built as 6 () 2 - Service-Type 6 bytes

[Wed Oct 15 17:40:56 2003] [debug] sip_radius.c(594): 06 06 00 00 00 01 [Wed Oct 15 17:40:56 2003] sip_radius.c(675) Building attr - Acct-Status-Type 2

[Wed Oct 15 17:40:56 2003] [debug] sip_radius.c(806): Attr built as 40 () 2 - Acct-Status-Type 6 bytes

[Wed Oct 15 17:40:56 2003] [debug] sip_radius.c(594): 28 06 00 00 00 02 [Wed Oct 15 17:40:56 2003] sip_radius.c(675) Building attr - Acct-Session-Id [email protected]

[Wed Oct 15 17:40:56 2003] [debug] sip_radius.c(806): Attr built as 44 () 1 - Acct-Session-Id 50 bytes

[Wed Oct 15 17:40:56 2003] [debug] sip_radius.c(594): 2c 32 30 30 33 30 39 34 63 34 2d 35 30 66 30 31 66 38 34 2d 34 33 35 66 63 64 32 34 2d 34 65 34 35 61 36 63 39 40 31 30 2e 32 32 2e 37 37 2e 32 34 38 [Wed Oct 15 17:40:56 2003] sip_radius.c(675) Building attr - Called-Station-Id <sip:7905@vvs-vitra>

[Wed Oct 15 17:40:56 2003] [debug] sip_radius.c(806): Attr built as 30 () 1 - Called-Station-Id 22 bytes

[Wed Oct 15 17:40:56 2003] [debug] sip_radius.c(594): 1e 16 3c 73 69 70 3a 37 39 30 35 40 76 76 73 2d 76 69 74 72 61 3e [Wed Oct 15 17:40:56 2003] sip_radius.c(675) Building attr - Calling-Station-Id "(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f0000f0b70ee8f-06e54737

[Wed Oct 15 17:40:56 2003] [debug] sip_radius.c(806): Attr built as 31 () 1 - Calling-Station-Id 78 bytes

[Wed Oct 15 17:40:56 2003] [debug] sip_radius.c(594): 1f 4e 22 28 76 76 73 2d 76 69 74 72 61 29 37 39 36 31 22 20 3c 73 69 70 3a 37 39 36 31 40 76 76 73 2d 76 69 74 72 61 3e 3b 74 61 67 3d 30 30 33 30 39 34 63 34 35 30 66 30 30 30 30 66 30 62 37 30 65 65 38 66 2d 30 36 65 35 34 37 33 37 [Wed Oct 15 17:40:56 2003] sip_radius.c(675) Building attr - h323-setup-time= 17:40:56.92 GMT Wed Oct 15 2003

[Wed Oct 15 17:40:56 2003] [debug] sip_radius.c(806): Attr built as 25 (VSA) 11 - h323-setup-time= 55 bytes

[Wed Oct 15 17:40:56 2003] [debug] sip_radius.c(594): 1a 37 00 00 00 09 19 31 68 33 32 33 2d 73 65 74 75 70 2d 74 69 6d 65 3d 31 37 3a 34 30 3a 35 36 2e 39 32 20 47 4d 54 20 57 65 64 20 4f 63 74 20 31 35 20 32 30 30 33 [Wed Oct 15 17:40:56 2003] sip_radius.c(675) Building attr - h323-disconnect-time= 17:40:56.125 GMT Wed Oct 15 2003

[Wed Oct 15 17:40:56 2003] [debug] sip_radius.c(806): Attr built as 29 (VSA) 11 - h323-disconnect-time= 61 bytes



[Wed Oct 15 17:40:56 2003] [debug] sip_radius.c(594): 1a 3d 00 00 00 09 1d 37 68 33 32 33 2d 64 69 73 63 6f 6e 6e 65 63 74 2d 74 69 6d 65 3d 31 37 3a 34 30 3a 35 36 2e 31 32 35 20 47 4d 54 20 57 65 64 20 4f 63 74 20 31 35 20 32 30 30 33 [Wed Oct 15 17:40:56 2003] sip_radius.c(675) Building attr - h323-call-origin= originate

[Wed Oct 15 17:40:56 2003] [debug] sip_radius.c(806): Attr built as 26 (VSA) 11 - h323-call-origin= 34 bytes

[Wed Oct 15 17:40:56 2003] [debug] sip_radius.c(594): 1a 22 00 00 00 09 1a 1c 68 33 32 33 2d 63 61 6c 6c 2d 6f 72 69 67 69 6e 3d 6f 72 69 67 69 6e 61 74 65 [Wed Oct 15 17:40:56 2003] sip_radius.c(675) Building attr - h323-call-type= VoIP

[Wed Oct 15 17:40:56 2003] [debug] sip_radius.c(806): Attr built as 27 (VSA) 11 - h323-call-type= 27 bytes

[Wed Oct 15 17:40:56 2003] [debug] sip_radius.c(594): 1a 1b 00 00 00 09 1b 15 68 33 32 33 2d 63 61 6c 6c 2d 74 79 70 65 3d 56 6f 49 50 [Wed Oct 15 17:40:56 2003] sip_radius.c(675) Building attr - sip-status-code= 486

[Wed Oct 15 17:40:56 2003] [debug] sip_radius.c(806): Attr built as 1 (VSA) 11 - sip-status-code= 27 bytes

[Wed Oct 15 17:40:56 2003] [debug] sip_radius.c(594): 1a 1b 00 00 00 09 01 15 73 69 70 2d 73 74 61 74 75 73 2d 63 6f 64 65 3d 34 38 36 [Wed Oct 15 17:40:56 2003] sip_radius.c(675) Building attr - session-protocol= sip

[Wed Oct 15 17:40:56 2003] [debug] sip_radius.c(806): Attr built as 1 (VSA) 11 - session-protocol= 28 bytes

[Wed Oct 15 17:40:56 2003] [debug] sip_radius.c(594): 1a 1c 00 00 00 09 01 16 73 65 73 73 69 6f 6e 2d 70 72 6f 74 6f 63 6f 6c 3d 73 69 70 [Wed Oct 15 17:40:56 2003] sip_radius.c(675) Building attr - call-id= [email protected]

[Wed Oct 15 17:40:56 2003] [debug] sip_radius.c(806): Attr built as 1 (VSA) 11 - call-id= 64 bytes

[Wed Oct 15 17:40:56 2003] [debug] sip_radius.c(594): 1a 40 00 00 00 09 01 3a 63 61 6c 6c 2d 69 64 3d 30 30 33 30 39 34 63 34 2d 35 30 66 30 31 66 38 34 2d 34 33 35 66 63 64 32 34 2d 34 65 34 35 61 36 63 39 40 31 30 2e 32 32 2e 37 37 2e 32 34 38

[Wed Oct 15 17:40:56 2003] sip_radius.c(675) Building attr - method= INVITE

[Wed Oct 15 17:40:56 2003] [debug] sip_radius.c(806): Attr built as 1 (VSA) 11 - method= 21 bytes

[Wed Oct 15 17:40:56 2003] [debug] sip_radius.c(594): 1a 15 00 00 00 09 01 0f 6d 65 74 68 6f 64 3d 49 4e 56 49 54 45 [Wed Oct 15 17:40:56 2003] sip_radius.c(675) Building attr - prev-hop-via= SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248

[Wed Oct 15 17:40:56 2003] [debug] sip_radius.c(806): Attr built as 1 (VSA) 11 - prev-hop-via= 72 bytes



[Wed Oct 15 17:40:56 2003] [debug] sip_radius.c(594): 1a 48 00 00 00 09 01 42 70 72 65 76 2d 68 6f 70 2d 76 69 61 3d 53 49 50 2f 32 2e 30 2f 55 44 50 20 31 30 2e 32 32 2e 37 37 2e 32 34 38 3a 35 30 36 30 3b 72 65 63 65 69 76 65 64 3d 31 30 2e 32 32 2e 37 37 2e 32 34 38 [Wed Oct 15 17:40:56 2003] sip_radius.c(675) Building attr - prev-hop-ip= a.22.77.248:5060

[Wed Oct 15 17:40:56 2003] [debug] sip_radius.c(806): Attr built as 1 (VSA) 11 - prev-hop-ip= 37 bytes

[Wed Oct 15 17:40:56 2003] [debug] sip_radius.c(594): 1a 25 00 00 00 09 01 1f 70 72 65 76 2d 68 6f 70 2d 69 70 3d 31 30 2e 32 32 2e 37 37 2e 32 34 38 3a 35 30 36 30 [Wed Oct 15 17:40:56 2003] sip_radius.c(675) Building attr - incoming-req-uri= sip:7905@vvs-vitra

[Wed Oct 15 17:40:56 2003] [debug] sip_radius.c(806): Attr built as 1 (VSA) 11 - incoming-req-uri= 43 bytes

[Wed Oct 15 17:40:56 2003] [debug] sip_radius.c(594): 1a 2b 00 00 00 09 01 25 69 6e 63 6f 6d 69 6e 67 2d 72 65 71 2d 75 72 69 3d 73 69 70 3a 37 39 30 35 40 76 76 73 2d 76 69 74 72 61 [Wed Oct 15 17:40:56 2003] sip_radius.c(675) Building attr - outgoing-req-uri= sip:[email protected]:5060;user=phone;transport=udp

[Wed Oct 15 17:40:56 2003] [debug] sip_radius.c(806): Attr built as 1 (VSA) 11 - outgoing-req-uri= 75 bytes

[Wed Oct 15 17:40:56 2003] [debug] sip_radius.c(594): 1a 4b 00 00 00 09 01 45 6f 75 74 67 6f 69 6e 67 2d 72 65 71 2d 75 72 69 3d 73 69 70 3a 37 39 30 35 40 31 30 2e 32 32 2e 37 36 2e 36 30 3a 35 30 36 30 3b 75 73 65 72 3d 70 68 6f 6e 65 3b 74 72 61 6e 73 70 6f 72 74 3d 75 64 70 [Wed Oct 15 17:40:56 2003] sip_radius.c(675) Building attr - next-hop-ip= a.22.76.60:5060

[Wed Oct 15 17:40:56 2003] [debug] sip_radius.c(806): Attr built as 1 (VSA) 11 - next-hop-ip= 36 bytes

[Wed Oct 15 17:40:56 2003] [debug] sip_radius.c(594): 1a 24 00 00 00 09 01 1e 6e 65 78 74 2d 68 6f 70 2d 69 70 3d 31 30 2e 32 32 2e 37 36 2e 36 30 3a 35 30 36 30 [Wed Oct 15 17:40:56 2003] sip_radius.c(675) Building attr - sip-hdr= From: "(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f0000f0b70ee8f-06e54737

[Wed Oct 15 17:40:56 2003] [debug] sip_radius.c(806): Attr built as 1 (VSA) 11 - sip-hdr= 98 bytes

[Wed Oct 15 17:40:56 2003] [debug] sip_radius.c(594): 1a 62 00 00 00 09 01 5c 73 69 70 2d 68 64 72 3d 46 72 6f 6d 3a 20 22 28 76 76 73 2d 76 69 74 72 61 29 37 39 36 31 22 20 3c 73 69 70 3a 37 39 36 31 40 76 76 73 2d 76 69 74 72 61 3e 3b 74 61 67 3d 30 30 33 30 39 34 63 34 35 30 66 30 30 30 30 66 30 62 37 30 65 65 38 66 2d 30 36 65 35 34 37 33 37 [Wed Oct 15 17:40:56 2003] sip_radius.c(675) Building attr - sip-hdr= To: <sip:7905@vvs-vitra>;tag=1186552587




[Wed Oct 15 17:40:56 2003] [debug] sip_radius.c(594): 1a 37 00 00 00 09 01 31 73 69 70 2d 68 64 72 3d 54 6f 3a 20 3c 73 69 70 3a 37 39 30 35 40 76 76 73 2d 76 69 74 72 61 3e 3b 74 61 67 3d 31 31 38 36 35 35 32 35 38 37 [Wed Oct 15 17:40:56 2003] sip_radius.c(675) Building attr - sip-hdr= CSeq: 101 INVITE


[Wed Oct 15 17:40:56 2003] [debug] sip_radius.c(594): 1a 20 00 00 00 09 01 1a 73 69 70 2d 68 64 72 3d 43 53 65 71 3a 20 31 30 31 20 49 4e 56 49 54 45

[Wed Oct 15 17:40:56 2003] sip_radius.c(1115) Radius: max number of servers to use is 2.[Wed Oct 15 17:40:56 2003] sip_radius.c(1120) Radius: Start with server 1.[Wed Oct 15 17:40:56 2003] sip_radius.c(852) Radius: The RA is:[Wed Oct 15 17:40:56 2003] [debug] sip_radius.c(594): 5e 6f 22 ad ac 98 83 52 21 cc ad b4 ed d0 20 fa

[Wed Oct 15 17:40:56 2003] sip_radius.c(1222) Radius: To send 965 bytes in request to b.19.174.128:1813.[Wed Oct 15 17:40:56 2003] [debug] sip_radius.c(594): 04 01 03 c5 5e 6f 22 ad ac 98 83 52 21 cc ad b4 ed d0 20 fa 04 06 ac 13 ae ef 3d 06 00 00 00 05 01 06 37 39 36 31 06 06 00 00 00 01 28 06 00 00 00 02 2c 32 30 30 33 30 39 34 63 34 2d 35 30 66 30 31 66 38 34 2d 34 33 35 66 63 64 32 34 2d 34 65 34 35 61 36 63 39 40 31 30 2e 32 32 2e 37 37 2e 32 34 38 1e 16 3c 73 69 70 3a 37 39 30 35 40 76 76 73 2d 76 69 74 72 61 3e 1f 4e 22 28 76 76 73 2d 76 69 74 72 61 29 37 39 36 31 22 20 3c 73 69 70 3a 37 39 36 31 40 76 76 73 2d 76 69 74 72 61 3e 3b 74 61 67 3d 30 30 33 30 39 34 63 34 35 30 66 30 30 30 30 66 30 62 37 30 65 65 38 66 2d 30 36 65 35 34 37 33 37 1a 37 00 00 00 09 19 31 68 33 32 33 2d 73 65 74 75 70 2d 74 69 6d 65 3d 31 37 3a 34 30 3a 35 36 2e 39 32 20 47 4d 54 20 57 65 64 20 4f 63 74 20 31 35 20 32 30 30 33 1a 3d 00 00 00 09 1d 37 68 33 32 33 2d 64 69 73 63 6f 6e 6e 65 63 74 2d 74 69 6d 65 3d 31 37 3a 34 30 3a 35 36 2e 31 32 35 20 47 4d 54 20 57 65 64 20 4f 63 74 20 31 35 20 32 30 30 33 1a 22 00 00 00 09 1a 1c 68 33 32 33 2d 63 61 6c 6c 2d 6f 72 69 67 69 6e 3d 6f 72 69 67 69 6e 61 74 65 1a 1b 00 00 00 09 1b 15 68 33 32 33 2d 63 61 6c 6c 2d 74 79 70 65 3d 56 6f 49 50 1a 1b 00 00 00 09 01 15 73 69 70 2d 73 74 61 74 75 73 2d 63 6f 64 65 3d 34 38 36 1a 1c 00 00 00 09 01 16 73 65 73 73 69 6f 6e 2d 70 72 6f 74 6f 63 6f 6c 3d 73 69 70 1a 40 00 00 00 09 01 3a 63 61 6c 6c 2d 69 64 3d 30 30 33 30 39 34 63 34 2d 35 30 66 30 31 66 38 34 2d 34 33 35 66 63 64 32 34 2d 34 65 34 35 61 36 63 39 40 31 30 2e 32 32 2e 37 37 2e 32 34 38 1a 15 00 00 00 09 01 0f 6d 65 74 68 6f 64 3d 49 4e 56 49 54 45 1a 48 00 00 00 09 01 42 70 72 65 76 2d 68 6f 70 2d 76 69 61 3d 53 49 50 2f 32 2e 30 2f 55 44 50 20 31 30 2e 32 32 2e 37 37 2e 32 34 38 3a 35 30 36 30 3b 72 65 63 65 69 76 65 64 3d 31 30 2e 32 32 2e 37 37 2e 32 34 38 1a 25 00 00 00 09 01 1f 70 72 65 76 2d 68 6f 70 2d 69 70



3d 31 30 2e 32 32 2e 37 37 2e 32 34 38 3a 35 30 36 30 1a 2b 00 00 00 09 01 25 69 6e 63 6f 6d 69 6e 67 2d 72 65 71 2d 75 72 69 3d 73 69 70 3a 37 39 30 35 40 76 76 73 2d 76 69 74 72 61 1a 4b 00 00 00 09 01 45 6f 75 74 67 6f 69 6e 67 2d 72 65 71 2d 75 72 69 3d 73 69 70 3a 37 39 30 35 40 31 30 2e 32 32 2e 37 36 2e 36 30 3a 35 30 36 30 3b 75 73 65 72 3d 70 68 6f 6e 65 3b 74 72 61 6e 73 70 6f 72 74 3d 75 64 70 1a 24 00 00 00 09 01 1e 6e 65 78 74 2d 68 6f 70 2d 69 70 3d 31 30 2e 32 32 2e 37 36 2e 36 30 3a 35 30 36 30 1a 62 00 00 00 09 01 5c 73 69 70 2d 68 64 72 3d 46 72 6f 6d 3a 20 22 28 76 76 73 2d 76 69 74 72 61 29 37 39 36 31 22 20 3c 73 69 70 3a 37 39 36 31 40 76 76 73 2d 76 69 74 72 61 3e 3b 74 61 67 3d 30 30 33 30 39 34 63 34 35 30 66 30 30 30 30 66 30 62 37 30 65 65 38 66 2d 30 36 65 35 34 37 33 37 1a 37 00 00 00 09 01 31 73 69 70 2d 68 64 72 3d 54 6f 3a 20 3c 73 69 70 3a 37 39 30 35 40 76 76 73 2d 76 69 74 72 61 3e 3b 74 61 67 3d 31 31 38 36 35 35 32 35 38 37 1a 20 00 00 00 09 01 1a 73 69 70 2d 68 64 72 3d 43 53 65 71 3a 20 31 30 31 20 49 4e 56 49 54 45 [Wed Oct 15 17:40:56 2003] sip_radius.c(1300) Radius: read 20 bytes in response from b.19.174.128:1813.[Wed Oct 15 17:40:56 2003] [debug] sip_radius.c(594): 05 01 00 14 e7 d5 dd 82 77 1c 90 18 84 6c c2 dc 8f bb d5 62 [Wed Oct 15 17:40:56 2003] sip_radius.c(1410) Radius: server 1 responded with Accept. Mark it for next time use.[Wed Oct 15 17:40:56 2003] mod_sip_call_forward.c(1200) cfb_received_response_handler(): branch_count=2 (tcb=0xf680b698)

[Wed Oct 15 17:40:56 2003] sip_dns.c(787) "A" Query for b.23.252.22 successful, Got 1 IP addresses[Wed Oct 15 17:40:56 2003] sip_dns.c(136) A Record : b.23.252.22[Wed Oct 15 17:40:56 2003] sip_sm.c(998) Sent 922 bytes UDP packet to b.23.252.22:5060 INVITE sip:[email protected] SIP/2.0Via: SIP/2.0/UDP b.19.174.239:5060;branch=f7ab66e0-a9f08f30-5b066032-b760acb8-3CC-Diversion: <sip:7905@vvs-vitra>;reason=user-busyRecord-Route: <sip:[email protected]:5060;maddr=b.19.174.239>Via: SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248From: "(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f0000f0b70ee8f-06e54737To: <sip:7905@vvs-vitra>Call-ID: [email protected]: 101 INVITEUser-Agent: CSCO/4Contact: <sip:[email protected]:5060>Expires: 180Content-Type: application/sdpContent-Length: 245Accept: application/sdp

v=0o=Cisco-SIPUA 9616 1172 IN IP4 a.22.77.248s=SIP Callc=IN IP4 a.22.77.248t=0 0m=audio 31880 RTP/AVP 0 8 18 101a=rtpmap:0 PCMU/8000a=rtpmap:8 PCMA/8000a=rtpmap:18 G729/8000a=rtpmap:101 telephone-event/8000



a=fmtp:101 0-15


[Wed Oct 15 17:40:56 2003] sip_protocol.c(5393) Received 484 bytes UDP packet from b.23.252.22:5060 SIP/2.0 100 TryingVia: SIP/2.0/UDP b.19.174.239:5060;branch=f7ab66e0-a9f08f30-5b066032-b760acb8-3,SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248From: "(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f0000f0b70ee8f-06e54737To: <sip:7905@vvs-vitra>;tag=CD0A90CC-20BCDate: Wed, 15 Oct 2003 17:47:33 GMTCall-ID: [email protected]: Cisco-SIPGateway/IOS-12.xCSeq: 101 INVITEAllow-Events: telephone-eventContent-Length: 0

[Wed Oct 15 17:40:56 2003] sip_sm.c(4820) Found existing TCB 0xf680b698[Wed Oct 15 17:40:56 2003] sip_protocol.c(5393) Received 782 bytes UDP packet from b.23.252.22:5060 SIP/2.0 183 Session ProgressVia: SIP/2.0/UDP b.19.174.239:5060;branch=f7ab66e0-a9f08f30-5b066032-b760acb8-3,SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248From: "(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f0000f0b70ee8f-06e54737To: <sip:7905@vvs-vitra>;tag=CD0A90CC-20BCDate: Wed, 15 Oct 2003 17:47:33 GMTCall-ID: [email protected]: Cisco-SIPGateway/IOS-12.xCSeq: 101 INVITEAllow-Events: telephone-eventContent-Type: application/sdpContent-Disposition: session;handling=requiredContent-Length: 207

v=0o=CiscoSystemsSIP-GW-UserAgent 3596 8875 IN IP4 b.23.252.22s=SIP Callc=IN IP4 b.23.252.22t=0 0m=audio 18444 RTP/AVP 0 100a=rtpmap:0 PCMU/8000a=rtpmap:100 X-NSE/8000a=fmtp:100 192-194

[Wed Oct 15 17:40:56 2003] sip_sm.c(4820) Found existing TCB 0xf680b698[Wed Oct 15 17:40:56 2003] sip_sm.c(998) Sent 707 bytes UDP packet to a.22.77.248:5060 SIP/2.0 183 Session Progress Via: SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248From: "(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f0000f0b70ee8f-06e54737To: <sip:7905@vvs-vitra>;tag=CD0A90CC-20BCDate: Wed, 15 Oct 2003 17:47:33 GMTCall-ID: [email protected]: Cisco-SIPGateway/IOS-12.xCSeq: 101 INVITEAllow-Events: telephone-eventContent-Type: application/sdp



Content-Disposition: session;handling=requiredContent-Length: 207


[Wed Oct 15 17:40:56 2003] sip_sm.c(998) Sent 889 bytes UDP packet to a.2.3.4:5060 INVITE sip:[email protected]:5060;user=phone;transport=udp SIP/2.0Via: SIP/2.0/UDP b.19.174.239:5060;branch=f7ab66e0-a9f08f30-5b066032-b760acb8-2Record-Route: <sip:[email protected]:5060;maddr=b.19.174.239>Via: SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248From: "(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f0000f0b70ee8f-06e54737To: <sip:7905@vvs-vitra>Call-ID: [email protected]: 101 INVITEUser-Agent: CSCO/4Contact: <sip:[email protected]:5060>Expires: 180Content-Type: application/sdpContent-Length: 245Accept: application/sdp


[Wed Oct 15 17:40:58 2003] sip_sm.c(998) Sent 889 bytes UDP packet to a.2.3.4:5060 INVITE sip:[email protected]:5060;user=phone;transport=udp SIP/2.0Via: SIP/2.0/UDP b.19.174.239:5060;branch=f7ab66e0-a9f08f30-5b066032-b760acb8-2Record-Route: <sip:[email protected]:5060;maddr=b.19.174.239>Via: SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248From: "(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f0000f0b70ee8f-06e54737To: <sip:7905@vvs-vitra>Call-ID: [email protected]: 101 INVITEUser-Agent: CSCO/4Contact: <sip:[email protected]:5060>Expires: 180Content-Type: application/sdpContent-Length: 245Accept: application/sdp

v=0o=Cisco-SIPUA 9616 1172 IN IP4 a.22.77.248s=SIP Call



c=IN IP4 a.22.77.248t=0 0m=audio 31880 RTP/AVP 0 8 18 101a=rtpmap:0 PCMU/8000a=rtpmap:8 PCMA/8000a=rtpmap:18 G729/8000a=rtpmap:101 telephone-event/8000a=fmtp:101 0-15

[Wed Oct 15 17:41:00 2003] sip_sm.c(2689) cannot failover, not routes available[Wed Oct 15 17:41:00 2003] mod_sip_acct.c(630) Accounting event type: non-200 to INVITE received from downstream or locally generated, subtype: local response on a branch







[Wed Oct 15 17:41:00 2003] [debug] sip_radius.c(594): 01 06 37 39 36 31 [Wed Oct 15 17:41:00 2003] sip_radius.c(675) Building attr - Service-Type 1














[Wed Oct 15 17:41:00 2003] [debug] sip_radius.c(594): 1a 37 00 00 00 09 19 31 68 33 32 33 2d 73 65 74 75 70 2d 74 69 6d 65 3d 31 37 3a 34 30 3a 35 36 2e 39 33 20 47 4d 54 20 57 65 64 20 4f 63 74 20 31 35 20 32 30 30 33 [Wed Oct 15 17:41:00 2003] sip_radius.c(675) Building attr - h323-disconnect-time= 17:41:00.461 GMT Wed Oct 15 2003








[Wed Oct 15 17:41:00 2003] [debug] sip_radius.c(594): 1a 1b 00 00 00 09 01 15 73 69 70 2d 73 74 61 74



75 73 2d 63 6f 64 65 3d 34 30 38 [Wed Oct 15 17:41:00 2003] sip_radius.c(675) Building attr - session-protocol= sip













[Wed Oct 15 17:41:00 2003] [debug] sip_radius.c(594): 1a 2b 00 00 00 09 01 25 69 6e 63 6f 6d 69 6e 67 2d 72 65 71 2d 75 72 69 3d 73 69 70 3a 37 39 30 35 40 76 76 73 2d 76 69 74 72 61 [Wed Oct 15 17:41:00 2003] sip_radius.c(675) Building attr - outgoing-req-uri= sip:[email protected]:5060;user=phone;transport=udp




[Wed Oct 15 17:41:00 2003] [debug] sip_radius.c(594): 1a 47 00 00 00 09 01 41 6f 75 74 67 6f 69 6e 67 2d 72 65 71 2d 75 72 69 3d 73 69 70 3a 37 39 30 35 40 31 2e 32 2e 33 2e 34 3a 35 30 36 30 3b 75 73 65 72 3d 70 68 6f 6e 65 3b 74 72 61 6e 73 70 6f 72 74 3d 75 64 70 [Wed Oct 15 17:41:00 2003] sip_radius.c(675) Building attr - next-hop-ip= a.2.3.4:5060


[Wed Oct 15 17:41:00 2003] [debug] sip_radius.c(594): 1a 20 00 00 00 09 01 1a 6e 65 78 74 2d 68 6f 70 2d 69 70 3d 31 2e 32 2e 33 2e 34 3a 35 30 36 30

[Wed Oct 15 17:41:00 2003] sip_radius.c(675) Building attr - sip-hdr= From: "(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f0000f0b70ee8f-06e54737


[Wed Oct 15 17:41:00 2003] [debug] sip_radius.c(594): 1a 62 00 00 00 09 01 5c 73 69 70 2d 68 64 72 3d 46 72 6f 6d 3a 20 22 28 76 76 73 2d 76 69 74 72 61 29 37 39 36 31 22 20 3c 73 69 70 3a 37 39 36 31 40 76 76 73 2d 76 69 74 72 61 3e 3b 74 61 67 3d 30 30 33 30 39 34 63 34 35 30 66 30 30 30 30 66 30 62 37 30 65 65 38 66 2d 30 36 65 35 34 37 33 37 [Wed Oct 15 17:41:00 2003] sip_radius.c(675) Building attr - sip-hdr= To: <sip:7905@vvs-vitra>;tag=28b4-313c


[Wed Oct 15 17:41:00 2003] [debug] sip_radius.c(594): 1a 36 00 00 00 09 01 30 73 69 70 2d 68 64 72 3d 54 6f 3a 20 3c 73 69 70 3a 37 39 30 35 40 76 76 73 2d 76 69 74 72 61 3e 3b 74 61 67 3d 32 38 62 34 2d 33 31 33 63 [Wed Oct 15 17:41:00 2003] sip_radius.c(675) Building attr - sip-hdr= CSeq: 101 INVITE



[Wed Oct 15 17:41:00 2003] sip_radius.c(1115) Radius: max number of servers to use is 2.[Wed Oct 15 17:41:00 2003] sip_radius.c(1120) Radius: Start with server 1.[Wed Oct 15 17:41:00 2003] sip_radius.c(852) Radius: The RA is:[Wed Oct 15 17:41:00 2003] [debug] sip_radius.c(594): 3e 10 c0 ae 10 ec 6d 15 69 18 b1 2c d8 ec d0 8f

[Wed Oct 15 17:41:00 2003] sip_radius.c(1222) Radius: To send 956 bytes in request to b.19.174.128:1813.[Wed Oct 15 17:41:00 2003] [debug] sip_radius.c(594): 04 02 03 bc 3e 10 c0 ae 10 ec 6d 15 69 18 b1 2c d8 ec d0 8f 04 06 ac 13 ae ef 3d 06 00 00 00 05 01 06 37 39 36 31 06 06 00 00 00 01 28 06 00 00



00 02 2c 32 30 30 33 30 39 34 63 34 2d 35 30 66 30 31 66 38 34 2d 34 33 35 66 63 64 32 34 2d 34 65 34 35 61 36 63 39 40 31 30 2e 32 32 2e 37 37 2e 32 34 38 1e 16 3c 73 69 70 3a 37 39 30 35 40 76 76 73 2d 76 69 74 72 61 3e 1f 4e 22 28 76 76 73 2d 76 69 74 72 61 29 37 39 36 31 22 20 3c 73 69 70 3a 37 39 36 31 40 76 76 73 2d 76 69 74 72 61 3e 3b 74 61 67 3d 30 30 33 30 39 34 63 34 35 30 66 30 30 30 30 66 30 62 37 30 65 65 38 66 2d 30 36 65 35 34 37 33 37 1a 37 00 00 00 09 19 31 68 33 32 33 2d 73 65 74 75 70 2d 74 69 6d 65 3d 31 37 3a 34 30 3a 35 36 2e 39 33 20 47 4d 54 20 57 65 64 20 4f 63 74 20 31 35 20 32 30 30 33 1a 3d 00 00 00 09 1d 37 68 33 32 33 2d 64 69 73 63 6f 6e 6e 65 63 74 2d 74 69 6d 65 3d 31 37 3a 34 31 3a 30 30 2e 34 36 31 20 47 4d 54 20 57 65 64 20 4f 63 74 20 31 35 20 32 30 30 33 1a 22 00 00 00 09 1a 1c 68 33 32 33 2d 63 61 6c 6c 2d 6f 72 69 67 69 6e 3d 6f 72 69 67 69 6e 61 74 65 1a 1b 00 00 00 09 1b 15 68 33 32 33 2d 63 61 6c 6c 2d 74 79 70 65 3d 56 6f 49 50 1a 1b 00 00 00 09 01 15 73 69 70 2d 73 74 61 74 75 73 2d 63 6f 64 65 3d 34 30 38 1a 1c 00 00 00 09 01 16 73 65 73 73 69 6f 6e 2d 70 72 6f 74 6f 63 6f 6c 3d 73 69 70 1a 40 00 00 00 09 01 3a 63 61 6c 6c 2d 69 64 3d 30 30 33 30 39 34 63 34 2d 35 30 66 30 31 66 38 34 2d 34 33 35 66 63 64 32 34 2d 34 65 34 35 61 36 63 39 40 31 30 2e 32 32 2e 37 37 2e 32 34 38 1a 15 00 00 00 09 01 0f 6d 65 74 68 6f 64 3d 49 4e 56 49 54 45 1a 48 00 00 00 09 01 42 70 72 65 76 2d 68 6f 70 2d 76 69 61 3d 53 49 50 2f 32 2e 30 2f 55 44 50 20 31 30 2e 32 32 2e 37 37 2e 32 34 38 3a 35 30 36 30 3b 72 65 63 65 69 76 65 64 3d 31 30 2e 32 32 2e 37 37 2e 32 34 38 1a 25 00 00 00 09 01 1f 70 72 65 76 2d 68 6f 70 2d 69 70 3d 31 30 2e 32 32 2e 37 37 2e 32 34 38 3a 35 30 36 30 1a 2b 00 00 00 09 01 25 69 6e 63 6f 6d 69 6e 67 2d 72 65 71 2d 75 72 69 3d 73 69 70 3a 37 39 30 35 40 76 76 73 2d 76 69 74 72 61 1a 47 00 00 00 09 01 41 6f 75 74 67 6f 69 6e 67 2d 72 65 71 2d 75 72 69 3d 73 69 70 3a 37 39 30 35 40 31 2e 32 2e 33 2e 34 3a 35 30 36 30 3b 75 73 65 72 3d 70 68 6f 6e 65 3b 74 72 61 6e 73 70 6f 72 74 3d 75 64 70 1a 20 00 00 00 09 01 1a 6e 65 78 74 2d 68 6f 70 2d 69 70 3d 31 2e 32 2e 33 2e 34 3a 35 30 36 30 1a 62 00 00 00 09 01 5c 73 69 70 2d 68 64 72 3d 46 72 6f 6d 3a 20 22 28 76 76 73 2d 76 69 74 72 61 29 37 39 36 31 22 20 3c 73 69 70 3a 37 39 36 31 40 76 76 73 2d 76 69 74 72 61 3e 3b 74 61 67 3d 30 30 33 30 39 34 63 34 35 30 66 30 30 30 30 66 30 62 37 30 65 65 38 66 2d 30 36 65 35 34 37 33 37 1a 36 00 00 00 09 01 30 73 69 70 2d 68 64 72 3d 54 6f 3a 20 3c 73 69 70 3a 37 39 30 35 40 76 76 73 2d 76 69 74 72 61 3e 3b 74 61 67 3d 32 38 62 34 2d 33 31 33 63 1a 20 00 00 00 09 01 1a 73 69 70 2d 68 64 72 3d 43 53 65 71 3a 20 31 30 31 20 49 4e 56 49 54 45 [Wed Oct 15 17:41:00 2003] sip_radius.c(1300) Radius: read 20 bytes in response from b.19.174.128:1813.[Wed Oct 15 17:41:00 2003] [debug] sip_radius.c(594): 05 02 00 14 dc 36 ee 93 0f 42 cf 6b 3a 19 da f5 d7 5e 82 de [Wed Oct 15 17:41:00 2003] sip_radius.c(1410) Radius: server 1 responded with Accept. Mark it for next time use.



[Wed Oct 15 17:41:08 2003] sip_protocol.c(5393) Received 953 bytes UDP packet from b.23.252.22:5060 SIP/2.0 200 OKVia: SIP/2.0/UDP b.19.174.239:5060;branch=f7ab66e0-a9f08f30-5b066032-b760acb8-3,SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248From: "(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f0000f0b70ee8f-06e54737To: <sip:7905@vvs-vitra>;tag=CD0A90CC-20BCDate: Wed, 15 Oct 2003 17:47:33 GMTCall-ID: [email protected]: Cisco-SIPGateway/IOS-12.xCSeq: 101 INVITEAllow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBSCRIBE, NOTIFY, INFOAllow-Events: telephone-eventContact: <sip:[email protected]:5060>Record-Route: <sip:[email protected]:5060;maddr=b.19.174.239>Content-Type: application/sdpContent-Length: 207


[Wed Oct 15 17:41:08 2003] sip_sm.c(4820) Found existing TCB 0xf680b698[Wed Oct 15 17:41:08 2003] mod_sip_acct.c(630) Accounting event type: 200 to INVITE received from downstream, subtype: response received from downstream





















[Wed Oct 15 17:41:08 2003] [debug] sip_radius.c(594): 1a 38 00 00 00 09 19 32 68 33 32 33 2d 73 65 74 75 70 2d 74 69 6d 65 3d 31 37 3a 34 30 3a 35 36 2e 31 34 36 20 47 4d 54 20 57 65 64 20 4f 63 74 20 31 35 20 32 30 30 33 [Wed Oct 15 17:41:08 2003] sip_radius.c(675) Building attr - h323-connect-time= 17:41:08.685 GMT Wed Oct 15 2003

[Wed Oct 15 17:41:08 2003] [debug] sip_radius.c(806): Attr built as 28 (VSA) 11 - h323-connect-time= 58 bytes

[Wed Oct 15 17:41:08 2003] [debug] sip_radius.c(594): 1a 3a 00 00 00 09 1c 34 68 33 32 33 2d 63 6f 6e 6e 65 63 74 2d 74 69 6d 65 3d 31 37 3a 34 31 3a 30 38 2e 36 38 35 20 47 4d 54 20 57 65 64 20 4f 63 74 20 31 35 20 32 30 30 33 [Wed Oct 15 17:41:08 2003] sip_radius.c(675) Building attr - h323-call-origin= originate







[Wed Oct 15 17:41:08 2003] [debug] sip_radius.c(594): 1a 2b 00 00 00 09 01 25 69 6e 63 6f 6d 69 6e 67 2d 72 65 71 2d 75 72 69 3d 73 69 70 3a 37 39 30 35 40 76 76 73 2d 76 69 74 72 61 [Wed Oct 15 17:41:08 2003] sip_radius.c(675) Building attr - outgoing-req-uri= sip:[email protected]


[Wed Oct 15 17:41:08 2003] [debug] sip_radius.c(594): 1a 33 00 00 00 09 01 2d 6f 75 74 67 6f 69 6e 67 2d 72 65 71 2d 75 72 69 3d 73 69 70 3a 39 39 30 32 33 31 32 36 40 31 37 32 2e 32 33 2e 32 35 32 2e 32 32 [Wed Oct 15 17:41:08 2003] sip_radius.c(675) Building attr - next-hop-ip= b.23.252.22:5060


[Wed Oct 15 17:41:08 2003] [debug] sip_radius.c(594): 1a 26 00 00 00 09 01 20 6e 65 78 74 2d 68 6f 70 2d 69 70 3d 31 37 32 2e 32 33 2e 32 35 32 2e 32 32 3a 35 30 36 30 [Wed Oct 15 17:41:08 2003] sip_radius.c(675) Building attr - sip-hdr= From: "(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f0000f0b70ee8f-06e54737


[Wed Oct 15 17:41:08 2003] [debug] sip_radius.c(594): 1a 62 00 00 00 09 01 5c 73 69 70 2d 68 64 72 3d 46 72 6f 6d 3a 20 22 28 76 76 73 2d 76 69 74 72 61 29 37 39 36 31 22 20 3c 73 69 70 3a 37 39 36 31 40 76 76 73 2d 76 69 74 72 61 3e 3b 74 61 67 3d 30 30 33 30 39 34 63 34 35 30 66 30 30 30 30 66 30 62 37 30 65 65 38 66 2d 30 36 65 35 34 37 33 37 [Wed Oct 15 17:41:08 2003] sip_radius.c(675) Building attr - sip-hdr= To: <sip:7905@vvs-vitra>;tag=CD0A90CC-20BC


[Wed Oct 15 17:41:08 2003] [debug] sip_radius.c(594): 1a 3a 00 00 00 09 01 34 73 69 70 2d 68 64 72 3d 54 6f 3a 20 3c 73 69 70 3a 37 39 30 35 40 76 76 73 2d 76 69 74 72 61 3e 3b 74 61 67 3d 43 44 30 41 39 30 43 43 2d 32 30 42 43 [Wed Oct 15 17:41:08 2003] sip_radius.c(675) Building attr - sip-hdr= CSeq: 101 INVITE





[Wed Oct 15 17:41:08 2003] sip_radius.c(1115) Radius: max number of servers to use is 2.[Wed Oct 15 17:41:08 2003] sip_radius.c(1120) Radius: Start with server 1.[Wed Oct 15 17:41:08 2003] sip_radius.c(852) Radius: The RA is:[Wed Oct 15 17:41:08 2003] [debug] sip_radius.c(594): 65 10 d3 17 a0 93 e3 1d 35 89 35 26 a6 5c d0 cb

[Wed Oct 15 17:41:08 2003] sip_radius.c(1222) Radius: To send 944 bytes in request to b.19.174.128:1813.[Wed Oct 15 17:41:08 2003] [debug] sip_radius.c(594): 04 03 03 b0 65 10 d3 17 a0 93 e3 1d 35 89 35 26 a6 5c d0 cb 04 06 ac 13 ae ef 3d 06 00 00 00 05 01 06 37 39 36 31 06 06 00 00 00 01 28 06 00 00 00 01 2c 32 30 30 33 30 39 34 63 34 2d 35 30 66 30 31 66 38 34 2d 34 33 35 66 63 64 32 34 2d 34 65 34 35 61 36 63 39 40 31 30 2e 32 32 2e 37 37 2e 32 34 38 1e 16 3c 73 69 70 3a 37 39 30 35 40 76 76 73 2d 76 69 74 72 61 3e 1f 4e 22 28 76 76 73 2d 76 69 74 72 61 29 37 39 36 31 22 20 3c 73 69 70 3a 37 39 36 31 40 76 76 73 2d 76 69 74 72 61 3e 3b 74 61 67 3d 30 30 33 30 39 34 63 34 35 30 66 30 30 30 30 66 30 62 37 30 65 65 38 66 2d 30 36 65 35 34 37 33 37 1a 38 00 00 00 09 19 32 68 33 32 33 2d 73 65 74 75 70 2d 74 69 6d 65 3d 31 37 3a 34 30 3a 35 36 2e 31 34 36 20 47 4d 54 20 57 65 64 20 4f 63 74 20 31 35 20 32 30 30 33 1a 3a 00 00 00 09 1c 34 68 33 32 33 2d 63 6f 6e 6e 65 63 74 2d 74 69 6d 65 3d 31 37 3a 34 31 3a 30 38 2e 36 38 35 20 47 4d 54 20 57 65 64 20 4f 63 74 20 31 35 20 32 30 30 33 1a 22 00 00 00 09 1a 1c 68 33 32 33 2d 63 61 6c 6c 2d 6f 72 69 67 69 6e 3d 6f 72 69 67 69 6e 61 74 65 1a 1b 00 00 00 09 1b 15 68 33 32 33 2d 63 61 6c 6c 2d 74 79 70 65 3d 56 6f 49 50 1a 1b 00 00 00 09 01 15 73 69 70 2d 73 74 61 74 75 73 2d 63 6f 64 65 3d 32 30 30 1a 1c 00 00 00 09 01 16 73 65 73 73 69 6f 6e 2d 70 72 6f 74 6f 63 6f 6c 3d 73 69 70 1a 40 00 00 00 09 01 3a 63 61 6c 6c 2d 69 64 3d 30 30 33 30 39 34 63 34 2d 35 30 66 30 31 66 38 34 2d 34 33 35 66 63 64 32 34 2d 34 65 34 35 61 36 63 39 40 31 30 2e 32 32 2e 37 37 2e 32 34 38 1a 15 00 00 00 09 01 0f 6d 65 74 68 6f 64 3d 49 4e 56 49 54 45 1a 48 00 00 00 09 01 42 70 72 65 76 2d 68 6f 70 2d 76 69 61 3d 53 49 50 2f 32 2e 30 2f 55 44 50 20 31 30 2e 32 32 2e 37 37 2e 32 34 38 3a 35 30 36 30 3b 72 65 63 65 69 76 65 64 3d 31 30 2e 32 32 2e 37 37 2e 32 34 38 1a 25 00 00 00 09 01 1f 70 72 65 76 2d 68 6f 70 2d 69 70 3d 31 30 2e 32 32 2e 37 37 2e 32 34 38 3a 35 30 36 30 1a 2b 00 00 00 09 01 25 69 6e 63 6f 6d 69 6e 67 2d 72 65 71 2d 75 72 69 3d 73 69 70 3a 37 39 30 35 40 76 76 73 2d 76 69 74 72 61 1a 33 00 00 00 09 01 2d 6f 75 74 67 6f 69 6e 67 2d 72 65 71 2d 75 72 69 3d 73 69 70 3a 39 39 30 32 33 31 32 36 40 31 37 32 2e 32 33 2e 32 35 32 2e 32 32 1a 26 00 00 00 09 01 20 6e 65 78 74 2d 68 6f 70 2d 69 70 3d 31 37 32 2e 32 33 2e 32 35 32 2e 32 32 3a 35 30 36 30 1a 62 00 00 00 09 01 5c 73 69 70 2d



68 64 72 3d 46 72 6f 6d 3a 20 22 28 76 76 73 2d 76 69 74 72 61 29 37 39 36 31 22 20 3c 73 69 70 3a 37 39 36 31 40 76 76 73 2d 76 69 74 72 61 3e 3b 74 61 67 3d 30 30 33 30 39 34 63 34 35 30 66 30 30 30 30 66 30 62 37 30 65 65 38 66 2d 30 36 65 35 34 37 33 37 1a 3a 00 00 00 09 01 34 73 69 70 2d 68 64 72 3d 54 6f 3a 20 3c 73 69 70 3a 37 39 30 35 40 76 76 73 2d 76 69 74 72 61 3e 3b 74 61 67 3d 43 44 30 41 39 30 43 43 2d 32 30 42 43 1a 20 00 00 00 09 01 1a 73 69 70 2d 68 64 72 3d 43 53 65 71 3a 20 31 30 31 20 49 4e 56 49 54 45

[Wed Oct 15 17:41:08 2003] sip_radius.c(1300) Radius: read 20 bytes in response from b.19.174.128:1813.[Wed Oct 15 17:41:08 2003] [debug] sip_radius.c(594): 05 03 00 14 66 90 86 f4 85 af 01 dc e1 ae 39 41 ef 4b 80 e4 [Wed Oct 15 17:41:08 2003] sip_radius.c(1410) Radius: server 1 responded with Accept. Mark it for next time use.[Wed Oct 15 17:41:08 2003] sip_sm.c(998) Sent 839 bytes UDP packet to a.22.77.248:5060 SIP/2.0 200 OK Via: SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248From: "(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f0000f0b70ee8f-06e54737To: <sip:7905@vvs-vitra>;tag=CD0A90CC-20BCDate: Wed, 15 Oct 2003 17:47:33 GMTCall-ID: [email protected]: Cisco-SIPGateway/IOS-12.xCSeq: 101 INVITEAllow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBSCRIBE, NOTIFY, INFOAllow-Events: telephone-eventContact: <sip:[email protected]:5060>Record-Route: <sip:7905@vvs-vitra:5060;maddr=b.19.174.239>Content-Type: application/sdpContent-Length: 207


[Wed Oct 15 17:41:08 2003] mod_sip_acct.c(630) Accounting event type: 200 to INVITE sent upstream, subtype: response received from downstream





















[Wed Oct 15 17:41:08 2003] [debug] sip_radius.c(594): 1a 37 00 00 00 09 19 31 68 33 32 33 2d 73 65 74 75 70 2d 74 69 6d 65 3d 31 37 3a 34 30 3a 35 36 2e 38 36 20 47 4d 54 20 57 65 64 20 4f 63 74 20 31 35 20 32 30 30 33



[Wed Oct 15 17:41:08 2003] sip_radius.c(675) Building attr - h323-connect-time= 17:41:08.702 GMT Wed Oct 15 2003

[Wed Oct 15 17:41:08 2003] [debug] sip_radius.c(806): Attr built as 28 (VSA) 11 - h323-connect-time= 58 bytes

[Wed Oct 15 17:41:08 2003] [debug] sip_radius.c(594): 1a 3a 00 00 00 09 1c 34 68 33 32 33 2d 63 6f 6e 6e 65 63 74 2d 74 69 6d 65 3d 31 37 3a 34 31 3a 30 38 2e 37 30 32 20 47 4d 54 20 57 65 64 20 4f 63 74 20 31 35 20 32 30 30 33 [Wed Oct 15 17:41:08 2003] sip_radius.c(675) Building attr - h323-call-origin= answer


[Wed Oct 15 17:41:08 2003] [debug] sip_radius.c(594): 1a 1f 00 00 00 09 1a 19 68 33 32 33 2d 63 61 6c 6c 2d 6f 72 69 67 69 6e 3d 61 6e 73 77 65 72 [Wed Oct 15 17:41:08 2003] sip_radius.c(675) Building attr - h323-call-type= VoIP











[Wed Oct 15 17:41:08 2003] [debug] sip_radius.c(594): 1a 15 00 00 00 09 01 0f 6d 65 74 68 6f 64 3d 49 4e 56 49 54 45



[Wed Oct 15 17:41:08 2003] sip_radius.c(675) Building attr - prev-hop-via= SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248






[Wed Oct 15 17:41:08 2003] [debug] sip_radius.c(594): 1a 2b 00 00 00 09 01 25 69 6e 63 6f 6d 69 6e 67 2d 72 65 71 2d 75 72 69 3d 73 69 70 3a 37 39 30 35 40 76 76 73 2d 76 69 74 72 61 [Wed Oct 15 17:41:08 2003] sip_radius.c(675) Building attr - outgoing-req-uri= sip:[email protected]


[Wed Oct 15 17:41:08 2003] [debug] sip_radius.c(594): 1a 33 00 00 00 09 01 2d 6f 75 74 67 6f 69 6e 67 2d 72 65 71 2d 75 72 69 3d 73 69 70 3a 39 39 30 32 33 31 32 36 40 31 37 32 2e 32 33 2e 32 35 32 2e 32 32 [Wed Oct 15 17:41:08 2003] sip_radius.c(675) Building attr - next-hop-ip= b.23.252.22:5060




[Wed Oct 15 17:41:08 2003] [debug] sip_radius.c(594): 1a 62 00 00 00 09 01 5c 73 69 70 2d 68 64 72 3d 46 72 6f 6d 3a 20 22 28 76 76 73 2d 76 69 74 72 61 29 37 39 36 31 22 20 3c 73 69 70 3a 37 39 36 31 40 76 76 73 2d 76 69 74 72 61 3e 3b 74 61 67 3d 30 30 33 30 39 34 63 34 35 30 66 30 30 30 30 66 30 62 37 30 65 65 38 66 2d 30 36 65 35 34 37



33 37 [Wed Oct 15 17:41:08 2003] sip_radius.c(675) Building attr - sip-hdr= To: <sip:7905@vvs-vitra>;tag=CD0A90CC-20BC


[Wed Oct 15 17:41:08 2003] [debug] sip_radius.c(594): 1a 3a 00 00 00 09 01 34 73 69 70 2d 68 64 72 3d 54 6f 3a 20 3c 73 69 70 3a 37 39 30 35 40 76 76 73 2d 76 69 74 72 61 3e 3b 74 61 67 3d 43 44 30 41 39 30 43 43 2d 32 30 42 43 [Wed Oct 15 17:41:08 2003] sip_radius.c(675) Building attr - sip-hdr= CSeq: 101 INVITE



[Wed Oct 15 17:41:08 2003] sip_radius.c(1115) Radius: max number of servers to use is 2.[Wed Oct 15 17:41:08 2003] sip_radius.c(1120) Radius: Start with server 1.[Wed Oct 15 17:41:08 2003] sip_radius.c(852) Radius: The RA is:[Wed Oct 15 17:41:08 2003] [debug] sip_radius.c(594): 75 c6 60 2b ec 25 e8 b9 d7 a6 54 15 c7 08 aa fb

[Wed Oct 15 17:41:08 2003] sip_radius.c(1222) Radius: To send 940 bytes in request to b.19.174.128:1813.[Wed Oct 15 17:41:08 2003] [debug] sip_radius.c(594): 04 04 03 ac 75 c6 60 2b ec 25 e8 b9 d7 a6 54 15 c7 08 aa fb 04 06 ac 13 ae ef 3d 06 00 00 00 05 01 06 37 39 36 31 06 06 00 00 00 01 28 06 00 00 00 01 2c 32 30 30 33 30 39 34 63 34 2d 35 30 66 30 31 66 38 34 2d 34 33 35 66 63 64 32 34 2d 34 65 34 35 61 36 63 39 40 31 30 2e 32 32 2e 37 37 2e 32 34 38 1e 16 3c 73 69 70 3a 37 39 30 35 40 76 76 73 2d 76 69 74 72 61 3e 1f 4e 22 28 76 76 73 2d 76 69 74 72 61 29 37 39 36 31 22 20 3c 73 69 70 3a 37 39 36 31 40 76 76 73 2d 76 69 74 72 61 3e 3b 74 61 67 3d 30 30 33 30 39 34 63 34 35 30 66 30 30 30 30 66 30 62 37 30 65 65 38 66 2d 30 36 65 35 34 37 33 37 1a 37 00 00 00 09 19 31 68 33 32 33 2d 73 65 74 75 70 2d 74 69 6d 65 3d 31 37 3a 34 30 3a 35 36 2e 38 36 20 47 4d 54 20 57 65 64 20 4f 63 74 20 31 35 20 32 30 30 33 1a 3a 00 00 00 09 1c 34 68 33 32 33 2d 63 6f 6e 6e 65 63 74 2d 74 69 6d 65 3d 31 37 3a 34 31 3a 30 38 2e 37 30 32 20 47 4d 54 20 57 65 64 20 4f 63 74 20 31 35 20 32 30 30 33 1a 1f 00 00 00 09 1a 19 68 33 32 33 2d 63 61 6c 6c 2d 6f 72 69 67 69 6e 3d 61 6e 73 77 65 72 1a 1b 00 00 00 09 1b 15 68 33 32 33 2d 63 61 6c 6c 2d 74 79 70 65 3d 56 6f 49 50 1a 1b 00 00 00 09 01 15 73 69 70 2d 73 74 61 74 75 73 2d 63 6f 64 65 3d 32 30 30 1a 1c 00 00 00 09 01 16 73 65 73 73 69 6f 6e 2d 70 72 6f 74 6f 63 6f 6c 3d 73 69 70 1a 40 00 00 00 09 01 3a 63 61 6c 6c 2d 69 64 3d 30 30 33 30 39 34 63 34 2d 35 30 66 30 31 66 38 34 2d 34 33 35 66 63 64 32 34 2d 34 65 34 35 61 36 63 39 40 31 30 2e 32 32 2e 37 37 2e 32 34 38 1a 15 00 00 00 09 01 0f 6d 65 74 68 6f 64 3d 49 4e 56 49 54 45 1a 48 00 00 00 09 01 42 70 72 65 76 2d 68 6f 70 2d 76 69 61 3d 53 49 50 2f 32 2e 30 2f 55 44 50 20



31 30 2e 32 32 2e 37 37 2e 32 34 38 3a 35 30 36 30 3b 72 65 63 65 69 76 65 64 3d 31 30 2e 32 32 2e 37 37 2e 32 34 38 1a 25 00 00 00 09 01 1f 70 72 65 76 2d 68 6f 70 2d 69 70 3d 31 30 2e 32 32 2e 37 37 2e 32 34 38 3a 35 30 36 30 1a 2b 00 00 00 09 01 25 69 6e 63 6f 6d 69 6e 67 2d 72 65 71 2d 75 72 69 3d 73 69 70 3a 37 39 30 35 40 76 76 73 2d 76 69 74 72 61 1a 33 00 00 00 09 01 2d 6f 75 74 67 6f 69 6e 67 2d 72 65 71 2d 75 72 69 3d 73 69 70 3a 39 39 30 32 33 31 32 36 40 31 37 32 2e 32 33 2e 32 35 32 2e 32 32 1a 26 00 00 00 09 01 20 6e 65 78 74 2d 68 6f 70 2d 69 70 3d 31 37 32 2e 32 33 2e 32 35 32 2e 32 32 3a 35 30 36 30 1a 62 00 00 00 09 01 5c 73 69 70 2d 68 64 72 3d 46 72 6f 6d 3a 20 22 28 76 76 73 2d 76 69 74 72 61 29 37 39 36 31 22 20 3c 73 69 70 3a 37 39 36 31 40 76 76 73 2d 76 69 74 72 61 3e 3b 74 61 67 3d 30 30 33 30 39 34 63 34 35 30 66 30 30 30 30 66 30 62 37 30 65 65 38 66 2d 30 36 65 35 34 37 33 37 1a 3a 00 00 00 09 01 34 73 69 70 2d 68 64 72 3d 54 6f 3a 20 3c 73 69 70 3a 37 39 30 35 40 76 76 73 2d 76 69 74 72 61 3e 3b 74 61 67 3d 43 44 30 41 39 30 43 43 2d 32 30 42 43 1a 20 00 00 00 09 01 1a 73 69 70 2d 68 64 72 3d 43 53 65 71 3a 20 31 30 31 20 49 4e 56 49 54 45 [Wed Oct 15 17:41:08 2003] sip_radius.c(1300) Radius: read 20 bytes in response from b.19.174.128:1813.[Wed Oct 15 17:41:08 2003] [debug] sip_radius.c(594): 05 04 00 14 1f fe ba e0 02 93 b5 8c ad 6e 79 9b bb 11 24 32 [Wed Oct 15 17:41:08 2003] sip_radius.c(1410) Radius: server 1 responded with Accept. Mark it for next time use.[Wed Oct 15 17:41:08 2003] sip_protocol.c(5393) Received 358 bytes UDP packet from a.22.77.248:50432 ACK sip:7905@vvs-vitra:5060 SIP/2.0Via: SIP/2.0/UDP a.22.77.248:5060From: "(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f0000f0b70ee8f-06e54737To: <sip:7905@vvs-vitra>;tag=CD0A90CC-20BCCall-ID: [email protected]: 101 ACKUser-Agent: CSCO/4Route: <sip:[email protected]:5060>Content-Length: 0

[Wed Oct 15 17:41:08 2003] sip_sm.c(3952) Found existing TCB 0xf680b698[Wed Oct 15 17:41:08 2003] sip_dns.c(787) "A" Query for b.23.252.22 successful, Got 1 IP addresses[Wed Oct 15 17:41:08 2003] sip_dns.c(136) A Record : b.23.252.22[Wed Oct 15 17:41:08 2003] sip_sm.c(998) Sent 503 bytes UDP packet to b.23.252.22:5060 ACK sip:[email protected]:5060 SIP/2.0Via: SIP/2.0/UDP b.19.174.239:5060;branch=f7ab66e0-a9f08f30-5b066032-b760acb8Record-Route: <sip:7905.f7ab66e0-a9f08f30-5b066032-b760acb8@vvs-vitra:5060;maddr=b.19.174.239>Via: SIP/2.0/UDP a.22.77.248:5060From: "(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f0000f0b70ee8f-06e54737To: <sip:7905@vvs-vitra>;tag=CD0A90CC-20BCCall-ID: [email protected]: 101 ACKUser-Agent: CSCO/4Content-Length: 0



[Wed Oct 15 17:41:21 2003] sip_protocol.c(5393) Received 358 bytes UDP packet from a.22.77.248:50432 BYE sip:7905@vvs-vitra:5060 SIP/2.0Via: SIP/2.0/UDP a.22.77.248:5060From: "(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f0000f0b70ee8f-06e54737To: <sip:7905@vvs-vitra>;tag=CD0A90CC-20BCCall-ID: [email protected]: 102 BYEUser-Agent: CSCO/4Content-Length: 0Route: <sip:[email protected]:5060>

[Wed Oct 15 17:41:21 2003] sip_sm.c(998) Sent 301 bytes UDP packet to a.22.77.248:5060 SIP/2.0 100 TryingVia: SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248Call-ID: [email protected]: "(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f0000f0b70ee8f-06e54737To: <sip:7905@vvs-vitra>;tag=CD0A90CC-20BCCSeq: 102 BYEContent-Length: 0

[Wed Oct 15 17:41:21 2003] mod_sip_acct.c(630) Accounting event type: BYE received from upstream, subtype: none

[Wed Oct 15 17:41:21 2003] sip_dns.c(787) "A" Query for b.23.252.22 successful, Got 1 IP addresses[Wed Oct 15 17:41:21 2003] sip_dns.c(136) A Record : b.23.252.22[Wed Oct 15 17:41:21 2003] sip_sm.c(998) Sent 429 bytes UDP packet to b.23.252.22:5060 BYE sip:[email protected]:5060 SIP/2.0Via: SIP/2.0/UDP b.19.174.239:5060;branch=17531ae2-b2a07b11-1c611b6a-e59e8867-1Via: SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248From: "(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f0000f0b70ee8f-06e54737To: <sip:7905@vvs-vitra>;tag=CD0A90CC-20BCCall-ID: [email protected]: 102 BYEUser-Agent: CSCO/4Content-Length: 0

[Wed Oct 15 17:41:21 2003] mod_sip_acct.c(630) Accounting event type: BYE sent downstream, subtype: none

[Wed Oct 15 17:41:21 2003] sip_protocol.c(5393) Received 446 bytes UDP packet from b.23.252.22:5060 SIP/2.0 200 OKVia: SIP/2.0/UDP b.19.174.239:5060;branch=17531ae2-b2a07b11-1c611b6a-e59e8867-1,SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248From: "(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f0000f0b70ee8f-06e54737To: <sip:7905@vvs-vitra>;tag=CD0A90CC-20BCDate: Wed, 15 Oct 2003 17:47:58 GMTCall-ID: [email protected]: Cisco-SIPGateway/IOS-12.xContent-Length: 0CSeq: 102 BYE



[Wed Oct 15 17:41:21 2003] sip_sm.c(4820) Found existing TCB 0xf680dac8[Wed Oct 15 17:41:21 2003] mod_sip_acct.c(630) Accounting event type: response to BYE received from downstream or locally generated, subtype: response received from downstream













[Wed Oct 15 17:41:21 2003] [debug] sip_radius.c(594): 2c 32 30 30 33 30 39 34 63 34 2d 35 30 66 30 31 66 38 34 2d 34 33 35 66 63 64 32 34 2d 34 65 34 35 61 36 63 39 40 31 30 2e 32 32 2e 37 37 2e 32 34 38 [Wed Oct 15 17:41:21 2003] sip_radius.c(675) Building attr - Called-Station-Id <sip:7905@vvs-vitra>;tag=CD0A90CC-20BC


[Wed Oct 15 17:41:21 2003] [debug] sip_radius.c(594): 1e 28 3c 73 69 70 3a 37 39 30 35 40 76 76 73 2d 76 69 74 72 61 3e 3b 74 61 67 3d 43 44 30 41 39 30 43 43 2d 32 30 42 43 [Wed Oct 15 17:41:21 2003] sip_radius.c(675) Building attr - Calling-Station-Id "(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f0000f0b70ee8f-06e54737




[Wed Oct 15 17:41:21 2003] [debug] sip_radius.c(594): 1f 4e 22 28 76 76 73 2d 76 69 74 72 61 29 37 39 36 31 22 20 3c 73 69 70 3a 37 39 36 31 40 76 76 73 2d 76 69 74 72 61 3e 3b 74 61 67 3d 30 30 33 30 39 34 63 34 35 30 66 30 30 30 30 66 30 62 37 30 65 65 38 66 2d 30 36 65 35 34 37 33 37 [Wed Oct 15 17:41:21 2003] sip_radius.c(675) Building attr - h323-disconnect-time= 17:41:21.605 GMT Wed Oct 15 2003















[Wed Oct 15 17:41:21 2003] sip_radius.c(675) Building attr - method= BYE


[Wed Oct 15 17:41:21 2003] [debug] sip_radius.c(594): 1a 12 00 00 00 09 01 0c 6d 65 74 68 6f 64 3d 42 59 45 [Wed Oct 15 17:41:21 2003] sip_radius.c(675) Building attr - prev-hop-via= SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248




[Wed Oct 15 17:41:21 2003] [debug] sip_radius.c(594): 1a 25 00 00 00 09 01 1f 70 72 65 76 2d 68 6f 70 2d 69 70 3d 31 30 2e 32 32 2e 37 37 2e 32 34 38 3a 35 30 36 30 [Wed Oct 15 17:41:21 2003] sip_radius.c(675) Building attr - incoming-req-uri= sip:7905@vvs-vitra:5060


[Wed Oct 15 17:41:21 2003] [debug] sip_radius.c(594): 1a 30 00 00 00 09 01 2a 69 6e 63 6f 6d 69 6e 67 2d 72 65 71 2d 75 72 69 3d 73 69 70 3a 37 39 30 35 40 76 76 73 2d 76 69 74 72 61 3a 35 30 36 30

[Wed Oct 15 17:41:21 2003] sip_radius.c(675) Building attr - outgoing-req-uri= sip:[email protected]:5060


[Wed Oct 15 17:41:21 2003] [debug] sip_radius.c(594): 1a 38 00 00 00 09 01 32 6f 75 74 67 6f 69 6e 67 2d 72 65 71 2d 75 72 69 3d 73 69 70 3a 39 39 30 32 33 31 32 36 40 31 37 32 2e 32 33 2e 32 35 32 2e 32 32 3a 35 30 36 30 [Wed Oct 15 17:41:21 2003] sip_radius.c(675) Building attr - next-hop-ip= b.23.252.22:5060






[Wed Oct 15 17:41:21 2003] [debug] sip_radius.c(594): 1a 62 00 00 00 09 01 5c 73 69 70 2d 68 64 72 3d 46 72 6f 6d 3a 20 22 28 76 76 73 2d 76 69 74 72 61 29 37 39 36 31 22 20 3c 73 69 70 3a 37 39 36 31 40 76 76 73 2d 76 69 74 72 61 3e 3b 74 61 67 3d 30 30 33 30 39 34 63 34 35 30 66 30 30 30 30 66 30 62 37 30 65 65 38 66 2d 30 36 65 35 34 37 33 37 [Wed Oct 15 17:41:21 2003] sip_radius.c(675) Building attr - sip-hdr= To: <sip:7905@vvs-vitra>;tag=CD0A90CC-20BC


[Wed Oct 15 17:41:21 2003] [debug] sip_radius.c(594): 1a 3a 00 00 00 09 01 34 73 69 70 2d 68 64 72 3d 54 6f 3a 20 3c 73 69 70 3a 37 39 30 35 40 76 76 73 2d 76 69 74 72 61 3e 3b 74 61 67 3d 43 44 30 41 39 30 43 43 2d 32 30 42 43 [Wed Oct 15 17:41:21 2003] sip_radius.c(675) Building attr - sip-hdr= CSeq: 102 BYE


[Wed Oct 15 17:41:21 2003] [debug] sip_radius.c(594): 1a 1d 00 00 00 09 01 17 73 69 70 2d 68 64 72 3d 43 53 65 71 3a 20 31 30 32 20 42 59 45 [Wed Oct 15 17:41:21 2003] sip_radius.c(1115) Radius: max number of servers to use is 2.[Wed Oct 15 17:41:21 2003] sip_radius.c(1120) Radius: Start with server 1.[Wed Oct 15 17:41:21 2003] sip_radius.c(852) Radius: The RA is:[Wed Oct 15 17:41:21 2003] [debug] sip_radius.c(594): 40 5d 0d 80 3b 78 3e ab 62 e0 e9 5c fd 60 56 6d

[Wed Oct 15 17:41:21 2003] sip_radius.c(1222) Radius: To send 913 bytes in request to b.19.174.128:1813.[Wed Oct 15 17:41:21 2003] [debug] sip_radius.c(594): 04 05 03 91 40 5d 0d 80 3b 78 3e ab 62 e0 e9 5c fd 60 56 6d 04 06 ac 13 ae ef 3d 06 00 00 00 05 01 06 37 39 36 31 06 06 00 00 00 01 28 06 00 00 00 02 2c 32 30 30 33 30 39 34 63 34 2d 35 30 66 30 31 66 38 34 2d 34 33 35 66 63 64 32 34 2d 34 65 34 35 61 36 63 39 40 31 30 2e 32 32 2e 37 37 2e 32 34 38 1e 28 3c 73 69 70 3a 37 39 30 35 40 76 76 73 2d 76 69 74 72 61 3e 3b 74 61 67 3d 43 44 30 41 39 30 43 43 2d 32 30 42 43 1f 4e 22 28 76 76 73 2d 76 69 74 72 61 29 37 39 36 31 22 20 3c 73 69 70 3a 37 39 36 31 40 76 76 73 2d 76 69 74 72 61 3e 3b 74 61 67 3d 30 30 33 30 39 34 63 34 35 30 66 30 30 30 30 66 30 62 37 30 65 65 38 66 2d 30 36 65 35 34 37 33 37 1a 3d 00 00 00 09 1d 37 68 33 32 33 2d 64 69 73 63 6f 6e 6e 65 63 74 2d 74 69 6d 65 3d 31 37 3a 34 31 3a 32 31 2e 36 30 35 20 47 4d 54 20 57 65 64 20 4f 63 74 20 31 35 20 32 30 30 33 1a 22 00 00 00 09 1a 1c 68 33 32 33 2d 63 61 6c 6c 2d 6f 72 69 67 69 6e 3d 6f 72 69 67 69 6e 61 74 65 1a 1b 00 00 00 09 1b 15 68 33 32 33 2d 63 61 6c 6c 2d 74 79 70 65 3d 56 6f 49 50 1a 1b 00 00 00 09 01 15 73 69 70 2d 73 74 61 74 75 73 2d 63 6f 64 65 3d 32 30 30 1a 1c 00 00 00 09 01 16 73 65 73 73 69 6f 6e 2d 70 72 6f 74 6f 63 6f 6c 3d 73 69 70 1a 40 00 00 00



09 01 3a 63 61 6c 6c 2d 69 64 3d 30 30 33 30 39 34 63 34 2d 35 30 66 30 31 66 38 34 2d 34 33 35 66 63 64 32 34 2d 34 65 34 35 61 36 63 39 40 31 30 2e 32 32 2e 37 37 2e 32 34 38 1a 12 00 00 00 09 01 0c 6d 65 74 68 6f 64 3d 42 59 45 1a 48 00 00 00 09 01 42 70 72 65 76 2d 68 6f 70 2d 76 69 61 3d 53 49 50 2f 32 2e 30 2f 55 44 50 20 31 30 2e 32 32 2e 37 37 2e 32 34 38 3a 35 30 36 30 3b 72 65 63 65 69 76 65 64 3d 31 30 2e 32 32 2e 37 37 2e 32 34 38 1a 25 00 00 00 09 01 1f 70 72 65 76 2d 68 6f 70 2d 69 70 3d 31 30 2e 32 32 2e 37 37 2e 32 34 38 3a 35 30 36 30 1a 30 00 00 00 09 01 2a 69 6e 63 6f 6d 69 6e 67 2d 72 65 71 2d 75 72 69 3d 73 69 70 3a 37 39 30 35 40 76 76 73 2d 76 69 74 72 61 3a 35 30 36 30 1a 38 00 00 00 09 01 32 6f 75 74 67 6f 69 6e 67 2d 72 65 71 2d 75 72 69 3d 73 69 70 3a 39 39 30 32 33 31 32 36 40 31 37 32 2e 32 33 2e 32 35 32 2e 32 32 3a 35 30 36 30 1a 26 00 00 00 09 01 20 6e 65 78 74 2d 68 6f 70 2d 69 70 3d 31 37 32 2e 32 33 2e 32 35 32 2e 32 32 3a 35 30 36 30 1a 62 00 00 00 09 01 5c 73 69 70 2d 68 64 72 3d 46 72 6f 6d 3a 20 22 28 76 76 73 2d 76 69 74 72 61 29 37 39 36 31 22 20 3c 73 69 70 3a 37 39 36 31 40 76 76 73 2d 76 69 74 72 61 3e 3b 74 61 67 3d 30 30 33 30 39 34 63 34 35 30 66 30 30 30 30 66 30 62 37 30 65 65 38 66 2d 30 36 65 35 34 37 33 37 1a 3a 00 00 00 09 01 34 73 69 70 2d 68 64 72 3d 54 6f 3a 20 3c 73 69 70 3a 37 39 30 35 40 76 76 73 2d 76 69 74 72 61 3e 3b 74 61 67 3d 43 44 30 41 39 30 43 43 2d 32 30 42 43 1a 1d 00 00 00 09 01 17 73 69 70 2d 68 64 72 3d 43 53 65 71 3a 20 31 30 32 20 42 59 45 [Wed Oct 15 17:41:21 2003] sip_radius.c(1300) Radius: read 20 bytes in response from b.19.174.128:1813.[Wed Oct 15 17:41:21 2003] [debug] sip_radius.c(594): 05 05 00 14 47 50 b4 d3 29 84 a9 a4 c8 db 7f a7 f7 c1 78 fc [Wed Oct 15 17:41:21 2003] sip_radius.c(1410) Radius: server 1 responded with Accept. Mark it for next time use.[Wed Oct 15 17:41:21 2003] sip_sm.c(998) Sent 371 bytes UDP packet to a.22.77.248:5060 SIP/2.0 200 OK Via: SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248From: "(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f0000f0b70ee8f-06e54737To: <sip:7905@vvs-vitra>;tag=CD0A90CC-20BCDate: Wed, 15 Oct 2003 17:47:58 GMTCall-ID: [email protected]: Cisco-SIPGateway/IOS-12.xContent-Length: 0CSeq: 102 BYE

[Wed Oct 15 17:41:21 2003] mod_sip_acct.c(630) Accounting event type: response to BYE sent upstream, subtype: response received from downstream















[Wed Oct 15 17:41:21 2003] [debug] sip_radius.c(594): 2c 32 30 30 33 30 39 34 63 34 2d 35 30 66 30 31 66 38 34 2d 34 33 35 66 63 64 32 34 2d 34 65 34 35 61 36 63 39 40 31 30 2e 32 32 2e 37 37 2e 32 34 38 [Wed Oct 15 17:41:21 2003] sip_radius.c(675) Building attr - Called-Station-Id <sip:7905@vvs-vitra>;tag=CD0A90CC-20BC


[Wed Oct 15 17:41:21 2003] [debug] sip_radius.c(594): 1e 28 3c 73 69 70 3a 37 39 30 35 40 76 76 73 2d 76 69 74 72 61 3e 3b 74 61 67 3d 43 44 30 41 39 30 43 43 2d 32 30 42 43 [Wed Oct 15 17:41:21 2003] sip_radius.c(675) Building attr - Calling-Station-Id "(vvs-vitra)7961" <sip:7961@vvs-vitra>;tag=003094c450f0000f0b70ee8f-06e54737


[Wed Oct 15 17:41:21 2003] [debug] sip_radius.c(594): 1f 4e 22 28 76 76 73 2d 76 69 74 72 61 29 37 39 36 31 22 20 3c 73 69 70 3a 37 39 36 31 40 76 76 73 2d 76 69 74 72 61 3e 3b 74 61 67 3d 30 30 33 30 39 34 63 34 35 30 66 30 30 30 30 66 30 62 37 30 65 65 38 66 2d 30 36 65 35 34 37 33 37 [Wed Oct 15 17:41:21 2003] sip_radius.c(675) Building attr - h323-disconnect-time= 17:41:21.601 GMT Wed Oct 15 2003




[Wed Oct 15 17:41:21 2003] [debug] sip_radius.c(594): 1a 3d 00 00 00 09 1d 37 68 33 32 33 2d 64 69 73 63 6f 6e 6e 65 63 74 2d 74 69 6d 65 3d 31 37 3a 34 31 3a 32 31 2e 36 30 31 20 47 4d 54 20 57 65 64 20 4f 63 74 20 31 35 20 32 30 30 33 [Wed Oct 15 17:41:21 2003] sip_radius.c(675) Building attr - h323-call-origin= answer


[Wed Oct 15 17:41:21 2003] [debug] sip_radius.c(594): 1a 1f 00 00 00 09 1a 19 68 33 32 33 2d 63 61 6c 6c 2d 6f 72 69 67 69 6e 3d 61 6e 73 77 65 72 [Wed Oct 15 17:41:21 2003] sip_radius.c(675) Building attr - h323-call-type= VoIP









[Wed Oct 15 17:41:21 2003] sip_radius.c(675) Building attr - method= BYE


[Wed Oct 15 17:41:21 2003] [debug] sip_radius.c(594): 1a 12 00 00 00 09 01 0c 6d 65 74 68 6f 64 3d 42 59 45 [Wed Oct 15 17:41:21 2003] sip_radius.c(675) Building attr - prev-hop-via= SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248






[Wed Oct 15 17:41:21 2003] [debug] sip_radius.c(594): 1a 25 00 00 00 09 01 1f 70 72 65 76 2d 68 6f 70 2d 69 70 3d 31 30 2e 32 32 2e 37 37 2e 32 34 38 3a 35 30 36 30 [Wed Oct 15 17:41:21 2003] sip_radius.c(675) Building attr - incoming-req-uri= sip:7905@vvs-vitra:5060


[Wed Oct 15 17:41:21 2003] [debug] sip_radius.c(594): 1a 30 00 00 00 09 01 2a 69 6e 63 6f 6d 69 6e 67 2d 72 65 71 2d 75 72 69 3d 73 69 70 3a 37 39 30 35 40 76 76 73 2d 76 69 74 72 61 3a 35 30 36 30

[Wed Oct 15 17:41:21 2003] sip_radius.c(675) Building attr - outgoing-req-uri= sip:[email protected]:5060


[Wed Oct 15 17:41:21 2003] [debug] sip_radius.c(594): 1a 38 00 00 00 09 01 32 6f 75 74 67 6f 69 6e 67 2d 72 65 71 2d 75 72 69 3d 73 69 70 3a 39 39 30 32 33 31 32 36 40 31 37 32 2e 32 33 2e 32 35 32 2e 32 32 3a 35 30 36 30 [Wed Oct 15 17:41:21 2003] sip_radius.c(675) Building attr - next-hop-ip= b.23.252.22:5060




[Wed Oct 15 17:41:21 2003] [debug] sip_radius.c(594): 1a 62 00 00 00 09 01 5c 73 69 70 2d 68 64 72 3d 46 72 6f 6d 3a 20 22 28 76 76 73 2d 76 69 74 72 61 29 37 39 36 31 22 20 3c 73 69 70 3a 37 39 36 31 40 76 76 73 2d 76 69 74 72 61 3e 3b 74 61 67 3d 30 30 33 30 39 34 63 34 35 30 66 30 30 30 30 66 30 62 37 30 65 65 38 66 2d 30 36 65 35 34 37 33 37



[Wed Oct 15 17:41:21 2003] sip_radius.c(675) Building attr - sip-hdr= To: <sip:7905@vvs-vitra>;tag=CD0A90CC-20BC


[Wed Oct 15 17:41:21 2003] [debug] sip_radius.c(594): 1a 3a 00 00 00 09 01 34 73 69 70 2d 68 64 72 3d 54 6f 3a 20 3c 73 69 70 3a 37 39 30 35 40 76 76 73 2d 76 69 74 72 61 3e 3b 74 61 67 3d 43 44 30 41 39 30 43 43 2d 32 30 42 43 [Wed Oct 15 17:41:21 2003] sip_radius.c(675) Building attr - sip-hdr= CSeq: 102 BYE


[Wed Oct 15 17:41:21 2003] [debug] sip_radius.c(594): 1a 1d 00 00 00 09 01 17 73 69 70 2d 68 64 72 3d 43 53 65 71 3a 20 31 30 32 20 42 59 45 [Wed Oct 15 17:41:21 2003] sip_radius.c(1115) Radius: max number of servers to use is 2.[Wed Oct 15 17:41:21 2003] sip_radius.c(1120) Radius: Start with server 1.[Wed Oct 15 17:41:21 2003] sip_radius.c(852) Radius: The RA is:[Wed Oct 15 17:41:21 2003] [debug] sip_radius.c(594): 5d e9 b7 99 56 94 1d 43 db f1 39 1c 56 93 69 4b

[Wed Oct 15 17:41:21 2003] sip_radius.c(1222) Radius: To send 910 bytes in request to b.19.174.128:1813.[Wed Oct 15 17:41:21 2003] [debug] sip_radius.c(594): 04 06 03 8e 5d e9 b7 99 56 94 1d 43 db f1 39 1c 56 93 69 4b 04 06 ac 13 ae ef 3d 06 00 00 00 05 01 06 37 39 36 31 06 06 00 00 00 01 28 06 00 00 00 02 2c 32 30 30 33 30 39 34 63 34 2d 35 30 66 30 31 66 38 34 2d 34 33 35 66 63 64 32 34 2d 34 65 34 35 61 36 63 39 40 31 30 2e 32 32 2e 37 37 2e 32 34 38 1e 28 3c 73 69 70 3a 37 39 30 35 40 76 76 73 2d 76 69 74 72 61 3e 3b 74 61 67 3d 43 44 30 41 39 30 43 43 2d 32 30 42 43 1f 4e 22 28 76 76 73 2d 76 69 74 72 61 29 37 39 36 31 22 20 3c 73 69 70 3a 37 39 36 31 40 76 76 73 2d 76 69 74 72 61 3e 3b 74 61 67 3d 30 30 33 30 39 34 63 34 35 30 66 30 30 30 30 66 30 62 37 30 65 65 38 66 2d 30 36 65 35 34 37 33 37 1a 3d 00 00 00 09 1d 37 68 33 32 33 2d 64 69 73 63 6f 6e 6e 65 63 74 2d 74 69 6d 65 3d 31 37 3a 34 31 3a 32 31 2e 36 30 31 20 47 4d 54 20 57 65 64 20 4f 63 74 20 31 35 20 32 30 30 33 1a 1f 00 00 00 09 1a 19 68 33 32 33 2d 63 61 6c 6c 2d 6f 72 69 67 69 6e 3d 61 6e 73 77 65 72 1a 1b 00 00 00 09 1b 15 68 33 32 33 2d 63 61 6c 6c 2d 74 79 70 65 3d 56 6f 49 50 1a 1b 00 00 00 09 01 15 73 69 70 2d 73 74 61 74 75 73 2d 63 6f 64 65 3d 32 30 30 1a 1c 00 00 00 09 01 16 73 65 73 73 69 6f 6e 2d 70 72 6f 74 6f 63 6f 6c 3d 73 69 70 1a 40 00 00 00 09 01 3a 63 61 6c 6c 2d 69 64 3d 30 30 33 30 39 34 63 34 2d 35 30 66 30 31 66 38 34 2d 34 33 35 66 63 64 32 34 2d 34 65 34 35 61 36 63 39 40 31 30 2e 32 32 2e 37 37 2e 32 34 38 1a 12 00 00 00 09 01 0c 6d 65 74 68 6f 64 3d 42 59 45 1a 48 00 00 00 09 01 42 70 72 65 76 2d 68 6f 70 2d 76 69 61 3d 53 49 50 2f 32 2e 30 2f 55 44 50 20 31 30 2e 32 32 2e 37 37 2e 32 34 38 3a 35 30 36 30 3b 72 65 63 65 69 76 65 64 3d 31 30 2e 32 32 2e 37 37 2e 32 34 38 1a 25 00 00 00 09 01 1f 70 72 65 76 2d 68 6f 70 2d 69 70 3d 31 30 2e 32 32 2e 37 37 2e 32


RADIUS Interface for Cisco SPS Scenario Output AppendixRADIUS Authentication Message Listings

34 38 3a 35 30 36 30 1a 30 00 00 00 09 01 2a 69 6e 63 6f 6d 69 6e 67 2d 72 65 71 2d 75 72 69 3d 73 69 70 3a 37 39 30 35 40 76 76 73 2d 76 69 74 72 61 3a 35 30 36 30 1a 38 00 00 00 09 01 32 6f 75 74 67 6f 69 6e 67 2d 72 65 71 2d 75 72 69 3d 73 69 70 3a 39 39 30 32 33 31 32 36 40 31 37 32 2e 32 33 2e 32 35 32 2e 32 32 3a 35 30 36 30 1a 26 00 00 00 09 01 20 6e 65 78 74 2d 68 6f 70 2d 69 70 3d 31 37 32 2e 32 33 2e 32 35 32 2e 32 32 3a 35 30 36 30 1a 62 00 00 00 09 01 5c 73 69 70 2d 68 64 72 3d 46 72 6f 6d 3a 20 22 28 76 76 73 2d 76 69 74 72 61 29 37 39 36 31 22 20 3c 73 69 70 3a 37 39 36 31 40 76 76 73 2d 76 69 74 72 61 3e 3b 74 61 67 3d 30 30 33 30 39 34 63 34 35 30 66 30 30 30 30 66 30 62 37 30 65 65 38 66 2d 30 36 65 35 34 37 33 37 1a 3a 00 00 00 09 01 34 73 69 70 2d 68 64 72 3d 54 6f 3a 20 3c 73 69 70 3a 37 39 30 35 40 76 76 73 2d 76 69 74 72 61 3e 3b 74 61 67 3d 43 44 30 41 39 30 43 43 2d 32 30 42 43 1a 1d 00 00 00 09 01 17 73 69 70 2d 68 64 72 3d 43 53 65 71 3a 20 31 30 32 20 42 59 45 [Wed Oct 15 17:41:21 2003] sip_radius.c(1300) Radius: read 20 bytes in response from b.19.174.128:1813.[Wed Oct 15 17:41:21 2003] [debug] sip_radius.c(594): 05 06 00 14 28 ec d1 83 39 07 52 70 ab c9 ce 4e 09 84 37 05 [Wed Oct 15 17:41:21 2003] sip_radius.c(1410) Radius: server 1 responded with Accept. Mark it for next time use.

RADIUS Authentication Message ListingsThe following output examples are organized by scenario:

• REGISTER-Accepted Scenario Messages, page 129

• REGISTER-Rejected Scenario Messages, page 135

• INVITE-Accepted Scenario Messages, page 140

• INVITE-Rejected Scenario Messages, page 148

REGISTER-Accepted Scenario Messages


The following is debug output from FreeRADIUS server with default accounting configuration:

rad_recv: Access-Request packet from host b.19.174.239:42200, id=1,length=424 NAS-IP-Address = b.19.174.239 NAS-Port-Type = Virtual User-Name = "7905" Digest-Response = "941e7ee75864b7f9d2fcc69b1c2beef9" Digest-Attributes = 0x0107434953434f Digest-Attributes = 0x020a3366663230636238 Digest-Attributes = 0x030a5245474953544552 Digest-Attributes = 0x040f7369703a7676732d7669747261 Digest-Attributes = 0x050661757468



Digest-Attributes = 0x06056d6435 Digest-Attributes = 0x080a3061653134323362 Digest-Attributes = 0x090a3030303030303031 Digest-Attributes = 0x0a0637393035 Cisco-AVPair = "sip-hdr=From:<sip:7905@vvs-vitra;user=phone>;tag=2067619830" Cisco-AVPair = "sip-hdr=Authorization: Digestusername="7905",realm="CISCO",nonce="3ff20cb8",uri="sip:vvs-vitra",response="941e7ee75864b7f9d2fcc69b1c2beef9",qop=auth,nc=00000001,cnonce="0ae1423b""modcall: entering group authorize for request 0 modcall[authorize]: module "preprocess" returns ok for request 0radius_xlat:'/usr/local/var/log/radius/radacct/b.19.174.239/auth-detail-20031230'rlm_detail:/usr/local/var/log/radius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%dexpands to/usr/local/var/log/radius/radacct/b.19.174.239/auth-detail-20031230 modcall[authorize]: module "auth_log" returns ok for request 0 rlm_digest: Converting Digest-Attributes to something sane... Digest-Realm = "CISCO" Digest-Nonce = "3ff20cb8" Digest-Method = "REGISTER" Digest-URI = "sip:vvs-vitra" Digest-QOP = "auth" Digest-Algorithm = "md5" Digest-CNonce = "0ae1423b" Digest-Nonce-Count = "00000001" Digest-User-Name = "7905"rlm_digest: Adding Auth-Type = DIGEST modcall[authorize]: module "digest" returns ok for request 0 rlm_realm: No '@' in User-Name = "7905", looking up realm NULL rlm_realm: No such realm "NULL" modcall[authorize]: module "suffix" returns noop for request 0 users: Matched 7905 at 81 modcall[authorize]: module "files" returns ok for request 0modcall: group authorize returns ok for request 0 rad_check_password: Found Auth-Type digestauth: type "digest"modcall: entering group authenticate for request 0A1 = 7905:CISCO:7905A2 = REGISTER:sip:vvs-vitraKD =3e19688eef774a7e696e7f4e03f3b9d3:3ff20cb8:00000001:0ae1423b:auth:25da9a7c988b416dddf56c2879e477e0 modcall[authenticate]: module "digest" returns ok for request 0modcall: group authenticate returns ok for request 0Sending Access-Accept of id 1 to b.19.174.239:42200Finished request 0Going to the next request--- Walking the entire request list ---Waking up in 6 seconds...


The error_log from Cisco SPS with the configuration listed in the “Configuring the REGISTER-Accepted Scenario” section on page 33.

[Tue Dec 30 23:39:36 2003] sip_protocol.c(5393) Received 415 bytes UDP packetfrom a.22.76.101:5060 REGISTER sip:vvs-vitra SIP/2.0Via: SIP/2.0/UDP a.22.76.101:5060From: <sip:7905@vvs-vitra;user=phone>;tag=2067619830





To: <sip:7905@vvs-vitra;user=phone>Call-ID: [email protected]: 1 REGISTERContact: <sip:[email protected]:5060;user=phone;transport=udp>;expires=3600User-Agent: Cisco-CP7905/1.01-030512AAllow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTERContent-Length: 0

[Tue Dec 30 23:39:36 2003] sip_sm.c(998) Sent 242 bytes UDP packet toa.22.76.101:5060 SIP/2.0 100 TryingVia: SIP/2.0/UDP a.22.76.101:5060;received=a.22.76.101Call-ID: [email protected]: <sip:7905@vvs-vitra;user=phone>;tag=2067619830To: <sip:7905@vvs-vitra;user=phone>CSeq: 1 REGISTERContent-Length: 0

[Tue Dec 30 23:39:36 2003] sip_sm.c(998) Sent 333 bytes UDP packet toa.22.76.101:5060 SIP/2.0 401 UnauthorizedVia: SIP/2.0/UDP a.22.76.101:5060;received=a.22.76.101Call-ID: [email protected]: <sip:7905@vvs-vitra;user=phone>;tag=2067619830To: <sip:7905@vvs-vitra;user=phone>CSeq: 1 REGISTERWWW-Authenticate: DIGEST realm="CISCO", nonce="3ff20cb8", qop="auth",algorithm=MD5Content-Length: 0

[Tue Dec 30 23:39:36 2003] sip_protocol.c(5393) Received 588 bytes UDP packetfrom a.22.76.101:5060 REGISTER sip:vvs-vitra SIP/2.0Via: SIP/2.0/UDP a.22.76.101:5060From: <sip:7905@vvs-vitra;user=phone>;tag=2067619830To: <sip:7905@vvs-vitra;user=phone>Call-ID: [email protected]: 2 REGISTERContact: <sip:[email protected]:5060;user=phone;transport=udp>;expires=3600User-Agent: Cisco-CP7905/1.01-030512AAllow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTERAuthorization: Digestusername="7905",realm="CISCO",nonce="3ff20cb8",uri="sip:vvs-vitra",response="941e7ee75864b7f9d2fcc69b1c2beef9",qop=auth,nc=00000001,cnonce="0ae1423b"Content-Length: 0

[Tue Dec 30 23:39:36 2003] sip_sm.c(998) Sent 242 bytes UDP packet toa.22.76.101:5060 SIP/2.0 100 TryingVia: SIP/2.0/UDP a.22.76.101:5060;received=a.22.76.101Call-ID: [email protected]: <sip:7905@vvs-vitra;user=phone>;tag=2067619830To: <sip:7905@vvs-vitra;user=phone>CSeq: 2 REGISTERContent-Length: 0



[Tue Dec 30 23:39:36 2003] sip_radius.c(675) Building attr - NAS-IP-Addressb.19.174.239

[Tue Dec 30 23:39:36 2003] [debug] sip_radius.c(806): Attr built as 4 () 4 -NAS-IP-Address 6 bytes

[Tue Dec 30 23:39:36 2003] [debug] sip_radius.c(594): 04 06 ac 13 ae ef [Tue Dec 30 23:39:36 2003] sip_radius.c(675) Building attr - NAS-Port-Type 5

[Tue Dec 30 23:39:36 2003] [debug] sip_radius.c(806): Attr built as 61 () 2 -NAS-Port-Type 6 bytes

[Tue Dec 30 23:39:36 2003] [debug] sip_radius.c(594): 3d 06 00 00 00 05 [Tue Dec 30 23:39:36 2003] sip_radius.c(675) Building attr - User-Name 7905

[Tue Dec 30 23:39:36 2003] [debug] sip_radius.c(806): Attr built as 1 () 1 -User-Name 6 bytes

[Tue Dec 30 23:39:36 2003] [debug] sip_radius.c(594): 01 06 37 39 30 35 [Tue Dec 30 23:39:36 2003] sip_radius.c(675) Building attr - Digest-Response941e7ee75864b7f9d2fcc69b1c2beef9

[Tue Dec 30 23:39:36 2003] [debug] sip_radius.c(806): Attr built as 206 () 1 -Digest-Response 34 bytes

[Tue Dec 30 23:39:36 2003] [debug] sip_radius.c(594): ce 22 39 34 31 65 37 65 65 37 35 38 36 34 62 37 66 39 64 32 66 63 63 36 39 62 31 63 32 62 65 65 66 39 [Tue Dec 30 23:39:36 2003] sip_radius.c(675) Building attr - digest-realmCISCO

[Tue Dec 30 23:39:36 2003] [debug] sip_radius.c(806): Attr built as 1 (DIGEST)21 - digest-realm 9 bytes

[Tue Dec 30 23:39:36 2003] [debug] sip_radius.c(594): cf 09 01 07 43 49 53 43 4f [Tue Dec 30 23:39:36 2003] sip_radius.c(675) Building attr - digest-nonce3ff20cb8

[Tue Dec 30 23:39:36 2003] [debug] sip_radius.c(806): Attr built as 2 (DIGEST)21 - digest-nonce 12 bytes

[Tue Dec 30 23:39:36 2003] [debug] sip_radius.c(594): cf 0c 02 0a 33 66 66 32 30 63 62 38 [Tue Dec 30 23:39:36 2003] sip_radius.c(675) Building attr - digest-methodREGISTER

[Tue Dec 30 23:39:36 2003] [debug] sip_radius.c(806): Attr built as 3 (DIGEST)21 - digest-method 12 bytes

[Tue Dec 30 23:39:36 2003] [debug] sip_radius.c(594): cf 0c 03 0a 52 45 47 49 53 54 45 52 [Tue Dec 30 23:39:36 2003] sip_radius.c(675) Building attr - digest-urisip:vvs-vitra

[Tue Dec 30 23:39:36 2003] [debug] sip_radius.c(806): Attr built as 4 (DIGEST)21 - digest-uri 17 bytes



[Tue Dec 30 23:39:36 2003] [debug] sip_radius.c(594): cf 11 04 0f 73 69 70 3a 76 76 73 2d 76 69 74 72 61 [Tue Dec 30 23:39:36 2003] sip_radius.c(675) Building attr - digest-qop auth

[Tue Dec 30 23:39:36 2003] [debug] sip_radius.c(806): Attr built as 5 (DIGEST)21 - digest-qop 8 bytes

[Tue Dec 30 23:39:36 2003] [debug] sip_radius.c(594): cf 08 05 06 61 75 74 68 [Tue Dec 30 23:39:36 2003] sip_radius.c(675) Building attr - digest-alg md5

[Tue Dec 30 23:39:36 2003] [debug] sip_radius.c(806): Attr built as 6 (DIGEST)21 - digest-alg 7 bytes

[Tue Dec 30 23:39:36 2003] [debug] sip_radius.c(594): cf 07 06 05 6d 64 35 [Tue Dec 30 23:39:36 2003] sip_radius.c(675) Building attr - digest-cnonce0ae1423b

[Tue Dec 30 23:39:36 2003] [debug] sip_radius.c(806): Attr built as 8 (DIGEST)21 - digest-cnonce 12 bytes

[Tue Dec 30 23:39:36 2003] [debug] sip_radius.c(594): cf 0c 08 0a 30 61 65 31 34 32 33 62 [Tue Dec 30 23:39:36 2003] sip_radius.c(675) Building attr - digest-noncecount00000001

[Tue Dec 30 23:39:36 2003] [debug] sip_radius.c(806): Attr built as 9 (DIGEST)21 - digest-noncecount 12 bytes

[Tue Dec 30 23:39:36 2003] [debug] sip_radius.c(594): cf 0c 09 0a 30 30 30 30 30 30 30 31 [Tue Dec 30 23:39:36 2003] sip_radius.c(675) Building attr - digest-username7905

[Tue Dec 30 23:39:36 2003] [debug] sip_radius.c(806): Attr built as 10(DIGEST) 21 - digest-username 8 bytes

[Tue Dec 30 23:39:36 2003] [debug] sip_radius.c(594): cf 08 0a 06 37 39 30 35 [Tue Dec 30 23:39:36 2003] sip_radius.c(675) Building attr - sip-hdr= From:<sip:7905@vvs-vitra;user=phone>;tag=2067619830

[Tue Dec 30 23:39:36 2003] [debug] sip_radius.c(806): Attr built as 1 (VSA) 11- sip-hdr= 68 bytes

[Tue Dec 30 23:39:36 2003] [debug] sip_radius.c(594): 1a 44 00 00 00 09 01 3e 73 69 70 2d 68 64 72 3d 46 72 6f 6d 3a 20 3c 73 69 70 3a 37 39 30 35 40 76 76 73 2d 76 69 74 72 61 3b 75 73 65 72 3d 70 68 6f 6e 65 3e 3b 74 61 67 3d 32 30 36 37 36 31 39 38 33 30 [Tue Dec 30 23:39:36 2003] sip_radius.c(675) Building attr - sip-hdr=Authorization: Digestusername="7905",realm="CISCO",nonce="3ff20cb8",uri="sip:vvs-vitra",response="941e7ee75864b7f9d2fcc69b1c2beef9",qop=auth,nc=00000001,cnonce="0ae1423b"


[Tue Dec 30 23:39:36 2003] [debug] sip_radius.c(594): 1a bb 00 00 00 09 01 b5 73 69 70 2d 68 64 72 3d 41 75 74 68 6f 72 69 7a 61 74 69 6f 6e 3a 20 44



69 67 65 73 74 20 75 73 65 72 6e 61 6d 65 3d 22 37 39 30 35 22 2c 72 65 61 6c 6d 3d 22 43 49 53 43 4f 22 2c 6e 6f 6e 63 65 3d 22 33 66 66 32 30 63 62 38 22 2c 75 72 69 3d 22 73 69 70 3a 76 76 73 2d 76 69 74 72 61 22 2c 72 65 73 70 6f 6e 73 65 3d 22 39 34 31 65 37 65 65 37 35 38 36 34 62 37 66 39 64 32 66 63 63 36 39 62 31 63 32 62 65 65 66 39 22 2c 71 6f 70 3d 61 75 74 68 2c 6e 63 3d 30 30 30 30 30 30 30 31 2c 63 6e 6f 6e 63 65 3d 22 30 61 65 31 34 32 33 62 22 [Tue Dec 30 23:39:36 2003] sip_radius.c(1115) Radius: max number of servers touse is 2.[Tue Dec 30 23:39:36 2003] sip_radius.c(1120) Radius: Start with server 1.[Tue Dec 30 23:39:36 2003] sip_radius.c(852) Radius: The RA is:[Tue Dec 30 23:39:36 2003] [debug] sip_radius.c(594): c1 b2 90 ad b0 f4 08 31 21 d6 73 e8 12 2d 89 c9

[Tue Dec 30 23:39:36 2003] sip_radius.c(1222) Radius: To send 424 bytes inrequest to b.19.174.128:1812.[Tue Dec 30 23:39:36 2003] [debug] sip_radius.c(594): 01 01 01 a8 c1 b2 90 ad b0 f4 08 31 21 d6 73 e8 12 2d 89 c9 04 06 ac 13 ae ef 3d 06 00 00 00 05 01 06 37 39 30 35 ce 22 39 34 31 65 37 65 65 37 35 38 36 34 62 37 66 39 64 32 66 63 63 36 39 62 31 63 32 62 65 65 66 39 cf 09 01 07 43 49 53 43 4f cf 0c 02 0a 33 66 66 32 30 63 62 38 cf 0c 03 0a 52 45 47 49 53 54 45 52 cf 11 04 0f 73 69 70 3a 76 76 73 2d 76 69 74 72 61 cf 08 05 06 61 75 74 68 cf 07 06 05 6d 64 35 cf 0c 08 0a 30 61 65 31 34 32 33 62 cf 0c 09 0a 30 30 30 30 30 30 30 31 cf 08 0a 06 37 39 30 35 1a 44 00 00 00 09 01 3e 73 69 70 2d 68 64 72 3d 46 72 6f 6d 3a 20 3c 73 69 70 3a 37 39 30 35 40 76 76 73 2d 76 69 74 72 61 3b 75 73 65 72 3d 70 68 6f 6e 65 3e 3b 74 61 67 3d 32 30 36 37 36 31 39 38 33 30 1a bb 00 00 00 09 01 b5 73 69 70 2d 68 64 72 3d 41 75 74 68 6f 72 69 7a 61 74 69 6f 6e 3a 20 44 69 67 65 73 74 20 75 73 65 72 6e 61 6d 65 3d 22 37 39 30 35 22 2c 72 65 61 6c 6d 3d 22 43 49 53 43 4f 22 2c 6e 6f 6e 63 65 3d 22 33 66 66 32 30 63 62 38 22 2c 75 72 69 3d 22 73 69 70 3a 76 76 73 2d 76 69 74 72 61 22 2c 72 65 73 70 6f 6e 73 65 3d 22 39 34 31 65 37 65 65 37 35 38 36 34 62 37 66 39 64 32 66 63 63 36 39 62 31 63 32 62 65 65 66 39 22 2c 71 6f 70 3d 61 75 74 68 2c 6e 63 3d 30 30 30 30 30 30 30 31 2c 63 6e 6f 6e 63 65 3d 22 30 61 65 31 34 32 33 62 22 [Tue Dec 30 23:39:36 2003] sip_radius.c(1300) Radius: read 20 bytes inresponse from b.19.174.128:1812.[Tue Dec 30 23:39:36 2003] [debug] sip_radius.c(594): 02 01 00 14 76 ec 5e db 1e 44 08 2e d5 2e c0 49 c6 b1 24 d9 [Tue Dec 30 23:39:36 2003] sip_radius.c(1410) Radius: server 1 responded withAccept. Mark it for next time use.[Tue Dec 30 23:39:36 2003] sip_sm.c(998) Sent 315 bytes UDP packet toa.22.76.101:5060 SIP/2.0 200 OKVia: SIP/2.0/UDP a.22.76.101:5060;received=a.22.76.101Call-ID: [email protected]: <sip:7905@vvs-vitra;user=phone>;tag=2067619830To: <sip:7905@vvs-vitra;user=phone>CSeq: 2 REGISTERContact: <sip:[email protected]:5060;user=phone;transport=udp>;expires=3600Content-Length: 0



REGISTER-Rejected Scenario Messages


Debug output from FreeRADIUS server with default accounting configuration:

rad_recv: Access-Request packet from host b.19.174.239:42198, id=3, length=424 NAS-IP-Address = b.19.174.239 NAS-Port-Type = Virtual User-Name = "7905" Digest-Response = "615abb60821975854f0c58eaebab2e53" Digest-Attributes = 0x0107434953434f Digest-Attributes = 0x020a3366663230646636 Digest-Attributes = 0x030a5245474953544552 Digest-Attributes = 0x040f7369703a7676732d7669747261 Digest-Attributes = 0x050661757468 Digest-Attributes = 0x06056d6435 Digest-Attributes = 0x080a3332356461326339 Digest-Attributes = 0x090a3030303030303031 Digest-Attributes = 0x0a0637393035 Cisco-AVPair = "sip-hdr=From: <sip:7905@vvs-vitra;user=phone>;tag=3563221112" Cisco-AVPair = "sip-hdr=Authorization: Digest username="7905",realm="CISCO",nonce="3ff20df6",uri="sip:vvs-vitra",response="615abb60821975854f0c58eaebab2e53",qop=auth,nc=00000001,cnonce="325da2c9""modcall: entering group authorize for request 0 modcall[authorize]: module "preprocess" returns ok for request 0radius_xlat: '/usr/local/var/log/radius/radacct/b.19.174.239/auth-detail-20031230'rlm_detail: /usr/local/var/log/radius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%d expands to /usr/local/var/log/radius/radacct/b.19.174.239/auth-detail-20031230 modcall[authorize]: module "auth_log" returns ok for request 0 rlm_digest: Converting Digest-Attributes to something sane... Digest-Realm = "CISCO" Digest-Nonce = "3ff20df6" Digest-Method = "REGISTER" Digest-URI = "sip:vvs-vitra" Digest-QOP = "auth" Digest-Algorithm = "md5" Digest-CNonce = "325da2c9" Digest-Nonce-Count = "00000001" Digest-User-Name = "7905"rlm_digest: Adding Auth-Type = DIGEST modcall[authorize]: module "digest" returns ok for request 0 rlm_realm: No '@' in User-Name = "7905", looking up realm NULL rlm_realm: No such realm "NULL" modcall[authorize]: module "suffix" returns noop for request 0 users: Matched 7905 at 81 modcall[authorize]: module "files" returns ok for request 0modcall: group authorize returns ok for request 0 rad_check_password: Found Auth-Type digestauth: type "digest"modcall: entering group authenticate for request 0A1 = 7905:CISCO:7905A2 = REGISTER:sip:vvs-vitraKD = 3e19688eef774a7e696e7f4e03f3b9d3:3ff20df6:00000001:325da2c9:auth:25da9a7c988b416dddf56c2879e477e0 rlm_digest: FAILED authentication modcall[authenticate]: module "digest" returns reject for request 0modcall: group authenticate returns reject for request 0auth: Failed to validate the user.Delaying request 0 for 1 secondsFinished request 0



Going to the next request--- Walking the entire request list ---Waking up in 1 seconds...--- Walking the entire request list ---Waking up in 1 seconds...--- Walking the entire request list ---Sending Access-Reject of id 3 to b.19.174.239:42198Waking up in 4 seconds...--- Walking the entire request list ---Cleaning up request 0 ID 3 with timestamp 3ff279a3Nothing to do. Sleeping until we see a request.


The following output is from the error_log file from Cisco SPS with the configuration listed in the “Configuring the REGISTER-Accepted Scenario” section on page 33.

[Tue Dec 30 23:44:54 2003] sip_protocol.c(5393) Received 415 bytes UDP packet from a.22.76.101:5060 REGISTER sip:vvs-vitra SIP/2.0Via: SIP/2.0/UDP a.22.76.101:5060From: <sip:7905@vvs-vitra;user=phone>;tag=3563221112To: <sip:7905@vvs-vitra;user=phone>Call-ID: [email protected]: 1 REGISTERContact: <sip:[email protected]:5060;user=phone;transport=udp>;expires=3600User-Agent: Cisco-CP7905/1.01-030512AAllow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTERContent-Length: 0

[Tue Dec 30 23:44:54 2003] sip_sm.c(998) Sent 242 bytes UDP packet to a.22.76.101:5060 SIP/2.0 100 TryingVia: SIP/2.0/UDP a.22.76.101:5060;received=a.22.76.101Call-ID: [email protected]: <sip:7905@vvs-vitra;user=phone>;tag=3563221112To: <sip:7905@vvs-vitra;user=phone>CSeq: 1 REGISTERContent-Length: 0

[Tue Dec 30 23:44:54 2003] sip_sm.c(998) Sent 333 bytes UDP packet to a.22.76.101:5060 SIP/2.0 401 UnauthorizedVia: SIP/2.0/UDP a.22.76.101:5060;received=a.22.76.101Call-ID: [email protected]: <sip:7905@vvs-vitra;user=phone>;tag=3563221112To: <sip:7905@vvs-vitra;user=phone>CSeq: 1 REGISTERWWW-Authenticate: DIGEST realm="CISCO", nonce="3ff20df6", qop="auth", algorithm=MD5Content-Length: 0

[Tue Dec 30 23:44:54 2003] sip_protocol.c(5393) Received 588 bytes UDP packet from a.22.76.101:5060 REGISTER sip:vvs-vitra SIP/2.0Via: SIP/2.0/UDP a.22.76.101:5060From: <sip:7905@vvs-vitra;user=phone>;tag=3563221112To: <sip:7905@vvs-vitra;user=phone>Call-ID: [email protected]




CSeq: 2 REGISTERContact: <sip:[email protected]:5060;user=phone;transport=udp>;expires=3600User-Agent: Cisco-CP7905/1.01-030512AAllow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTERAuthorization: Digest username="7905",realm="CISCO",nonce="3ff20df6",uri="sip:vvs-vitra",response="615abb60821975854f0c58eaebab2e53",qop=auth,nc=00000001,cnonce="325da2c9"Content-Length: 0

[Tue Dec 30 23:44:54 2003] sip_sm.c(998) Sent 242 bytes UDP packet to a.22.76.101:5060 SIP/2.0 100 TryingVia: SIP/2.0/UDP a.22.76.101:5060;received=a.22.76.101Call-ID: [email protected]: <sip:7905@vvs-vitra;user=phone>;tag=3563221112To: <sip:7905@vvs-vitra;user=phone>CSeq: 2 REGISTERContent-Length: 0

[Tue Dec 30 23:44:54 2003] sip_radius.c(675) Building attr - NAS-IP-Address b.19.174.239

[Tue Dec 30 23:44:54 2003] [debug] sip_radius.c(806): Attr built as 4 () 4 - NAS-IP-Address 6 bytes


[Tue Dec 30 23:44:54 2003] [debug] sip_radius.c(806): Attr built as 61 () 2 - NAS-Port-Type 6 bytes


[Tue Dec 30 23:44:54 2003] [debug] sip_radius.c(806): Attr built as 1 () 1 - User-Name 6 bytes

[Tue Dec 30 23:44:54 2003] [debug] sip_radius.c(594): 01 06 37 39 30 35 [Tue Dec 30 23:44:54 2003] sip_radius.c(675) Building attr - Digest-Response 615abb60821975854f0c58eaebab2e53

[Tue Dec 30 23:44:54 2003] [debug] sip_radius.c(806): Attr built as 206 () 1 - Digest-Response 34 bytes

[Tue Dec 30 23:44:54 2003] [debug] sip_radius.c(594): ce 22 36 31 35 61 62 62 36 30 38 32 31 39 37 35 38 35 34 66 30 63 35 38 65 61 65 62 61 62 32 65 35 33 [Tue Dec 30 23:44:54 2003] sip_radius.c(675) Building attr - digest-realm CISCO

[Tue Dec 30 23:44:54 2003] [debug] sip_radius.c(806): Attr built as 1 (DIGEST) 21 - digest-realm 9 bytes

[Tue Dec 30 23:44:54 2003] [debug] sip_radius.c(594): cf 09 01 07 43 49 53 43 4f [Tue Dec 30 23:44:54 2003] sip_radius.c(675) Building attr - digest-nonce 3ff20df6

[Tue Dec 30 23:44:54 2003] [debug] sip_radius.c(806): Attr built as 2 (DIGEST) 21 - digest-nonce 12 bytes



[Tue Dec 30 23:44:54 2003] [debug] sip_radius.c(594): cf 0c 02 0a 33 66 66 32 30 64 66 36 [Tue Dec 30 23:44:54 2003] sip_radius.c(675) Building attr - digest-method REGISTER

[Tue Dec 30 23:44:54 2003] [debug] sip_radius.c(806): Attr built as 3 (DIGEST) 21 - digest-method 12 bytes

[Tue Dec 30 23:44:54 2003] [debug] sip_radius.c(594): cf 0c 03 0a 52 45 47 49 53 54 45 52 [Tue Dec 30 23:44:54 2003] sip_radius.c(675) Building attr - digest-uri sip:vvs-vitra

[Tue Dec 30 23:44:54 2003] [debug] sip_radius.c(806): Attr built as 4 (DIGEST) 21 - digest-uri 17 bytes

[Tue Dec 30 23:44:54 2003] [debug] sip_radius.c(594): cf 11 04 0f 73 69 70 3a 76 76 73 2d 76 69 74 72 61 [Tue Dec 30 23:44:54 2003] sip_radius.c(675) Building attr - digest-qop auth

[Tue Dec 30 23:44:54 2003] [debug] sip_radius.c(806): Attr built as 5 (DIGEST) 21 - digest-qop 8 bytes


[Tue Dec 30 23:44:54 2003] [debug] sip_radius.c(806): Attr built as 6 (DIGEST) 21 - digest-alg 7 bytes

[Tue Dec 30 23:44:54 2003] [debug] sip_radius.c(594): cf 07 06 05 6d 64 35 [Tue Dec 30 23:44:54 2003] sip_radius.c(675) Building attr - digest-cnonce 325da2c9

[Tue Dec 30 23:44:54 2003] [debug] sip_radius.c(806): Attr built as 8 (DIGEST) 21 - digest-cnonce 12 bytes

[Tue Dec 30 23:44:54 2003] [debug] sip_radius.c(594): cf 0c 08 0a 33 32 35 64 61 32 63 39 [Tue Dec 30 23:44:54 2003] sip_radius.c(675) Building attr - digest-noncecount 00000001

[Tue Dec 30 23:44:54 2003] [debug] sip_radius.c(806): Attr built as 9 (DIGEST) 21 - digest-noncecount 12 bytes

[Tue Dec 30 23:44:54 2003] [debug] sip_radius.c(594): cf 0c 09 0a 30 30 30 30 30 30 30 31 [Tue Dec 30 23:44:54 2003] sip_radius.c(675) Building attr - digest-username 7905

[Tue Dec 30 23:44:54 2003] [debug] sip_radius.c(806): Attr built as 10 (DIGEST) 21 - digest-username 8 bytes

[Tue Dec 30 23:44:54 2003] [debug] sip_radius.c(594): cf 08 0a 06 37 39 30 35 [Tue Dec 30 23:44:54 2003] sip_radius.c(675) Building attr - sip-hdr= From: <sip:7905@vvs-vitra;user=phone>;tag=3563221112

[Tue Dec 30 23:44:54 2003] [debug] sip_radius.c(806): Attr built as 1 (VSA) 11 - sip-hdr= 68 bytes

[Tue Dec 30 23:44:54 2003] [debug] sip_radius.c(594): 1a 44 00 00 00 09 01 3e 73 69 70 2d 68 64 72 3d 46 72 6f 6d 3a 20 3c 73 69 70 3a 37 39 30 35 40 76 76 73 2d 76 69 74 72 61 3b 75 73 65 72 3d 70 68 6f 6e 65 3e 3b 74 61 67 3d 33 35 36 33 32 32



31 31 31 32 [Tue Dec 30 23:44:54 2003] sip_radius.c(675) Building attr - sip-hdr= Authorization: Digest username="7905",realm="CISCO",nonce="3ff20df6",uri="sip:vvs-vitra",response="615abb60821975854f0c58eaebab2e53",qop=auth,nc=00000001,cnonce="325da2c9"


[Tue Dec 30 23:44:54 2003] [debug] sip_radius.c(594): 1a bb 00 00 00 09 01 b5 73 69 70 2d 68 64 72 3d 41 75 74 68 6f 72 69 7a 61 74 69 6f 6e 3a 20 44 69 67 65 73 74 20 75 73 65 72 6e 61 6d 65 3d 22 37 39 30 35 22 2c 72 65 61 6c 6d 3d 22 43 49 53 43 4f 22 2c 6e 6f 6e 63 65 3d 22 33 66 66 32 30 64 66 36 22 2c 75 72 69 3d 22 73 69 70 3a 76 76 73 2d 76 69 74 72 61 22 2c 72 65 73 70 6f 6e 73 65 3d 22 36 31 35 61 62 62 36 30 38 32 31 39 37 35 38 35 34 66 30 63 35 38 65 61 65 62 61 62 32 65 35 33 22 2c 71 6f 70 3d 61 75 74 68 2c 6e 63 3d 30 30 30 30 30 30 30 31 2c 63 6e 6f 6e 63 65 3d 22 33 32 35 64 61 32 63 39 22 [Tue Dec 30 23:44:54 2003] sip_radius.c(1115) Radius: max number of servers to use is 2.[Tue Dec 30 23:44:54 2003] sip_radius.c(1120) Radius: Start with server 1.[Tue Dec 30 23:44:54 2003] sip_radius.c(852) Radius: The RA is:[Tue Dec 30 23:44:54 2003] [debug] sip_radius.c(594): 29 e1 18 55 45 3d c7 f7 0d 46 20 43 1a 46 b9 dc

[Tue Dec 30 23:44:54 2003] sip_radius.c(1222) Radius: To send 424 bytes in request to b.19.174.128:1812.[Tue Dec 30 23:44:54 2003] [debug] sip_radius.c(594): 01 03 01 a8 29 e1 18 55 45 3d c7 f7 0d 46 20 43 1a 46 b9 dc 04 06 ac 13 ae ef 3d 06 00 00 00 05 01 06 37 39 30 35 ce 22 36 31 35 61 62 62 36 30 38 32 31 39 37 35 38 35 34 66 30 63 35 38 65 61 65 62 61 62 32 65 35 33 cf 09 01 07 43 49 53 43 4f cf 0c 02 0a 33 66 66 32 30 64 66 36 cf 0c 03 0a 52 45 47 49 53 54 45 52 cf 11 04 0f 73 69 70 3a 76 76 73 2d 76 69 74 72 61 cf 08 05 06 61 75 74 68 cf 07 06 05 6d 64 35 cf 0c 08 0a 33 32 35 64 61 32 63 39 cf 0c 09 0a 30 30 30 30 30 30 30 31 cf 08 0a 06 37 39 30 35 1a 44 00 00 00 09 01 3e 73 69 70 2d 68 64 72 3d 46 72 6f 6d 3a 20 3c 73 69 70 3a 37 39 30 35 40 76 76 73 2d 76 69 74 72 61 3b 75 73 65 72 3d 70 68 6f 6e 65 3e 3b 74 61 67 3d 33 35 36 33 32 32 31 31 31 32 1a bb 00 00 00 09 01 b5 73 69 70 2d 68 64 72 3d 41 75 74 68 6f 72 69 7a 61 74 69 6f 6e 3a 20 44 69 67 65 73 74 20 75 73 65 72 6e 61 6d 65 3d 22 37 39 30 35 22 2c 72 65 61 6c 6d 3d 22 43 49 53 43 4f 22 2c 6e 6f 6e 63 65 3d 22 33 66 66 32 30 64 66 36 22 2c 75 72 69 3d 22 73 69 70 3a 76 76 73 2d 76 69 74 72 61 22 2c 72 65 73 70 6f 6e 73 65 3d 22 36 31 35 61 62 62 36 30 38 32 31 39 37 35 38 35 34 66 30 63 35 38 65 61 65 62 61 62 32 65 35 33 22 2c 71 6f 70 3d 61 75 74 68 2c 6e 63 3d 30 30 30 30 30 30 30 31 2c 63 6e 6f 6e 63 65 3d 22 33 32 35 64 61 32 63 39 22 [Tue Dec 30 23:44:56 2003] sip_radius.c(1300) Radius: read 20 bytes in response from b.19.174.128:1812.[Tue Dec 30 23:44:56 2003] [debug] sip_radius.c(594): 03 03 00 14 fe dd 35 8a 4a d2 7c ca 91 47 df 2b 9d b1 3a b2



[Tue Dec 30 23:44:56 2003] sip_radius.c(1319) Radius: received a response of type: 03 for a request of type: 01[Tue Dec 30 23:44:56 2003] sip_radius.c(1333) Radius: server 1 responded with Reject. Mark it for next time use.[Tue Dec 30 23:44:56 2003] sip_sm.c(998) Sent 333 bytes UDP packet to a.22.76.101:5060 SIP/2.0 401 UnauthorizedVia: SIP/2.0/UDP a.22.76.101:5060;received=a.22.76.101Call-ID: [email protected]: <sip:7905@vvs-vitra;user=phone>;tag=3563221112To: <sip:7905@vvs-vitra;user=phone>CSeq: 2 REGISTERWWW-Authenticate: DIGEST realm="CISCO", nonce="3ff20df8", qop="auth", algorithm=MD5Content-Length: 0

INVITE-Accepted Scenario Messages


The following debug output is from the FreeRADIUS server with default accounting configuration:

rad_recv: Access-Request packet from host b.19.174.239:42197, id=2,length=471 NAS-IP-Address = b.19.174.239 NAS-Port-Type = Virtual User-Name = "7963" Digest-Response = "ff6ee3d3658bc88a468c6c00ea1e8dca" Digest-Attributes = 0x0107434953434f Digest-Attributes = 0x020a3366663230643364 Digest-Attributes = 0x0308494e56495445 Digest-Attributes = 0x04147369703a3137322e31392e3137342e323339 Digest-Attributes = 0x050661757468 Digest-Attributes = 0x06054d4435 Digest-Attributes = 0x080a3164323638343164 Digest-Attributes = 0x090a3030303030303031 Digest-Attributes = 0x0a0637393633 Cisco-AVPair = "sip-hdr=From: "7963"<sip:7963@vvs-vitra>;tag=003094c450f0004524cb90f6-4ecd43a6" Cisco-AVPair = "sip-hdr=Proxy-Authorization: Digestusername="7963",realm="CISCO",uri="sip:b.19.174.239",response="ff6ee3d3658bc88a468c6c00ea1e8dca",nonce="3ff20d3d",cnonce="1d26841d",qop=auth,nc=00000001,algorithm=MD5"modcall: entering group authorize for request 0 modcall[authorize]: module "preprocess" returns ok for request 0radius_xlat:'/usr/local/var/log/radius/radacct/b.19.174.239/auth-detail-20031230'rlm_detail:/usr/local/var/log/radius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%dexpands to/usr/local/var/log/radius/radacct/b.19.174.239/auth-detail-20031230 modcall[authorize]: module "auth_log" returns ok for request 0 rlm_digest: Converting Digest-Attributes to something sane... Digest-Realm = "CISCO" Digest-Nonce = "3ff20d3d" Digest-Method = "INVITE" Digest-URI = "sip:b.19.174.239" Digest-QOP = "auth" Digest-Algorithm = "MD5" Digest-CNonce = "1d26841d" Digest-Nonce-Count = "00000001" Digest-User-Name = "7963"rlm_digest: Adding Auth-Type = DIGEST modcall[authorize]: module "digest" returns ok for request 0



rlm_realm: No '@' in User-Name = "7963", looking up realm NULL rlm_realm: No such realm "NULL" modcall[authorize]: module "suffix" returns noop for request 0 users: Matched 7963 at 80 modcall[authorize]: module "files" returns ok for request 0modcall: group authorize returns ok for request 0 rad_check_password: Found Auth-Type digestauth: type "digest"modcall: entering group authenticate for request 0A1 = 7963:CISCO:7963A2 = INVITE:sip:b.19.174.239KD =4a278b24f1a57dbb1f435baa29c52e9c:3ff20d3d:00000001:1d26841d:auth:aac772b9e1655193b6a615d4c48727ba modcall[authenticate]: module "digest" returns ok for request 0modcall: group authenticate returns ok for request 0Sending Access-Accept of id 2 to b.19.174.239:42197Finished request 0Going to the next request--- Walking the entire request list ---Waking up in 6 seconds...--- Walking the entire request list ---Cleaning up request 0 ID 2 with timestamp 3ff278eaNothing to do. Sleeping until we see a request.



[Tue Dec 30 23:41:49 2003] sip_protocol.c(5393) Received 645 bytes UDP packetfrom a.22.77.248:53095 INVITE sip:7905@vvs-vitra SIP/2.0Via: SIP/2.0/UDP a.22.77.248:5060From: "7963" <sip:7963@vvs-vitra>;tag=003094c450f0004524cb90f6-4ecd43a6To: <sip:7905@vvs-vitra>Call-ID: [email protected]: 101 INVITEUser-Agent: CSCO/4Contact: <sip:[email protected]:5060>Expires: 180Content-Type: application/sdpContent-Length: 246Accept: application/sdp


[Tue Dec 30 23:41:49 2003] sip_sm.c(998) Sent 275 bytes UDP packet toa.22.77.248:5060 SIP/2.0 100 Trying




Via: SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248Call-ID: [email protected]: "7963" <sip:7963@vvs-vitra>;tag=003094c450f0004524cb90f6-4ecd43a6To: <sip:7905@vvs-vitra>CSeq: 101 INVITEContent-Length: 0

[Tue Dec 30 23:41:49 2003] sip_sm.c(998) Sent 399 bytes UDP packet toa.22.77.248:5060 SIP/2.0 407 Proxy Authentication RequiredVia: SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248Call-ID: [email protected]: "7963" <sip:7963@vvs-vitra>;tag=003094c450f0004524cb90f6-4ecd43a6To: <sip:7905@vvs-vitra>;tag=6a31-5a90CSeq: 101 INVITEProxy-Authenticate: DIGEST realm="CISCO", nonce="3ff20d3d", qop="auth",algorithm=MD5Content-Length: 0

[Tue Dec 30 23:41:49 2003] sip_protocol.c(5393) Received 276 bytes UDP packetfrom a.22.77.248:51352 ACK sip:7905@vvs-vitra SIP/2.0Via: SIP/2.0/UDP a.22.77.248:5060From: "7963" <sip:7963@vvs-vitra>;tag=003094c450f0004524cb90f6-4ecd43a6To: <sip:7905@vvs-vitra>;tag=6a31-5a90Call-ID: [email protected]: 101 ACKContent-Length: 0

[Tue Dec 30 23:41:49 2003] sip_sm.c(3952) Found existing TCB 0xf680b9f8[Tue Dec 30 23:41:49 2003] sip_protocol.c(5393) Received 818 bytes UDP packetfrom a.22.77.248:53095 INVITE sip:7905@vvs-vitra SIP/2.0Via: SIP/2.0/UDP a.22.77.248:5060From: "7963" <sip:7963@vvs-vitra>;tag=003094c450f0004524cb90f6-4ecd43a6To: <sip:7905@vvs-vitra>Call-ID: [email protected]: 102 INVITEUser-Agent: CSCO/4Contact: <sip:[email protected]:5060>Proxy-Authorization: Digestusername="7963",realm="CISCO",uri="sip:b.19.174.239",response="ff6ee3d3658bc88a468c6c00ea1e8dca",nonce="3ff20d3d",cnonce="1d26841d",qop=auth,nc=00000001,algorithm=MD5Expires: 180Content-Type: application/sdpContent-Length: 246




[Tue Dec 30 23:41:49 2003] sip_sm.c(998) Sent 275 bytes UDP packet toa.22.77.248:5060 SIP/2.0 100 TryingVia: SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248Call-ID: [email protected]: "7963" <sip:7963@vvs-vitra>;tag=003094c450f0004524cb90f6-4ecd43a6To: <sip:7905@vvs-vitra>CSeq: 102 INVITEContent-Length: 0

[Tue Dec 30 23:41:49 2003] sip_radius.c(675) Building attr - NAS-IP-Addressb.19.174.239

[Tue Dec 30 23:41:49 2003] [debug] sip_radius.c(806): Attr built as 4 () 4 -NAS-IP-Address 6 bytes


[Tue Dec 30 23:41:49 2003] [debug] sip_radius.c(806): Attr built as 61 () 2 -NAS-Port-Type 6 bytes


[Tue Dec 30 23:41:49 2003] [debug] sip_radius.c(806): Attr built as 1 () 1 -User-Name 6 bytes

[Tue Dec 30 23:41:49 2003] [debug] sip_radius.c(594): 01 06 37 39 36 33 [Tue Dec 30 23:41:49 2003] sip_radius.c(675) Building attr - Digest-Responseff6ee3d3658bc88a468c6c00ea1e8dca

[Tue Dec 30 23:41:49 2003] [debug] sip_radius.c(806): Attr built as 206 () 1 -Digest-Response 34 bytes

[Tue Dec 30 23:41:49 2003] [debug] sip_radius.c(594): ce 22 66 66 36 65 65 33 64 33 36 35 38 62 63 38 38 61 34 36 38 63 36 63 30 30 65 61 31 65 38 64 63 61 [Tue Dec 30 23:41:49 2003] sip_radius.c(675) Building attr - digest-realmCISCO

[Tue Dec 30 23:41:49 2003] [debug] sip_radius.c(806): Attr built as 1 (DIGEST)21 - digest-realm 9 bytes

[Tue Dec 30 23:41:49 2003] [debug] sip_radius.c(594): cf 09 01 07 43 49 53 43 4f [Tue Dec 30 23:41:49 2003] sip_radius.c(675) Building attr - digest-nonce3ff20d3d

[Tue Dec 30 23:41:49 2003] [debug] sip_radius.c(806): Attr built as 2 (DIGEST)21 - digest-nonce 12 bytes

[Tue Dec 30 23:41:49 2003] [debug] sip_radius.c(594): cf 0c 02 0a 33 66 66 32 30 64 33 64 [Tue Dec 30 23:41:49 2003] sip_radius.c(675) Building attr - digest-methodINVITE



[Tue Dec 30 23:41:49 2003] [debug] sip_radius.c(806): Attr built as 3 (DIGEST)21 - digest-method 10 bytes

[Tue Dec 30 23:41:49 2003] [debug] sip_radius.c(594): cf 0a 03 08 49 4e 56 49 54 45 [Tue Dec 30 23:41:49 2003] sip_radius.c(675) Building attr - digest-urisip:b.19.174.239

[Tue Dec 30 23:41:49 2003] [debug] sip_radius.c(806): Attr built as 4 (DIGEST)21 - digest-uri 22 bytes

[Tue Dec 30 23:41:49 2003] [debug] sip_radius.c(594): cf 16 04 14 73 69 70 3a 31 37 32 2e 31 39 2e 31 37 34 2e 32 33 39 [Tue Dec 30 23:41:49 2003] sip_radius.c(675) Building attr - digest-qop auth

[Tue Dec 30 23:41:49 2003] [debug] sip_radius.c(806): Attr built as 5 (DIGEST)21 - digest-qop 8 bytes

[Tue Dec 30 23:41:49 2003] [debug] sip_radius.c(594): cf 08 05 06 61 75 74 68 [Tue Dec 30 23:41:49 2003] sip_radius.c(675) Building attr - digest-alg MD5

[Tue Dec 30 23:41:49 2003] [debug] sip_radius.c(806): Attr built as 6 (DIGEST)21 - digest-alg 7 bytes

[Tue Dec 30 23:41:49 2003] [debug] sip_radius.c(594): cf 07 06 05 4d 44 35 [Tue Dec 30 23:41:49 2003] sip_radius.c(675) Building attr - digest-cnonce1d26841d

[Tue Dec 30 23:41:49 2003] [debug] sip_radius.c(806): Attr built as 8 (DIGEST)21 - digest-cnonce 12 bytes

[Tue Dec 30 23:41:49 2003] [debug] sip_radius.c(594): cf 0c 08 0a 31 64 32 36 38 34 31 64 [Tue Dec 30 23:41:49 2003] sip_radius.c(675) Building attr - digest-noncecount00000001

[Tue Dec 30 23:41:49 2003] [debug] sip_radius.c(806): Attr built as 9 (DIGEST)21 - digest-noncecount 12 bytes

[Tue Dec 30 23:41:49 2003] [debug] sip_radius.c(594): cf 0c 09 0a 30 30 30 30 30 30 30 31 [Tue Dec 30 23:41:49 2003] sip_radius.c(675) Building attr - digest-username7963

[Tue Dec 30 23:41:49 2003] [debug] sip_radius.c(806): Attr built as 10(DIGEST) 21 - digest-username 8 bytes

[Tue Dec 30 23:41:49 2003] [debug] sip_radius.c(594): cf 08 0a 06 37 39 36 33 [Tue Dec 30 23:41:49 2003] sip_radius.c(675) Building attr - sip-hdr= From:"7963" <sip:7963@vvs-vitra>;tag=003094c450f0004524cb90f6-4ecd43a6


[Tue Dec 30 23:41:49 2003] [debug] sip_radius.c(594): 1a 57 00 00 00 09 01 51 73 69 70 2d 68 64 72 3d 46 72 6f 6d 3a 20 22 37 39 36 33 22 20 3c 73 69 70 3a 37 39 36 33 40 76 76 73 2d 76 69 74 72 61 3e 3b 74 61 67 3d 30 30 33 30 39 34 63 34 35 30



66 30 30 30 34 35 32 34 63 62 39 30 66 36 2d 34 65 63 64 34 33 61 36 [Tue Dec 30 23:41:49 2003] sip_radius.c(675) Building attr - sip-hdr=Proxy-Authorization: Digestusername="7963",realm="CISCO",uri="sip:b.19.174.239",response="ff6ee3d3658bc88a468c6c00ea1e8dca",nonce="3ff20d3d",cnonce="1d26841d",qop=auth,nc=00000001,algorithm=MD5


[Tue Dec 30 23:41:49 2003] [debug] sip_radius.c(594): 1a d4 00 00 00 09 01 ce 73 69 70 2d 68 64 72 3d 50 72 6f 78 79 2d 41 75 74 68 6f 72 69 7a 61 74 69 6f 6e 3a 20 44 69 67 65 73 74 20 75 73 65 72 6e 61 6d 65 3d 22 37 39 36 33 22 2c 72 65 61 6c 6d 3d 22 43 49 53 43 4f 22 2c 75 72 69 3d 22 73 69 70 3a 31 37 32 2e 31 39 2e 31 37 34 2e 32 33 39 22 2c 72 65 73 70 6f 6e 73 65 3d 22 66 66 36 65 65 33 64 33 36 35 38 62 63 38 38 61 34 36 38 63 36 63 30 30 65 61 31 65 38 64 63 61 22 2c 6e 6f 6e 63 65 3d 22 33 66 66 32 30 64 33 64 22 2c 63 6e 6f 6e 63 65 3d 22 31 64 32 36 38 34 31 64 22 2c 71 6f 70 3d 61 75 74 68 2c 6e 63 3d 30 30 30 30 30 30 30 31 2c 61 6c 67 6f 72 69 74 68 6d 3d 4d 44 35 [Tue Dec 30 23:41:49 2003] sip_radius.c(1115) Radius: max number of servers touse is 2.[Tue Dec 30 23:41:49 2003] sip_radius.c(1120) Radius: Start with server 1.[Tue Dec 30 23:41:49 2003] sip_radius.c(852) Radius: The RA is:[Tue Dec 30 23:41:49 2003] [debug] sip_radius.c(594): dd 31 92 00 04 a8 de 8f b7 13 76 be 58 40 41 dd

[Tue Dec 30 23:41:49 2003] sip_radius.c(1222) Radius: To send 471 bytes inrequest to b.19.174.128:1812.[Tue Dec 30 23:41:49 2003] [debug] sip_radius.c(594): 01 02 01 d7 dd 31 92 00 04 a8 de 8f b7 13 76 be 58 40 41 dd 04 06 ac 13 ae ef 3d 06 00 00 00 05 01 06 37 39 36 33 ce 22 66 66 36 65 65 33 64 33 36 35 38 62 63 38 38 61 34 36 38 63 36 63 30 30 65 61 31 65 38 64 63 61 cf 09 01 07 43 49 53 43 4f cf 0c 02 0a 33 66 66 32 30 64 33 64 cf 0a 03 08 49 4e 56 49 54 45 cf 16 04 14 73 69 70 3a 31 37 32 2e 31 39 2e 31 37 34 2e 32 33 39 cf 08 05 06 61 75 74 68 cf 07 06 05 4d 44 35 cf 0c 08 0a 31 64 32 36 38 34 31 64 cf 0c 09 0a 30 30 30 30 30 30 30 31 cf 08 0a 06 37 39 36 33 1a 57 00 00 00 09 01 51 73 69 70 2d 68 64 72 3d 46 72 6f 6d 3a 20 22 37 39 36 33 22 20 3c 73 69 70 3a 37 39 36 33 40 76 76 73 2d 76 69 74 72 61 3e 3b 74 61 67 3d 30 30 33 30 39 34 63 34 35 30 66 30 30 30 34 35 32 34 63 62 39 30 66 36 2d 34 65 63 64 34 33 61 36 1a d4 00 00 00 09 01 ce 73 69 70 2d 68 64 72 3d 50 72 6f 78 79 2d 41 75 74 68 6f 72 69 7a 61 74 69 6f 6e 3a 20 44 69 67 65 73 74 20 75 73 65 72 6e 61 6d 65 3d 22 37 39 36 33 22 2c 72 65 61 6c 6d 3d 22 43 49 53 43 4f 22 2c 75 72 69 3d 22 73 69 70 3a 31 37 32 2e 31 39 2e 31 37 34 2e 32 33 39 22 2c 72 65 73 70 6f 6e 73 65 3d 22 66 66 36 65 65 33 64 33 36 35 38 62 63 38 38 61 34 36 38 63 36 63 30 30 65 61 31 65 38 64 63 61 22 2c 6e 6f 6e 63 65 3d 22 33 66 66 32 30 64 33 64 22 2c 63 6e 6f 6e 63 65 3d 22 31 64 32 36 38 34 31 64 22 2c 71 6f 70 3d 61 75 74 68 2c 6e 63 3d 30 30 30 30 30 30 30 31 2c 61 6c 67 6f 72 69



74 68 6d 3d 4d 44 35 [Tue Dec 30 23:41:49 2003] sip_radius.c(1300) Radius: read 20 bytes inresponse from b.19.174.128:1812.[Tue Dec 30 23:41:49 2003] [debug] sip_radius.c(594): 02 02 00 14 2b 39 72 bd 6a 76 8e ac f6 09 ae bd c9 50 5a 39 [Tue Dec 30 23:41:49 2003] sip_radius.c(1410) Radius: server 1 responded withAccept. Mark it for next time use.[Tue Dec 30 23:41:49 2003] sip_sm.c(828) TCB_PROXIED_STATE_TIMER : 180seconds.[Tue Dec 30 23:41:49 2003] sip_sm.c(2057) Translation yielded 1 URLs :<sip:[email protected]:5060;user=phone;transport=udp>[Tue Dec 30 23:41:49 2003] sip_dns.c(787) "A" Query for a.22.76.101successful, Got 1 IP addresses[Tue Dec 30 23:41:49 2003] sip_dns.c(136) A Record : a.22.76.101[Tue Dec 30 23:41:49 2003] sip_sm.c(998) Sent 758 bytes UDP packet toa.22.76.101:5060 INVITE sip:[email protected]:5060;user=phone;transport=udp SIP/2.0Via: SIP/2.0/UDPb.19.174.239:5060;branch=d6326196-b7e8e00e-e9ece47f-c9a447f3-1Via: SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248From: "7963" <sip:7963@vvs-vitra>;tag=003094c450f0004524cb90f6-4ecd43a6To: <sip:7905@vvs-vitra>Call-ID: [email protected]: 102 INVITEUser-Agent: CSCO/4Contact: <sip:[email protected]:5060>Expires: 180Content-Type: application/sdpContent-Length: 246


[Tue Dec 30 23:41:49 2003] sip_protocol.c(5393) Received 475 bytes UDP packetfrom a.22.76.101:5060 SIP/2.0 100 TryingVia: SIP/2.0/UDPb.19.174.239:5060;branch=d6326196-b7e8e00e-e9ece47f-c9a447f3-1Via: SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248From: "7963" <sip:7963@vvs-vitra>;tag=003094c450f0004524cb90f6-4ecd43a6To: <sip:7905@vvs-vitra>;tag=1164004558Call-ID: [email protected]: 102 INVITEServer: Cisco-CP7905/1.01-030512AAllow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTERContent-Length: 0

[Tue Dec 30 23:41:49 2003] sip_sm.c(4820) Found existing TCB 0xf680b698[Tue Dec 30 23:41:49 2003] sip_protocol.c(5393) Received 476 bytes UDP packetfrom a.22.76.101:5060 SIP/2.0 180 Ringing



Via: SIP/2.0/UDPb.19.174.239:5060;branch=d6326196-b7e8e00e-e9ece47f-c9a447f3-1Via: SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248From: "7963" <sip:7963@vvs-vitra>;tag=003094c450f0004524cb90f6-4ecd43a6To: <sip:7905@vvs-vitra>;tag=1164004558Call-ID: [email protected]: 102 INVITEServer: Cisco-CP7905/1.01-030512AAllow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTERContent-Length: 0

[Tue Dec 30 23:41:49 2003] sip_sm.c(4820) Found existing TCB 0xf680b698[Tue Dec 30 23:41:49 2003] sip_sm.c(998) Sent 395 bytes UDP packet toa.22.77.248:5060 SIP/2.0 180 Ringing Via: SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248From: "7963" <sip:7963@vvs-vitra>;tag=003094c450f0004524cb90f6-4ecd43a6To: <sip:7905@vvs-vitra>;tag=1164004558Call-ID: [email protected]: 102 INVITEServer: Cisco-CP7905/1.01-030512AAllow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTERContent-Length: 0

[Tue Dec 30 23:41:53 2003] sip_protocol.c(5393) Received 771 bytes UDP packetfrom a.22.76.101:5060 SIP/2.0 200 OKVia: SIP/2.0/UDPb.19.174.239:5060;branch=d6326196-b7e8e00e-e9ece47f-c9a447f3-1Via: SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248From: "7963" <sip:7963@vvs-vitra>;tag=003094c450f0004524cb90f6-4ecd43a6To: <sip:7905@vvs-vitra>;tag=1164004558Call-ID: [email protected]: 102 INVITEContact: <sip:[email protected]:5060;user=phone;transport=udp>Server: Cisco-CP7905/1.01-030512AAllow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTERContent-Length: 203Content-Type: application/sdp


[Tue Dec 30 23:41:53 2003] sip_sm.c(4820) Found existing TCB 0xf680b698[Tue Dec 30 23:41:53 2003] sip_sm.c(998) Sent 690 bytes UDP packet toa.22.77.248:5060 SIP/2.0 200 OK Via: SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248From: "7963" <sip:7963@vvs-vitra>;tag=003094c450f0004524cb90f6-4ecd43a6To: <sip:7905@vvs-vitra>;tag=1164004558Call-ID: [email protected]: 102 INVITE



Contact: <sip:[email protected]:5060;user=phone;transport=udp>Server: Cisco-CP7905/1.01-030512AAllow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTERContent-Length: 203Content-Type: application/sdp


INVITE-Rejected Scenario Messages


The following debug output is from the FreeRADIUS server with default accounting configuration:

rad_recv: Access-Request packet from host b.19.174.239:42202, id=4, length=438 NAS-IP-Address = b.19.174.239 NAS-Port-Type = Virtual User-Name = "7905" Digest-Response = "fc700864da67fdda09e9cb484c3792b4" Digest-Attributes = 0x0107434953434f Digest-Attributes = 0x020a3366663230653663 Digest-Attributes = 0x0308494e56495445 Digest-Attributes = 0x04147369703a37393633407676732d7669747261 Digest-Attributes = 0x050661757468 Digest-Attributes = 0x06056d6435 Digest-Attributes = 0x080a6263313165653031 Digest-Attributes = 0x090a3030303030303031 Digest-Attributes = 0x0a0637393035 Cisco-AVPair = "sip-hdr=From: <sip:7905@vvs-vitra;user=phone>;tag=3104391408" Cisco-AVPair = "sip-hdr=Proxy-Authorization: Digest username="7905",realm="CISCO",nonce="3ff20e6c",uri="sip:7963@vvs-vitra",response="fc700864da67fdda09e9cb484c3792b4",qop=auth,nc=00000001,cnonce="bc11ee01""modcall: entering group authorize for request 0 modcall[authorize]: module "preprocess" returns ok for request 0radius_xlat: '/usr/local/var/log/radius/radacct/b.19.174.239/auth-detail-20031230'rlm_detail: /usr/local/var/log/radius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%d expands to /usr/local/var/log/radius/radacct/b.19.174.239/auth-detail-20031230 modcall[authorize]: module "auth_log" returns ok for request 0 rlm_digest: Converting Digest-Attributes to something sane... Digest-Realm = "CISCO" Digest-Nonce = "3ff20e6c" Digest-Method = "INVITE" Digest-URI = "sip:7963@vvs-vitra" Digest-QOP = "auth" Digest-Algorithm = "md5" Digest-CNonce = "bc11ee01" Digest-Nonce-Count = "00000001" Digest-User-Name = "7905"rlm_digest: Adding Auth-Type = DIGEST modcall[authorize]: module "digest" returns ok for request 0 rlm_realm: No '@' in User-Name = "7905", looking up realm NULL



rlm_realm: No such realm "NULL" modcall[authorize]: module "suffix" returns noop for request 0 users: Matched 7905 at 81 modcall[authorize]: module "files" returns ok for request 0modcall: group authorize returns ok for request 0 rad_check_password: Found Auth-Type digestauth: type "digest"modcall: entering group authenticate for request 0A1 = 7905:CISCO:7905A2 = INVITE:sip:7963@vvs-vitraKD = 3e19688eef774a7e696e7f4e03f3b9d3:3ff20e6c:00000001:bc11ee01:auth:66b1cda66f0c9e67399b01a9d48cfe27 rlm_digest: FAILED authentication modcall[authenticate]: module "digest" returns reject for request 0modcall: group authenticate returns reject for request 0auth: Failed to validate the user.Delaying request 0 for 1 secondsFinished request 0Going to the next request--- Walking the entire request list ---Waking up in 1 seconds...--- Walking the entire request list ---Waking up in 1 seconds...--- Walking the entire request list ---Sending Access-Reject of id 4 to b.19.174.239:42202Waking up in 4 seconds...--- Walking the entire request list ---Cleaning up request 0 ID 4 with timestamp 3ff27a19Nothing to do. Sleeping until we see a request.



[Tue Dec 30 23:46:52 2003] sip_protocol.c(5393) Received 718 bytes UDP packet from a.22.76.101:5060 INVITE sip:7963@vvs-vitra;user=phone SIP/2.0Via: SIP/2.0/UDP a.22.76.101:5060From: <sip:7905@vvs-vitra;user=phone>;tag=3104391408To: <sip:7963@vvs-vitra;user=phone>Call-ID: [email protected]: 1 INVITEContact: <sip:[email protected]:5060;user=phone;transport=udp>User-Agent: Cisco-CP7905/1.01-030512AAllow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTERExpires: 300Content-Length: 257Content-Type: application/sdp

v=0o=7905 12797 12797 IN IP4 a.22.76.101s=Cisco 7905 SIP Callc=IN IP4 a.22.76.101t=0 0m=audio 16384 RTP/AVP 0 18 8 101a=rtpmap:0 PCMU/8000/1a=rtpmap:18 G729/8000/1a=rtpmap:8 PCMA/8000/1a=rtpmap:101 telephone-event/8000a=fmtp:101 0-15




[Tue Dec 30 23:46:52 2003] sip_sm.c(998) Sent 240 bytes UDP packet to a.22.76.101:5060 SIP/2.0 100 TryingVia: SIP/2.0/UDP a.22.76.101:5060;received=a.22.76.101Call-ID: [email protected]: <sip:7905@vvs-vitra;user=phone>;tag=3104391408To: <sip:7963@vvs-vitra;user=phone>CSeq: 1 INVITEContent-Length: 0

[Tue Dec 30 23:46:52 2003] sip_sm.c(998) Sent 364 bytes UDP packet to a.22.76.101:5060 SIP/2.0 407 Proxy Authentication RequiredVia: SIP/2.0/UDP a.22.76.101:5060;received=a.22.76.101Call-ID: [email protected]: <sip:7905@vvs-vitra;user=phone>;tag=3104391408To: <sip:7963@vvs-vitra;user=phone>;tag=3c95-6c35CSeq: 1 INVITEProxy-Authenticate: DIGEST realm="CISCO", nonce="3ff20e6c", qop="auth", algorithm=MD5Content-Length: 0

[Tue Dec 30 23:46:52 2003] sip_protocol.c(5393) Received 313 bytes UDP packet from a.22.76.101:5060 ACK sip:7963@vvs-vitra;user=phone SIP/2.0Via: SIP/2.0/UDP a.22.76.101:5060;received=a.22.76.101From: <sip:7905@vvs-vitra;user=phone>;tag=3104391408To: <sip:7963@vvs-vitra;user=phone>;tag=3c95-6c35Call-ID: [email protected]: 1 ACKUser-Agent: Cisco-CP7905/1.01-030512AContent-Length: 0

[Tue Dec 30 23:46:52 2003] sip_sm.c(3952) Found existing TCB 0xf680c418[Tue Dec 30 23:46:52 2003] sip_protocol.c(5393) Received 902 bytes UDP packet from a.22.76.101:5060 INVITE sip:7963@vvs-vitra;user=phone SIP/2.0Via: SIP/2.0/UDP a.22.76.101:5060From: <sip:7905@vvs-vitra;user=phone>;tag=3104391408To: <sip:7963@vvs-vitra;user=phone>Call-ID: [email protected]: 2 INVITEContact: <sip:[email protected]:5060;user=phone;transport=udp>User-Agent: Cisco-CP7905/1.01-030512AAllow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTERProxy-Authorization: Digest username="7905",realm="CISCO",nonce="3ff20e6c",uri="sip:7963@vvs-vitra",response="fc700864da67fdda09e9cb484c3792b4",qop=auth,nc=00000001,cnonce="bc11ee01"Expires: 300Content-Length: 257Content-Type: application/sdp

v=0o=7905 12802 12802 IN IP4 a.22.76.101s=Cisco 7905 SIP Callc=IN IP4 a.22.76.101t=0 0m=audio 16384 RTP/AVP 0 18 8 101a=rtpmap:0 PCMU/8000/1



a=rtpmap:18 G729/8000/1a=rtpmap:8 PCMA/8000/1a=rtpmap:101 telephone-event/8000a=fmtp:101 0-15

[Tue Dec 30 23:46:52 2003] sip_sm.c(998) Sent 240 bytes UDP packet to a.22.76.101:5060 SIP/2.0 100 TryingVia: SIP/2.0/UDP a.22.76.101:5060;received=a.22.76.101Call-ID: [email protected]: <sip:7905@vvs-vitra;user=phone>;tag=3104391408To: <sip:7963@vvs-vitra;user=phone>CSeq: 2 INVITEContent-Length: 0

[Tue Dec 30 23:46:52 2003] sip_radius.c(675) Building attr - NAS-IP-Address b.19.174.239

[Tue Dec 30 23:46:52 2003] [debug] sip_radius.c(806): Attr built as 4 () 4 - NAS-IP-Address 6 bytes


[Tue Dec 30 23:46:52 2003] [debug] sip_radius.c(806): Attr built as 61 () 2 - NAS-Port-Type 6 bytes


[Tue Dec 30 23:46:52 2003] [debug] sip_radius.c(806): Attr built as 1 () 1 - User-Name 6 bytes

[Tue Dec 30 23:46:52 2003] [debug] sip_radius.c(594): 01 06 37 39 30 35 [Tue Dec 30 23:46:52 2003] sip_radius.c(675) Building attr - Digest-Response fc700864da67fdda09e9cb484c3792b4

[Tue Dec 30 23:46:52 2003] [debug] sip_radius.c(806): Attr built as 206 () 1 - Digest-Response 34 bytes

[Tue Dec 30 23:46:52 2003] [debug] sip_radius.c(594): ce 22 66 63 37 30 30 38 36 34 64 61 36 37 66 64 64 61 30 39 65 39 63 62 34 38 34 63 33 37 39 32 62 34 [Tue Dec 30 23:46:52 2003] sip_radius.c(675) Building attr - digest-realm CISCO

[Tue Dec 30 23:46:52 2003] [debug] sip_radius.c(806): Attr built as 1 (DIGEST) 21 - digest-realm 9 bytes

[Tue Dec 30 23:46:52 2003] [debug] sip_radius.c(594): cf 09 01 07 43 49 53 43 4f [Tue Dec 30 23:46:52 2003] sip_radius.c(675) Building attr - digest-nonce 3ff20e6c

[Tue Dec 30 23:46:52 2003] [debug] sip_radius.c(806): Attr built as 2 (DIGEST) 21 - digest-nonce 12 bytes

[Tue Dec 30 23:46:52 2003] [debug] sip_radius.c(594): cf 0c 02 0a 33 66 66 32 30 65 36 63 [Tue Dec 30 23:46:52 2003] sip_radius.c(675) Building attr - digest-method INVITE



[Tue Dec 30 23:46:52 2003] [debug] sip_radius.c(806): Attr built as 3 (DIGEST) 21 - digest-method 10 bytes

[Tue Dec 30 23:46:52 2003] [debug] sip_radius.c(594): cf 0a 03 08 49 4e 56 49 54 45 [Tue Dec 30 23:46:52 2003] sip_radius.c(675) Building attr - digest-uri sip:7963@vvs-vitra

[Tue Dec 30 23:46:52 2003] [debug] sip_radius.c(806): Attr built as 4 (DIGEST) 21 - digest-uri 22 bytes

[Tue Dec 30 23:46:52 2003] [debug] sip_radius.c(594): cf 16 04 14 73 69 70 3a 37 39 36 33 40 76 76 73 2d 76 69 74 72 61 [Tue Dec 30 23:46:52 2003] sip_radius.c(675) Building attr - digest-qop auth

[Tue Dec 30 23:46:52 2003] [debug] sip_radius.c(806): Attr built as 5 (DIGEST) 21 - digest-qop 8 bytes


[Tue Dec 30 23:46:52 2003] [debug] sip_radius.c(806): Attr built as 6 (DIGEST) 21 - digest-alg 7 bytes

[Tue Dec 30 23:46:52 2003] [debug] sip_radius.c(594): cf 07 06 05 6d 64 35 [Tue Dec 30 23:46:52 2003] sip_radius.c(675) Building attr - digest-cnonce bc11ee01

[Tue Dec 30 23:46:52 2003] [debug] sip_radius.c(806): Attr built as 8 (DIGEST) 21 - digest-cnonce 12 bytes

[Tue Dec 30 23:46:52 2003] [debug] sip_radius.c(594): cf 0c 08 0a 62 63 31 31 65 65 30 31 [Tue Dec 30 23:46:52 2003] sip_radius.c(675) Building attr - digest-noncecount 00000001

[Tue Dec 30 23:46:52 2003] [debug] sip_radius.c(806): Attr built as 9 (DIGEST) 21 - digest-noncecount 12 bytes

[Tue Dec 30 23:46:52 2003] [debug] sip_radius.c(594): cf 0c 09 0a 30 30 30 30 30 30 30 31 [Tue Dec 30 23:46:52 2003] sip_radius.c(675) Building attr - digest-username 7905

[Tue Dec 30 23:46:52 2003] [debug] sip_radius.c(806): Attr built as 10 (DIGEST) 21 - digest-username 8 bytes

[Tue Dec 30 23:46:52 2003] [debug] sip_radius.c(594): cf 08 0a 06 37 39 30 35 [Tue Dec 30 23:46:52 2003] sip_radius.c(675) Building attr - sip-hdr= From: <sip:7905@vvs-vitra;user=phone>;tag=3104391408


[Tue Dec 30 23:46:52 2003] [debug] sip_radius.c(594): 1a 44 00 00 00 09 01 3e 73 69 70 2d 68 64 72 3d 46 72 6f 6d 3a 20 3c 73 69 70 3a 37 39 30 35 40 76 76 73 2d 76 69 74 72 61 3b 75 73 65 72 3d 70 68 6f 6e 65 3e 3b 74 61 67 3d 33 31 30 34 33 39 31 34 30 38 [Tue Dec 30 23:46:52 2003] sip_radius.c(675) Building attr - sip-hdr= Proxy-Authorization: Digest username="7905",realm="CISCO",nonce="3ff20e6c",uri="sip:7963@vvs-vitra",response="fc700864da67fdda09e9cb484c3792b4",qop=auth,nc=00000001,cnonce="bc11ee01"




[Tue Dec 30 23:46:52 2003] [debug] sip_radius.c(594): 1a c6 00 00 00 09 01 c0 73 69 70 2d 68 64 72 3d 50 72 6f 78 79 2d 41 75 74 68 6f 72 69 7a 61 74 69 6f 6e 3a 20 44 69 67 65 73 74 20 75 73 65 72 6e 61 6d 65 3d 22 37 39 30 35 22 2c 72 65 61 6c 6d 3d 22 43 49 53 43 4f 22 2c 6e 6f 6e 63 65 3d 22 33 66 66 32 30 65 36 63 22 2c 75 72 69 3d 22 73 69 70 3a 37 39 36 33 40 76 76 73 2d 76 69 74 72 61 22 2c 72 65 73 70 6f 6e 73 65 3d 22 66 63 37 30 30 38 36 34 64 61 36 37 66 64 64 61 30 39 65 39 63 62 34 38 34 63 33 37 39 32 62 34 22 2c 71 6f 70 3d 61 75 74 68 2c 6e 63 3d 30 30 30 30 30 30 30 31 2c 63 6e 6f 6e 63 65 3d 22 62 63 31 31 65 65 30 31 22 [Tue Dec 30 23:46:52 2003] sip_radius.c(1115) Radius: max number of servers to use is 2.[Tue Dec 30 23:46:52 2003] sip_radius.c(1120) Radius: Start with server 1.[Tue Dec 30 23:46:52 2003] sip_radius.c(852) Radius: The RA is:[Tue Dec 30 23:46:52 2003] [debug] sip_radius.c(594): a1 75 d0 c2 f9 1d 3f 77 45 b7 8c 76 04 47 57 19

[Tue Dec 30 23:46:52 2003] sip_radius.c(1222) Radius: To send 438 bytes in request to b.19.174.128:1812.[Tue Dec 30 23:46:52 2003] [debug] sip_radius.c(594): 01 04 01 b6 a1 75 d0 c2 f9 1d 3f 77 45 b7 8c 76 04 47 57 19 04 06 ac 13 ae ef 3d 06 00 00 00 05 01 06 37 39 30 35 ce 22 66 63 37 30 30 38 36 34 64 61 36 37 66 64 64 61 30 39 65 39 63 62 34 38 34 63 33 37 39 32 62 34 cf 09 01 07 43 49 53 43 4f cf 0c 02 0a 33 66 66 32 30 65 36 63 cf 0a 03 08 49 4e 56 49 54 45 cf 16 04 14 73 69 70 3a 37 39 36 33 40 76 76 73 2d 76 69 74 72 61 cf 08 05 06 61 75 74 68 cf 07 06 05 6d 64 35 cf 0c 08 0a 62 63 31 31 65 65 30 31 cf 0c 09 0a 30 30 30 30 30 30 30 31 cf 08 0a 06 37 39 30 35 1a 44 00 00 00 09 01 3e 73 69 70 2d 68 64 72 3d 46 72 6f 6d 3a 20 3c 73 69 70 3a 37 39 30 35 40 76 76 73 2d 76 69 74 72 61 3b 75 73 65 72 3d 70 68 6f 6e 65 3e 3b 74 61 67 3d 33 31 30 34 33 39 31 34 30 38 1a c6 00 00 00 09 01 c0 73 69 70 2d 68 64 72 3d 50 72 6f 78 79 2d 41 75 74 68 6f 72 69 7a 61 74 69 6f 6e 3a 20 44 69 67 65 73 74 20 75 73 65 72 6e 61 6d 65 3d 22 37 39 30 35 22 2c 72 65 61 6c 6d 3d 22 43 49 53 43 4f 22 2c 6e 6f 6e 63 65 3d 22 33 66 66 32 30 65 36 63 22 2c 75 72 69 3d 22 73 69 70 3a 37 39 36 33 40 76 76 73 2d 76 69 74 72 61 22 2c 72 65 73 70 6f 6e 73 65 3d 22 66 63 37 30 30 38 36 34 64 61 36 37 66 64 64 61 30 39 65 39 63 62 34 38 34 63 33 37 39 32 62 34 22 2c 71 6f 70 3d 61 75 74 68 2c 6e 63 3d 30 30 30 30 30 30 30 31 2c 63 6e 6f 6e 63 65 3d 22 62 63 31 31 65 65 30 31 22 [Tue Dec 30 23:46:54 2003] sip_radius.c(1300) Radius: read 20 bytes in response from b.19.174.128:1812.[Tue Dec 30 23:46:54 2003] [debug] sip_radius.c(594): 03 04 00 14 1f 75 ff 29 f5 eb c1 d7 ba 14 2c 26 35 ee 0c 6f [Tue Dec 30 23:46:54 2003] sip_radius.c(1319) Radius: received a response of type: 03 for a request of type: 01[Tue Dec 30 23:46:54 2003] sip_radius.c(1333) Radius: server 1 responded with Reject. Mark it for next time use.


RADIUS Interface for Cisco SPS Scenario Output AppendixRADIUS Preauthentication Message Listings

[Tue Dec 30 23:46:54 2003] sip_sm.c(998) Sent 364 bytes UDP packet to a.22.76.101:5060 SIP/2.0 407 Proxy Authentication RequiredVia: SIP/2.0/UDP a.22.76.101:5060;received=a.22.76.101Call-ID: [email protected]: <sip:7905@vvs-vitra;user=phone>;tag=3104391408To: <sip:7963@vvs-vitra;user=phone>;tag=6a31-5a90CSeq: 2 INVITEProxy-Authenticate: DIGEST realm="CISCO", nonce="3ff20e6e", qop="auth", algorithm=MD5Content-Length: 0

[Tue Dec 30 23:46:54 2003] sip_protocol.c(5393) Received 313 bytes UDP packet from a.22.76.101:5060 ACK sip:7963@vvs-vitra;user=phone SIP/2.0Via: SIP/2.0/UDP a.22.76.101:5060;received=a.22.76.101From: <sip:7905@vvs-vitra;user=phone>;tag=3104391408To: <sip:7963@vvs-vitra;user=phone>;tag=6a31-5a90Call-ID: [email protected]: 2 ACKUser-Agent: Cisco-CP7905/1.01-030512AContent-Length: 0 .

RADIUS Preauthentication Message ListingsOutput example for the INVITE-Rejected scenario.

INVITE-Rejected Scenario Messages


The following is debug output from the FreeRADIUS server with default accounting configuration:

rad_recv: Access-Request packet from host b.19.174.239:44629, id=1, length=235 User-Name = "7963" Service-Type = Call-Check Cisco-AVPair = "prev-hop-ip=a.22.77.248:5060" Cisco-AVPair = "resource-service=query" Cisco-AVPair = "[email protected]" Called-Station-Id = "<sip:7905@vvs-vitra>" Acct-Session-Id = "[email protected]"modcall: entering group authorize for request 0 modcall[authorize]: module "preprocess" returns ok for request 0radius_xlat: '/usr/local/var/log/radius/radacct/b.19.174.239/auth-detail-20040102'rlm_detail: /usr/local/var/log/radius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%d expands to /usr/local/var/log/radius/radacct/b.19.174.239/auth-detail-20040102 modcall[authorize]: module "auth_log" returns ok for request 0 modcall[authorize]: module "digest" returns noop for request 0 rlm_realm: No '@' in User-Name = "7963", looking up realm NULL rlm_realm: No such realm "NULL" modcall[authorize]: module "suffix" returns noop for request 0 users: Matched 7963 at 80 modcall[authorize]: module "files" returns ok for request 0modcall: group authorize returns ok for request 0 rad_check_password: Found Auth-Type digestauth: type "digest"modcall: entering group authenticate for request 0



ERROR: No Digest-Nonce: Cannot perform Digest authentication modcall[authenticate]: module "digest" returns invalid for request 0modcall: group authenticate returns invalid for request 0auth: Failed to validate the user.Delaying request 0 for 1 secondsFinished request 0Going to the next request--- Walking the entire request list ---Waking up in 1 seconds...--- Walking the entire request list ---Waking up in 1 seconds...--- Walking the entire request list ---Sending Access-Reject of id 1 to b.19.174.239:44629Waking up in 4 seconds...--- Walking the entire request list ---Cleaning up request 0 ID 1 with timestamp 3ff63741Nothing to do. Sleeping until we see a request.


The following output is from the error_log from Cisco SPS with the configuration listed in the “Configuring RADIUS Authentication” section on page 30.

[Fri Jan 02 19:51:27 2004] sip_protocol.c(5393) Received 645 bytes UDP packet from a.22.77.248:53095 INVITE sip:7905@vvs-vitra SIP/2.0Via: SIP/2.0/UDP a.22.77.248:5060From: "7963" <sip:7963@vvs-vitra>;tag=003094c450f00046366cef46-2c78a2acTo: <sip:7905@vvs-vitra>Call-ID: [email protected]: 101 INVITEUser-Agent: CSCO/4Contact: <sip:[email protected]:5060>Expires: 180Content-Type: application/sdpContent-Length: 246Accept: application/sdp


[Fri Jan 02 19:51:27 2004] sip_sm.c(998) Sent 275 bytes UDP packet to a.22.77.248:5060 SIP/2.0 100 TryingVia: SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248Call-ID: [email protected]: "7963" <sip:7963@vvs-vitra>;tag=003094c450f00046366cef46-2c78a2acTo: <sip:7905@vvs-vitra>CSeq: 101 INVITEContent-Length: 0




[Fri Jan 02 19:51:27 2004] mod_sip_rpms.c(574) find_prevhop_match() returns success.[Fri Jan 02 19:51:27 2004] mod_sip_rpms.c(473) Ready to do pre-auth query.[Fri Jan 02 19:51:27 2004] sip_radius.c(675) Building attr - User-Name 7963

[Fri Jan 02 19:51:27 2004] [debug] sip_radius.c(806): Attr built as 1 () 1 - User-Name 6 bytes

[Fri Jan 02 19:51:27 2004] [debug] sip_radius.c(594): 01 06 37 39 36 33 [Fri Jan 02 19:51:27 2004] sip_radius.c(675) Building attr - Service-Type 10

[Fri Jan 02 19:51:27 2004] [debug] sip_radius.c(806): Attr built as 6 () 2 - Service-Type 6 bytes

[Fri Jan 02 19:51:27 2004] [debug] sip_radius.c(594): 06 06 00 00 00 0a [Fri Jan 02 19:51:27 2004] sip_radius.c(675) Building attr - prev-hop-ip= a.22.77.248:5060

[Fri Jan 02 19:51:27 2004] [debug] sip_radius.c(806): Attr built as 1 (VSA) 11 - prev-hop-ip= 37 bytes

[Fri Jan 02 19:51:27 2004] [debug] sip_radius.c(594): 1a 25 00 00 00 09 01 1f 70 72 65 76 2d 68 6f 70 2d 69 70 3d 31 30 2e 32 32 2e 37 37 2e 32 34 38 3a 35 30 36 30 [Fri Jan 02 19:51:27 2004] sip_radius.c(675) Building attr - resource-service= query

[Fri Jan 02 19:51:27 2004] [debug] sip_radius.c(806): Attr built as 1 (VSA) 11 - resource-service= 30 bytes

[Fri Jan 02 19:51:27 2004] [debug] sip_radius.c(594): 1a 1e 00 00 00 09 01 18 72 65 73 6f 75 72 63 65 2d 73 65 72 76 69 63 65 3d 71 75 65 72 79 [Fri Jan 02 19:51:27 2004] sip_radius.c(675) Building attr - call-id= [email protected]

[Fri Jan 02 19:51:27 2004] [debug] sip_radius.c(806): Attr built as 1 (VSA) 11 - call-id= 64 bytes

[Fri Jan 02 19:51:27 2004] [debug] sip_radius.c(594): 1a 40 00 00 00 09 01 3a 63 61 6c 6c 2d 69 64 3d 30 30 33 30 39 34 63 34 2d 35 30 66 30 38 35 31 66 2d 34 62 38 61 31 66 30 37 2d 35 61 66 32 62 33 35 33 40 31 30 2e 32 32 2e 37 37 2e 32 34 38

[Fri Jan 02 19:51:27 2004] sip_radius.c(675) Building attr - Called-Station-Id <sip:7905@vvs-vitra>

[Fri Jan 02 19:51:27 2004] [debug] sip_radius.c(806): Attr built as 30 () 1 - Called-Station-Id 22 bytes

[Fri Jan 02 19:51:27 2004] [debug] sip_radius.c(594): 1e 16 3c 73 69 70 3a 37 39 30 35 40 76 76 73 2d 76 69 74 72 61 3e [Fri Jan 02 19:51:27 2004] sip_radius.c(675) Building attr - Acct-Session-Id [email protected]

[Fri Jan 02 19:51:27 2004] [debug] sip_radius.c(806): Attr built as 44 () 1 - Acct-Session-Id 50 bytes

[Fri Jan 02 19:51:27 2004] [debug] sip_radius.c(594): 2c 32 30 30 33 30 39 34 63 34 2d 35 30 66 30 38 35 31 66 2d 34 62 38 61 31 66 30 37 2d 35 61 66 32 62 33 35 33 40 31 30 2e 32 32 2e 37 37 2e 32



34 38 [Fri Jan 02 19:51:27 2004] mod_sip_rpms.c(520) The pre-auth query radius message is built as:

[Fri Jan 02 19:51:27 2004] [debug] sip_radius.c(594): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 06 37 39 36 33 06 06 00 00 00 0a 1a 25 00 00 00 09 01 1f 70 72 65 76 2d 68 6f 70 2d 69 70 3d 31 30 2e 32 32 2e 37 37 2e 32 34 38 3a 35 30 36 30 1a 1e 00 00 00 09 01 18 72 65 73 6f 75 72 63 65 2d 73 65 72 76 69 63 65 3d 71 75 65 72 79 1a 40 00 00 00 09 01 3a 63 61 6c 6c 2d 69 64 3d 30 30 33 30 39 34 63 34 2d 35 30 66 30 38 35 31 66 2d 34 62 38 61 31 66 30 37 2d 35 61 66 32 62 33 35 33 40 31 30 2e 32 32 2e 37 37 2e 32 34 38 1e 16 3c 73 69 70 3a 37 39 30 35 40 76 76 73 2d 76 69 74 72 61 3e 2c 32 30 30 33 30 39 34 63 34 2d 35 30 66 30 38 35 31 66 2d 34 62 38 61 31 66 30 37 2d 35 61 66 32 62 33 35 33 40 31 30 2e 32 32 2e 37 37 2e 32 34 38 [Fri Jan 02 19:51:27 2004] mod_sip_rpms.c(523) Send the pre-auth message to RPMS server.

[Fri Jan 02 19:51:27 2004] sip_radius.c(1115) Radius: max number of servers to use is 1.[Fri Jan 02 19:51:27 2004] sip_radius.c(1120) Radius: Start with server 1.[Fri Jan 02 19:51:27 2004] sip_radius.c(852) Radius: The RA is:[Fri Jan 02 19:51:27 2004] [debug] sip_radius.c(594): 1d 73 e6 4a cb a1 83 c2 f5 9a a3 de fc 26 c2 a3

[Fri Jan 02 19:51:27 2004] sip_radius.c(1222) Radius: To send 235 bytes in request to b.19.174.128:1812.[Fri Jan 02 19:51:27 2004] [debug] sip_radius.c(594): 01 01 00 eb 1d 73 e6 4a cb a1 83 c2 f5 9a a3 de fc 26 c2 a3 01 06 37 39 36 33 06 06 00 00 00 0a 1a 25 00 00 00 09 01 1f 70 72 65 76 2d 68 6f 70 2d 69 70 3d 31 30 2e 32 32 2e 37 37 2e 32 34 38 3a 35 30 36 30 1a 1e 00 00 00 09 01 18 72 65 73 6f 75 72 63 65 2d 73 65 72 76 69 63 65 3d 71 75 65 72 79 1a 40 00 00 00 09 01 3a 63 61 6c 6c 2d 69 64 3d 30 30 33 30 39 34 63 34 2d 35 30 66 30 38 35 31 66 2d 34 62 38 61 31 66 30 37 2d 35 61 66 32 62 33 35 33 40 31 30 2e 32 32 2e 37 37 2e 32 34 38 1e 16 3c 73 69 70 3a 37 39 30 35 40 76 76 73 2d 76 69 74 72 61 3e 2c 32 30 30 33 30 39 34 63 34 2d 35 30 66 30 38 35 31 66 2d 34 62 38 61 31 66 30 37 2d 35 61 66 32 62 33 35 33 40 31 30 2e 32 32 2e 37 37 2e 32 34 38 [Fri Jan 02 19:51:27 2004] mod_sip_db_mysql.c(279) DBMySQL: MySQL successfully connected to localhost.

[Fri Jan 02 19:51:28 2004] [notice] A new sipd child process (4959) has started.[Fri Jan 02 19:51:29 2004] sip_radius.c(1300) Radius: read 20 bytes in response from b.19.174.128:1812.[Fri Jan 02 19:51:29 2004] [debug] sip_radius.c(594): 03 01 00 14 10 c5 23 77 e9 98 cd ac c0 ea 80 b4 de a4 33 36 [Fri Jan 02 19:51:29 2004] sip_radius.c(1319) Radius: received a response of type: 03 for a request of type: 01[Fri Jan 02 19:51:29 2004] sip_radius.c(1333) Radius: server 1 responded with Reject. Mark it for next time use.[Fri Jan 02 19:51:29 2004] mod_sip_rpms.c(531) Pre-auth is rejected by RPMS server. Return 480 back to client.[Fri Jan 02 19:51:29 2004] sip_sm.c(3339) Pre-Authentication failed, return 480 to client.[Fri Jan 02 19:51:29 2004] sip_sm.c(998) Sent 306 bytes UDP packet to a.22.77.248:5060 SIP/2.0 480 Temporarily Unavailable



Via: SIP/2.0/UDP a.22.77.248:5060;received=a.22.77.248Call-ID: [email protected]: "7963" <sip:7963@vvs-vitra>;tag=003094c450f00046366cef46-2c78a2acTo: <sip:7905@vvs-vitra>;tag=2a0a-4b90CSeq: 101 INVITEContent-Length: 0

[Fri Jan 02 19:51:29 2004] sip_protocol.c(5393) Received 276 bytes UDP packet from a.22.77.248:51617 ACK sip:7905@vvs-vitra SIP/2.0Via: SIP/2.0/UDP a.22.77.248:5060From: "7963" <sip:7963@vvs-vitra>;tag=003094c450f00046366cef46-2c78a2acTo: <sip:7905@vvs-vitra>;tag=2a0a-4b90Call-ID: [email protected]: 101 ACKContent-Length: 0


I N D E X

A

Access-Request packets

attributes field 28, 41

authenticator field 27, 41

code field 26, 40

identifier field 27, 40

length field 27, 41

standard attributes 28

standard attributes (table) 28, 42

VSAs 29, 42

VSAs (table) 30

accounting

call flow (figure) 2

call-flow process 2

Cisco SPS overview 1

client-side 4

components (figure) 1

configuration example 18

configuration screens 50

configuring RADIUS 13

correlating records 12

message listings 62

overview 1

RADIUS 1

record format 7

server side 2

accounting record

authenticator field 8

code field 7

identifier field 7

length field 7

attribute value

See AV.

authentication

Cisco SPS overview 25



configuring 30

message listings 62, 129

overview 25

RADIUS 25

C

Call Detail Record

See CDR.

call detail record

See CDR.

call flow 23

INVITE accepted (figure) 37

INVITEaccepted (figure) 47

INVITE rejected (figure) 38, 48

REGISTER accepted (figure) 35

REGISTER rejected (figure) 36

successful call (figure) 19

unsuccessful call (figure) 21

cautions

usage in text x

CDR

RADIUS 1

Cisco Session Initiation Protocol (SIP) Proxy Server (SPS)

See Cisco SPS.

Cisco SPS

accounting requests 1

accounting screens 50

authentication 25

authentication screens 56

correlating records 12

overview vii


Index

preauthentication screens 59

RFCs vii

user interface appendix 49

client-side accounting 4

command syntax conventions viii

configuring

RADIUS accounting 13

D

directives

accounting module 15

RPMS module 45

SIP server core, accounting 16

SIP server core, authentication 32

SIP server core, preauthentication 45

documentation conventions viii

F

forked call


forked call (figure) 23

I

INVITE accepted

call flow (figure) 37, 47

INVITE rejected

call flow (figure) 38, 48

M

message listings

summary appendix 61


N

notes, usage in text x

P

preauthentication

components (figure) 39



configuring 43

message listings 154

RPMS 39

SLA 39

R

RADIUS

accounting record format 6, 7

accounting requests 1

authentication 25

CDR 1

configuring accounting 13

configuring authentication 30

configuring preauthentication 43

data format 26, 40

overview vii

request state machine 14

REGISTER accepted


REGISTER rejected


Resource Policy Management System

See RPMS.

RPMS

preauthentication 39

state machine (figure) 44

Index

S

server-side accounting 2

service-level agreement

See SLA.

service-level agreements

See SLA.

SLA

preauthentication vii, 39

successful cal


U

unsuccessful call


V

vendor specific attribute

See VSA.

vendor-specific attribute

See VSA.

VSA

Access-Request packet 29, 42

Cisco 3

sip-hdr 6

Index


RADIUS Interface for Cisco SPS - Cisco - Global Home … Documentation Organization viii RADIUS...

Documents

Transcript of RADIUS Interface for Cisco SPS - Cisco - Global Home … Documentation Organization viii RADIUS...