Skipped content of type multipart/alternative
http://bugs.digium.com/bug_view_advanced_page.php?bug_id=0003490 apply the patch: app_dial_CID_nodelete.patch and the deleting of the original callerid will stop in v1.0.5. Also in CVS_HEAD preserving original callerid has been given a flag 'o' in the dial string. MATT--- -----Original Message----- From: BiGReDSaL@ziplip.com [mailto:BiGReDSaL@ziplip.com] Sent: Friday, February 04, 2005 11:24 AM To: asterisk-users@lists.digium.com Subject: [Asterisk-Users] Callerid problems with 1.0.5 I just upgraded my two asterisk boxes to 1.0.5 stable and I've noticed that callerid is not functioning properly. My setup looks like this: SIP Phone <--> SER <--> Asterisk <--> Asterisk <---> PSTN No iax is being used at this time. The problem can be best described by the following scenarios: 1.) SIP to PSTN call: When a SIP phone calls a PSTN bound number, the callerid displayed on the PSTN phone is the number of the PSTN phone instead of the SIP phone's number. 2.) PSTN to SIP call: When a PSTN phone calls a SIP Phone number, the callerid displayed on the SIP phone is the number of the SIP phone instead of the PSTN phone's number. For both scenarios - ${CALLERID}, ${EXTEN}, and ${CALLERIDNUM} all have the number of the called phone for ZAP to SIP, SIP to ZAP, and SIP to SIP. I have noticed that explicitly declaring SetCallerID(${CALLERID}) before my dial seems to fixe this issue for only the ZAP to SIP piece. In the next Asterisk where a SIP to SIP relay is occurring ${CALLERID} ends up matchign ${EXTEN} again. This is causing some havoc with users calling cell phone from SIP phones. Some users are being dumped into certain company's cell phone voicemail because the callerid is keyed to the called phone's number. Has anyone else experienced this problem with 1.0.5 stable? I checked the bugs.digum.com page and found a similar bug with regard to the call being delivered to the manager API. Also, I searched the configs and I did not see any new settings related to callerid. If this is a simple configuration change introduced into version 1.0.5, any info would be greatly appreciated.
Supposedly when a call is parked and/or transferred they wanted the callerid to reflect the person who is on that phone call. That's the only reason I saw mentioned for the change. As for why it was made default I have no idea, but now in CVS_HEAD at least you can turn that feature off. And in v1.0.5 you can patch your system to remove that feature. MATT--- -----Original Message----- From: Kevin P. Fleming [mailto:kpfleming@starnetworks.us] Sent: Friday, February 04, 2005 12:01 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [Asterisk-Users] Callerid problems with 1.0.5 mattf wrote:> Also in CVS_HEAD preserving original callerid has been given a flag 'o' in > the dial string.I have to wonder why the default behavior was changed to this non-standard usage though; in what situations do we want the CLID/CNAM of the _recipient_ to be passed to them? _______________________________________________ Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Hello, patching v1.0.5 on my system removed the problem for me. But yes it seems strange that this feature was inserted into a final release with very little documentation of the wide implications that are caused by the change. This was corrected in CVS with the addition of a diabling flag for the dial command, but maybe this is a message that we should start an official beta release period before a release so that people can test pre-releases even for just a week to report problems before it is unleashed upon the world as an official release MATT--- -----Original Message----- From: Mark Eissler [mailto:mark@mixtur.com] Sent: Friday, February 04, 2005 9:26 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [Asterisk-Users] Callerid problems with 1.0.5 Yikes! On Feb 4, 2005, at 1:26 PM, Jay Milk wrote:> Can someone clarify what's going on here? > > I'm running 1.0.5, and I see caller-id come through just fine from one > extension to the other, as well as for incoming and outgoing calls > (iax2). What are you folks seeing there? >The behavior that was reported by Kevin is/was exactly the same behavior that I was experiencing with 1.0.5 and reported in another thread. I switched back to 1.0.2 to resolve that problem and another I was experiencing (SIP calls ringing forever instead of disconnecting even when voicemail had already picked up). Reading through the bug tracker on this one I must say I'm a bit confused. I understand the concept of showing useful/relevant callerid when a call is transferred (from park or some other extension) but I don't understand why a call should ever show the recipient extension's callerid. My understanding is that this is the default behavior when no other callerid is present and for some reason inbound callerid is getting wiped out because it's not correct. That some people are experiencing problems with this while others are not leads me to believe that it might be a problem that is exacerbated depending upon the dialplan setup. I'm just thinking this at the top of my head now, haven't looked back at my dialplan yet. What's annoying, either way, is that when this change was made the behavior of existing, functioning setups broke. I don't recall seeing any documentation for 1.0.5 that noted this might be the case and if the documentation is lacking...well, that's a problem. -mark -- Mark Eissler, mark@mixtur.com Mixtur Interactive, Inc. -@- http://www.mixtur.com _______________________________________________ Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users