Affichage des résultats 1 à 6 sur 6

Discussion: Fresh Install

  1. #1
    Membre Association
    Date d'inscription
    janvier 2011
    Localisation
    Strasbourg
    Messages
    59
    Downloads
    0
    Uploads
    0

    Angry Fresh Install

    Bonjour,

    Je viens de faire une fresh install d'asterisk avec une B410P.
    Asterisk 1.8.22.0 + Dahdi 2.6.2 + Libpri 1.4.14

    J'ai créé un truck sur Port1 de la Carte = Span1
    J'ai créé 2 users ... 8100 + 8096

    J'ai un dialplan avec des regles .... et je veux sortir !!!

    National _0[1-5]XXXXXXXX Span 1
    International _00. Span 1
    Portables _0[6-7]XXXXXXXX Span 1
    Num_Spec _0[8-9]XXXXXXXX Span 1
    Num_Court _XNNN Span 1

    == Using SIP RTP CoS mark 5
    -- Executing [0618830604@DLPN_Solares:1] Macro("SIP/8100-00000003", "trunkdial-failover-0.3,DAHDI/g1/0618830604,,span_1,,0388309774") in new stack
    -- Executing [s@macro-trunkdial-failover-0.3:1] GotoIf("SIP/8100-00000003", "0?1-fmsetcid,1") in new stack
    -- Executing [s@macro-trunkdial-failover-0.3:2] GotoIf("SIP/8100-00000003", "1?1-setgbobname,1") in new stack
    -- Goto (macro-trunkdial-failover-0.3,1-setgbobname,1)
    -- Executing [1-setgbobname@macro-trunkdial-failover-0.3:1] Set("SIP/8100-00000003", "CALLERID(name)=Solares Bauen") in new stack
    -- Executing [1-setgbobname@macro-trunkdial-failover-0.3:2] Goto("SIP/8100-00000003", "s,3") in new stack
    -- Goto (macro-trunkdial-failover-0.3,s,3)
    -- Executing [s@macro-trunkdial-failover-0.3:3] Set("SIP/8100-00000003", "CALLERID(num)=0388309774") in new stack
    -- Executing [s@macro-trunkdial-failover-0.3:4] Set("SIP/8100-00000003", "CALLERID(all)=0388309774") in new stack
    -- Executing [s@macro-trunkdial-failover-0.3:5] GotoIf("SIP/8100-00000003", "1?1-dial,1") in new stack
    -- Goto (macro-trunkdial-failover-0.3,1-dial,1)
    -- Executing [1-dial@macro-trunkdial-failover-0.3:1] Dial("SIP/8100-00000003", "DAHDI/g1/0618830604") in new stack
    -- Requested transfer capability: 0x00 - SPEECH
    -- Called DAHDI/g1/0618830604
    -- Span 1: Channel 0/1 got hangup, cause 3
    -- Hungup 'DAHDI/i1/0618830604-3'
    == Everyone is busy/congested at this time (1:0/0/1)
    -- Executing [1-dial@macro-trunkdial-failover-0.3:2] GotoIf("SIP/8100-00000003", "0 > 0 ?1-CHANUNAVAIL,1:1-out,1") in new stack
    -- Goto (macro-trunkdial-failover-0.3,1-out,1)
    -- Executing [1-out@macro-trunkdial-failover-0.3:1] Hangup("SIP/8100-00000003", "") in new stack
    == Spawn extension (macro-trunkdial-failover-0.3, 1-out, 1) exited non-zero on 'SIP/8100-00000003' in macro 'trunkdial-failover-0.3'
    == Spawn extension (DLPN_Solares, 0618830604, 1) exited non-zero on 'SIP/8100-00000003'

    En entrée pas de soucis, mon catchall vers un groupe est OK !!!

    ipbx*CLI> dahdi show channels
    Chan Extension Context Language MOH Interpret Blocked State
    pseudo default default In Service
    1 DID_span_1 fr default In Service
    2 DID_span_1 fr default In Service
    ipbx*CLI>

    ipbx*CLI> sip show users
    Username Secret Accountcode Def.Context ACL ForcerPort
    8096 DLPN_Solares No Yes
    8100 DLPN_Solares No Yes
    ipbx*CLI>


    root@ipbx: $ cat /etc/dahdi/system.conf
    # Autogenerated by /usr/sbin/dahdi_genconf on Wed Jun 5 00:44:29 2013
    # If you edit this file and execute /usr/sbin/dahdi_genconf again,
    # your manual changes will be LOST.
    # Dahdi Configuration File
    #
    # This file is parsed by the Dahdi Configurator, dahdi_cfg
    #
    # Span 1: B4/0/1 "B4XXP (PCI) Card 0 Span 1" (MASTER) AMI/CCS
    span=1,1,0,ccs,ami
    # termtype: te
    bchan=1-2
    hardhdlc=3
    echocanceller=mg2,1-2

    # Span 2: B4/0/2 "B4XXP (PCI) Card 0 Span 2" RED
    span=2,2,0,ccs,ami
    # termtype: te
    bchan=4-5
    hardhdlc=6
    echocanceller=mg2,4-5

    # Span 3: B4/0/3 "B4XXP (PCI) Card 0 Span 3" RED
    span=3,3,0,ccs,ami
    # termtype: te
    bchan=7-8
    hardhdlc=9
    echocanceller=mg2,7-8

    # Span 4: B4/0/4 "B4XXP (PCI) Card 0 Span 4" RED
    span=4,4,0,ccs,ami
    # termtype: te
    bchan=10-11
    hardhdlc=12
    echocanceller=mg2,10-11

    # Global data

    loadzone = us
    defaultzone = us
    root@ipbx: $

    J'ai l'impression que ce GUI de Digium pour asterisk fout la merde quand il parse les files ....

    Donc je sors pas !!! une idée
    Alternatiq Informatique

    SSII spécialisée dans l'architecture Open Source

  2. #2
    Membre Association
    Date d'inscription
    janvier 2011
    Localisation
    Strasbourg
    Messages
    59
    Downloads
    0
    Uploads
    0

    Infos du CLI

    Appel Entrant : OK

    -- Accepting call from '9xx07xx13' to '388xx97xx' on channel 0/1, span 1
    -- Executing [388xx97xx@DID_span_1:1] Goto("DAHDI/i1/954077413-2", "ringroups-custom-1,s,1") in new stack
    -- Goto (ringroups-custom-1,s,1)
    -- Executing [s@ringroups-custom-1:1] NoOp("DAHDI/i1/9xx07xx13-2", "Accueil") in new stack
    -- Executing [s@ringroups-custom-1:2] Dial("DAHDI/i1/9xx07xx13-2", "SIP/8100,20,i") in new stack
    == Using SIP RTP CoS mark 5
    -- Called SIP/8100
    -- SIP/8100-00000001 is ringing
    -- Span 1: Channel 0/1 got hangup, cause 16
    == Spawn extension (ringroups-custom-1, s, 2) exited non-zero on 'DAHDI/i1/954077413-2'
    -- Hungup 'DAHDI/i1/9xx07xx13-2'

    Emmeteur = 09xx07xx13
    Recevant = 0388xx97xx

    Pourquoi le 0 est supprimé ?




    Appel Sortant : NOK

    == Using SIP RTP CoS mark 5
    -- Executing [06xx83xx04@DLPN_solares:1] Macro("SIP/8100-00000002", "trunkdial-failover-0.3,DAHDI/g1/06xx83xx04,,span_1,,0388xx97xx") in new stack
    -- Executing [s@macro-trunkdial-failover-0.3:1] GotoIf("SIP/8100-00000002", "0?1-fmsetcid,1") in new stack
    -- Executing [s@macro-trunkdial-failover-0.3:2] GotoIf("SIP/8100-00000002", "1?1-setgbobname,1") in new stack
    -- Goto (macro-trunkdial-failover-0.3,1-setgbobname,1)
    -- Executing [1-setgbobname@macro-trunkdial-failover-0.3:1] Set("SIP/8100-00000002", "CALLERID(name)=Solares Bauen") in new stack
    -- Executing [1-setgbobname@macro-trunkdial-failover-0.3:2] Goto("SIP/8100-00000002", "s,3") in new stack
    -- Goto (macro-trunkdial-failover-0.3,s,3)
    -- Executing [s@macro-trunkdial-failover-0.3:3] Set("SIP/8100-00000002", "CALLERID(num)=0388xx97xx") in new stack
    -- Executing [s@macro-trunkdial-failover-0.3:4] Set("SIP/8100-00000002", "CALLERID(all)=0388xx97xx") in new stack
    -- Executing [s@macro-trunkdial-failover-0.3:5] GotoIf("SIP/8100-00000002", "1?1-dial,1") in new stack
    -- Goto (macro-trunkdial-failover-0.3,1-dial,1)
    -- Executing [1-dial@macro-trunkdial-failover-0.3:1] Dial("SIP/8100-00000002", "DAHDI/g1/06xx83xx04") in new stack
    -- Requested transfer capability: 0x00 - SPEECH
    -- Called DAHDI/g1/06xx83xx04
    -- Span 1: Channel 0/1 got hangup, cause 3
    -- Hungup 'DAHDI/i1/06xx83xx04-3'
    == Everyone is busy/congested at this time (1:0/0/1)
    -- Executing [1-dial@macro-trunkdial-failover-0.3:2] GotoIf("SIP/8100-00000002", "0 > 0 ?1-CHANUNAVAIL,1:1-out,1") in new stack
    -- Goto (macro-trunkdial-failover-0.3,1-out,1)
    -- Executing [1-out@macro-trunkdial-failover-0.3:1] Hangup("SIP/8100-00000002", "") in new stack
    == Spawn extension (macro-trunkdial-failover-0.3, 1-out, 1) exited non-zero on 'SIP/8100-00000002' in macro 'trunkdial-failover-0.3'
    == Spawn extension (DLPN_solares, 06xx83xx04, 1) exited non-zero on 'SIP/8100-00000002'


    Appelé = 06xx83xx04
    Appelant = 0388xx97xx
    Alternatiq Informatique

    SSII spécialisée dans l'architecture Open Source

  3. #3
    Membre Association Avatar de celya
    Date d'inscription
    septembre 2010
    Messages
    135
    Downloads
    0
    Uploads
    0
    Quel est ton opérateur ?

    Tu a essayer d'appeler sans le 0 devant ton numéro.
    CELYA : www.celya.fr
    ASTERISK SERVICE : www.asterisk-service.fr
    MAVISIOCONF : www.mavisioconf.fr
    ATERISK : www.aterisk.fr

  4. #4
    Membre Senior
    Date d'inscription
    janvier 2011
    Localisation
    Villejuif 94
    Messages
    337
    Downloads
    0
    Uploads
    0
    Bonjour,

    certainement un problème de réglage ISDN
    la plupart du temps la numérotation est sur 9 chiffres, le 0 est géré par l'équipement

    déjà dans /etc/dahdi/system.conf
    loadzone=fr
    defaultzone=fr

    pour /etc/asterisk/chan_dahdi.conf ça dépend de l'opérateur

    par expérience chez SFR

    switchtype=euroisdn
    pridialplan=dynamic
    internationalprefix = 00
    nationalprefix = 0

    chez Completel

    switchtype=euroisdn
    pridialplan=unknown
    internationalprefix = 00
    nationalprefix = 0

    la différence au niveau de pridialplan entre SFR et Completel joue sur la présentation des numéros en sortie

  5. #5
    Membre Senior
    Date d'inscription
    septembre 2010
    Localisation
    Where the sun shines
    Messages
    1 418
    Downloads
    0
    Uploads
    0
    appel ok : 9 chiffres sans le 0
    appel ko: 10 chiffres avec le 0

    cause=3: No route to destination (http://helpdesk.netcentral.co.uk/ind...barticleid=293)

  6. #6
    Membre Association
    Date d'inscription
    janvier 2011
    Localisation
    Strasbourg
    Messages
    59
    Downloads
    0
    Uploads
    0
    Citation Envoyé par olppp Voir le message
    Bonjour,

    certainement un problème de réglage ISDN
    la plupart du temps la numérotation est sur 9 chiffres, le 0 est géré par l'équipement

    déjà dans /etc/dahdi/system.conf
    loadzone=fr
    defaultzone=fr

    pour /etc/asterisk/chan_dahdi.conf ça dépend de l'opérateur

    par expérience chez SFR

    switchtype=euroisdn
    pridialplan=dynamic
    internationalprefix = 00
    nationalprefix = 0

    chez Completel

    switchtype=euroisdn
    pridialplan=unknown
    internationalprefix = 00
    nationalprefix = 0

    la différence au niveau de pridialplan entre SFR et Completel joue sur la présentation des numéros en sortie
    Bonjour,

    OK avec les infos, mais pourquoi la config vi la GUI de digium ne fait pas le boulot correctement ?

    Le fichier system.conf passe de :

    # Autogenerated by /usr/sbin/dahdi_genconf on Tue Jun 11 16:53:24 2013
    # If you edit this file and execute /usr/sbin/dahdi_genconf again,
    # your manual changes will be LOST.
    # Dahdi Configuration File
    #
    # This file is parsed by the Dahdi Configurator, dahdi_cfg
    #
    # Span 1: B4/0/1 "B4XXP (PCI) Card 0 Span 1" (MASTER)
    span=1,1,0,ccs,ami
    # termtype: te
    bchan=1-2
    hardhdlc=3
    echocanceller=mg2,1-2

    # Span 2: B4/0/2 "B4XXP (PCI) Card 0 Span 2"
    span=2,2,0,ccs,ami
    # termtype: te
    bchan=4-5
    hardhdlc=6
    echocanceller=mg2,4-5

    # Span 3: B4/0/3 "B4XXP (PCI) Card 0 Span 3"
    span=3,3,0,ccs,ami
    # termtype: te
    bchan=7-8
    hardhdlc=9
    echocanceller=mg2,7-8

    # Span 4: B4/0/4 "B4XXP (PCI) Card 0 Span 4"
    span=4,4,0,ccs,ami
    # termtype: te
    bchan=10-11
    hardhdlc=12
    echocanceller=mg2,10-11

    # Global data

    loadzone = fr
    defaultzone = fr

    a ceci :

    span = 1,1,0,ccs,ami
    span = 2,2,0,ccs,ami
    bchan = 1-2,4-5
    hardhdlc = 3,6
    echocanceller = mg2,1-240
    loadzone = fr
    defaultzone = fr

    et que le dahdi-channels dans /etc/asterisk ne passe pas :

    ; Autogenerated by /usr/sbin/dahdi_genconf on Wed Jun 12 15:27:10 2013
    ; If you edit this file and execute /usr/sbin/dahdi_genconf again,
    ; your manual changes will be LOST.
    ; Dahdi Channels Configurations (chan_dahdi.conf)
    ;
    ; This is not intended to be a complete chan_dahdi.conf. Rather, it is intended
    ; to be #include-d by /etc/chan_dahdi.conf that will include the global settings
    ;

    ; Span 1: B4/0/1 "B4XXP (PCI) Card 0 Span 1" AMI/CCS
    group=0,11
    context=from-pstn
    switchtype = euroisdn
    signalling = bri_cpe_ptmp
    channel => 1-2
    context = default
    group = 63

    ; Span 2: B4/0/2 "B4XXP (PCI) Card 0 Span 2" (MASTER) AMI/CCS
    group=0,12
    context=from-pstn
    switchtype = euroisdn
    signalling = bri_cpe_ptmp
    channel => 4-5
    context = default
    group = 63

    ; Span 3: B4/0/3 "B4XXP (PCI) Card 0 Span 3" AMI/CCS RED
    group=0,13
    context=from-pstn
    switchtype = euroisdn
    signalling = bri_cpe_ptmp
    channel => 7-8
    context = default
    group = 63

    ; Span 4: B4/0/4 "B4XXP (PCI) Card 0 Span 4" AMI/CCS RED
    group=0,14
    context=from-pstn
    switchtype = euroisdn
    signalling = bri_cpe_ptmp
    channel => 10-11
    context = default
    group = 63


    à ceci :

    ; Autogenerated by /usr/sbin/dahdi_genconf on Wed Jun 12 15:27:10 2013
    ; If you edit this file and execute /usr/sbin/dahdi_genconf again,
    ; your manual changes will be LOST.
    ; Dahdi Channels Configurations (chan_dahdi.conf)
    ;
    ; This is not intended to be a complete chan_dahdi.conf. Rather, it is intended
    ; to be #include-d by /etc/chan_dahdi.conf that will include the global settings
    ;

    ; Span 1: B4/0/1 "B4XXP (PCI) Card 0 Span 1" AMI/CCS
    group=0,11
    context=from-pstn
    switchtype = euroisdn
    signalling = bri_cpe
    channel => 1-2
    context = default
    group = 63

    ; Span 2: B4/0/2 "B4XXP (PCI) Card 0 Span 2" (MASTER) AMI/CCS
    group=0,12
    context=from-pstn
    switchtype = euroisdn
    signalling = bri_cpe
    channel => 4-5
    context = default
    group = 63

    ; Span 3: B4/0/3 "B4XXP (PCI) Card 0 Span 3" AMI/CCS RED
    group=0,13
    context=from-pstn
    switchtype = euroisdn
    signalling = bri_cpe
    channel => 7-8
    context = default
    group = 63

    ; Span 4: B4/0/4 "B4XXP (PCI) Card 0 Span 4" AMI/CCS RED
    group=0,14
    context=from-pstn
    switchtype = euroisdn
    signalling = bri_cpe
    channel => 10-11
    context = default
    group = 63


    ce qui est important, c'est que je passe de FT en bri_cpe_ptmp a du completel bri_cpe et que sans le faire à la mano ... rien se fait !!!
    Alternatiq Informatique

    SSII spécialisée dans l'architecture Open Source

Règles de messages

  • Vous ne pouvez pas créer de nouvelles discussions
  • Vous ne pouvez pas envoyer des réponses
  • Vous ne pouvez pas envoyer des pièces jointes
  • Vous ne pouvez pas modifier vos messages
  •