On Fre, 2008-11-14 at 10:07 +0100, Wolfgang Pichler wrote: > The original setup does contain two calling numbers, the user provided > number and the network number - the new setup does only contain the user > provided number > The original setup does have at the called number numbering plan 1 - > isdn numbering plan - the new setup does have 0 = unknown This should not matter, except if the PBX needs to see both numbers as they are (but in this case I wouldn't expect it to answer with 'invalid information element' as it does). > The numbering plan issue could get fixed by setting the numbering plan > (may i also set the numbering plan before i create the new call - so > that it does not affect all calls ?) No, its either fixed for all calls or derived from the called number for all calls. > Some suggestions how to proceed would be very helpfull I'm pretty sure that the wrong User information layer 1 byte is to blame. Especially since I've tested it with my libpri (version 1.2.2 + bristuff 0.3.0.pre1n, already pretty old) and for a digital call, the user-layer 1 byte is *not* there (Bearer Capability is only 4 bytes long, not 5 as in your SETUP). Libpri contains the following code: static FUNC_SEND(transmit_bearer_capability) ... if ((tc & PRI_TRANS_CAP_DIGITAL)&&(pri->switchtype == PRI_SWITCH_EUROISDN_E1)) { /* Apparently EuroISDN switches don't seem to like user layer 2/3 */ return 4; } /* add userlayer 1 info */ Since you have switchtype=euroisdn in your zapata.conf (as seen in previous email), this should prevent the user-layer-1 byte to be added. Maybe you just have to upgrade to a newer version of libpri (and maybe Asterisk too). > And - i am not sure - is this more a -dev or -users question ? Starting to look more like a user thing. Let's continue on asterisk-user (just saw your question there). Regards, Mike -- Dr. Michael Neuhauser mailto:mike@firmix.at Firmix Software GmbH sip:mike@firmix.at Vienna/Austria/Europe tel:+43-1-7890849-30 Linux Development and Services http://www.firmix.at/