| Justin Steinberg 2007-06-22, 1:11 pm |
| Battery reversal is a form of disconnect supervision. In your case,
whatever is connected to your FXO port does not support battery reversal,
this is why your call is disconnected after the first ring. You are correct
to use no battery-reversal.
http://www.cisco.com/en/US/products....html#wp1497730
Is it possible that you are oversubscribed? I.e. all your FXO port
connections to GSM are engaged with either inbound or outbound calls?
Justin
On 6/22/07, gokhan senol <gokhanciscottl@yahoo.com> wrote:
>
> hi
>
> any idea pls, still i have big trouble with this issue.
>
>
> i got ccm 4.1.3 and fxo ports connected fct's for gsm connections
> Gateway and CCM has mgcp connection.
> On callmanager fxo port configuration, I configured AttendantDN for
> routing incoming calls to this DN.
>
> what is the relation of using battery reversal command for routing the
> incoming calls to Attendant DN which is specifed on callmanager.
>
> Because if i enabled *battery-reversal* under fxo port(it is also enabled
> default), calls directed to Attendant DN but only one time phone rings and
> then disconnects.
>
> But if i use *no battery-reversal* command under voice-port ,calls go to
> the AttendantDN and call can be set up succeessfully.But this time i often
> face to outgoing calls busy problem.
>
> voice port config
>
>
>
> voice-port 0/1/1
> timing hookflash-out 500
> description 5339203444
> !
>
> any idea
> thansk
> Gokhan
>
> ------------------------------
> Pinpoint customers
> <http://us.rd.yahoo.com/evt=48250/*h...&s=Y&s2=EM&b=50>who
> are looking for what you sell.
>
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
|