[asterisk-users] Remote-Party-Id and Attended Transfers
Has anyone noticed that Asterisk seems to always set the remote-party-id in a SIP invite to be the same value as the From: field? In most cases that isn't a problem. However, in the case of an attended transfer it IS a problem. The remote-party-id should be the party who initially called and the From: should be the party doing the attended transfer. This seems like a bug. - Doug. ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[asterisk-users] Remote-Party-Id and Attended Transfers
Has anyone noticed that Asterisk seems to always set the remote-party-id in a SIP invite to be the same value as the From: field? In most cases that isn't a problem. However, in the case of an attended transfer it IS a problem. The remote-party-id should be the party who initially called and the From: should be the party doing the attended transfer. This seems like a bug. - Doug. ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Remote-Party-Id and Attended Transfers
Douglas Garstang wrote: Has anyone noticed that Asterisk seems to always set the remote-party-id in a SIP invite to be the same value as the From: field? In most cases that isn't a problem. However, in the case of an attended transfer it IS a problem. The remote-party-id should be the party who initially called and the From: should be the party doing the attended transfer. This seems like a bug. pbx-1*CLI show application dial [snip] o- Specify that the CallerID that was present on the *calling* channel be set as the CallerID on the *called* channel. This was the behavior of Asterisk 1.0 and earlier. [snip] Also from UPGRADE.txt: Dialing: * The Caller*ID of the outbound leg is now the extension that was called, rather than the Caller*ID of the inbound leg of the call. The o flag for Dial can be used to restore the original behavior if desired. Note that if you are looking for the originating callerid from the manager event, there is a new manager event Dial which provides the source and destination channels and callerid. ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [asterisk-users] Remote-Party-Id and Attended Transfers
Doug, I've seen that and a similar thing with reversed from and to fields on a reinvite issue I'm having in 1.4. Olle was going to look at it. Kevin Collins -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Douglas Garstang Sent: Wednesday, November 01, 2006 3:13 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: [asterisk-users] Remote-Party-Id and Attended Transfers Has anyone noticed that Asterisk seems to always set the remote-party-id in a SIP invite to be the same value as the From: field? In most cases that isn't a problem. However, in the case of an attended transfer it IS a problem. The remote-party-id should be the party who initially called and the From: should be the party doing the attended transfer. This seems like a bug. - Doug. ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
RE: [asterisk-users] Remote-Party-Id and Attended Transfers
-Original Message- From: Eric ManxPower Wieling [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 01, 2006 1:58 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [asterisk-users] Remote-Party-Id and Attended Transfers Douglas Garstang wrote: Has anyone noticed that Asterisk seems to always set the remote-party-id in a SIP invite to be the same value as the From: field? In most cases that isn't a problem. However, in the case of an attended transfer it IS a problem. The remote-party-id should be the party who initially called and the From: should be the party doing the attended transfer. This seems like a bug. pbx-1*CLI show application dial [snip] o- Specify that the CallerID that was present on the *calling* channel be set as the CallerID on the *called* channel. This was the behavior of Asterisk 1.0 and earlier. [snip] Also from UPGRADE.txt: Dialing: * The Caller*ID of the outbound leg is now the extension that was called, rather than the Caller*ID of the inbound leg of the call. The o flag for Dial can be used to restore the original behavior if desired. Note that if you are looking for the originating callerid from the manager event, there is a new manager event Dial which provides the source and destination channels and callerid. Thanks, but how is this related to setting the Remote-Party-Id? Doug. ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
