 |
History
| Log In
|
|
|
|
[
Permlink
| « Hide
]
Dung Le - 2008-02-03 02:46
It also happens with calls from another SCS or PSTN.
For SMC, 1535 and 11XX sets could you please also attach a PCAP trace. Thanks for this.
Not sure if you are using the correct method to do a consultative Transfer on the SMC 3456
You should answer the call Then click on Actions select "Call then Transfer" I have tried this and the call does transfer but then I am seeing a known interop issue with M50: "Q01757316 SCS500R2 normal Intercom transfer to M50R3 goes to Voicemail" Hi Chris,
I retested this problem on new build (3.9.7-011877) but it is still persisting. I recorded all the process on SMC set and attached in above. I also attached the software to open that file. (That is free software at the link below: http://support.webex.com/support/downloads.html ) Attached files:
conf_xfer_incoming_call_from_BCM.pcap conf_xfer_incoming_call_from_BCM.wrf Desktop_Recoder.zip In the first case, looking at the call flow, I see that when B sends the REFER to C, C does not provide a response -- it should respond 202 Accepted quite quickly. C also does not appear to be generating the INVITE, but it might not be routed through sipX, so I might not see it in the sipX logs.
Set C identifies itself as "PolycomSoundPointIP-SPIP_650-UA/2.1.1.0052". We've had trouble with the 2.0 and 2.1 firmware and strongly suggest you upgrade to 2.2 before using Polycoms further. Nguyen,
A few questions and recommendations: #1- As Dale pointed out, can this be retried using Polycom f/w 2.2? #2- Is the Polycom configured with a DNS server that can resolve the domain "bcm.com" to the IP address of the BCM? #3- Is it possible to get a trace of this problem taken at the Polycom? Thanks! bob Hi Robert,
I retested this issue on new build (3.9.7-011968) and the problem is still persisting. ( blind transfer passed but consultative transfer failed) CLID and parties in this scenario are as below: Set A: 2255 (BCM set) Set B: 4311 (SMC456 version 2.3 RC4 (Nortel) build 46034) Set C: 4303 (LG6830 version 1.2.38sp) Call-Id: Y2VmY2I2NzA4OTYzYWFmZWM5MDljNmFkYWJlOTQ2NWE. Attached files: + sipx-configuration.tar.gz + SMC_BCM_xfer.pcap + merged.xml + SMC_BCM_xfer.wmv_ Nguyen,
Could you look at the three questions I posted in my last comment and provide an answer? Thank you. Also, please verify that Account Settings->Tolpology->IP Address == Use Local IP Address. and that 'Enable ICE' is disabled. Thanks, bob Hi Robert,
Please get my update on below: #1- As Dale pointed out, can this be retried using Polycom f/w 2.2? --> The scenario failed without belong on the client (set C). I retested the problem with set C is LG6830 (version 1.2.38sp) as mentioned above. #2- Is the Polycom configured with a DNS server that can resolve the domain "bcm.com" to the IP address of the BCM? --> We used SIP trunk between BCM and SCSin direct mode (using IP address not using domain of BCM, only set name to distinguish BCMs on our system, you can see domain name of BCM exchanged by IP address on sniffed file attached). #3- Is it possible to get a trace of this problem taken at the Polycom? --> If you attend to me retest again with set C is Polycom to narrow the problem, I will update it for you later. Can you also answer the ICE question Robert asked.
Looking at call-Id Y2VmY2I2NzA4OTYzYWFmZWM5MDljNmFkYWJlOTQ2NWE, I see it from 4303 to 4311. But I don't see any other call in the consultative transfer sequence; I don't see any other dialogs during the life of that dialog. A successful consultative transfer creates 3 dialogs, what are their call-Ids?
Hi Robert,
I captured new packet and snapshot of this scenario with new client as below: Set A: 2255 (BCM set) Set B: 4311 (SMC456 version 2.3 RC4 (Nortel) build 46034) Set C: 4021 (PolycomSoundPointIP-SPIP_650-UA/2.2.2.0084) Call-ID: 30e4dec8-a145f07-13c4-47ce475b-3850cb53-47ce475b@10.20.95.7 Polycom is updated firmware as requirement. SMC3456's parameters are also set as your requirement (Disable: ICE; Using: Use Local IP address). I captured sniff file at SMC and Polycom. To see the package at SMC, please filter: sip&&ip.addr==10.20.90.176 And the package at Polycom, please filer: sip&&ip.addr==10.20.90.178 And after press transfer at SMC, set A and set C is disconnected, set B is also disconnected later. I saw that BCM replied to set C (Polycom) with the message: 484 Address Incomplete (packet number 1975). P/s : the problem also happens like that with LG1535. Attached files: BCM_SMC_xfer_Mar05.pcap merged_Mar05.xml sipx-configuration_Mar05.tar.gz The problem also happens like that with SMC3455
The executing phone attempts to complete the cons. transf. by sending
a REFER at frame 1971. The Refer-To header is: Refer-To: "BCM50R3"<sip:anonymous@10.20.95.7?Replaces=...> The address here should be the known contact of the other end of the other call, which is <sip:anonymous@10.20.95.7:5060;maddr=10.20.95.7;transport=udp> I suspect that the SMC 3456 is picking up the To header rather than the Contact header. Frame 1972 is the stimulated INVITE. Its request-URI is sip:anonymous@10.20.95.7. The response to that at 1975 is "484 Address Incomplete". The response is generated by the BCM VoIP Gateway. Whether the gateway should reject this address is unclear, because the request-URI is missing the port number part, which the gateway seems to use in any URI referring to itself. Problems seen: The SMC 3456 is not copying the Contact header of the far end of the other call into the Refer-To header. There are at least two behaviors collaborating to the failure here.
#1- SMC seems to invert the order of the consultative transfer. Normally, if you use SIP phone to transfer Set A to Set C, we would expect to Phone to refer Set A to Set C but in actual fact, we see in the trace that SMC is referring Set C to Set A. I opened XECS-1171 to track this separately. #2- BCM is misconfigured and does not provide user part in From: and Contact: headers. Providing that information will help work around SMC's behavior as explained in #1. I will supply specific BCM configuration steps once I figure it out. Bob I have tried to re-create this issue using SMC 3456 Build 2.5 version 49518 amd I cannot reproduce with SCS 2.5 Build Software Communication System (3.11.6-013497 2008-09-24T04:48:20)
Could you please close the Jira? Thanks Chris |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Bug
Closed
Major
SMC3456 can not consultative transfer the incoming call from BCM to another extension of SCS.
