Re: [asterisk-users] CallerID from Samsung PBX line on FXO
Ira said at 13/11/2010 17:50:
At 05:56 AM 11/13/2010, you wrote:
John Novack said at 13/11/2010 12:58:
Ronny Adsetts wrote:
[...]
The problem I'm trying to solve at the moment is getting caller ID
info passed over to the SIP phones when calls are placed. The
exten = s,1,Verbose(1,Samsung 209 ${CALLERID(all)})
And I get the following:
Executing [...@samsung-209:1] Verbose(Zap/1-1, 1|Samsung 209
) in new stack
Try changing that line to:
exten = s,1,wait(1) or maybe wait(2)
That's what I had to do when I first set up Asterisk. Gives Asterisk
time to get the CID.
Right. Thanks for that pointer. I'll tweak the Wait() time once I've figured
out how the Samsung is actually sending the data, ie., in what format.
Ronny
--
Ronny Adsetts
Technical Director
Amazing Internet Ltd, London
t: +44 20 8607 9535
f: +44 20 8607 9536
w: www.amazinginternet.com
Registered office: UK House, 82 Heath Road, Twickenham TW1 4BW
Registered in England. Company No. 4042957
signature.asc
Description: OpenPGP digital signature
--
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
http://www.asterisk.org/hello
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
[asterisk-users] CallerID from Samsung PBX line on FXO
Hi, I've now set up Asterisk to interface with our current Samsung iDCS 100 PBX via an 8SLI analogue extension card in the Samsung and an Openvox A400P04 4-FXO card in the Asterisk box. It all works in that I can place calls in both directions from the office Samsung extensions and Asterisk SIP extensions. The only tricky bit was getting the FXO to detect hang-up from the Samsung correctly - a tweak on the Samsung config to make it hang up properly fixed this. So far Asterisk has been a joy to configure (apart from the default config which IMO should be stripped back to bare-bones and the config shipped as examples in the doc folder - this may be the fault of my distribution who's packages I used rather than get in to the hassle of software maintenance). The problem I'm trying to solve at the moment is getting caller ID info passed over to the SIP phones when calls are placed. The caller ID is coming through as 'asterisk' which I assume is the default if nothing is present. So does anyone have any idea on how to get caller ID info passed over from the incoming calls on the FXO lines? Or even how to find out if the caller ID info is being sent by the Samsung? Thanks for any help. Ronny -- Ronny Adsetts Technical Director Amazing Internet Ltd, London t: +44 20 8607 9535 f: +44 20 8607 9536 w: www.amazinginternet.com Registered office: UK House, 82 Heath Road, Twickenham TW1 4BW Registered in England. Company No. 4042957 signature.asc Description: OpenPGP digital signature -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] CallerID from Samsung PBX line on FXO
Ronny Adsetts wrote: Hi, I've now set up Asterisk to interface with our current Samsung iDCS 100 PBX via an 8SLI analogue extension card in the Samsung and an Openvox A400P04 4-FXO card in the Asterisk box. It all works in that I can place calls in both directions from the office Samsung extensions and Asterisk SIP extensions. The only tricky bit was getting the FXO to detect hang-up from the Samsung correctly - a tweak on the Samsung config to make it hang up properly fixed this. So far Asterisk has been a joy to configure (apart from the default config which IMO should be stripped back to bare-bones and the config shipped as examples in the doc folder - this may be the fault of my distribution who's packages I used rather than get in to the hassle of software maintenance). The problem I'm trying to solve at the moment is getting caller ID info passed over to the SIP phones when calls are placed. The caller ID is coming through as 'asterisk' which I assume is the default if nothing is present. So does anyone have any idea on how to get caller ID info passed over from the incoming calls on the FXO lines? Or even how to find out if the caller ID info is being sent by the Samsung? Thanks for any help. Ronny Assuming the Samsung is using the standard US method, a butt set across the output of one of the lines in monitor mode should allow you to hear the FSK tones between the first and second ring. Or a cheap CallerID box should display as well. Also assume you have the Asterisk end set to wait for the signal. there should be a one ring delay in the response from Asterisk as it waits for the FSK signal. John Novack -- Dog is my Co-pilot -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] CallerID from Samsung PBX line on FXO
John Novack said at 13/11/2010 12:58:
Ronny Adsetts wrote:
[...]
The problem I'm trying to solve at the moment is getting caller ID
info passed over to the SIP phones when calls are placed. The
caller ID is coming through as 'asterisk' which I assume is the
default if nothing is present. So does anyone have any idea on how
to get caller ID info passed over from the incoming calls on the
FXO lines? Or even how to find out if the caller ID info is being
sent by the Samsung?
Assuming the Samsung is using the standard US method, a butt set
across the output of one of the lines in monitor mode should allow
you to hear the FSK tones between the first and second ring. Or a
cheap CallerID box should display as well.
Also assume you have the Asterisk end set to wait for the signal.
there should be a one ring delay in the response from Asterisk as it
waits for the FSK signal.
I've tried a variety of options but currently have the following in the
[channels] section of zapata.conf:
usecallerid=yes
callerid=asreceived
cidsignalling=dtmf
cidstart=ring
sendcalleridafter=2
hidecallerid=no
I added the following to one of the FXO contexts:
exten = s,1,Verbose(1,Samsung 209 ${CALLERID(all)})
And I get the following:
Executing [...@samsung-209:1] Verbose(Zap/1-1, 1|Samsung 209 ) in new
stack
Not sure what means but I assume it's something like a null string?
Anyway, that's as successful as I've been, ie., not. :-).
Ronny
--
Ronny Adsetts
Technical Director
Amazing Internet Ltd, London
t: +44 20 8607 9535
f: +44 20 8607 9536
w: www.amazinginternet.com
Registered office: UK House, 82 Heath Road, Twickenham TW1 4BW
Registered in England. Company No. 4042957
signature.asc
Description: OpenPGP digital signature
--
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
http://www.asterisk.org/hello
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] CallerID from Samsung PBX line on FXO
At 05:56 AM 11/13/2010, you wrote:
John Novack said at 13/11/2010 12:58:
Ronny Adsetts wrote:
[...]
The problem I'm trying to solve at the moment is getting caller ID
info passed over to the SIP phones when calls are placed. The
exten = s,1,Verbose(1,Samsung 209 ${CALLERID(all)})
And I get the following:
Executing [...@samsung-209:1] Verbose(Zap/1-1, 1|Samsung 209
) in new stack
Try changing that line to:
exten = s,1,wait(1) or maybe wait(2)
That's what I had to do when I first set up Asterisk. Gives Asterisk
time to get the CID.
Ira
--
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
http://www.asterisk.org/hello
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] CallerID from Samsung PBX line on FXO
Ronny Adsetts wrote:
John Novack said at 13/11/2010 12:58:
Ronny Adsetts wrote:
[...]
The problem I'm trying to solve at the moment is getting caller ID
info passed over to the SIP phones when calls are placed. The
caller ID is coming through as 'asterisk' which I assume is the
default if nothing is present. So does anyone have any idea on how
to get caller ID info passed over from the incoming calls on the
FXO lines? Or even how to find out if the caller ID info is being
sent by the Samsung?
Assuming the Samsung is using the standard US method, a butt set
across the output of one of the lines in monitor mode should allow
you to hear the FSK tones between the first and second ring. Or a
cheap CallerID box should display as well.
Also assume you have the Asterisk end set to wait for the signal.
there should be a one ring delay in the response from Asterisk as it
waits for the FSK signal.
I've tried a variety of options but currently have the following in the
[channels] section of zapata.conf:
usecallerid=yes
callerid=asreceived
cidsignalling=dtmf
cidstart=ring
sendcalleridafter=2
hidecallerid=no
I added the following to one of the FXO contexts:
exten = s,1,Verbose(1,Samsung 209 ${CALLERID(all)})
And I get the following:
Executing [...@samsung-209:1] Verbose(Zap/1-1, 1|Samsung 209 ) in new
stack
Not sure what means but I assume it's something like a null string?
Anyway, that's as successful as I've been, ie., not. :-).
Ronny
What method does the Samsung use to send CLID?
For US systems, the FSK signal is between the first and second ring, is
NOT dtmf, and cidstart=ring isn't correct
You need to state where in the world the samsung thinks it is, and how
it is configured to send CLID.
If it isn't US, then others will have to help
In the US Asterisk will insert the proper delay when you state
usecallerid=yes
John Novack
--
Dog is my Co-pilot
--
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
http://www.asterisk.org/hello
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
