[Asterisk-Users] Grandstream Budgetone 100 Caller ID shows extension, not incoming Caller ID

2005-04-30 Thread Amit Sharma
Hi, Is this a known problem with Grandstream Budgetone 100, I could see several people complaining about this but no answers. Details -- 1) I am simply trying to go from one SIP extension to another, so the zapata.conf and zaptel.conf entries are irrelavant. 2) I added a NoOp(CALLERID=${

[Asterisk-Users] Grandstream Budgetone 100 Caller ID shows extension, not incoming Caller ID

2004-09-12 Thread Steven P. Donegan
I've looked through the archives - and see questions similar to mine, but no answers. What, if anything, can be done to get the incoming Caller ID to be presented on the Budgetone's Caller ID display? In all other respects the phone+Asterisk seem to be extremely happy with each other.

Re: [Asterisk-Users] Grandstream Budgetone 100 Caller ID shows extension, not incoming Caller ID

2005-04-30 Thread Brian Capouch
Amit Sharma wrote: Hi, Is this a known problem with Grandstream Budgetone 100, I could see several people complaining about this but no answers. Details -- 1) I am simply trying to go from one SIP extension to another, so the zapata.conf and zaptel.conf entries are irrelavant. 2) I added

Re: [Asterisk-Users] Grandstream Budgetone 100 Caller ID shows extension, not incoming Caller ID

2004-09-12 Thread Duane
Steven P. Donegan wrote: I've looked through the archives - and see questions similar to mine, but no answers. What, if anything, can be done to get the incoming Caller ID to be presented on the Budgetone's Caller ID display? In all other respects the phone+Asterisk seem to be extremely happy wi

Re: [Asterisk-Users] Grandstream Budgetone 100 Caller ID shows extension, not incoming Caller ID

2004-09-12 Thread Eric Wieling
On Sun, 2004-09-12 at 09:41, Duane wrote: > Steven P. Donegan wrote: > > > I've looked through the archives - and see questions similar to mine, > > but no answers. What, if anything, can be done to get the incoming > > Caller ID to be presented on the Budgetone's Caller ID display? In all > >

Re: [Asterisk-Users] Grandstream Budgetone 100 Caller ID shows extension, not incoming Caller ID

2004-09-12 Thread Steven P. Donegan
Eric Wieling wrote: On Sun, 2004-09-12 at 09:41, Duane wrote: Steven P. Donegan wrote: I've looked through the archives - and see questions similar to mine, but no answers. What, if anything, can be done to get the incoming Caller ID to be presented on the Budgetone's Caller ID display? I

Re: [Asterisk-Users] Grandstream Budgetone 100 Caller ID shows extension, not incoming Caller ID

2004-09-12 Thread Steve Maroney
Try upgrading the firmware Thank you, Steve Maroney On Sun, 12 Sep 2004, Steven P. Donegan wrote: > Eric Wieling wrote: > > >On Sun, 2004-09-12 at 09:41, Duane wrote: > > > > > >>Steven P. Donegan wrote: > >> > >> > >> > >>>I've looked through the archives - and see questions similar to mine, >

Re: [Asterisk-Users] Grandstream Budgetone 100 Caller ID shows extension, not incoming Caller ID

2004-09-12 Thread Steven P. Donegan
Firmware now current (1.0.5.11) - no change in what is displayed on the phone. Good thought though :-) Steve Maroney wrote: Try upgrading the firmware Thank you, Steve Maroney On Sun, 12 Sep 2004, Steven P. Donegan wrote: Eric Wieling wrote: On Sun, 2004-09-12 at 09:41, Duane wrote:

Re: [Asterisk-Users] Grandstream Budgetone 100 Caller ID shows extension, not incoming Caller ID

2004-09-12 Thread Dave Cotton
On Sun, 2004-09-12 at 09:56 -0700, Steven P. Donegan wrote: > >>sip.conf configlet: > >> > >>[1000] > >>type=friend > >>username=1000 > >>fromuser=1000 > >>callerid=Computer Room <1000> Just a thought I've had funnies before because * is picky about the syntax of the caller ID. callerid="Compute

Re: [Asterisk-Users] Grandstream Budgetone 100 Caller ID shows extension, not incoming Caller ID

2004-09-12 Thread Steve Maroney
Im not sure if you mentioned this or not, but what is your call originatiing from ? On an FXO port ? Make sure your zapata.conf file is correct. There are a lot of callerid options in there. Thank you, Steve Maroney On Sun, 12 Sep 2004, Steven P. Donegan wrote: > Firmware now current (1.0.5.11)