[Asterisk-Dev] dump_user_user() and other UUI questions

John Todd jtodd at loligo.com
Fri Sep 19 17:14:26 MST 2003


[comments in-line]
At 3:15 PM -0700 9/19/03, tony mancill wrote:
>Hi John,
>
>Thank you very much for the guidance and the references.  I'm glad to hear
>that UUI in SIP is being thought about by others as well.  I'm also
>working with VXML platforms, so it makes sense that Nuance would want
>this.  In my experience, you sort of get a blank stare when you talk to
>commerical PRI <-> VoIP gateway providers for this, so this seems like a
>cool opportunity for * to provide something that you can't buy anywhere
>else.

There are many features that * has that you can't buy anywhere else.  ;-)

>I'll take a look at II digits as well, since these sort of go together
>with UUI.  If anyone wants to at least see what UUI they're receiving off
>of a PRI circuit, here's the basic patch:
>
>--- libpri/q931.c       Tue Sep 16 14:29:21 2003
>+++ libpri_20030918/q931.c      Thu Sep 18 15:42:44 2003
>@@ -830,10 +830,11 @@
>
>  static void dump_user_user(q931_ie *ie, int len, char prefix)
>  {
>-
>+       char cnum[256];
>+       q931_get_number(cnum, sizeof(cnum), ie->data + 1, len - 3);
>+       pri_message("%c User-User Information (len=%2d) ['%s']\n", prefix,
>len, cnum);
>  }
>
>I'll submit a better patch that deals with non-printing characters and
>such via the mantis interface.
[snip]

I await your patch, and I would also be interested in any further 
work you could do towards making this a set-able option for outbound 
PRI calls as well.  This could be a "secret" method of communications 
between two previously unrelated Asterisk end nodes across the PSTN 
if the carrier will transport the data unchanged.  Data that could 
possibly be stored in there might be 
"iax2://3023321212@some.host.com/" or even just a pointer to an ENUM 
entry.  Each end could then hang up (not answer?) the PRI setup 
message, and then re-path the call out through IP.

...boy, would AT&T be pissed. He he he.

That is just one of many possible uses and data formats would need a 
lot more thought, but it's certainly one to think about.  I don't 
have time to look at the spec in detail, but it sounds like it might 
be workable.  Can anyone speak to this who knows the q.931 spec and 
practical usages in more detail?

JT



More information about the asterisk-dev mailing list