[Home]

Summary:ASTERISK-15453: [regression] Transfer is broken
Reporter:tootai (tootai)Labels:
Date Opened:2010-01-18 06:40:05.000-0600Date Closed:2010-02-22 16:03:34.000-0600
Priority:BlockerRegression?Yes
Status:Closed/CompleteComponents:Resources/res_features
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:On call transfer, the called extension is ringing and when the user is picking up the call, the originate of the transfer receive the message "pbx-invalid". Switching back to 1.4.28 make this feature working normally.

Here are the verbose logs from the end of the call (extension anature105 want to transfer a call to extension anature102):

[Jan 18 11:48:55] VERBOSE[28467] logger.c:     -- SIP/anature102-000001a5 is ringing
[Jan 18 11:48:56] VERBOSE[28467] logger.c:     -- SIP/anature102-000001a5 answered Local/102@to-ANature-2e66,2
[Jan 18 11:48:56] VERBOSE[28466] logger.c:     -- Local/102@to-ANature-2e66,1 stopped sounds
[Jan 18 11:48:56] VERBOSE[28466] logger.c:     -- Local/102@to-ANature-2e66,1 answered Local/102@from-ANature-3e04,2
[Jan 18 11:48:56] VERBOSE[28465] logger.c:     -- Stopped music on hold on Local/100@to-ANature-abad,2
[Jan 18 11:48:56] VERBOSE[28467] logger.c:   == Spawn extension (to-ANature, 102, 1) exited non-zero on 'Local/102@to-ANature-2e66,2'
[Jan 18 11:48:56] VERBOSE[28465] logger.c:     -- <SIP/anature105-000001a4> Playing 'pbx-invalid' (language 'fr')
[Jan 18 11:48:56] VERBOSE[28466] logger.c:   == Spawn extension (from-ANature, 102, 20) exited non-zero on 'Local/102@from-ANature-3e04,2'
Comments:By: tootai (tootai) 2010-01-18 09:50:59.000-0600

Question: is it normal to tag a bug as "related" to a bug which is opened against another version? And even more, an SVN one ...

Daniel
By: Leif Madsen (lmadsen) 2010-01-18 11:36:17.000-0600

It is normal to tag issues that appear similar, because the same code can be found in several versions.
By: Leif Madsen (lmadsen) 2010-01-18 11:37:22.000-0600

Which kind of transfer is this? Is this being done with built-in feature transfers, or SIP transfers? It appears to be done with a star code using the built-in transfer features, but want to double check.

Please provide steps on how to reproduce this issue.
By: tootai (tootai) 2010-01-18 12:27:58.000-0600

[featuremap]
atxfer=*2

...

Hitting *2 (customer phones are Snom300/320) you than have the atxfer behavior with transfer announcement.

Daniel
By: warlock52 (warlock52) 2010-01-18 22:47:12.000-0600

Attended Transfer also not working here with internal feature using star code. The recieving caller gets the call ringing but as soon as he tries to answer gets hungup with "Normal Clearing" (Zoiper) and the caller gets the message "I am sorry that is not a valid Extension, Please try again." after hearing the ringback untill the calling party tries to answer.
By: Leif Madsen (lmadsen) 2010-01-19 16:10:46.000-0600

I have confirmed this with Asterisk 1.4 revision 241228 today.
By: Leif Madsen (lmadsen) 2010-02-04 14:42:32.000-0600

Can someone please retest with anything after revision 244151 which closed issue ASTERISK-15367 ? That may be what resolves this issue?
By: David Brillert (aragon) 2010-02-05 11:52:13.000-0600

lmadesen: I just installed 244151 and tested my reported scenario and the transfer problem is fixed in this revision.