Shared Call Appearances 1

[ryannoll]

Hello,

I am attempting to setup two shared call appearances utilizing SIP trunking. I am following the directions provided at

https://www.emetrotel.com/tsd/main-categories/shared-call-appearances.

For the most part, I am able to setup the appropriate trunk and inbound route. However, I am unable to use the associated keys to make an outgoing call. (Incoming works fine, and I am able to make one outgoing call which is associated with the first defined outgoing trunk through the extension/intercom key.)

What I am unable to do is to make an outgoing call using the Shared Call Appearance key. When I attempt to make an outgoing call using an SCA key there is no dial tone and the asterisk log shows the following message when I push the SCA key in an attempt to make an outgoing call:

[pre]
VERBOSE[2305] chan_ucx.c: 101 ignored keypress on key # NXX-XXXX - wrong state 01
-- or --
VERBOSE[2305] chan_ucx.c: 101 ignored keypress on key # NXX-XXXX - wrong state 20
[/pre]

When making an outgoing call, using the extension/intercom key the following is output in the asterisk log:

[pre]
VERBOSE[27216][C-00000026] netsock2.c: Using SIP RTP TOS bits 184
VERBOSE[27216][C-00000026] netsock2.c: Using SIP RTP CoS mark 5
VERBOSE[27216][C-00000026] app_dial.c: Called SIP/ucx1/9665
VERBOSE[27216][C-00000026] app_dial.c: SIP/ucx1-0000001d answered UCX/101@101-00000032
VERBOSE[27217][C-00000026] bridge_channel.c: Channel SIP/ucx1-0000001d joined 'simple_bridge' basic-bridge <512e5b20-2afa-4af4-af20-8808b1721b46>
VERBOSE[27216][C-00000026] bridge_channel.c: Channel UCX/101@101-00000032 joined 'simple_bridge' basic-bridge <512e5b20-2afa-4af4-af20-8808b1721b46>
VERBOSE[27216][C-00000026] chan_ucx.c: 101 moving UCX/101@101-00000032 from key 0 to 5 SCA:1@SCG1
[/pre]
Note: There is also a SIP/ucx2 which corresponds to the second SCA key.

If outgoing calls are possible via the SCA keys, what configuration step am I missing? A pointer would be greatly appreciated.

Thank you,
Ryan

 

[ucxguy]

You cannot press an SCA key and expect to make a call using that key. When making an outbound call, the outbound route selected for the call is used to determine if the call will be assigned to an SCA key or not. Therefore, an SCA key can be selected by the system only after the dialing is complete (all digits dialed).

 

[ryannoll]

Ucxguy,

Thank you for the clarification.

Ryan

 

[random192]

One work around I've used is to add a prefix to dial to facilitate line selection so for instance they have to dial 5 before selects line one dial 6 before selects line two.

 

[ryannoll]

random192,

Thanks for the suggestion. I too had thought of the same solution, except, I'm using 2 digit routes.

For "line1", I have an outbound route defined as the following:
[li]Route Name: Outbound1[/li]
[li]Shared Calls Tag: SCG1[/li]
[li]Dial Patterns: () + 71 | NXXNXXXXXX and () + 71 | NXXXXXX[/li]
[li]Trunk Sequence: [The desired trunk][/li]

For "line2", I have an outbound route defined as the following:
[li]Route Name: Outbound1[/li]
[li]Shared Calls Tag: SCG2[/li]
[li]Dial Patterns: () + 72 | NXXNXXXXXX and () + 72 | NXXXXXX[/li]
[li]Trunk Sequence: [The desired trunk][/li]

I also created an "Emergency911" route defined as the following:
[li]Route Name: Emergency911[/li]
[li]Dial Pattern: () + | 911[/li]
[li]Trunk sequence: [The desired trunk(s)][/li]
This should allow me to dial 911 and have it go out my desired trunks, which are connected to my service provider (fiber) through an FXO-ATA.

Thanks for the reminder, I should have posted a solution earlier in case someone else needed a similar functionality. To me this is not necessarily the ideal solution (I would have liked to be able to push the shared appearance), but at least it is close enough.

-Ryan