Okay, another Cisco related issue (sorry!). Single Asterisk box at location 1. Single Cisco box at location 2, however the Cisco is also the PBX for location 3 (same physical machine, calls routed via VoIP). Trying to have Asterisk be able to call EITHER Call Manager location. The single SIP trunk in CCM (version 6.1 mind you) only allows a single device pool to be selected. So configuring calls to one location...no problem. One location at a time that is. If I want to be able to call the 3rd location I have to select a separate device pool and restart the trunk. Then calls to the 2nd location stop working. Multiple trunks in CCM doesn't appear to fix the issue, and creating multiple SIP profiles isn't permitted apparently. Any thoughts? -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20080325/d80e37b7/attachment.htm
I really have to learn to do more playing around before asking the group these questions! Here's the solution: Create a second SIP Security Profile (but not on port 5061, since it's reserved for secured connections...I used 5080). Create a second trunk port using this second SIP security profile. In Asterisk, you have to have two entries in sip.conf: [callman01] type=friend context=incoming host=x.x.x.x disallow=all allow=ulaw allow=alaw nat=yes canreinvite=yes qualify=yes [callman02] type=friend context=incoming host=x.x.x.x disallow=all allow=ulaw allow=alaw nat=yes canreinvite=yes qualify=yes port=5080 They can both point to the same IP address. Any needs more information just let me know. On Tue, Mar 25, 2008 at 7:35 AM, Aaron Fransen <aaron.fransen at gmail.com> wrote:> Okay, another Cisco related issue (sorry!). > > Single Asterisk box at location 1. > Single Cisco box at location 2, however the Cisco is also the PBX for > location 3 (same physical machine, calls routed via VoIP). > > Trying to have Asterisk be able to call EITHER Call Manager location. The > single SIP trunk in CCM (version 6.1 mind you) only allows a single device > pool to be selected. So configuring calls to one location...no problem. One > location at a time that is. > > If I want to be able to call the 3rd location I have to select a separate > device pool and restart the trunk. Then calls to the 2nd location stop > working. > > Multiple trunks in CCM doesn't appear to fix the issue, and creating > multiple SIP profiles isn't permitted apparently. > > Any thoughts? >-------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20080325/82721d6a/attachment.htm
Aaron wrote:> Okay, another Cisco related issue (sorry!).> Single Asterisk box at location 1. > Single Cisco box at location 2, however the Cisco is > also the PBX for location 3 (same physical machine, calls > routed via VoIP).> Trying to have Asterisk be able to call EITHER Call Manager > location. The single SIP trunk in CCM (version 6.1 mind you) > only allows a single device pool to be selected. So configuring > calls to one location...no problem. One location at a time that > is.All you are missing is a translation of CCM terms into Asterisk concepts. A CCM Device Pool is similar to a context, a logical grouping Of devices. CCM extends the concept in that Device Pool membership controls/aids device provisioning. There is one major difference, and that is membership in a common Device Pool DOES NOT mean devices can call each other. Call 'routing' is handled by Calling Search Spaces. You want to have a CSS that included both locations Device Pools and assign that CSS to the trunk. The major caveat there is that the two locations should have non-overlapping dialplans. If they do overlap, you will need Translation Patterns, which can strip/prepend digits and be configured to search a different CSS> If I want to be able to call the 3rd location I have to select > a separate device pool and restart the trunk. Then calls to the > 2nd location stop working.> Multiple trunks in CCM doesn't appear to fix the issue, and > creating multiple SIP profiles isn't permitted apparently.> Any thoughts?Hope that helps...