12-25-2012 06:34 PM - edited 03-18-2019 12:20 AM
Dear All,
I have a caller display ID issue with cisco ISDN Gateway and I hope someone can answer for me.
I have a ISDNGW, VCSC and an Endpoint (C40).
Endpoint is registered to VCSC with E.164 (xxxxx491).
When doing an outbound ISDN call from the endpoint with directory
number(DID) xxxxx491, the caller ID display on the receiving endpoint is
xxxxx490 which is the ISDNGW’s main number.
Is it possible to configure on ISDNGW to xxxxx491 instead?
Thanks in advance.
Solved! Go to Solution.
12-26-2012 01:34 PM
Hi Bo. If you can, double check settting under Settings>ISDN "Send Calling Number to ISDN Network" set to Always or Only if Numeric and the ISDN Side permits it, will send E164 alias of the system out to the ISDN network.
If this is not the case, h323 log and and ISDN, connection and H320 set to Errors, Warnings, Information and Trace of the call would be helpful. Clear the event log first, set these and then run the call. Set the modules back to default after the test is over.
Check this, and lets see where this goes if you want to.
VR
Patrick
12-25-2012 07:56 PM
Hi!
This should work, but there might be some limitations you might hit as:
* your provider does not support that you can set outbound call ids
* your provider always send the main number + the additional msn and your remote site only shows the main number
* you have to send an other number like just 491 or even more digits
* you send something unwanted (like you have a sip call or findme causing something which you did not expect)
* you are connected to some isdn pbx which is messing something up
* config on the isdn gw
* something else unforseen :-)
What do you get when you receive a call, the full xxxxx491 or just a part like 491? And what do you send out?
A good start is to look in the log files / traces of the isdn gw what is received and send out to isdn
and then talk to your isdn provider what should be presented.
Please remember to rate helpful responses and identify
12-26-2012 01:34 PM
Hi Bo. If you can, double check settting under Settings>ISDN "Send Calling Number to ISDN Network" set to Always or Only if Numeric and the ISDN Side permits it, will send E164 alias of the system out to the ISDN network.
If this is not the case, h323 log and and ISDN, connection and H320 set to Errors, Warnings, Information and Trace of the call would be helpful. Clear the event log first, set these and then run the call. Set the modules back to default after the test is over.
Check this, and lets see where this goes if you want to.
VR
Patrick
12-26-2012 03:27 PM
Always should be the default setting, changing it to numeric only can make sense, at least to try,
anyhow I would suggest to do the logging to see what he really receives / sends out and also to
check with his ISDN provider how the number needs to be signaled.
From the docu:
Send calling number to ISDN network | Select the appropriate setting. Some networks do not allow you to set this and the call will fail if you; in others, the call will only work if the caller's number is forwarded and the DN is set exactly right; and in most networks, the setting is completely ignored. Experiment and see which setting works best. |
|
Please remember to rate helpful responses and identify
01-01-2013 10:49 PM
Dear Martin and Patrick
Thank you so much for your help.
Problem have beeb solved.
The problem is the settting under Settings>ISDN "Send Calling Number to ISDN Network" set to 'Never'.
After set to 'Always' everything is working fine. Endpoint's E.164 can send out to far end.
Wish you,Happy New Year 2013!
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: