criptos at aullox.com
Guest
|
 Posted: Thu Feb 28, 2008 1:35 pm Post subject: [asterisk-users] Unicall mfcr2 testcall issues in mexico out |
 |
|
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Same effect...
I belive that is a nortel issue.
But I have no idea of how to debug it to fix it... any advice is helped..
Also the provider, asked me for the tone table.... because he can set
the tone table as he wishes...
TIA.
Testcalll output
./testcall
Chan 10, class 'mfcr2', variant 'mx,10,4,0', end 0, caller 0, from '' to ''
Loading protocol mfcr2
Thread for channel 0
MFC/R2 Chan 10: Call control(9)
MFC/R2 Chan 10: Unblock
MFC/R2 Chan 10: 1001 -> [1/BLOCKED /Idle /Idle ]
MFC/R2 Chan 10: far_unblocking_expired
MFC/R2 Chan 10: local_unblocking_expired
Chan 10: -- Far end unblocked! 
Chan 10: -- Far end unblocked!
Chan 10: -- Local end unblocked!
Chan 10: -- Local end unblocked!
MFC/R2 Chan 10: <- 0001 [1/IDLE /Idle /Idle ]
MFC/R2 Chan 10: Detected
MFC/R2 Chan 10: Creating a new call with CRN 32769
MFC/R2 Chan 10: 1101 -> [2/DETECTED/Seize ack /Seize ack ]
Chan 10: -- Detected on channel 0, CRN 32769
Chan 10: -- Detected on channel 0, CRN 32769
MFC/R2 Chan 10: <- 8 on [2/DETECTED/Seize ack /Seize ack ]
MFC/R2 Chan 10: 6 on -> [2/DETECTED/Group C /Category req ]
MFC/R2 Chan 10: <- 8 off [2/DETECTED/Group C /Category req ]
MFC/R2 Chan 10: 6 off -> [2/DETECTED/Group C /Category req ]
Main thread
MFC/R2 Chan 10: R2 prot. err. [2/DETECTED/Group C /Category req ]
cause 32771 - T3 timed out
MFC/R2 Chan 10: 1001 -> [1/IDLE /Idle /Idle ]
Chan 10: -- Protocol failure on channel 0, cause (32771) T3 timed out
Chan 10: -- Protocol failure on channel 0, cause (32771) T3 timed out
Main thread
MFC/R2 Chan 10: <- 1001 [1/IDLE /Idle /Idle ]
MFC/R2 Chan 10: 1001 -> [1/IDLE /Idle /Idle ]
Main thread
Moises Silva wrote:
| Quote: | This may fix your issue:
mx,10,4,0
By default Mexico variant has the option "get ANI after DNIS". Which
it means just after getting the DNIS digits we will request the
calling party category and DNIS. The Nortel PBX seems to not like
calling party category requests and they want to go straight to group
II signal instead of group C. Adding a 0 as options will disable the
"get ANI after DNIS" option and go straight to Group II signals.
Give that a try and let us know, tho, I still wonder why the Nortel
does not accept the Calling Party Category Request and Switch to Group
C signal. Is the Nortel PBX properly configured for M?xico variant???
Mois?s Silva
On Wed, Feb 27, 2008 at 8:56 PM, Andres Tello Abrego <criptos at aullox.com> wrote:
Thanks Carlos...
Using mx,10,4.... didn't work.
Chan 31, class 'mfcr2', variant 'mx,10,4', end 0, caller 0, from '' to ''
Loading protocol mfcr2
Thread for channel 0
MFC/R2 Chan 31: Call control(9)
MFC/R2 Chan 31: Unblock
MFC/R2 Chan 31: 1001 -> [1/BLOCKED /Idle /Idle ]
MFC/R2 Chan 31: far_unblocking_expired
MFC/R2 Chan 31: local_unblocking_expired
Chan 31: -- Far end unblocked!
Chan 31: -- Far end unblocked!
Chan 31: -- Local end unblocked!
Chan 31: -- Local end unblocked!
MFC/R2 Chan 31: <- 0001 [1/IDLE /Idle /Idle ]
MFC/R2 Chan 31: Detected
MFC/R2 Chan 31: Creating a new call with CRN 32769
MFC/R2 Chan 31: 1101 -> [2/DETECTED/Seize ack /Seize ack ]
Chan 31: -- Detected on channel 0, CRN 32769
Chan 31: -- Detected on channel 0, CRN 32769
Main thread
MFC/R2 Chan 31: <- 8 on [2/DETECTED/Seize ack /Seize ack ]
MFC/R2 Chan 31: 1 on -> [2/DETECTED/Group A /DNIS request ]
MFC/R2 Chan 31: <- 8 off [2/DETECTED/Group A /DNIS request ]
MFC/R2 Chan 31: 1 off -> [2/DETECTED/Group A /DNIS request ]
MFC/R2 Chan 31: <- 6 on [2/DETECTED/Group A /DNIS request ]
MFC/R2 Chan 31: 1 on -> [2/DETECTED/Group A /DNIS request ]
MFC/R2 Chan 31: <- 6 off [2/DETECTED/Group A /DNIS request ]
MFC/R2 Chan 31: 1 off -> [2/DETECTED/Group A /DNIS request ]
MFC/R2 Chan 31: <- 1 on [2/DETECTED/Group A /DNIS request ]
MFC/R2 Chan 31: 1 on -> [2/DETECTED/Group A /DNIS request ]
MFC/R2 Chan 31: <- 1 off [2/DETECTED/Group A /DNIS request ]
MFC/R2 Chan 31: 1 off -> [2/DETECTED/Group A /DNIS request ]
MFC/R2 Chan 31: <- 0 on [2/DETECTED/Group A /DNIS request ]
MFC/R2 Chan 31: 6 on -> [2/DETECTED/Group C /Category req ]
MFC/R2 Chan 31: <- 0 off [2/DETECTED/Group C /Category req ]
MFC/R2 Chan 31: 6 off -> [2/DETECTED/Group C /Category req ]
Main thread
Main thread
Main thread
MFC/R2 Chan 31: R2 prot. err. [2/DETECTED/Group C /Category req ]
cause 32771 - T3 timed out
MFC/R2 Chan 31: 1001 -> [1/IDLE /Idle /Idle ]
Chan 31: -- Protocol failure on channel 0, cause (32771) T3 timed out
Chan 31: -- Protocol failure on channel 0, cause (32771) T3 timed out
MFC/R2 Chan 31: <- 1001 [1/IDLE /Idle /Idle ]
MFC/R2 Chan 31: 1001 -> [1/IDLE /Idle /Idle ]
Carlos Chavez wrote:
| Quote: | I do not know if this will make a difference but the protocol-variant
for Mexico should be:
|
| Quote: | protocol-variant mx,10,4
|
| Quote: | You only get 10 digits from the phone company.
|
| Quote: | On Wed, 2008-02-27 at 18:03 -0800, Andres Tello Abrego wrote:
| Quote: | protocol-variant mx,20,4
------------------------------------------------------------------------
|
|
|
_______________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
iD8DBQFHxv7tEXCJrml2yYoRAuYwAJ0VfdImkv3sHZQQMxZNZEMl5VZkWQCeMqui
PtyrCz8GMGrw2kbGhOXZsg4=
=1IgX
-----END PGP SIGNATURE----- |
|
Search
