Problems with queus and ring groups ...

Discussion in 'General' started by augustynr, Jan 22, 2009.

  1. augustynr

    Joined:
    Nov 20, 2007
    Messages:
    113
    Likes Received:
    0
    Hi,
    I have 1.3 server running and have problems with phones not ringing at all or starting to ring later then others. All phones are Aastra 57i.
    I have most problems with two 57i phones with 560 module attached they seem to take longest to ring.
    Any solutions to this?
    Thanks ...
     
  2. dicko

    Joined:
    Oct 24, 2008
    Messages:
    4,099
    Likes Received:
    0
    Sorry, but not enough info. here.

    How are the phones provisioned?
    How are the Queues set up?
    How are the Ring groups setup,?
    How do the phones behave on extension to extension dialing?
    How do the phones behave on making an outbound call?
    How do other inbound calls behave?



    what clues does "sip show peers" give?
     
  3. augustynr

    Joined:
    Nov 20, 2007
    Messages:
    113
    Likes Received:
    0
    Thank you for jumping in.

    Phones have been provisioned using using aastra scripts as per one thread on this forum.
    I attached copy of my queue and ring group conf.
    Phones have no problem ( as far as I know ) communicating between extensions.
    Sometimes we cannot hear the ring when calling though remote phone rings and all works ok.

    Inbound and outbound work ok, as far as I can say.
    The delay we see on 221 extension and 222
    Thank you ...

    sip show peers

    334 (Unspecified) D N 0 UNKNOWN
    333/333 192.168.2.9 D N 5060 OK (133 ms)
    332/332 192.168.2.3 D N 5060 OK (145 ms)
    331/331 192.168.2.5 D N 5060 OK (143 ms)
    330/330 192.168.2.7 D N 5060 OK (139 ms)
    250 (Unspecified) D N 0 UNKNOWN
    249 (Unspecified) D N 0 UNKNOWN
    248 (Unspecified) D N 0 UNKNOWN
    247/247 (Unspecified) D N 0 UNKNOWN
    246/246 192.168.1.51 D N 5060 OK (31 ms)
    242/242 192.168.1.50 D N 5060 OK (41 ms)
    241/241 192.168.1.46 D N 5060 OK (42 ms)
    240/240 192.168.1.47 D N 5060 OK (41 ms)
    239/239 192.168.1.56 D N 5060 OK (41 ms)
    238/238 192.168.1.45 D N 5060 OK (44 ms)
    237/237 192.168.1.43 D N 5060 OK (43 ms)
    236/236 192.168.1.42 D N 5060 OK (42 ms)
    235/235 192.168.1.60 D N 5060 OK (44 ms)
    234/234 192.168.1.41 D N 5060 OK (41 ms)
    233/233 192.168.1.48 D N 5060 OK (41 ms)
    232/232 192.168.1.44 D N 5060 OK (42 ms)
    231/231 192.168.1.53 D N 5060 OK (43 ms)
    230/230 192.168.1.23 D N 5060 OK (41 ms)
    229/229 192.168.1.55 D N 5060 OK (44 ms)
    228/228 192.168.1.54 D N 5060 OK (42 ms)
    227/227 192.168.1.52 D N 5060 OK (45 ms)
    226/226 192.168.1.34 D N 5060 OK (40 ms)
    225/225 192.168.1.63 D N 5060 OK (30 ms)
    224/224 192.168.1.22 D N 5060 OK (41 ms)
    223/223 192.168.1.37 D N 5060 OK (30 ms)
    222/222 192.168.1.49 D N 5060 OK (36 ms)
    2213/2213 192.168.1.39 D N 5060 OK (35 ms)
    2212/2212 192.168.1.39 D N 5060 OK (91 ms)
    2211/2211 192.168.1.39 D N 5060 OK (90 ms)
    221/221 192.168.1.39 D N 5060 OK (89 ms)
     
  4. augustynr

    Joined:
    Nov 20, 2007
    Messages:
    113
    Likes Received:
    0
  5. dicko

    Joined:
    Oct 24, 2008
    Messages:
    4,099
    Likes Received:
    0
    An pertinent excerpt of your "sip show peers"

    223/223 192.168.1.37 D N 5060 OK (30 ms)
    222/222 192.168.1.49 D N 5060 OK (36 ms)
    2213/2213 192.168.1.39 D N 5060 OK (35 ms)
    2212/2212 192.168.1.39 D N 5060 OK (91 ms)
    2211/2211 192.168.1.39 D N 5060 OK (90 ms)
    221/221 192.168.1.39 D N 5060 OK (89 ms)


    OK

    Step 1,


    I see you have registered 4 extensions with the device at 192.168.1.39,

    I think you think of this device as extension 221, yet it is more . . .

    you have
    221
    2211
    2212
    2213

    in your dialplan,

    thusly 221 wil not be uniquely identified until timeout or dial termination is expressed,
    possible explaining your delayed ringing.

    (ping return time we'll worry about later, and possible problems with xml provisioning in Elastix)


    can your remove those 4 digit extensions from 211 to get things back to "base level" and check behavior again?


    your extension 222 looks normal, please verify it's abnormal behaviour.
     
  6. augustynr

    Joined:
    Nov 20, 2007
    Messages:
    113
    Likes Received:
    0
    Ok, i am resetting the phone with just one extension registered to the phone.
    I was under the impression that I could have each line separate extension?
    Is that not true?
     
  7. augustynr

    Joined:
    Nov 20, 2007
    Messages:
    113
    Likes Received:
    0
    You can see what I am referring to by looking at this log, please notice, first extension started ringing 6 secs before the last one did:

    [root@elastix ~]# tail -f /var/log/asterisk/full | grep ringing
    [Jan 22 01:19:38] VERBOSE[11824] logger.c: -- SIP/241-b707a150 is ringing
    [Jan 22 01:19:38] VERBOSE[11820] logger.c: -- Local/241@from-internal-3931,1 is ringing
    [Jan 22 01:19:39] VERBOSE[11831] logger.c: -- SIP/229-08861950 is ringing
    [Jan 22 01:19:39] VERBOSE[11820] logger.c: -- Local/229@from-internal-c3f5,1 is ringing
    [Jan 22 01:19:39] VERBOSE[11834] logger.c: -- SIP/233-b70004d0 is ringing
    [Jan 22 01:19:39] VERBOSE[11820] logger.c: -- Local/233@from-internal-6603,1 is ringing
    [Jan 22 01:19:39] VERBOSE[11822] logger.c: -- SIP/236-0886d5f8 is ringing
    [Jan 22 01:19:39] VERBOSE[11820] logger.c: -- Local/236@from-internal-6690,1 is ringing
    [Jan 22 01:19:39] VERBOSE[11829] logger.c: -- SIP/226-b70a7228 is ringing
    [Jan 22 01:19:39] VERBOSE[11820] logger.c: -- Local/226@from-internal-996a,1 is ringing
    [Jan 22 01:19:39] VERBOSE[11829] logger.c: -- SIP/226-b70a7228 is ringing
    [Jan 22 01:19:45] VERBOSE[11826] logger.c: -- SIP/221-088af740 is ringing
    [Jan 22 01:19:45] VERBOSE[11820] logger.c: -- Local/221@from-internal-0058,1 is ringing
    [Jan 22 01:19:45] VERBOSE[11821] logger.c: -- SIP/235-b707cc70 is ringing
    [Jan 22 01:19:45] VERBOSE[11820] logger.c: -- Local/235@from-internal-4592,1 is ringing
    [Jan 22 01:19:46] VERBOSE[11827] logger.c: -- SIP/222-b70b0008 is ringing
    [Jan 22 01:19:46] VERBOSE[11820] logger.c: -- Local/222@from-internal-cf63,1 is ringing
    [Jan 22 01:19:53] VERBOSE[11833] logger.c: -- SIP/230-08856da0 is ringing
    [Jan 22 01:19:53] VERBOSE[11820] logger.c: -- Local/230@from-internal-fb13,1 is ringing
    [Jan 22 01:19:54] VERBOSE[11823] logger.c: -- SIP/239-b707a150 is ringing
    [Jan 22 01:19:54] VERBOSE[11820] logger.c: -- Local/239@from-internal-27d1,1 is ringing
     
  8. dicko

    Joined:
    Oct 24, 2008
    Messages:
    4,099
    Likes Received:
    0
    Are you provisioning the aastra phones from the phone's web server on top of the xml programming?

    Apparently so because my implimentation of those aastra xml files (with only minimal editing of the .prf files) just provides a very generic .cfg file.

    but you must have built those 2211 2212 2213 extensions on the phones and freepbx for a reason.


    Ca you elucidite, what are you trying to do?

    The log you posted show only the logger data, you grepped out the important bits
     
  9. augustynr

    Joined:
    Nov 20, 2007
    Messages:
    113
    Likes Received:
    0
    I added this lines into the phone cfg file. I have a problem that when a call comes in it should ring all these phones before it goes to IVR. The problem with group is that if receptionist is on the phone and next call comes in she is not able to get to it.
    So I was trying to add two extension to the group that way the second call still should be available on next line for her to pick up.
     
  10. dicko

    Joined:
    Oct 24, 2008
    Messages:
    4,099
    Likes Received:
    0
    What I see here is:-

    Jan 22 01:19:38] VERBOSE[11824] logger.c: -- SIP/241-b707a150 is ringing
    [Jan 22 01:19:38] VERBOSE[11820] logger.c: -- Local/241@from-internal-3931,1 is ringing
    [Jan 22 01:19:39] VERBOSE[11831] logger.c: -- SIP/229-08861950 is ringing
    [Jan 22 01:19:39] VERBOSE[11820] logger.c: -- Local/229@from-internal-c3f5,1 is ringing
    [Jan 22 01:19:39] VERBOSE[11834] logger.c: -- SIP/233-b70004d0 is ringing
    [Jan 22 01:19:39] VERBOSE[11820] logger.c: -- Local/233@from-internal-6603,1 is ringing
    [Jan 22 01:19:39] VERBOSE[11822] logger.c: -- SIP/236-0886d5f8 is ringing
    [Jan 22 01:19:39] VERBOSE[11820] logger.c: -- Local/236@from-internal-6690,1 is ringing
    [Jan 22 01:19:39] VERBOSE[11829] logger.c: -- SIP/226-b70a7228 is ringing
    [Jan 22 01:19:39] VERBOSE[11820] logger.c: -- Local/226@from-internal-996a,1 is ringing
    [Jan 22 01:19:39] VERBOSE[11829] logger.c: -- SIP/226-b70a7228 is ringing

    at 19:38

    241,229,233,236,226 and 226 (again) are rung sequentially,

    then at 19:45 (6 seconds later) ext 221 235 and 222 are sequentially rung, I suspect that the delay is because 221 is not unique (at least when it comes to DTMF) within you dialplan,

    [Jan 22 01:19:45] VERBOSE[11826] logger.c: -- SIP/221-088af740 is ringing
    [Jan 22 01:19:45] VERBOSE[11820] logger.c: -- Local/221@from-internal-0058,1 is ringing
    [Jan 22 01:19:45] VERBOSE[11821] logger.c: -- SIP/235-b707cc70 is ringing
    [Jan 22 01:19:45] VERBOSE[11820] logger.c: -- Local/235@from-internal-4592,1 is ringing
    [Jan 22 01:19:46] VERBOSE[11827] logger.c: -- SIP/222-b70b0008 is ringing
    [Jan 22 01:19:46] VERBOSE[11820] logger.c: -- Local/222@from-internal-cf63,1 is ringing

    In my experience I find that a "closed" dial plan is always more efficient, depending on the size of your deployment, use a consitent length for your "endpoints", be they extensions, queues, ring groups or anything, otherwise you ultimately expose yourself to "open" dialplan termination decision.

    Also there are several options of ring strategy in the ring group, try other methods and see if you can tie down your clog. (Also check that the receptionist has call waiting enabled)
     
  11. augustynr

    Joined:
    Nov 20, 2007
    Messages:
    113
    Likes Received:
    0
    Thanks, I have deleted 2211, 2212 and 2213 extensions from elastix box and from the phone config.
    I still have the same problem of extensions ringing delay of up to 15 secs.
    I am not sure what you referring to as a "closed" dial plan, can you explain
     
  12. dicko

    Joined:
    Oct 24, 2008
    Messages:
    4,099
    Likes Received:
    0
    In a "Closed Dial Plan" briefly and only an example

    extensions: 200-299
    faxes: 300-399
    ring groups: 400-499
    IVR's: 500-599

    etc.

    any call to the internal context can be resolved uniquely in three digits,

    all these can be defined in a dialplan by [2-5]xx, leaving 1xxx. and 0xx. to go where they will.

    that [2-5]xx belongs in the aastra.cfg file in the dialstring setting, then you can set live dialpad: on and simply dialling 3 digits (if valid) will immediately connect to that number because both phoe and pbx know that anything that matches that "regular expression" is unique .

    if the call waiting thing doesn't work (provided your aastra shows those multiple appearances of 221 and you have the right strategy it should)
    then fell free to do what you did but this time use 721 722 723 for example


    (other examples of closed plan dialling, everyone in the NANP (North American Numbering Plan)
    all numbers are unique with a 3 digit areacode a three digit exchange code and a four digit subsriber code, (we assume 1 for the countrycode))

    an example of open plan might be Austria ( country code 43) interanlly anything between 5 and 15 digits is legitimate, but they mostly use isdn so it's not a problem for them, your dialplan with 221 and 2212 both legitimate but . . .)
     
  13. augustynr

    Joined:
    Nov 20, 2007
    Messages:
    113
    Likes Received:
    0
    Thank you, that is what I have now but I still have a problem of extensions ringing with delays ....
     
  14. dicko

    Joined:
    Oct 24, 2008
    Messages:
    4,099
    Likes Received:
    0
    did you restart asterisk or just reload since the changes,

    can you post a more complete trace of the ring group behavior in the new scenario?

    I further note that all your numbers on 221 are showing registered at port 5060, I suggest you change the registration port for each number on the same phone.
     
  15. augustynr

    Joined:
    Nov 20, 2007
    Messages:
    113
    Likes Received:
    0
  16. accesip

    Joined:
    May 16, 2007
    Messages:
    113
    Likes Received:
    0
    I have this kind of problem (ring after 15 - 20 secondes) when the LAN gateway is down.
    Maybe phones need the gateway to work fine?
     
  17. augustynr

    Joined:
    Nov 20, 2007
    Messages:
    113
    Likes Received:
    0
    Thanks
    I think phones get gateway conf from dhcp.
    What is strange that phones with modules get delayed most ... 7 secs and random delays when part of the queue.
     
  18. accesip

    Joined:
    May 16, 2007
    Messages:
    113
    Likes Received:
    0
    Even if you don't use DHCP, you need a working gateway to have phone ringing.
     
  19. augustynr

    Joined:
    Nov 20, 2007
    Messages:
    113
    Likes Received:
    0
    Now I am lost, Why would I need a gateway ( I assume router ) to have phone ring?
    Most phones are on the same subnet so they all should experience the problem, if that was the couse. I think I am missing something ...
    btw: we do use dhcp ...
     
  20. accesip

    Joined:
    May 16, 2007
    Messages:
    113
    Likes Received:
    0
    I only give my experience. I've installed more than 10 elastix server in my clients, each time the gateway is down, each time the ring arrived 10 to 20 secondes after.
    Brice
     

Share This Page