Bookmark this page:
Yahoo!
Windows Live
del.icio.us
digg
Netscape
|
|
||||||||||||||||
|
Posted by Nick on July 28, 2006, 12:01 am
Please log in for more thread options hi, guys, I have problem on making outboud call throught our D/240SC-T1 card. And, We have a T1 to this card, I am using global call gc_makecall() to make outboud calls. And the protocol basically is ISDN, not TAPI.The BusType is SCBus.Protocol is ISDN 5ESS. Every time, when I call the gc_makecall(), nothing happenedd. I don't know if I need to do any other settings, or should I use different protocol? I am using SR 5.1, which sample program I should use to test? Thanks a lot. | ||||||||||||||||
|
Posted by Nick on July 28, 2006, 7:06 pm
Please log in for more thread options Nick wrote: And also, the T1 is from MCI, now is verizon. | ||||||||||||||||
|
Posted by Ray Cassick \(Home\) on July 28, 2006, 9:16 pm
Please log in for more thread options
The protocol is really dependent upon what your line is provisioned for and what the provider uses. Chances are if you are not seeing any yellow or red alarms your framing and coding are ok and unless you are getting errors back making the API call (gc_makecall) then your protocol is probably ok. I recommend a few things. 1) Check with your provider an ensure that your line is provisioned to allow outbound calls. ISDN lines can be set up in the PBX specifically for inbound or outbound only. Make sure you are set up for what you need. 2) Run a D-channel trace and take a look at the messages being exchanged for signaling. Maybe that will lead you to something. 3) Call your provider and have them trace their end when you make a call and tell you what they are seeing. Might point to something also. 4) 5.1 is VERY old and no longer supported by Intel/Dialogic. I always suggest that you move to the latest that you can get support for, in this case SR 5.1.1 FP1 SU 69 or greater. If your problem ends up being because of a bug in the software (I would not rule that out) you are not going to get a fix on software that old. 5) Never rule out a CO type issue. Maybe they have routing set up odd on tier end, maybe you need a special dial string or something like an account code along with the number. Ask them. The D-channel trace may also point to something here. Hope this helps a bit. > hi, guys,
> I have problem on making outboud call throught our D/240SC-T1 card. > And, We have a T1 to this card, I am using global call gc_makecall() to > make outboud calls. And the protocol basically is ISDN, not TAPI.The > BusType is SCBus.Protocol is ISDN 5ESS. Every time, when I call the > gc_makecall(), nothing happenedd. I don't know if I need to do any > other settings, or should I use different protocol? > I am using SR 5.1, which sample program I should use to test? > Thanks a lot. > | ||||||||||||||||
|
Posted by Nick on July 31, 2006, 6:18 pm
Please log in for more thread options
Thanks, I will try this. Ray Cassick (Home) wrote: > The protocol is really dependent upon what your line is provisioned for and
> what the provider uses. Chances are if you are not seeing any yellow or red > alarms your framing and coding are ok and unless you are getting errors back > making the API call (gc_makecall) then your protocol is probably ok. > > I recommend a few things. > > 1) Check with your provider an ensure that your line is provisioned to > allow outbound calls. ISDN lines can be set up in the PBX specifically for > inbound or outbound only. Make sure you are set up for what you need. > > 2) Run a D-channel trace and take a look at the messages being exchanged > for signaling. Maybe that will lead you to something. > > 3) Call your provider and have them trace their end when you make a call > and tell you what they are seeing. Might point to something also. > > 4) 5.1 is VERY old and no longer supported by Intel/Dialogic. I always > suggest that you move to the latest that you can get support for, in this > case SR 5.1.1 FP1 SU 69 or greater. If your problem ends up being because of > a bug in the software (I would not rule that out) you are not going to get a > fix on software that old. > > 5) Never rule out a CO type issue. Maybe they have routing set up odd on > tier end, maybe you need a special dial string or something like an account > code along with the number. Ask them. The D-channel trace may also point to > something here. > > Hope this helps a bit. > > > > hi, guys,
> > I have problem on making outboud call throught our D/240SC-T1 card. > > And, We have a T1 to this card, I am using global call gc_makecall() to > > make outboud calls. And the protocol basically is ISDN, not TAPI.The > > BusType is SCBus.Protocol is ISDN 5ESS. Every time, when I call the > > gc_makecall(), nothing happenedd. I don't know if I need to do any > > other settings, or should I use different protocol? > > I am using SR 5.1, which sample program I should use to test? > > Thanks a lot. > > | ||||||||||||||||
|
Posted by Nick on August 1, 2006, 4:48 pm
Please log in for more thread options
It works now. I think the T1 is fine, I am running it on 4ESS. Verizon told me they are running at 4ESS. I use isdiag tool following this link: http://threebit.net/projects/jvr/current/doc/html/ At the very bottom, it showed how to make a outgoing call. I followed the steps, and it worked in isdiag. Looks like we can not use the default setting all the time. I am trying to make it work in code. Nick wrote: > Thanks, I will try this.
> > Ray Cassick (Home) wrote: > > The protocol is really dependent upon what your line is provisioned for and
> > what the provider uses. Chances are if you are not seeing any yellow or red > > alarms your framing and coding are ok and unless you are getting errors back > > making the API call (gc_makecall) then your protocol is probably ok. > > > > I recommend a few things. > > > > 1) Check with your provider an ensure that your line is provisioned to > > allow outbound calls. ISDN lines can be set up in the PBX specifically for > > inbound or outbound only. Make sure you are set up for what you need. > > > > 2) Run a D-channel trace and take a look at the messages being exchanged > > for signaling. Maybe that will lead you to something. > > > > 3) Call your provider and have them trace their end when you make a call > > and tell you what they are seeing. Might point to something also. > > > > 4) 5.1 is VERY old and no longer supported by Intel/Dialogic. I always > > suggest that you move to the latest that you can get support for, in this > > case SR 5.1.1 FP1 SU 69 or greater. If your problem ends up being because of > > a bug in the software (I would not rule that out) you are not going to get a > > fix on software that old. > > > > 5) Never rule out a CO type issue. Maybe they have routing set up odd on > > tier end, maybe you need a special dial string or something like an account > > code along with the number. Ask them. The D-channel trace may also point to > > something here. > > > > Hope this helps a bit. > > > > > > > hi, guys,
> > > I have problem on making outboud call throught our D/240SC-T1 card. > > > And, We have a T1 to this card, I am using global call gc_makecall() to > > > make outboud calls. And the protocol basically is ISDN, not TAPI.The > > > BusType is SCBus.Protocol is ISDN 5ESS. Every time, when I call the > > > gc_makecall(), nothing happenedd. I don't know if I need to do any > > > other settings, or should I use different protocol? > > > I am using SR 5.1, which sample program I should use to test? > > > Thanks a lot. > > > | ||||||||||||||||

What protocol I should use in order to make outbound call?
Yahoo!
Windows Live
del.icio.us
digg
Netscape 






> I have problem on making outboud call throught our D/240SC-T1 card.
> And, We have a T1 to this card, I am using global call gc_makecall() to
> make outboud calls. And the protocol basically is ISDN, not TAPI.The
> BusType is SCBus.Protocol is ISDN 5ESS. Every time, when I call the
> gc_makecall(), nothing happenedd. I don't know if I need to do any
> other settings, or should I use different protocol?
> I am using SR 5.1, which sample program I should use to test?
> Thanks a lot.