Yeah, did that too.. and still seeing the unmodified P-Asserted Identity...
On Wed, Mar 16, 2016 at 11:27 AM, Anthony Holloway < avholloway+cisco-v...@gmail.com> wrote: > If you apply it under voice service voip > sip, then it's applied to all > outgoing messages, regardless of dial-peer. Specifying it on the dial-peer > level is redundant at that point, though it does take precedence over the > global configuration. > > You can debug ccsip mess and grab an outgoing INVITE example and paste it > into the tool I linked before. > > On Wed, Mar 16, 2016 at 9:32 AM, Jonathan Charles <jonv...@gmail.com> > wrote: > >> Thanks, I checked and the voice class sip profile is on every dial peer >> not pointing at CCM, it is also applied under voice service voip - sip... >> >> I will run the debug after hours to see why it is not being applied... >> >> >> >> Jonathan >> >> On Wed, Mar 16, 2016 at 12:47 AM, Anthony Holloway < >> avholloway+cisco-v...@gmail.com> wrote: >> >>> Hey Jonathan, >>> >>> Make sure that the profile is on the correct outgoing dial-peer. SIP >>> profiles are only executed in the outgoing dial-peer, after the dial-peer >>> has been matched/selected. >>> >>> You can use debug voip ccapi inout or debug voip dialpeer to find out >>> which outgoing dial-peer is being matched. Also, you can use debug ccsip >>> all to see if and what the SIP profile is doing. >>> >>> Assuming dial-peer 200 is your guys, then you can use this tool to help >>> you design your profile: >>> >>> http://www.cisco.com/web/tsweb/tools/sip-profile/index.html >>> >>> I pasted your profile into the tool and gave it a sample input (it's >>> brief, I know) and here is the result: >>> >>> [image: Inline image 1] >>> >>> You should note that the red indicates a match and a replace happened, >>> but also note that the replaced pattern contains an extra > at the end. >>> The reason is because you told it the match ended with .com and not .com>. >>> The reason the first < was replace appropriately, is because your (.*) >>> accounts for it, as well as the space before it. >>> >>> I made a small adjustment to your profile, mainly to shorten it up, but >>> to also cleanup the extra > at the end >>> >>> [image: Inline image 2] >>> >>> I've never tried this next method before, but it seems a little cleaner >>> (less regex) than the above two modify profiles, albeit it takes two steps >>> to execute: >>> >>> [image: Inline image 3] >>> >>> That last option may not actually work in a real IOS device, as I'm not >>> sure if the message is re-read from the top after a rule matches. >>> >>> I hope that helps. >>> >>> On Wed, Mar 16, 2016 at 12:12 AM, Jonathan Charles <jonv...@gmail.com> >>> wrote: >>> >>>> So, we have a Century Link SIP trunk and we need to send a specific >>>> P-Asserted Identity for the call to work. >>>> >>>> We have: a >>>> >>>> voice class sip-profiles 101 >>>> >>>> request INVITE sip-header P-Asserted-Identity modify >>>> "P-Asserted-Identity:(.*)@voip.centurylink.com" "P-Asserted-Identity: < >>>> sip:3125551...@voip.centurylink.com>" >>>> ! >>>> >>>> TO change the P-Asserted ID to what CL wants... however it is not >>>> making the change... >>>> >>>> >>>> dial-peer voice 200 voip >>>> voice-class sip asserted-id pai >>>> voice-class sip profiles 101 >>>> >>>> What do we need to do to force a specific P-Asserted Identity...? >>>> >>>> >>>> TIA! >>>> >>>> >>>> >>>> Jonathan >>>> >>>> _______________________________________________ >>>> cisco-voip mailing list >>>> cisco-voip@puck.nether.net >>>> https://puck.nether.net/mailman/listinfo/cisco-voip >>>> >>>> >>> >> >
_______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip