Aastra Phone Configs

[Rick Neubauer]

Here is a screenshot of one of our phones.

 

 

 

 

Display name on Screen

Display Ext. Number (I use the internal extension here)

This is the SIP Username (it wont work if it isn’t here.)

This also has to be the Sip Username as well  (Kazoo will automatically replace it when you make a call.) It is just labeled incorrectly on the aastra interface

SIP Username

SIP Password

 

 

 

 

 

 

SIP Realm (Voice.customer.umojo.com)

Port (Leave this)

Secondary Registrar (we aren’t using this today, but will be using it pretty soon as we scale to a second data center)

 

 

 

 

 

 

SIP Realm (same as above)

 

 

Secondary Registrar Realm (we aren’t using this today, but will be using it pretty soon as we scale to a second data center)

 

 

 

 

 

If you want to do BLF, then you need use the full SIP address for example :   jgufy_6@ Voice.customer.umojo.com  That will allow the BLf to work on the aastra phones. 

 

 

We used to standardize on Aastra, but have recently moved to Polycom.  They have finally caught up on the auto-discovery, and the XML interface has finally caught up to the Aastra’s.  We are working with a few startup ITSP’s to get a collective together to get groupdiscount pricing from Polycom.  Send me you contact info and perhaps we can talk this week to discuss it. IT includes Polycom’s zero-touch provisioning, discounts from Distributors, etc.

 

 

 

 

 

-----Original Message-----
From: 2600h...@googlegroups.com [mailto:2600h...@googlegroups.com] On Behalf Of Dan Denson
Sent: Saturday, August 18, 2012 11:14 PM
To: 2600h...@googlegroups.com
Subject: Re: BLA/SLA

 

Yes, 6755i with latest firmware. I can't get it to register.

 

-please excuse my brevity, this message sent from my smartphone-

 

On Aug 18, 2012, at 10:01 PM, Rick Neubauer <rneu...@umojo.com> wrote:

 

> Hi Dan,

> 

> We have been running Aastra on our deployment for a while. What models are you using? They need to be the 675xi series. Just make sure you are running the latest firmware.

> 

> Sent from my iPhone

> 

> On Aug 18, 2012, at 7:18 PM, "Dan Denson" <dand...@gmail.com> wrote:

> 

>> Thanks.  I have a boatload of aastras sp in hoping to use them up and

>> then switch to polycom.

>> 

>> -please excuse my brevity, this message sent from my smartphone-

>> 

>> On Aug 18, 2012, at 6:17 PM, Darren Schreiber <dar...@2600hz.com> wrote:

>> 

>>> No restrictions I know of - it's been used on Linksys, Polycom and

>>> Yealink that I am aware so far. There are some phones that take

>>> extra effort so that when you pickup the parked/held line it dials the correct pickup code.

>>> 

>>> --

>>> Darren Schreiber

>>> CEO / Co-Founder

>>> 

>>> 

>>> 

>>> 

>>> 

>>> 

>>> On 8/18/12 5:15 PM, "dan" <dand...@gmail.com> wrote:

>>> 

>>>> Darren, are there any phone restrictions you know of on this?

>>>> Specifically, is this something that only works on a yealink or

>>>> does a polycom (or aastra) support this as well?  Is this simply a

>>>> BLF for the users extension assigned to a button?

>>>> 

>>>> On Sat, Aug 18, 2012 at 5:55 PM, Darren Schreiber

>>>> <dar...@2600hz.com>

>>>> wrote:

>>>>> Are you asking about Shared Line Appearance?

>>>>> 

>>>>> If so, we do not directly. But we do support a reasonable

>>>>> alternative that we call "personal parking" which uses BLFs which

>>>>> can simulate the same concept.

>>>>> 

>>>>> --

>>>>> Darren Schreiber

>>>>> CEO / Co-Founder

>>>>> 

>>>>> 

>>>>> 

>>>>> 

>>>>> 

>>>>> 

>>>>> 

>>>>> On 8/18/12 12:43 PM, "Dan Denson" <dand...@gmail.com> wrote:

>>>>> 

>>>>>> Guys, do you or are you planning on supporting BLA/SLA?

>>>>>> 

>>>>>> -please excuse my brevity, this message sent from my smartphone-

>>>>> 

>>> 

>> 

> 

 

[dan]

I have matched your config, changing just the proxy, registrar, and putting my own ship credentials in.  I am on the hosted kazoo so i did [customer_id].sip.2600hz.com as given on the device setting in kazoo for the proxy and registrar.

When the phone tries to register, it just shows status 500.  I did a factory default and changed only the auth info, proxy, and registrar.

[Rick Neubauer]

try with the caller ID being the same as the username as well.

 

Rick Neubauer

CEO

Umojo

101 Jorie Blvd. Ste 138

Oak Brook, IL 60523

---

From: 2600h...@googlegroups.com [2600h...@googlegroups.com] on behalf of dan [dand...@gmail.com]
Sent: Monday, August 20, 2012 8:06 AM
To: 2600h...@googlegroups.com
Subject: Re: Aastra Phone Configs

[dan]

same result

[dan]

Thanks for the help Rick, I finally have it working.  looking back, always had a bad combination of proxy/registrar/ and credentials. 

[Rick Neubauer]

Glad you got it working.

 

[Hussein M Said]

Hi
How did you get BLF to work? I use an a AASTRA 6737i and I tried various configuration, and I can't get the SUBSCRIBE request to have the proper contact IP address unless I enable BLA on the phone, which gets BLF to work but skews the contact info. I have 4 BLF soft keys configured.

I am running Kazoo 3.22 release. Using tSip softphone works like a charm. The proxy is just the SIP realm. If I leave the outbound proxy configuration out, the SUBSCRIBE is never sent.

thanks

thanks

[Hussein M Said]

This was an issue with faulty aastra.cfg file, and not using realm for the registrar part. I can emulate key system properly now. For those who want proper key system to work, I used the SCA Kamailio module and got all line appearances to work, reflect state of other line appearances and put a call (no park) on hold on one line appearance and pick it up on another phone from same line appearance. I had to modify the default.cfg slightly to get call-info header detection so that the SCA module can work properly, especially to inject the Replaces header when picking up a held call. This of course required Broadsoft line side support on the phone to be enabled and Kazoo support for multiple bindings to an AOR which seems to have been added to 4.0 but wasn't present in 3.22(forking never worked on this branch for me). Ideally, one can extend omnipresence to do the same to leverage kazoo clustering and HA, but for now, it's a good start for a demo.

[Darren Schreiber]

You have SLA working on 4.0?

On 6/23/16, 4:48 PM, "2600h...@googlegroups.com on behalf of Hussein M Said" <2600h...@googlegroups.com on behalf of hsai...@gmail.com> wrote:

This was an issue with faulty aastra.cfg file, and not using realm for the registrar part. I can emulate key system properly now. For those who want proper key system to work, I used the SCA Kamailio module and got all line appearances to work, reflect state of other line appearances and put a call (no park) on hold on one line appearance and pick it up on another phone from same line appearance. I had to modify the default.cfg slightly to get call-info header detection so that the SCA module can work properly, especially to inject the Replaces header when picking up a held call. This of course required Broadsoft line side support on the phone to be enabled and Kazoo support for multiple bindings to an AOR which seems to have been added to 4.0 but wasn't present in 3.22(forking never worked on this branch for me). Ideally, one can extend omnipresence to do the same to leverage kazoo clustering and HA, but for now, it's a good start for a demo.

--
You received this message because you are subscribed to the Google Groups "2600hz-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to 2600hz-dev+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Hussein M Said]

Hi Darren
Yes, I built 4.0 from source(erlang, 18.3, kamailio from master, FS from master, and Kazoo 4.0). I have to be clear though that I used Kamailio SCA module and figured out how to create the subscription database in dbtext. THE SCA module as I indicated implements the call-info sip extensions and line-seize event packages. The only update I did to the default.cfg was to insert hooks for the SCA API in the proper route and reply portions of the script. Join does not work(looked at the code and not hard to add it). I tried few basic scenarios, answer, hold, then pick up from other phones and seems to work fine. I see some SCA errors related to database updates failing. Line seize works fine and outgoing calls work. More call flows need to be tested. Mind you I use omnipresence with BLF to park calls on shared orbits, pickup ringing calls from another phone and barge-in using intercoms as well.

Kr
Hussein

[Darren Schreiber]

Is this on a cluster w/ multiple zones and federation?

If so, we’d love to see this committed back to a branch for more testing if you are willing.

[Hussein Said]

All on same VM, no clustering or federation as I struggled building the RPMs to deploy a cluster(using couchdb 2.0). 
I wish I can take credit for it, but I have done no code changes to any modules in Kamailio other than compiling the SCA module and updating the script....this is all pure configuration which I am happy to share on this thread  If you're interested. Long term, it may make more sense for omnipresence to handle subscription management and REPLACES injection for the SIP INVITE.



  Original Message  
From: Darren Schreiber
Sent: Friday, June 24, 2016 10:25 AM
To: 2600h...@googlegroups.com
Reply To: 2600h...@googlegroups.com

Subject: Re: Aastra Phone Configs

You received this message because you are subscribed to a topic in the Google Groups "2600hz-dev" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/2600hz-dev/acUi-ZY0Y-w/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 2600hz-dev+...@googlegroups.com.

[Darren Schreiber]

Hmmmm this would be good to test in a federated environment as I think a lot more work needs to be done there but would be super excited if I was wrong ☺

Want to commit the change anyway?

[Hussein Said]

Sure. I'll have some cycles next week . I will commit default.cfg, build scripts I used, config files and some instructions.

  Original Message  
From: Darren Schreiber

Sent: Friday, June 24, 2016 12:06 PM

[altm]

Hi guys, 

 Have anyone managed to get Aastra 55i working on Kazoo 3.22 using outbound proxy.    I keep receiving contact mismatch. 

I am using this: 

sip outbound support: 1

sip remove route: 1

sip contact matching: 2

sip symmetric udp signaling: 0

sip rport: 0

I have tested different versions so far from 3.2.2 to 3.3.1 and same behavior. 

If I dont use sip outbound support: 1  then  I fall in a weird NAT issue where ACK messages get lost and call drops. 

I dont have this issue with Yealink, Cisco, Bria or Zoiper...  

Should i throw this phone to thru the window?... 

[fred]

On that screenshot, I think outbound proxy server and port should be filled in same as proxy server.

[altm]

I finally got it working with Kazoo 3.22 using the following parameters: 

sip line1 outbound proxy:  <OP IP address> 

sip line1 outbound proxy port: 5060

sip outbound support:

sip remove route:

sip contact matching: 2

sip symmetric udp signaling:

sip rport:

On Monday, August 20, 2012 at 2:28:12 AM UTC+10, rneubauer wrote: