Maheshbabu (or Vjmaheshbabu?),
1. I suggest you to remove your customers' info off the logs before attaching them
2. You have posted two not consecutive logs, the first ends @11:12:32.859, the second starts @11:13:45.093
3. Anyway, from the info I have:[list]
[li]agent 2509, logged on dn 399, dials ***7960[/li]
[li]requests conference call for recording[/li][/list]
###missing log###
[list][li]the agent seems now to be on a consult call with ***8946 [/li]
[li]the agent tries to initiate a conference calling again ***8946 (!!)[/li]
[li]obviously SIPServer doesn't really like that and responds with
[font=Times New Roman] [size=8pt]
sipcs: Call 0x045f1f30 is consult. No Consult call anymore
Response (496): for CRequest@042E9E40 RequestInitiateConference-amb-rec-ser-01[2756]/39
11:13:49.750 Trc 36002 Request rejected: error code 496(Call in invalid state)
@11:13:49.7500 [0] 7.5.000.41 send_to_client: message EventError
(Call in invalid state)
AttributeEventSequenceNumber 0000000000203061
AttributeTimeinuSecs 750000
AttributeTimeinSecs 1242279829 (11:13:49)
AttributeErrorCode 496
AttributeErrorMessage 'Call in invalid state'
AttributeThisDN '399'
AttributeConnID 009c01b0078e3956
AttributeOtherDN '***8946'
AttributeUserData [91] 00 01 00 00..
'GSIP_EMRGREC_FN' '2009-05-14\2509\2509_2009-05-14_309388437960_399_399_009c01b0078e3880'
AttributeReferenceID 39
AttributeClientID 2869
[/size][/font][/list]
[list][li]SIPServer doesn't get himself persuaded by the agent trying over and over again to initiate the conference call
[/li][/list]
Fra