Inquery in CSCtx15355 iwf@VCS_IP_Address

[Arbenjamin]

Dear all,

WIth refer to releas note X7-2 page 17,

Resolved caveats

CSCtx15355

Symptom: When receiving a H.323 Setup message and interworking it on the Cisco VCS, the SIP INVITE may go out with Contact and From headers of iwf@VCS_IP_Address if there is no Calling Party Number details in the H323-UserInformation section - VCS interworking should in that case take the calling party ID from other source information in the H.323 message, e.g.Q931 Calling Party Number digits.

Conditions: None.

Workaround: None.

However, We have faced this problem in our VCS X7.2 enironment. (Since the search history in the VCS display the

iwf@VCS_IP_Address ).

Can anyone explain on the term "if there is no Calling Party Number details in the H323-UserInformation section " in the Symptom ?

Just as a example, there are jabber client, is there any Calling Party Number in the H323 section?

Would anyone mind explaining the detail of the symptom?

Best Regards,

Ben

[Martin Koch]

If you have a jabber video client it will use sip in the first place to the call should not end up as an h323 call.

Could you describe your exact setup and call flow as well as what the exact issue and behavior is.

[VC VEGA]

Dear Martin,

We have received serveral cases from our clients, so we have carried some testing in our lab environment.

In the basic setup( one VCS control and one Expressway),

Source endpoint: EX60 SW TC5 (dail out with H323 protocol)

Destination endpoint: Jabber 4.2

1.CSCtx15355 issue may happen in the first 15 -30 mins of new created jabber account.

2.CSCtx15355 issue can be reproduced if the source endpint H323 alias is modified to "ex60@domain.com "(we have manally add a SPACE at the end of the alias)

3.CSCtx15355 issue can be reproduced if soruce endpoint as the third party H323 endpoint.

Since iwf@VCS_IP_Address is a valid address to the jabber user, we would like gather more information of issue in order to prevent.

Best Regards,

Ben