Eternl loop on a tdm22b card

[Aug 14 17:33:37] WARNING[29307]: app_macro.c:212 _macro_exec: No such context ‘macro-dundi-e164’ for macro ‘dundi-e164’
– Executing [918585479064@internal:2] Dial(“Zap/2-1”, “Zap/g2/18585479064”) in new stack
– Called g2/18585479064
– Zap/1-1 is ringing
– Zap/1-1 is ringing
– Zap/1-1 is ringing
– Zap/1-1 is ringing
– Zap/1-1 is ringing
– Zap/1-1 is ringing
– Hungup ‘Zap/1-1’
== Spawn extension (internal, 918585479064, 2) exited non-zero on ‘Zap/2-1’
– Hungup ‘Zap/2-1’
[b] AS YOU CAN SEE, WHEN I GENERTA A CALL ON Z202, IT SEND IT TO RING ON ZAP 1. THIS WILL NOT OCURR IF I INITIATE THE CALL ON ZAP1 WHICH WILL PROCESS LKE THIS

[Aug 14 22:05:08] WARNING[29805]: app_macro.c:212 _macro_exec: No such context ‘macro-dundi-e164’ for macro ‘dundi-e164’
– Executing [90115216862319684@international:2] Dial(“Zap/1-1”, “Zap/g2/0115216862319684”) in new stack
– Called g2/0115216862319684
– Zap/3-1 answered Zap/1-1
– Native bridging Zap/1-1 and Zap/3-1
– Hungup ‘Zap/3-1’
== Spawn extension (international, 90115216862319684, 2) exited non-zero on ‘Zap/1-1’
– Hungup ‘Zap/1-1’
[b]

I think is on the bridging process where the issue might be. Again it happens some times, which is very odd since a programatic problem USUALLY either is persistent of incurrs in some form of saturation opf a buffer of memeory leak. but NOT intermitent at will

ANY COMMENTS???
Thank you all in advance for any comments. any help is welcome[/b]

[I have answered this question in the Support forum]