[cisco-voip] How to get farend dn in BIB recording

[Roberto.Guo]

Hi Wes,

Sorry for not answering your question.
The Version of  Cisco Call Manager in my environment is: 7.0.2.20000-5
and there is only one publisher for development use, there is no subscribers
.

I have just tested it on Cisco Call Manager 6.0.1.2000-4 without
subscribers.
And the result is the same as on CCM7, I get two sip invite message, the
devicename in the "from header" of the tow SIP INVITE messages are all the
devicename of the nearenddevice, the two SIP INVITE messages are as below:

"from header" of the first SIP INVITE message:
From:  <sip:8009 at 192.168.1.60 <sip%3A8009 at 192.168.1.60>
;x-nearend;x-refci=22710449;x-nearenddevice=SEP0017A4D0431E>;tag=00e54066-3454-4313-a880-97a2798d2cd2-22710454

"from header" of the second SIP INVITE message:
From:  <sip:8009 at 192.168.1.60 <sip%3A8009 at 192.168.1.60>
;x-farend;x-refci=22710449;x-nearenddevice=SEP0017A4D0431E>;tag=00e54066-3454-4313-a880-97a2798d2cd2-22710457


Thanks and best regards!

2009/7/9 Wes Sisk <wsisk at cisco.com>

> Hi Robert,
>
> Not answering my question is not very conducive to soliciting additional
> assistance.  I reviewed and agree the behavior you describe should be the
> behavior.  the defect i cited was closed after that specific subscirber CM
> node was reinstalled and the behavior was never observed again.
>
> So, either you have a reproducible failure in a thus far unnamed version of
> CM.  If it is reproducible on another cluster of the same version then it's
> time for a TAC case and bug investigation.
>
> Or, you have a one off issue with a server of unknown origin.  In which
> case it's time to insert disk1 and reinstall.
>
> Regards,
> wes
>
>
> On Wednesday, July 08, 2009 12:08:24 PM, Roberto.Guo
> <roberto.guo at gmail.com> <roberto.guo at gmail.com> wrote:
>
> Thanks for your attention,  in cisco's documetn, I saw the text below
> For a recording call to the recorder, the special tag in the "from header"
> of the SIP INVITE message indicates the source of the voice stream.
> For Agent Voice
> From "AgentUserName" <sip:agentDN at ccm;x-nearend;x-refCI=12345;
> x-nearenddevice=[agent_devicename]"
> For Customer Voice
> From "AgentUserName" <sip:agentDN at ccm;x-farend;x-refCI=12345;x-farenddevice=[farend_devicename]"
>
>
> but in my environment , I made a call from 8009 to 8006, but I saw the two
> Invite messages are not like the document says, I can only get 8009's device
> name from the nearend Invite message, but I can't get 8006's device name
> from the other Invite message.Below are the two Invite message's after I
> made the call from 8009 to 8006:
>
> From: <sip:8009 at 192.168.0.70 <sip%3A8009 at 192.168.0.70>
> ;x-nearend;x-refci=20846793;x-nearenddevice=SEP001873C0AF4A>;tag=01122845-1fca-452a-94f7-9baa2e9c84a3-20846798
> From: <sip:8009 at 192.168.0.70 <sip%3A8009 at 192.168.0.70>
> ;x-farend;x-refci=20846793;x-nearenddevice=SEP001873C0AF4A>;tag=01122845-1fca-452a-94f7-9baa2e9c84a3-20846801
>
>      Thanks very much!
>
>
> 2009/7/6 Wes Sisk <wsisk at cisco.com>
>
>> what version?  per:
>> CSCsr71132    Call Recording does not send 2nd Invite to recorder for
>> farenddevice
>>
>> there should be 2 invites one for near and one for far.
>>
>> /wes
>>
>> On Friday, July 03, 2009 2:46:00 PM, Roberto.Guo <roberto.guo at gmail.com><roberto.guo at gmail.com>wrote:
>>
>>  Hi All
>>
>>       I work on BIB recording these days, the sip trunk can receive 2
>> invite messages from ccm, but I can't get the farend DN from the “from
>> header” of the SIP INVITE message. In my test, I make a call from 8006 to
>> 8009(which is configed to record automaticly), when the call is setup, the
>> DN in the from header of the two SIP INVITE message are all 8009, how can I
>> know who calls 8009?
>>
>>      thanks!
>>
>>
>> ------------------------------
>>
>> _______________________________________________
>> cisco-voip mailing listcisco-voip at puck.nether.nethttps://puck.nether.net/mailman/listinfo/cisco-voip
>>
>>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20090710/f99de13b/attachment.html>