[cisco-voip] PBX-to-IPPBX calls
Ratko Dodevski
rade239 at gmail.com
Fri Jun 5 12:10:58 EDT 2009
:) That's nice idea but... they don't have support, and TAC would probably
say that AIRSPAN is doing something wrong, and AIRSPAN maybe don't even have
support, and so on, and so on... also i'm few days late with implementaion
so I don't have the luxury of time waste.
Ratko
On Fri, Jun 5, 2009 at 5:58 PM, Paul <asobihoudai at yahoo.com> wrote:
> I think it's time to call Cisco TAC.
>
> http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html
>
>
> ------------------------------
> *From:* Ratko Dodevski <rade239 at gmail.com>
> *To:* Jason Burns <burns.jason at gmail.com>
> *Cc:* "cisco-voip at puck.nether.net" <cisco-voip at puck.nether.net>
> *Sent:* Friday, June 5, 2009 11:44:34 AM
> *Subject:* Re: [cisco-voip] PBX-to-IPPBX calls
>
> Hi Jason, I very much appreciate your help... I'm confused why would the
> ISDN messages be OK for numbers that are on PSTN or GSM but not valid for
> phones registered on AIRSPAN. Phones on AIRSPAN are working OK and are part
> of the national network. Customer is the biggest telephone provider in
> Macedonia and both platforms are working. I'will send you Q931 debug
> messages and router config so please if you have time, maybe you can take a
> glance.
>
> Thanks again
> Ratko
> __________________________________________
>
>
>
>
> On Fri, Jun 5, 2009 at 5:07 PM, Jason Burns <burns.jason at gmail.com> wrote:
>
>> Cause i = 0x80E018 - Mandatory information element missing
>> Cause i = 0x80E27D - Message not compatible with call state or not
>> implemented
>> Cause i = 0x82E5 - Message not compatible with call state
>>
>> Those messages indicate to me that you're sending q931 messages that the
>> far end switch doesn't like, or that youre getting messages that you don't
>> like. A sure fire indication at the far end isdn switch type is not
>> configured the same as your local isdn switch type.
>>
>> If you're set to primary-qsig, are you positive that your provider is also
>> set to primary-qsig?
>>
>> This may not be causing the problem you reported below, but I can only fix
>> the problems I see error messages for, and those errors tell me your switch
>> type is mismatched.
>>
>> For the problem with the call disconnect it would be helpful to get
>> relevant debugs (SIP, Q931) from each device involved.
>>
>>
>> On Fri, Jun 5, 2009 at 5:47 AM, Ratko Dodevski <rade239 at gmail.com> wrote:
>>
>>> Thanks for replying,
>>> PRI switch-type is set as primary-qsig. I should mention that when i make
>>> phone calls to PSTN or GSM network trough the IPPBX it works just fine, but
>>> i can't make calls with phones that are registerd with the IPPBX (which i
>>> think is some Israelian AIRSPAN).
>>>
>>>
>>> Ratko
>>>
>>>
>>> On Fri, Jun 5, 2009 at 4:58 AM, Jason Burns <burns.jason at gmail.com>wrote:
>>>
>>>> It sounds like your PRI Switch Type is set incorrectly based on the type
>>>> of q931 errors you're getting. Is it NI2, 5ESS, DMS100?
>>>>
>>>> On Thu, Jun 4, 2009 at 6:30 PM, Ratko Dodevski <rade239 at gmail.com>wrote:
>>>>
>>>>> Hi, i have question (obviously :) )
>>>>> I have big troubles connecting a TDM PBX to a IPPBX through SBC via
>>>>> SIP. When I do *debug isdn q931 *I keep getting this massages:
>>>>> Cause i = 0x80E018 - Mandatory information element missing
>>>>> Cause i = 0x80E27D - Message not compatible with call state or not
>>>>> implemented
>>>>> Cause i = 0x82E5 - Message not compatible with call state
>>>>>
>>>>> Called number is ringing but when i pick-up it gives me busy dial and
>>>>> if i hung-up it rings again. On the SBC I can see that after picking router
>>>>> sends BYE signal with "Bearer capability not implemented" and instantly
>>>>> sending 2 more invites for call.
>>>>> I tried with setting bearer-cap Speech and i use the command isdn
>>>>> incoming-voice voice.
>>>>>
>>>>> Tried many combinations... Any ideas ????
>>>>>
>>>>> Thanks
>>>>> --
>>>>> Ratko
>>>>>
>>>>> _______________________________________________
>>>>> cisco-voip mailing list
>>>>> cisco-voip at puck.nether.net
>>>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>>>
>>>>>
>>>>
>>>
>>>
>>> --
>>> Ratko
>>>
>>
>>
>
>
> --
> Ratko
>
>
--
Ratko
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20090605/f4ba0755/attachment.html>
More information about the cisco-voip
mailing list