[cisco-voip] Can't call out local lines

[Kris Seraphine]

voice-port x/x/x
 signal loop
 shut
 no shut

This will change the signaling to loop start on the voice port.  If you have
these ports configured as MGCP in CallManager, you'll eventually need to
delete and recreate them because you can only set the port type while
creating the port.

Changing it on the gateway should work temporarily and at least verify if
this solves the problem.

You'll know the ports are working as loopstart by looking at the vpm signal
debug output.  Instead of seeing GS in places you'll see LS.

On Tue, Jul 21, 2009 at 1:29 PM, Jeff Ruttman <ruttmanj at carewisc.org> wrote:

>  Thanks Kris.  Yes, I verified with a buttset as you describe, and I did
> not have to do anything but connect the set to get dialtone.  I did remember
> someone posting one time that the telco had up and changed existing
> lines from ground to loop (or vice versa) but as yet I'm not sure how to
> make the config changes to loopstart, so I've not tried it. But I will work
> on this and give it a try.
>
> Thanks
> jeff
>
>  ------------------------------
> *From:* Kris Seraphine [mailto:baryonyx5 at gmail.com]
> *Sent:* Tuesday, July 21, 2009 1:10 PM
> *To:* Jeff Ruttman
> *Cc:* cisco-voip at puck.nether.net
> *Subject:* Re: [cisco-voip] Can't call out local lines
>
> You say you've verified you get dial tone and can place a local call.  Are
> you saying you removed the local lines from the gateway and connected them
> to a butt set to test?  If so, unless you are touching one of the leads to a
> ground to get dialtone, these lines sound like loop start.  Your debug
> output below shows them as ground start.
>
> Maybe the CO switched them on you.
>
> On Tue, Jul 21, 2009 at 12:18 PM, Jeff Ruttman <ruttmanj at carewisc.org>wrote:
>
>>  Greetings,
>>
>> Suddenly one of our sites gets fast busy when dialing locally.  We have
>> trunks lines to DIDs for inbound calls, and 3 local lines for outbound local
>> calls.  (LD comes out of our PRI here at the main site.)  On site, I've
>> verified that we get dial tone and can place a local call.  I also swapped
>> out the EVM w/ FXO cards in the router.  It's an mgcp gateway with ports
>> 2/9, 10, and 11 configured groundstart on the FXO subunit.  After dialing a
>> local number and a 10 count I get fast busy.
>>
>> So far I can't see any config difference in CUCM or on the router when
>> comparing to different but similar sites, and it's not like we changed
>> anything anyway.
>>
>> Not sure where to go from here....
>> Thanks
>> jeff
>>
>> vpm sig shows this when placing a local call:
>>
>> 013656: Jul 21 17:49:07.977 CST: htsp_timer_stop3 htsp_setup_req
>> 013657: Jul 21 17:49:07.977 CST: htsp_process_event: [2/0/9, FXOGS_PARK,
>> E_HTSP_SETUP_REQ]
>> 013658: Jul 21 17:49:07.981 CST: htsp_process_event: [2/0/9, FXOGS_PARK,
>> E_HTSP_RELEASE_REQ]
>> 013659: Jul 21 17:49:07.981 CST: fxogs_park_release_req
>> 013660: Jul 21 17:49:07.997 CST: htsp_timer_stop3 htsp_setup_req
>> 013661: Jul 21 17:49:08.001 CST: htsp_process_event: [2/0/10, FXOGS_PARK,
>> E_HTSP_SETUP_REQ]
>> 013662: Jul 21 17:49:08.005 CST: htsp_process_event: [2/0/10, FXOGS_PARK,
>> E_HTSP_RELEASE_REQ]
>> 013663: Jul 21 17:49:08.005 CST: fxogs_park_release_req
>> 013664: Jul 21 17:49:08.025 CST: htsp_timer_stop3 htsp_setup_req
>> 013665: Jul 21 17:49:08.029 CST: htsp_process_event: [2/0/11,
>> FXOGS_ONHOOK, E_HTSP_SETUP_REQ]fxogs_onhook_setup
>> 013666: Jul 21 17:49:08.029 CST: [2/0/11] set signal state = 0x0 timestamp
>> = 0
>> 013667: Jul 21 17:49:08.029 CST: htsp_timer - 10000 msec
>> 013668: Jul 21 17:49:08.205 CST: htsp_process_event: [2/0/11,
>> FXOGS_WAIT_TIP_GROUND, E_DSP_SIG_0110]
>> 013669: Jul 21 17:49:18.029 CST: htsp_process_event: [2/0/11,
>> FXOGS_WAIT_TIP_GROUND, E_HTSP_EVENT_TIMER]fxogs_offhook_disc
>> 013670: Jul 21 17:49:18.029 CST: htsp_timer_stop
>> 013671: Jul 21 17:49:18.029 CST: [2/0/11] set signal state = 0x4 timestamp
>> = 0
>> 013672: Jul 21 17:49:18.029 CST: htsp_timer - 2000 msec
>> 013673: Jul 21 17:49:18.029 CST: htsp_process_event: [2/0/11,
>> FXOGS_ONHOOK, E_HTSP_RELEASE_REQ]fxogs_onhook_release
>> 013674: Jul 21 17:49:18.029 CST: htsp_timer_stop2
>> 013675: Jul 21 17:49:18.029 CST: htsp_timer_stop3
>> 013676: Jul 21 17:49:20.029 CST: htsp_process_event: [2/0/11,
>> FXOGS_ONHOOK, E_HTSP_EVENT_TIMER]
>>
>> CONFIDENTIALITY NOTICE: The information contained in this email including
>> attachments is intended for the specific delivery to and use by the
>> individual(s) to whom it is addressed, and includes information which should
>> be considered as private and confidential. Any review, retransmission,
>> dissemination, or taking of any action in reliance upon this information by
>> anyone other than the intended recipient is prohibited. If you have received
>> this message in error, please reply to the sender immediately and delete the
>> original message and any copy of it from your computer system. Thank you.
>>
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voip at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>>
>
>
> --
> kris seraphine
>
> CONFIDENTIALITY NOTICE: The information contained in this email including
> attachments is intended for the specific delivery to and use by the
> individual(s) to whom it is addressed, and includes information which should
> be considered as private and confidential. Any review, retransmission,
> dissemination, or taking of any action in reliance upon this information by
> anyone other than the intended recipient is prohibited. If you have received
> this message in error, please reply to the sender immediately and delete the
> original message and any copy of it from your computer system. Thank you.
>



-- 
kris seraphine
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20090721/e81e2f16/attachment.html>