Avaya Support Forums  

Go Back   Avaya Support Forums > Avaya Aura & Unified Communications

Thread Tools Search this Thread Display Modes
Old 09-29-2014, 08:33 AM
rime rime is offline
Join Date: Dec 2011
Posts: 60
rime has 10 reputation points
Default traceSM: understanding T: F: P: U: fields

When traceSM is running and displays message headers between entities, I can guess the meaning of the T: and F: fields, but what do U: and P: mean exactly ?

17:04:36.323 | |<--INVITE--| | | | | | (79) T:00447899998xxx F:+441942252xxx U:00447899998xxx P:terminating
Reply With Quote
Old 09-29-2014, 10:58 PM
sunilkumarv sunilkumarv is offline
Join Date: Mar 2010
Location: India
Posts: 124
sunilkumarv has 24 reputation pointssunilkumarv has 24 reputation points


u => uri
p => phase

Phase header is used for origination based routing. below is more info about this

Origination based routing vs. regular (R-URI based) routing
  • Origination based routing is a construct that SRE employs to route the incoming requests based on call phase to originator of the request or to destination of the request.
  • By default, SRE routes the requests based on origination (PAI) unless asked for termination based routing. It takes care of incoming requests, say EC-500, that SRE must route to the URE belonging to the originator of the call.
  • There are going to be cases, where the requesting elements (say URE) may want SRE to route requests based on termination rather than origination. In such instances, the requesting elements fill 'phase=term' tag in route header while forwarding request to SRE. On detecting such request, SRE shall route request to a URE associated with the user specified in R-URI.
  • Summary:
    • If the incoming request contains phase tag, SRE routes requests based on tag.
    • If there is no tag, SRE routes incoming requests based on origination.
    • For outbound calls, SRE reads the phase from route header belong to itself. SRE inserts same phase tag in the route header it inserts for the destination.
    • SRE never creates or flips the phase tag.
While routing calls to and from external network, SRE can also enforce additional policies while making routing decision. The policies include least-cost routing, time based routing (time of day, day of week), media preferences, logging requests with particular origination/destination. In case of network (interface or n/w element) failure detection, SRE routes the requests based on alternate routing rule


AVAYA| Voice: US:- +1 720 444 5271, India: +91 80 6715 3277 | Email:sunilkumarv@avaya.com|

Last edited by sunilkumarv; 09-29-2014 at 11:19 PM. Reason: adding more info
Reply With Quote

tracesm sip

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

All times are GMT -7. The time now is 02:33 PM.

This Forum is provided solely for the use and convenience of Avaya customers and partners. Use of the Forum is subject to the Terms and Use and Privacy Statement found at www.avaya.com. No other use is permitted. The Forum including all content posted is “AS IS” and Avaya expressly disclaims all warranties and/or guarantees as to its accuracy, reliability, usefulness, quality or non-infringement of intellectual property. Avaya reserves the right to remove any content posted on the Forum at any time and for whatever reason.

Avaya will not be liable for any content posted on this Forum, including, without limitation, any errors or omissions or for any losses or damages of any kind incurred as a result of use or reliance on any content, regardless of its origin.

You expressly understand and agree that you assume all risks associated with use or reliance on this content.